Here's yet another design version, following many helpful suggestions
from Henrik.
Gzip Content-Encoding in Squid Design
Version Choice
The goal will be to get these changes into Squid3 HEAD.
Content-Encoding Protocol
The content-encoding protocol is describedi
Header field cases
Henrik Nordstrom wrote:
On Fri, 5 Mar 2004, Jon Kay wrote:
If Accept-Encoding field is present in client request
If server or cache response contains Content-Encoding field with
encodings that are a subset of what the client accepts
This must be relaxed to just
Henrik Nordstrom wrote:
On Wed, 3 Mar 2004, Jon Kay wrote:
Because current browser implementations treat Content-Encoding much as
though it was Transfer-Encoding, we will implement Content-Encoding and
Accept-Encoding as though they were actually the Transfer-Encoding and
TE described
Coontent-Encoding and Transfer-Encoding is fundamentally different in
their operation far beyond the hop-by-hop vs end-to-end difference. You
can not interchange one for the other.
It is not safe to assume a clients accepts gzip TE only because they
accept gzip content-encoding. For one
On Wed, 3 Mar 2004, Jon Kay wrote:
Because current browser implementations treat Content-Encoding much as
though it was Transfer-Encoding, we will implement Content-Encoding and
Accept-Encoding as though they were actually the Transfer-Encoding and
TE described in the HTTP specifications.
Hi there,
I'm back with this task (again).
Jon: you are far more advanced than I am on understanding squid. I can start helping
content compression writing GzipCoder, if you want to.
(Already discussed) About TE/Transfer-Encoding vs Accept-Encoding/Content-Encoding:
Content-Encoding
Here's a new version of the design document, that incorporates the
results of your suggestions.
I hope this is better...
Jon
Gzip Content-Encoding in Squid Design
Version Choice
The goal will be to get these changes into Squid3 HEAD.
Content-Encoding Protocol
Because
