Re: Intuit claims bugs in Squid 2.2!

Yes, it is true that Squid will reject such requests. Squid does not
want a Content-Length header on cachable methods where the meaning of
the request entity is undefined. This is to alert on possible future
cache incompability in case people begins to use request entities on
such methods.

Which brings me to ask the question: Why do you send a request-entity in
a GET request? A Content-Length: 0 header signals a zero bytes
request-entity which is different from no request-entity at all.

Note: Changing Squid to accept this specific case of a 0 bytes request
entities is trivial.

Change client_side.c:clientCheckContentLength()

From
    case METHOD_GET:
    case METHOD_HEAD:
        /* We do not want to see a request entity on GET/HEAD requests
*/
        return !has_cont_len;

To
    case METHOD_GET:
    case METHOD_HEAD:
        /* We do not want to see a request entity with data on GET/HEAD
requests */
        return r->content_length <= 0;

Ps: This is not tested in any way what so ever, but it should work...

--
Henrik Nordstrom
Squid hacker
Quicken Quotes Live Technical Support / Rhonda wrote:
> Under certain conditions with Squid, it seems that a request (fully to
> specifications) as follows:
> 
> GET /path/to/file/filename.conf HTTP/1.0
> Content-Length: 0