Re: [squid-users] "Accept-Encoding" header

From: Henrik Nordstrom <hno@dont-contact.us>
Date: Fri, 21 Jun 2002 11:31:55 +0200

You could help with the effort to make Squid HTTP/1.1 compliant... it
is not a small task however due to the high complexity of HTTP/1.1
and HTTP/1.0 interactions.

Our you can use Content-Encoding within HTTP/1.0. It is only
Transfer-encoding that is incompatible with HTTP/1.0 as it changes
the hop-to-hop message format. (Content-Encoding is end-to-end, and
does not change the message format, only the entity format within the
message).

What a HTTP/1.1 server MUST do when responding to a HTTP/1.0 request
with HTTP/1.1 end-to-end features that may be incompatible with a
HTTP/1.0 cache is to respond with a Expires header indicating that
the object is expired immediately. In addition to this it should
respond with the proper HTTP/1.1 headers such as Vary, Cache-control
etc to allow HTTP/1.1 agents along the path (browsers and caches) to
take benefit from the richer semantics of HTTP/1.1. This is the only
way to safely use HTTP/1.1 extensions that affects reply entity
format within HTTP/1.0.

Regards
Henrik

On Friday 21 June 2002 06.38, Slava Bizyayev wrote:
> It sounds a very bad news for the content compression. Let me try
> to explain:
>
> On httpd I have to decide whether the content compression should be
> applied to the response of the particular request, or not. In fact,
> I can not (safely) compress data when the request is coming through
> the proxy. Even I find in Via, that the primary request was
> HTTP/1.1 (let's say from MSIE-6.0), I have to send back the
> HTTP/1.0 response, which should not be compressed and/or chunked.
> Finally, the web traffic through the proxy will be several times
> bigger, and every end-user of your proxy (especially on dialup)
> will wait longer for every uncompressed web page. (Should I mention
> the closed connection too?)
>
> I firmly believe, this is not what we all wish to happen, but I
> have no clue how to create better response for the proxy in this
> case. Especially, keeping in mind the rfc2616 option for proxy to
> replace the (partial) value of Via for the security purposes.
>
> Please, could you share with me your ideas, how could we together
> serve your clients better? Probably, I'm missing something
> important?
>
> Thanks,
> Slava
>
>
> From: "Henrik Nordstrom" <hno@squid-cache.org>
>
> > yes.
> >
> > Regards
> > Henrik
> >
> > Slava Bizyayev wrote:
> > > May I consider the any version of Squid never uses HTTP/1.1 for
> > > outbound requests?
Received on Fri Jun 21 2002 - 03:36:46 MDT

This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:08:45 MST