https://bz.apache.org/bugzilla/show_bug.cgi?id=57853
Yann Ylavic <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO --- Comment #1 from Yann Ylavic <[email protected]> --- According to tcpdump, it seems you have configured either ProxyPass or BalancerMember with the parameter ping=1. The ping parameter gives the time to wait for *any* response (timeout), hopefully a "100 Continue", but if another status is received instead, it will still be forwarded to the client as is (thus, mod_proxy_http does not explicitely wait for a "100 Continue" but for any response within the ping timeout). The purpose of ping is that if a timeout occurs (before receiving any response), the same request can be retried with an other balancer member (if any). With ping=1, this leaves only one second to the backend to respond, whereas in the trace we can see that the response takes a little more than that (the difference bewteen frame 16 and 13 is ~1.018s), hence the connection close before the (ignored) reponse. However, I agree that mod_proxy should not send both the HTTP header and the body (full request) when ping is configured, otherwise it cannot send the same (likely non idempotent) request to another backend, even if a timeout (or 503) occured. I am working on a fix regarding this (both end-to-end and ping 100-continue). But I guess it won't fix your issue which probably requires that you use a higher ping timeout, since the backend needs more than that to generate a response. -- 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]
