On Wednesday 13 August 2003 23.49, Robert Collins wrote: > Please note, that if you have squid adding a CE to a http response, > you MUST follow the RFC2616 notes on non-semantically-transparent > proxies. > > Offhand that means adding a 214 warning (i.e. Warning: 214 > this.proxy.com "Added gzip content-encoding")
And as you are constructing a new entity you must take care to reflect this in entity identity headers such as ETag unless you know for sure the client will always be using this transforming proxy when connecting to the internet and the transform is always exacly identical. CE falls under the chapter Server driven content negotiation, and all rules which applies to server driven content negotiation applies to CE transformations. >From a protocol point of view Transfer-Encoding is much more suited for proxies (is in fact what it is suited for). Transfer-Encoding however requires HTTP/1.1 which in turn requires Transfer-Encoding.. (mutual requirement), and Squid does not yet have a working framework for Transfer-Encoding making it a HTTP/1.0 proxy.. Regards Henrik
