W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > January to April 1996

Re: Data Integrity

From: Ted Hardie <hardie@merlot.arc.nasa.gov>
Date: Thu, 15 Feb 1996 15:05:20 -0800 (PST)
Message-Id: <199602152305.PAA18362@merlot.arc.nasa.gov>
To: Shel Kaphan <sjk@amazon.com>
Cc: http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
Shel Kaplan writes:
> This points to the likelihood of confusion when overloading the same
> token (``no-cache'') with a meaning in both requests and responses.
> In Roy's proposed spec for HTTP 1.1, cache-control: no-cache in
> requests indicates that the request cannot be serviced by any
> intermediate server -- only the origin server.  In responses,
> cache-control: no-cache indicates that the response cannot be stored
> in a cache.  So the hypothetical implementor you describe would be
> wrong to make that assumption.
> --Shel

I believe switching to cache-control: reload from clients and 
cache-control: no-cache would solve this particular confusion.

Received on Thursday, 15 February 1996 15:01:52 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:40:16 UTC