RE: Cache-Control: no-cache

[ henrik, I'm not on squid-dev, so you may need to forward this ]

> * must-revalidate, cached object MUST NOT be returned if validation
> fails.

I read must-revalidate as cached object must not be returned if not fresh
(according to its max-age, Expires, etc)

> There is a slight difference in no-cache and max-age=0, in
> that objects
> tagged with no-cache or must-revalidate MUST NOT be sent to clients
> without sucessful revalidation, while max-age MAY be overridden by
> configuration or revalidation failures.

Ah, that's it. Thank you. The algorithm I put in my last mail should cover
this; however, I forgot Pragma: no-cache.

> The HTTP/1.1 draft 6 standard contains a great deal of
> information, but
> is in part badly structured. There are many overlapping areas

You might find this a bit helpful, although it's not up-to-date as it should
be:
http://www.geocities.com/SiliconValley/Garage/3246/http11rq.txt
Received on Tue Jul 29 2003 - 13:15:58 MDT