W3C home > Mailing lists > Public > http-caching-historical@w3.org > January 1996

RE: GET, POST, and side-effects

From: Paul Leach <paulle@microsoft.com>
Date: Thu, 4 Jan 96 13:33:34 PST
To: http-caching@pa.dec.com, mogul@pa.dec.com
Message-Id: red-16-msg960104212812MTP[01.52.00]000000b0-5325
It seems pretty straightforward that if a proxy forwards a POST, and 
gets back a Location: URI and Expires: or Cache-Control: headers that 
say that the returned entity will be fresh for some period of time, it 
should be able to serve that entity safely from the cache for that 
period of time, and do GET I-M-Ss on it after that time to determine if 
it is still fresh.  Maybe very few POSTs will do this, because most 
POSTs are for dynamically generated content, but that doesn't affect 
the correctness of the argument.

A very similar argument applies to PUT.

Received on Thursday, 4 January 1996 21:39:48 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:55:57 UTC