Search squid archive

Re: Invalid Response

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On fre, 2007-11-23 at 15:49 +0100, apmailist@xxxxxxx 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
http://www.squid-cache.org/Versions/v2/HEAD/changesets/11708.patch

Regards
Henrik

Attachment: signature.asc
Description: This is a digitally signed message part


[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux