Summary: | mod_proxy_http fails with 502 when backend sends 401 and closes connection immediately | ||
---|---|---|---|
Product: | Apache httpd-2 | Reporter: | Bruno Harbulot <bruno> |
Component: | mod_proxy_http | Assignee: | Apache HTTPD Bugs Mailing List <bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | apache, michaelo, szg0000 |
Priority: | P2 | ||
Version: | 2.4.25 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | All |
Description
Bruno Harbulot
2017-02-09 12:32:56 UTC
I think this is fixed by BZ 60330. I must revert my comment. It is not fixed by the noted issue. Here is another in-detail description of the issue: https://www.mail-archive.com/users@tomcat.apache.org/msg135207.html This is fixed in 2.4.43 with end to end 100-continue negotiation. If the backend (Jetty) responds with a final status to a 100-continue request then mod_proxy will forward the response without ever trying to forward the request body. |