Re: RANT

Ah well that's a relief then because I have chunked working :-]

Once I get the downstream decode happening so the stored objects aren't encoded, (and so copying to membuf for downstream
non-encoded connections can be avoided) and I've checked a few possible gotcha's that I've identified as I trudge through the source
I'll make a diff and post for review.

This is why I pulled the other encoding stuff out for a second pass.

Rob

----- Original Message -----
From: "Henrik Nordstrom" <hno@hem.passagen.se>
To: "Robert Collins" <robert.collins@itdomain.com.au>
Cc: <squid-dev@squid-cache.org>
Sent: Friday, January 12, 2001 7:36 PM
Subject: Re: RANT

> Robert Collins wrote:
>
> > workarounds?
> > -Don't assume that a http/1.1 client is capable of chunked transfer coding (rfc 2616 says they must be)
> > - set up an ACL for testing via headers for sending /1.1 responses?
> > - start sending http/1.1 and check quickly for minimal compliance (don't cache varys etc etc)
>
> The fact that Squid cannot handle chunked transfer encoding is the main
> reason why it cannot pretend to be /1.1.
>
> Vary is handled (by not caching such objects).
>
> /Henrik
>
>
Received on Fri Jan 12 2001 - 22:11:20 MST