https://bz.apache.org/bugzilla/show_bug.cgi?id=55433
Deepak Wagadre <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Version|2.2.15 |2.4.6 Hardware|PC |Macintosh Resolution|DUPLICATE |--- --- Comment #5 from Deepak Wagadre <[email protected]> --- 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 [email protected]) : 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: [email protected] For additional commands, e-mail: [email protected]
