From: Jeff Trawick <trawick@apache.org>
Date: Fri, 22 May 2015 19:21:56 +0000 (+0000)
Subject: extremely slow response
X-Git-Tag: 2.4.13~58
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=6aee8020b009a99a4a3b2fe98887c9a35c69f01e;p=thirdparty%2Fapache%2Fhttpd.git

extremely slow response


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x@1681199 13f79535-47bb-0310-9956-ffa450edef68
---

diff --git a/STATUS b/STATUS
index 4707edd60c3..7776cb2bff5 100644
--- a/STATUS
+++ b/STATUS
@@ -214,6 +214,9 @@ PATCHES PROPOSED TO BACKPORT FROM TRUNK:
              returned according to {output,backend}_failed. So the clarification is
              possibly as simple as renaming output_failed => client_failed (r1674056 added
              above), WDYT?
+     trawick: It still looks to me that an error with ap_pass_brigade (towards
+              client) can turn into a 400 error, which is what I was concerned
+              about originally.
 
   *) http: Don't remove the Content-Length of zero from a HEAD response if
      it comes from an origin server, module or script. Allow the previous