Re: [SQU] Store.log, time cache expires ?

Most likely the cache will only last a few milliseconds with the server
down.
a) It is quite likely that not all content of the server is cached and
fresh in the cache.
b) Certain user actions can force a cache refresh. The most common is
the reload button.

The expires in store.log is the expires header sent by the server. Squid
will normally obey this unless cache replacement or other actions (i.e.
reload button) forces it to behave in some other way.

To help the situation somewhat, make sure that all important content are
recently refreshed in the cache (shift-reload in the browser, or the -r
option to the squid client program), and then enable "ignore-reload" and
"offline_mode" in squid.conf before taking down the real server. You
should also make sure the IP address of the real server is up but
refusing connections while there are maintenance on the server. This to
ensure that Squid will quickly fall back on the cache if it tries to
revalidate any content..

--
Henrik Nordstrom
Squid hacker
Hillel Bilman wrote:
> 
> Hi Duane, I read in the FAQ some of your documentation
> and I wondered if you could shed some light.
> 
> I'm running Squid 2.3 Stable3 as an http accelerator.
> We have set the expires headers to be three days.
> Last night I was asked how long the cache will last for before
> the three days are up and therefore if it's OK to take down the main
> sever.  I tried to read in the store.log the expires tag  - is that in
> seconds the time until that object it will be expired?
> Where in the logs can I see how long something has before it will be
> expired?
> 
> Thanks any help appreciated
> 
> Regards
> H Bilman
> Managing Member
> HZB Technologies
> Tel: +27 11 443 6164
> cell: +27 832300002
> e-mail: hillel@iafrica.com
> 
> --
> To unsubscribe, see http://www.squid-cache.org/mailing-lists.html
--
To unsubscribe, see http://www.squid-cache.org/mailing-lists.html