Dr. Ernst-Udo Wallenborn wrote:
But there is the occasional Netscape 4.7 out there, and it issues a HTTP/1.0 request with Connection:Keep-Alive. The reverse proxy treats it as a non-persistent connection and answers with a Connection:close. As a result, each gif on my test page produces a new connection. In our current 1.3.x reverse proxy we use the ap_proxy_ka.diff patch to keep the connectio alive, being fully aware that this patch is quite a hack.
Supporting HTTP/1.0 Keepalives was hard to do, and if my rusty memory serves there were issues in HTTP/1.1 with HTTP/1.0 keepalives - thus I didn't worry about keepalives in the HTTP/1.0 case.
Is the resultant non-keepalive load significantly high to cause a problem?
Regards,
Graham
--
-----------------------------------------
[EMAIL PROTECTED] "There's a moon
over Bourbon Street
tonight..."
