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=8672>. 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=8672 mod_proxy HTTP/1.1 delay Summary: mod_proxy HTTP/1.1 delay Product: Apache httpd-1.3 Version: 1.3.24 Platform: Sun OS/Version: Solaris Status: NEW Severity: Normal Priority: Other Component: mod_proxy AssignedTo: bugs@httpd.apache.org ReportedBy: [EMAIL PROTECTED] In our environment, we use apache as a proxy for our backend weblogic 5.1 servers. I just recently upgraded our apache server in our QA environment to apache 1.3.24 because I noticed that there were quite a few enhancements to mod_proxy. Unfortunately, apache 1.3.24 seems to be very very slow when dealing with http/1.1 proxy requests. It looks like what is happening is that the client makes an HTTP/1.1 request to the apache server. The apache server then sends a HTTP/1.1 request to the weblogic server. It processes the request, then sends back it's reply, along with a Connection: Keep-Alive header. The apache server then keeps that connection open, but doesn't send any further requests along that connection, and doesn't send the reply to the client. Eventually, the weblogic server kills the idle connection, and apache sends the reply back to the client. Is this the proper way for an http/1.1 proxy to work?
