On May 19, 2008, at 3:36 PM, Adam Woodworth wrote:
So let's consider the case of a web browser that uses keepalives. If the web browser has a keepalive connection, and the connection closes behind it's back so that the next time the browser tries to use the connection it fails (like this problem we're having with mod_proxy), what should the web browser do?
As far as the web browser is concerned, it should have no idea or concept that the server it is talking to is not the server that is generating the content. In other words, the situation is no different (and should not be) that the case where the web browser has a keepalive and the server closes that connection... The current code tries tries to ensure that.
