DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17928>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17928 mod_proxy hangs when backend server returns a 304 Summary: mod_proxy hangs when backend server returns a 304 Product: Apache httpd-2.0 Version: 2.0.44 Platform: PC OS/Version: Linux Status: NEW Severity: Normal Priority: Other Component: mod_proxy AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] When working in reverse proxy mode, apache does return a 304 code to the frontend client *only when* the backend connection closes. Conditions: - apache 2.0.44 - mod_proxy configured in reverse proxy mode - HTTP/1.1 on frontend and backend - Keepalive On for both frontend and backend connection - ProxyErrorOverride On - backend server sends a 304 not modified code. When the client refreshes the page, the backend responds with 304 not modified, and keeps the connection alive (that�s normal behavior). Instead of sending the responds front to the client, mod_proxy waits until KeepAliveTimeout of the backend connection expires, the send the response to the front client. NOTE: You can make the problem worst by increasing KeepAliveTimeout on the backend webserver. A workaround is to set KeepAlive Off on the backend. However, it doesn�t address the problem on mod_proxy box. The issue manifests when you set ProxyErrorOverride On. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
