Re: refresh_pattern in squid-2.3

http://www.ircache.net/cgi-bin/cacheability.py reports

This object will be considered stale, because it doesn't have any
freshness information assigned. It doesn't have a validator present. The
Web server didn't send a Date header for this object, which may cause
problems.

The min age of the refresh pattern you presented is supposed to be used
for cases like this. Not that I would recommend using that refresh
pattern.

It seems to work as expected here using a patchy Squid-2.3.STABLE1 with
the refresh pattern

refresh_pattern -i ^http://www.yahoo.com 120 20% 4320

--
Henrik Nordstrom
Squid hacker
Asfihani wrote:
> 
> Dear sir,
> 
> I have squid-2.2.STABLE.4 in my slackware linux. And it work as usually.
> When I try moving to squid-2.3, I got  some trouble in refresh_pattern.
> I can't find like TCP_IMS_HIT or TCP_HIT in squid-2.3 in my access.log file.
> Example, when I visit http://www.yahoo.com and wait untill done, and I move to another computer
> and opening http://www.yahoo.com it's still connect to default parent or can't read from disk
> 
> this is my refresh_pattern configuration :
> refresh_pattern -i            .         1440    90%     10080 override-expire ignore-reload reload-into-ims
> reload_into_ims off
> 
> my question :
> - Is my configuration wrong ?
> - Did refresh pattern doesn't work with reload_into_ims off ?
> 
> Thanks. Greeting from Indonesia
> --
> Asfihani
> [http://www.its-sby.edu/asfik]