Re: Warning: header, need origin

I am absolutely opposed to including anything even remotely similar
to a "protect my ignorant ass" warning in HTTP.  It would just result
in everyone protecting their ass rather than attempting to determine
whether or not a resource is actually cachable.

Including such a warning in the specification would cause grave damage
to everything we are trying to accomplish with caching.

In other words, remove it now.  People who cache in spite of cache-control
will do so in spite of any warning and including a warning in the protocol
has no legal significance to either party unless both parties are consciously
aware that the message is being sent AND will be seen by the person
making the decision to cache.


 ...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 Wednesday, 3 April 1996 22:58:43 UTC