Re: [squid-users] Squid & HTTP compression

On 13/01/11 05:49, karj wrote:
> Hi Amos,
> IIS is adding the correct headers
>
> But
> Seems to me that squid removes them
> For example the Content-Encoding gzip is missing (thru squid)!
>
>
> ----------- Direct IIS
> -----------------------------------------------------------------------
> I get this
>
> Cache-Control stale-if-error=1200, stale-while-revalidate=28300
> Content-Length 7238
> Content-Type text/css
> Content-Encoding gzip
> Last-Modified Mon, 20 Dec 2010 15:57:34 GMT
> Accept-Ranges bytes
> Vary Accept-Encoding
> Server Microsoft-IIS/6.0
> Date Wed, 12 Jan 2011 16:39:29 GMT
>
> --------- Thru Squid
> -----------------------------------------------------------------------
> I get this
>
> Content-Length 45868
> Content-Type text/css
> Etag "2f0cb9e5ea0cb1:e6a8"
> Cache-Control stale-if-error=1200, stale-while-revalidate=28300
> Last-Modified Mon, 20 Dec 2010 15:57:36 GMT
> Accept-Ranges bytes
> Server Microsoft-IIS/6.0
> Date Wed, 12 Jan 2011 10:38:08 GMT
> Age 21775
> X-Cache HIT from xx.xx.xx
> X-Cache-Lookup HIT from xx.xx.xx:80

This is a HIT. An earlier stored copy saved from some other client
request. I guess you are hitting a case of bad variant labeling, and the
stored copy is an old one with no encoding.
   Note how there is also no Vary: header which tells Squid to look at
the encoding type when re-using this response.

In 2.7 you need to turn on broken_vary_encoding feature and tell it that
this server or website is broken.

That or you are using header_access to wrongly remove things.

> Via 1.1 xx.xx.xx:80 (squid)
> Connection keep-alive
>
>
> Thanks
> In advance
>

Amos

-- 
Please be using
   Current Stable Squid 2.7.STABLE9 or 3.1.10
   Beta testers wanted for 3.2.0.4