Re: refresh pattern

Very aggressive caching, which will surely break a lot of web
applications if used alone without exceptions. Defenitely NOT something
I would recommend as a default refresh pattern in any setup.

In cleartext what it says:

for every obect not matched in a rule above this:
1. If a explicit expiry time is set by the origin server then cache the
object until expired.
2. If last-modified time is known, then the object is considered fresh
the same amount of time since it was last modified (modified 30 minutes
ago, then fresh for another 30 minutes). At most 86400 minutes, or 60
days.
3. If no expiry/modification time is known, then consider the object
fresh for 30 days.

You should NEVER EVER have a default min age other than 0 unless you
know exactly what you are doing. Using this aggressive refresh rules
will in most situations defeat caching since users will quickly learn
that they have to push the reload button to get fresh data, and will
push it often, even when not required.

---
Henrik Nordstrom
Spare time Squid hacker
Lubna Sorour wrote:
> 
> What does this line mean?
> 
> refresh_pattern         .       43200 100% 86400