RE: [squid-users] Squid & HTTP compression

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
Via 1.1 xx.xx.xx:80 (squid)
Connection keep-alive

Thanks
In advance

-----Original Message-----
From: Amos Jeffries [mailto:squid3_at_treenet.co.nz]
Sent: Wednesday, January 12, 2011 12:48 PM
To: squid-users_at_squid-cache.org
Subject: Re: [squid-users] Squid & HTTP compression

On 12/01/11 10:02, Leonardo Rodrigues wrote:
>
> squid 2.7 cannot handle HTTP/1.1 which is needed for, among other
> things, the chunk encoding (compression) one. You'll simply not be
> able to get it working with squid 2.7.
>
> i know squid 3.1 has made great improvements on HTTP/1.1 support, but
> as i dont use it, i cannot guarantee you what's working and what's not.
>
> check squid 3.1 changelogs looking for HTTP/1.1 related things. Also
> i'd suggest you to search this mailing list archives, as HTTP/1.1
> support on squid was vastly discused here by other users.
>

FWIW:

squid-2.7 and 3.1 have equal levels of support for the various encodings.
Both doing de-coding chunks as required. Neither do any changes for the
deflate/gzip/compress/sdch coding types.

Both have roughly equal handling of coded variants. 3.1.10 and later have
better ETag comparisons.

>
> Em 11/01/11 14:07, karj escreveu:
>> Hello everyone,
>>
>> I have a small problem with squid (Squid 2.7.STABLE9).
>>
>> I'm trying to optimize our IIS6 web portal. I activated HTTP
>> compression both for static and dynamic content, and this works OK
>> when the browser asks for content directly to the IIS server ...
>>
>> BUT, when the browser asks for content thru Squid.
>> Content is effectively served by IIS but as the Content-Encoding
>> header is missing, so nor IE or FireFox can handle it !
>>

karj, are you saying that IIS is not adding any header? there is nothing
Squid can do about that. Absence of a header indicates there is no coding
used on that object.

Or are you saying that Squid removes the header without decoding?

Amos

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