DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=38763>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=38763 Summary: mod_proxy does not handle asynchronous connection close correctly Product: Apache httpd-2 Version: 2.3-HEAD Platform: All OS/Version: All Status: NEW Keywords: RFC Severity: regression Priority: P2 Component: mod_proxy AssignedTo: bugs@httpd.apache.org ReportedBy: [EMAIL PROTECTED] We get sporadic "Bad Gateway" errors from mod_proxy. In the error log we have entries like: [Fri Feb 17 17:10:19 2006] [error] [client 192.168.55.72] proxy: error reading status line from remote server appsrv01i We were able to track down the error to situation when the server asynchronously closes kept-alive connections and the client sent new requests. According to http://www.w3.org/Protocols/rfc2616/rfc2616-sec8.html the following rules must be followed for persistent connections: - A client, server, or proxy MAY close the transport connection at any time - This means that clients, servers, and proxies MUST be able to recover from asynchronous close events. Why are these rules not implemented in mod_proxy? I do consider mod_proxy not to be HTTP keep-alive compliant in the current implementation. Please comment. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
