Re: Cache-Control: max-age on client side?

Joe Cooper wrote:
> Robert Collins wrote:
>
>>
>>> -----Original Message-----
>>> From: Joe Cooper [mailto:joe@swelltech.com] Sent: Friday, March 08,
>>> 2002 11:15 PM
>>> To: squid-dev@squid-cache.org
>>> Subject: Cache-Control: max-age on client side?
>>>
>>>
>>> Hey guys,
>>>
>>> Quick question: Does Squid handle Cache-Control: max-age on the
>>> client side?
>>>
>>> I'd like to be able to force a revalidation (without forcing a full
>>> reload) from a client side request...As far as I can tell from
>>> reading the code, only server side Cache-Control: proxy-revalidate
>>> and must-revalidate and max-age are supported for this. But I don't
>>> quite understand what's happening in http.c WRT max-age and other
>>> cache-control headers, so I may be missing it.
>>>
>>
>> No comment, I'd need to go check the code. See client_side as well
>> though.
>
>
>
> It isn't in client_side...which is where my assumption that it isn't
> supported comes from. (There is no REVALIDATE stuff in client_side at
> all.)

But it does appear to be working as I would expect it to if it were
supported.

I get a 304 (not modified) until I touch the origin file...then it
resends the whole object. And Squid does the right thing in both cases.

Thanks, Robert. I think that's one for the 1.1 checklist.

-- 
Joe Cooper <joe@swelltech.com>
http://www.swelltech.com
Web Caching Appliances and Support