You are viewing a plain text version of this content. The canonical link for it is here.

Posted to bugs@httpd.apache.org by bu...@apache.org on 2021/12/02 03:51:20 UTC

[Bug 55433] mod_proxy ignores final status code for aborted requests that Expect: 100-continue

https://bz.apache.org/bugzilla/show_bug.cgi?id=55433

Deepak Wagadre <de...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
            Version|2.2.15                      |2.4.6
           Hardware|PC                          |Macintosh
         Resolution|DUPLICATE                   |---

--- Comment #5 from Deepak Wagadre <de...@gmail.com> ---
We have APACHE version 2.4.6 and we still see this error. Where the backend
server send 401 to Apache but it responds with 502 (Bad Gateway). Please
confirm if the changes made in the bug 60330 is ported to 2.4.6 APACHE version.

Scenario(Same as mentioned by jon.abourbih@gmail.com) :

Using mod_proxy as a reverse proxy,  client sends a request with Expect:
100-continue, mod_proxy forwards the Expect header upstream. Even if the
upstream server responds with a final status code (e.g. 401 Unauthorized, or
413 Request Entity Too Large) instead of a 100 Continue, mod_proxy continues to
send data to the upstream server. If the upstream server closes the connection
after sending the final status code, httpd responds to the client with a 502
Bad Gateway message instead of the origin server's final status code.

-- 
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org