https://bz.apache.org/bugzilla/show_bug.cgi?id=65886
--- Comment #8 from Yann Ylavic <[email protected]> --- (In reply to Archie Cobbs from comment #3) > > Why should ProxyTimeout's DEFAULT value (Timeout) ever override its > CONFIGURED value (ProxyTimeout) ? I definitely don't get it. The rationale is/was that since Timeout is the one applied on the client connection side, and ProxyTimeout (or ProxyPass timeout= parameter) the one(s) on the backend side, we'd use the smallest when tunneling between the client and backend because if one side times out the tunnel should be terminated. But this was probably a poor choice because in most cases it actually obliges to change existing configuration to set both timeouts at the same/highest value. Poor choices happen.. As Rüdiger said, note that in 2.4.43 no timeout was enforced in mod_proxy for websocket tunneling (neither ProxyTimeout nor Timeout, so the timeout was actually infinite), your configuration worked regardless of ProxyTimeout probably thanks to the heartbeat. The above change was made precisely to honor a timeout while tunneling without an ad hoc mechanism. Let's change this again for 2.4.53. -- 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]
