On 29/07/11 10:29, canoeberry wrote:
When I connect directly to www.google.co.uk using HTTP/1.1 I get a chunked
encoding response and the connection is kept open and everything is great.
See below:
GET http://www.google.co.uk/ HTTP/1.1
Host: www.google.co.uk
And the response:
HTTP/1.1 200 OK
Date: Thu, 21 Jul 2011 14:22:12 GMT
<snip>
Transfer-Encoding: chunked
If I do the exact same thing through our squid proxy, with the default
configuration file, I get the following response:
HTTP/1.0 200 OK
Date: Thu, 21 Jul 2011 14:44:55 GMT
Expires: -1
<snip>
Via: 1.0 ip-10-204-107-78 (squid/3.1.10)
Connection: close
Yikes - I think I see the error. Google responded with HTTP/1.0 when going
through the proxy. Perhaps I have to tell squid to use HTTP/1.1?
Normal correct behaviour. I see no problem there.
* Chunking is not an HTTP/1.0 feature.
* content which gets chunked is "unknown length"
* HTTP/1.0 software is required to close a connection to signal
end-of-object. Which chunking was created in 1.1 to avoid.
If you want end-to-end HTTP/1.1 with chunking you need Squid-3.2 beta
software. 2.7 series can advetise HTTP/1.1 but does not relay the chunking.
Amos
--
Please be using
Current Stable Squid 2.7.STABLE9 or 3.1.14
Beta testers wanted for 3.2.0.10
