Re: [squid-users] Invalid Response

From: Henrik Nordstrom <>
Date: Fri, 23 Nov 2007 23:36:54 +0100

On fre, 2007-11-23 at 15:49 +0100, wrote:

> Taken from "Wireshark> Follow TCP Stream" . Tcpdump was done on the squid
> server.
> HTTP/1.1 200 OK
> Date: Mon, 05 Nov 2007 14:22:52 GMT
> Server: Apache/2.0.52 (Red Hat)
> Transfer-Encoding: chunked
> Content-Length: 1532
> Connection: close
> Content-Type: text/html; charset=utf-8
> 5ea
> <html>
> <head>
> (3 lines more than what you aked for)

It's a broken message. It's not allowed to have both Content-Length and
Transfer-Encoding: chunked. This violates a MUST NOT requirement in the
HTTP specifications.

Additionally there is another MUST NOT requirement which forbids chunked
encoding to at all be used in responses to HTTP/1.0 requests (Squid is
still 1.0). But Squid do handle this if seen.. (too many servers getting
this wrong, and Squid is progressing towards HTTP/1.1 support)

So two major errors in that HTTP response.

But yes, Squid should not barf this loudly on this, and is infact
already fixed but forgot to merge that to 2.6.. not sure why..

You can find the patch at


Received on Fri Nov 23 2007 - 15:36:59 MST

This archive was generated by hypermail pre-2.1.9 : Sat Dec 01 2007 - 12:00:02 MST