Re: [squid-users] How to determine why an object isn't being cached?

Denis Haskin wrote:

> What I'm trying to do is set my (origin server) response headers
> appropriately so that an authorized request is validated and subsequent
> requests for the same object with the same credential are satisfied out
> of
> Squid's cache, but non-authorized requests are re-validated and
> rejected.

Squid currently only implements caching of public objects.

I don't think it would be too hard to extend this to include the
"s-maxage" or "must-revalidate" criterias. See RFC2616 section 14.8 for
details about how things should behave in such cases..

Note: Squid does not yet implement the s-* cache-control directives from
RFC2616. Only the older directives from RFC2068.

--
Henrik Nordstrom
Squid Hacker