Re: [squid-users] Always TCP_REFRESH_MISS with www.heise.de

Martin Schr�der wrote:

>On 2006-02-24 23:58:01 +0100, Martin Schr�der wrote:
>
>
>>setup is a default squid as transparent proxy on OpenBSD. It
>>works for most hosts, but for www.heise.de it nearly always does
>>a TCP_REFRESH_MISS/200 like this:
>>
>>
 From http://www.squid-cache.org/Doc/FAQ/FAQ-6.html#ss6.7...

TCP_REFRESH_MISS:
The requested object was cached but STALE. The IMS query returned the
new content.

>>1140821829.506 233 192.168.17.2 TCP_REFRESH_MISS/200 466 GET http://www.heise.de/tp/r4/icons/frame/eol.gif - DIRECT/193.99.144.85 image/gif
>>
>>Last-Modified: Tue, 09 Nov 2004 10:37:18 GMT
>>Mozilla shows expiry as 13.04.2006 06:50:54
>>
>>Any idea why this is not cached?
>>
>>
>
>More info from LiveHeaders:
>---------------------------------------
>http://www.heise.de/icons/ho/heise.gif
>
>GET /icons/ho/heise.gif HTTP/1.1
>Host: www.heise.de
>User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.7.3) Gecko/20040913
>Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
>Accept-Language: de-DE,de;q=0.8,en-GB;q=0.5,en;q=0.3
>Accept-Encoding: gzip,deflate
>Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
>Keep-Alive: 300
>Connection: keep-alive
>Cookie: RMID=8666070e3dd6df80; personality=kind&p&uid&8517&un&Martin%20Schr%F6der&md5&e8b552aa6f099fa3c4d5ff38cb3fb80e
>If-Modified-Since: Mon, 26 Dec 2005 10:07:01 GMT
>If-None-Match: "13a298-e68-43afc0c5"
>Cache-Control: max-age=0
>
>
>
Your browser is requesting fresh content (max-age=0). Try requesting
the content (without hitting reload) from another computer and see if
your results are any different.

>HTTP/1.0 200 OK
>Date: Fri, 24 Feb 2006 23:35:54 GMT
>Server: Apache/1.3.34
>Cache-Control: max-age=2592000
>Expires: Sun, 26 Mar 2006 23:35:54 GMT
>Last-Modified: Mon, 26 Dec 2005 10:07:01 GMT
>Etag: "2b6a83-e68-43afc0c5"
>Accept-Ranges: bytes
>Content-Length: 3688
>Content-Type: image/gif
>X-Cache: MISS from gryphon.oneiros.de
>Connection: keep-alive
>---------------------------------------
>
>

The server "chose" to return a 200 instead of a 304 (which would have
shown up as a TCP_REFRESH_HIT).

>Thanks in advance
> Martin
>
>
Chris
Received on Fri Feb 24 2006 - 19:22:08 MST