Re: [squid-users] Cache not refreshing

From: Henrik Nordstrom <hno@dont-contact.us>
Date: Wed, 24 Mar 2004 17:12:35 +0100 (CET)

On Wed, 24 Mar 2004, Bruno Lustosa wrote:

> * Henrik Nordstrom <hno@squid-cache.org> [23-03-2004 19:38]:
> > > I think these are the relevant lines. They were taken the first time I
> > > tried to open the url:
> > >
> > > 1080047467.580 1 cerberus.elnet.grupomk TCP_HIT/200 942 GET http://www.ministeriokoinonyadelouvor.com.br/ lofofora NONE/- text/html
> >
> > This was fresh in the cache. See refresh_pattern.
> >
> > > 1080047467.602 22 cerberus.elnet.grupomk TCP_NEGATIVE_HIT/404 1177 GET http://www.ministeriokoinonyadelouvor.com.br/_site/shop_home.cfm lofofora NONE/- text/html
> >
> > This was known to not exists.. see negative_ttl
> >
> > > 1080047469.352 1668 cerberus.elnet.grupomk TCP_MISS/404 3011 GET http://www.ministeriokoinonyadelouvor.com.br/favicon.ico lofofora DIRECT/200.255.218.31 text/html
> >
> > And this was not found..
>
> That's the strange thing. The page was there. Is there any chance squid
> will cache the 404, and when people try to access, they will get the
> 404, regardless of the fact there is something there now?

see negative_ttl

> I've just got the same experience again. A file on the web server was
> deleted, but it would still show in the browser. That is, until I forced
> a browser refresh.

Yes.

> Perhaps I should tweak my refresh_pattern settings? The default seems to
> be causing some trouble.

There is no "optimal" cache setting. There is always a tradeoff in how up
to date the information is and hit ratio. If you see caching as a big
problem then the best action is to not cache (see the no_cache directive).

Regards
Henrik
Received on Wed Mar 24 2004 - 09:12:38 MST

This archive was generated by hypermail pre-2.1.9 : Thu Apr 01 2004 - 12:00:02 MST