Re: upcoming changes to TTLs.

rob@sloth.rpi.net.au writes:

>At 10:13 PM 27/10/1996 -0800, you wrote:
>>For the next 1.1 beta version I have changed the way Squid handles
>>object lifetimes. Instead of calculating a TTL when the object
>>enters the cache, it now checks for "freshness" or "staleness"
>>when the request is made.
>
>[...]
>
>>
>>If the object age is less than 'min', it is fresh.
>>
>>If the object expiry time has been reached, it is stale.
>>
>>If the object age is more than 'max', it is stale.
>
>Can I clarify something? Will this ignore these bloody Expires headers
>that Microsoft keep feeding us with an expiry of now?

Yes, if you write:

    refresh_pattern http://.*microsoft.com/ 60 50% 1440

Then your cache would immediately return HITs for microsoft.com URLs
less than 60 minutes old.

But note there are other headers they can send to prevent caching,
such as "Cache-Control: private."

Duane W.
Received on Mon Oct 28 1996 - 09:19:39 MST