Re: [squid-users] Next problem: squid ignoring my vary header

Stefan Hartmann wrote:
> Hi,
>
> next problem arising when trying content-compression: Squid seems to
> ignore my "Vary: Accept-Encoding" header. From the logs (log_mime_hdr
> on, inserted line breaks for better reading):
>
> 1240918625.344 1 111.111.111.111 TCP_MEM_HIT/200 28399 GET
> http://our.server.de/library/js/ajax_v4-6-21.js - NONE/-
> application/x-javascript
>
> [
> Host: our.server.de
> User-Agent: Nutscrape/1.0 (CP/M; 8-bit)
> Cache-Control: max-age=259200
> ]
> [
> HTTP/1.0 200 OK
> X-Powered-By: ASP.NET
> Vary: Accept-Encoding
> Expires: Tue, 28 Apr 2009 13:32:59 GMT
> Date: Tue, 28 Apr 2009 11:32:59 GMT
> Content-Type: application/x-javascript
> Content-Length: 28115
> Content-Encoding: gzip
> X-Cache: HIT from accel3
> Connection: close
> ]
>
> No Accept-Encoding in the request Headers, but i get a HIT from a
> (previously cached) request with "Accept-Encoding: gzip" and so
> Content-Encoding: gzip in the reply to my Request without
> Accept-Encoding (and yes, the response was gzipped).
>
> Any Idea? Could this be the result of a missing validator (Etag) and i
> will have to enable "broken_vary_encoding" ?!?
>
> Regards,
> Stefan
>

I have heard this before in here. What version of Squid?

broken_vary_encoding copes with servers sending gzip data with plain
text type.

The requests you have shown does not specify any limits on the data type
accepted back. Squid treats it as anything the client version of HTTP
can receive is acceptable.

I believe if you added a Accept-Encoding: header with values other than
'gzip' which Squid has stored you would get back something else for that
encoding.

Amos

-- 
Please be using
   Current Stable Squid 2.7.STABLE6 or 3.0.STABLE14
   Current Beta Squid 3.1.0.7