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 - 01:51:50 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:13:17 MST