Re: Data Integrity

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.

				Ted