From: Jeff Trawick <trawick@apache.org>
Date: Wed, 15 Apr 2015 15:29:45 +0000 (+0000)
Subject: Jeff's ajp confusion
X-Git-Tag: 2.4.13~241
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=7b339aa12b7f4405548247e897653c1f17485a88;p=thirdparty%2Fapache%2Fhttpd.git

Jeff's ajp confusion


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

diff --git a/STATUS b/STATUS
index fcc7f27b49a..de8ff71d021 100644
--- a/STATUS
+++ b/STATUS
@@ -171,6 +171,16 @@ PATCHES PROPOSED TO BACKPORT FROM TRUNK:
                   http://svn.apache.org/r1643543
      2.4.x patch: trunk works (module CHANGES)
      +1: ylavic, jim
+     trawick: Eric and I were working through this and I (at least) ran into this
+              particular roadblock: output_failed sometimes means that we couldn't
+              write to the client and sometimes means that we couldn't read from
+              the client; laster, output_fails triggers setting the status to 400.
+              HTTP status shouldn't be 400 for a problem writing to the client.
+              (Maybe I missed some guarantee that 400 is only for an error reading
+              enough request body??)  I think it would be good to separate output_failed
+              from input_failed so that the code is more clear and we can more
+              easily tell that the status code is appropriate.  (And unfortunately
+              I don't volunteer to test it :( )
 
    * core: Add ap_errorlog_provider to make ErrorLog logging modular. This
            backport keeps syslog logging as part of httpd core and only adds