Re: [squid-users] Http1.0/1.1 issues

Squid is HTTP/1.0 and does not understand how to process chunked
transfer encoding as this uses a different message format compared to
HTTP/1.0.

What you need to fix is this broken application who responds with
chunked transfer encoding in response to a HTTP/1.0 request.

Hacking Squid to respond as if it was HTTP/1.1 will only make the
problem significantly worse as this will lead the browsers to beleive
Squid is HTTP/1.1 capable and they will start sending chunked transfer
encoding to Squid as well when posting forms etc..

And yes. In the long run Squid should become HTTP/1.1 capable, but we
are not there yet as a fair amount of work remains. A good reason to
support the developers to help HTTP/1.1 support in Squid to become a
reality and not only a dream.

A HTTP/1.1 client who receives a chunked transfer encoding as a HTTP/1.0
reply MAY (or perhaps even SHOULD) try to decode the chunked data by the
"be strict about what you send, liberal about what you accept" policy of
Internet protocols. It is only servers who MUST NOT send chunked
transfer encoded replies in response to HTTP/1.0 requests as the reply
path most certainly is not capable of understanding chunked encoding
correcly in such case.

Regards
Henrik

"K. Scott Bethke" wrote:

> Greetings,
>
> It seems for whatever reason we have hit a snag in this system. Whats
> happening is that we have a small program that acts as a proxy for
> authenticated users on the website, squid acts normal when we attach to the
> webserver alone and grab content (i.e we get a 1.1 session, and chunked
> connection works as intended. However for whatever reason when this small
> program starts to relay content (basically feeding it back through apache)
> the client always defaults to 1.0 (through squid, if we go direct to the
> webserver and bypass squid the browser always sees a 1.1 connection),
> however the system sends back a chunked response as if it SHOULD be a 1.1
> connection. More interesting is that I.E just displays the chunked coding
> info, Mozzilla and Netscape just pretends they know its a real 1.1
> connection (even though we have verified via sniffer that it IS a 1.0
> connection) and they parse the chunked characters fine.
>
> Any idea what I can change in 2.5STABLE1 source to force all clients to 1.1
> even when its getting a required 1.0 connection?
>
> -Scotty
Received on Thu Dec 05 2002 - 15:17:09 MST