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.

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!

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