No-Cache: Squid vs RFC2616

The Squid FAQ (12.23) states Squid-2 does not cache a document
returned with the response header Cache-Control:No-Cache.

However, RFC2616 (HTTP1.1), Section 14.9.1, specifies the no-cache directive
to mean "a cache MUST NOT use the response to satisfy a subsequent
request without successful revalidation with the origin server."
I take this to mean the response is cachable, but on a subsequent
request the cache need to send an IMS request to the origin server,
not necessarily refetch the object.

Can anyone clarify this apparent discrepancy?

Thanks,
Sandy Dykes
Received on Sat Mar 04 2000 - 03:36:00 MST