Re: "Cache-control: no-cache", "Cache-control: private", and , extensibility

> I guess I share Jeff's difficulty conjuring up a case where it
> would be meaningful to cache a response w/o associated headers.

It isn't my area of expertise (I don't do stateful sessions -- hell, I
don't even bother to look at the content of a site that uses stateful
sessions, since it is a wasteful practice 99% of the time).

The capability exists because, after perusal of Dave Kristol's state
info discussions, I found that there was no way to express those
semantics within the existing HTTP syntax.  Therefore, rather than
assume I knew all possible applications of HTTP, I chose a syntax
which gave that capability to the server.

If it turns out not to be useful, it won't be used.  The syntax itself
does not burden the caches if it isn't used, and implementation is trivial.


 ...Roy T. Fielding
    Department of Information & Computer Science    (fielding@ics.uci.edu)
    University of California, Irvine, CA 92717-3425    fax:+1(714)824-4056
    http://www.ics.uci.edu/~fielding/

Received on Tuesday, 20 February 1996 18:59:29 UTC