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

From: Henrik Nordstrom <hno@dont-contact.us>
Date: Sat, 9 Mar 2002 04:27:30 +0100

It is supported. See refresh.c for the hairy details.

Regards
Henrik

On Friday 08 March 2002 13:15, Joe Cooper wrote:
> 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.
>
> Also, I seem to be hitting a weirdness in client/squidclient when
> using the -H option--I was trying to test using max-age, but found
> whenever I append a header to the client request using the -H
> option it just hangs for about 30 seconds and then returns with
> nothing, and nothing shows up in the access log. Taking out the -H
> section makes the request work, and changing the -H to a
> 'Cache-Control: no-cache' exhibits the same behavior. Squid
> version is 2.4STABLE4.
>
> Thanks!
Received on Fri Mar 08 2002 - 20:29:41 MST

This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:14:50 MST