On 09/19/2008 11:24 PM, Adam Woodworth wrote:
Now that we're using 2.2.9 in the field, I've noticed a problem with r657443, or at least it's a problem for our application. r657443 added code to shutdown the connection w/o any response with an EOC in the case that a second (or later) request on a keepalive connection failed to get a response from the backend. The problem with this is that it will also do this for connections to the backend that timed out. For our application, we want actual timeouts to be caught as normal and kicked back through to the client as a 50x error.
Hm. Good point. I have to think about it, because a timeout error can justify a repeated request (like when a firewall between frontend and backend cut the connection and now the packets are simply dropped by the firewall and a fresh one would fix this). Bug me here if I forget about it. Regards Rüdiger
