From f4afe4d70b5a561aede6d7dcdcde8fa86e379aa7 Mon Sep 17 00:00:00 2001 From: Amos Jeffries Date: Wed, 18 Aug 2010 20:27:34 -0600 Subject: [PATCH] Author: Alex Rousskov Bug 3016: HTTP/1.1 compliance: default keep-alive for 1.0/1.1 clients. aka. NTLM Authentication with Java UA + SSL Problem Moved httpMsgIsPersistent(version, headers) to HttpMsg::persistent(void). This move makes it clear that the logic applies only to the message being examined and not some irrelevant information such as HTTP version supported by Squid. Side-effects: * Squid starts using persistent connections with HTTP/1.1 clients that do not send "Connection: close". --- src/client_side.cc | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/src/client_side.cc b/src/client_side.cc index 04b5bd9f11..a25cbddf88 100644 --- a/src/client_side.cc +++ b/src/client_side.cc @@ -704,10 +704,7 @@ clientSetKeepaliveFlag(ClientHttpRequest * http) debugs(33, 3, "clientSetKeepaliveFlag: method = " << RequestMethodStr(request->method)); - /* We are HTTP/1.0 facing clients still */ - HttpVersion http_ver(1,0); - - if (httpMsgIsPersistent(http_ver, req_hdr)) + if (httpMsgIsPersistent(request->http_ver, req_hdr)) request->flags.proxy_keepalive = 1; } -- 2.47.3