My Squid Version is 2.6/STABLE14
Here's my refresh_pattern from squid.conf
#Suggested default:
refresh_pattern ^ftp: 1440 20% 10080
refresh_pattern ^gopher: 1440 0% 1440
#The following line will ignore a client no-cache header
#refresh_pattern -i \.vid$ 0 90% 2880 ignore-reload
refresh_pattern -i \.vid$ 7200 100% 10080 ignore-reload
refresh_pattern . 0 20% 4320
A link to the file looks something like this --> http://ftp.mydomain.com/websites/data/myvideofile.vid
I have to set up a station to grab the header but I can tell you that it does not seem out of the ordinary.
There is one cache-control: Pragma: no-cache
I believe I handle this with the ignore-reload options.
Our server is an IIS server running on Windows 2003.
I also ran a test with min and max age of 0 and 1 respectively, and it seems to work. I receive a TCP_REFRESH_HIT, which is what I would have expected as these files do not change.
Please let me know if you have any other ideas on how to track down why it would release from cache before min age with no Expiration set on the object.
Open to any suggestions.
Thanks
----- Original Message ----
From: Michael Alger <squid_at_mm.quex.org>
To: squid-users_at_squid-cache.org
Sent: Wednesday, September 24, 2008 8:09:50 AM
Subject: Re: [squid-users] Object becomes STALE: refresh_pattern min and max
On Wed, Sep 24, 2008 at 05:29:52AM -0700, BUI18 wrote:
> I went through your same thinking as you described below.
>
> I checked the Expires header from the server and we do not set
> one. I checked via Fiddler web debug tool. I also verified with
> the dev guys here regarding no Expires header. I have set the min
> and max via refresh_pattern because of the absence of the Expires
> header thinking that Squid would keep it FRESH.
>
> Notice the -1 for expiration header (I do not set one on the
> object). My min age is 5 days so I'm not sure why the object
> would be released from cache in less than 2 days.
>
> If the object was released from cache, when the user tried to
> access file, Squid reports TCP_REFRESH_MISS, which to me means
> that it was found in cache but when it sends a If-Modified-Since
> request, it thinks that the file has been modified (which it was
> not as seen by the lastmod date indicated in the store.log below.
Interesting that it's caching the file for 2 days. What are the full
headers returned with the object? Any other cache control headers?
Is there any chance you have a conflicting refresh_pattern, so the
freshness rules being applied aren't the ones you're expecting? May
be worth doing some tests with very small max ages to confirm it's
matching the right rule.
Received on Wed Sep 24 2008 - 18:21:55 MDT
This archive was generated by hypermail 2.2.0 : Fri Sep 26 2008 - 12:00:03 MDT