- From: Roy T. Fielding <fielding@liege.ICS.UCI.EDU>
- Date: Fri, 07 Jun 1996 15:59:53 -0700
- To: Paul Leach <paulle@microsoft.com>
- Cc: "'jg@w3.org'" <jg@w3.org>, http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
> The proxy-revalidate directive has the same meaning as the > must-revalidate directive, except that it does not apply to non-shared > user-agent caches. It can be used on a response to an authenticated > request to permit the user's cache to store and later return the > response without needing to revalidate it (since it has already been > authenticated once by that user) , while still requiring proxies that > service many users to revalidate each time (in order to make sure that > each user has been authenticated). Note that such authenticated > responses also need the Cache-Control: public directive in order to > allow them to be cached at all. Since proxy-revalidate says it "has the same meaning as" must-revalidate, then it should be listed in 13.4 as modifying cachability, and the last sentence above should be removed. Aha, so that's where those spaces before commas come from ... ;-) ......Roy
Received on Friday, 7 June 1996 17:04:37 UTC