[squid-dev] [PATCH] Must revalidate CC:no-cache responses

Eduard Bagdasaryan eduard.bagdasaryan at measurement-factory.com
Mon Sep 5 09:52:12 UTC 2016


2016-09-04 18:31 GMT+03:00 Amos Jeffries <squid3 at treenet.co.nz>:

 > * ccPrivate is only cacheable in the same conditions as
 > ccNoCacheNoParams so should be a ENTRY_REVALIDATE_ALWAYS as well

It is unclear what are these "same" conditions. RFC 7234 5.2.2.6:

    The "private" response directive indicates that the response message
    is intended for a single user and MUST NOT be stored by a shared
    cache.

In my understanding Squid (as a shared cache) must not store "private"
responses at all (while user agents could). Is this correct? If yes,
currently Squid violates this MUST.

On the other hand, "no-cache" without field-names does not impose
constraints on storing in the cache, but restricts the cache to always
revalidate.


Eduard.


More information about the squid-dev mailing list