Re: [squid-users] ecap adapter munging cached body

First, request and reply headers for a cached version, as gzip isn't included in the Accept-Encoding header.

Request:

GET /styles/media.css HTTP/1.1
User-Agent: httperf/0.9.0
Host: www.example.com
Accept-Encoding: deflate

Reply:

HTTP/1.0 200 OK
Cache-Control: max-age=86400
Expires: Sun, 23 Jan 2011 06:06:04 GMT
Vary: Accept-Encoding
Last-Modified: Thu, 30 Jul 2009 11:30:14 GMT
Mime-Version: 1.0
Date: Sat, 22 Jan 2011 06:06:04 GMT
Server: AOLserver/4.5.1
Content-Type: text/css; charset=utf-8
Content-Length: 2654
Age: 1
X-Cache: HIT from www.example.com
X-Cache-Lookup: HIT from www.example.com:80
Via: 1.0 www.example.com (squid/3.1.10)
Connection: keep-alive

Now, request and reply headers when accepting gzip.

Request:

GET /styles/media.css HTTP/1.1
User-Agent: httperf/0.9.0
Host: www.example.com
Accept-Encoding: gzip,deflate

Reply:

HTTP/1.0 200 OK
Cache-Control: max-age=86400
Expires: Sun, 23 Jan 2011 06:06:08 GMT
Vary: Accept-Encoding
Last-Modified: Thu, 30 Jul 2009 11:30:14 GMT
Mime-Version: 1.0
Date: Sat, 22 Jan 2011 06:06:08 GMT
Server: AOLserver/4.5.1
Content-Type: text/css; charset=utf-8
Content-Encoding: gzip
X-Cache: MISS from www.example.com
X-Cache-Lookup: MISS from www.example.com:80
Via: 1.0 www.example.com (squid/3.1.10)
Connection: keep-alive

I see that the gzipped version doesn't reply with a Content-Length header.

Tried with Firefox for a more standard request, exactly the same response headers.

Regards,
Jonathan Wolfe

On Jan 21, 2011, at 9:00 PM, squid-users-digest-help_at_squid-cache.org wrote:

> That sounds like the opposite of good behaviour. Can you produce full request and reply headers flowing between the client and Squid for your test transactions?
Received on Sat Jan 22 2011 - 06:22:31 MST