It seems like even though squid does not update the cache with headers from a 304 reply as recorded here: http://www.squid-cache.org/bugs/show_bug.cgi?id=7 It should still obey the max-age directive for Surrogate-Control, shouldn't it? I mean, even when the LastModified Header is just a few seconds in the past, when using: Surrogate-Control: max-age=3600, content="ESI/1.0" I still get a TCP_REFRESH_HIT instead of a TCP_HIT the second time I hit it. It's just that now, I no longer get:
Warning: 113 www.myserver.com (squid/3.0-PRE3-20031106) This cache hit is still fresh and more than 1 day old
Any advice or clarification of how this works would be appreciated.
Thanks.
From: "Y Jones" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: [squid-users] TCP_HIT with Surrogate-Control? Date: Fri, 07 Nov 2003 14:05:58 -0500
No matter what number I set max-age to for Surrogate-Control, I get TCP_REFRESH_HIT.
I have to unset the Surrogate-Control header to get a TCP_HIT. Can someone tell
me how to set the headers to get a TCP_HIT with Surrogate-Control?
These are my apache headers that result in TCP_REFRESH_HIT:
HTTP/1.1 200 OK Date: Fri, 07 Nov 2003 18:56:59 GMT Server: Apache/1.3.28 (Unix) Cache-Control: max-age=86400 Expires: Sat, 08 Nov 2003 18:56:59 GMT Surrogate-Control: max-age=3600, content="ESI/1.0" Last-Modified: Wed, 05 Nov 2003 20:20:23 GMT Connection: close Content-Type: text/html
I am using squid/3.0-PRE3-20031106 in accelerator mode.
Thanks in advance.
_________________________________________________________________
Crave some Miles Davis or Grateful Dead? Your old favorites are always playing on MSN Radio Plus. Trial month free! http://join.msn.com/?page=offers/premiumradio
