Re: Cookies and caching

On Wed, 24 Jan 2001, Chemolli Francesco (USI) wrote:

> How is the current caching policy WRT cookies?
>
> Thinko: while certain cookies effectively render a
> page uncacheable, others (bugs, trackers, etc.)
> can be ignored for caching purposes, others obviously shouldn't.
> which cookies should and which shouldn't should anyways be
> left to a server's administrator to decide.
> So the idea is to allow some kind of regexp-based cookie-related
> ACL to be used with no_cache directives.
>
> Thoughts?

12.19 How does Squid deal with Cookies?

The presence of Cookies headers in requests does not affect whether
or not an HTTP reply can be cached. Similarly, the presense of
Set-Cookie headers in replies does not affect whether the reply
can be cached.

The proper way to deal with Set-Cookie reply headers, according to
RFC 2109 is to cache the whole object, EXCEPT the Set-Cookie header
lines.

With Squid-1.1, we can not filter out specific HTTP headers, so
Squid-1.1 does not cache any response which contains a Set-Cookie
header.

With Squid-2, however, we can filter out specific HTTP headers.
But instead of filtering them on the receiving-side, we filter them
on the sending-side. Thus, Squid-2 does cache replies with Set-Cookie
headers, but it filters out the Set-Cookie header itself for cache
hits.
Received on Wed Jan 24 2001 - 10:46:59 MST