W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > September to December 1999

Re: Clarification on cacheability

From: Roy T. Fielding <fielding@kiwi.ICS.UCI.EDU>
Date: Wed, 22 Dec 1999 17:14:32 -0800
To: "Josh Cohen (Exchange)" <joshco@exchange.microsoft.com>
cc: "HTTP-WG (E-mail)" <http-wg@hplb.hpl.hp.com>
Message-ID: <199912221714.aa02992@gremlin-relay.ics.uci.edu>
>But any cache can cache it as long as it obeys the cache-control/expires
>header.
>The navdoc is safe to cache..

If one client is led to believe that they have received a representation
of the requested resource, while another client is led to believe that
they have received instructions on how to navigate to such a representation,
then the navdoc is not safe for a shared cache.  If, however, the target
of the request is supposed to be navigation instructions, then the
response should be 200 (and thus be cacheable by default).

....Roy
Received on Thursday, 23 December 1999 01:15:39 EST

This archive was generated by hypermail pre-2.1.9 : Wednesday, 24 September 2003 06:33:34 EDT