- From: Koen Holtman <koen@win.tue.nl>
- Date: Thu, 4 Apr 1996 13:22:28 +0200 (MET DST)
- To: mogul@pa.dec.com (Jeffrey Mogul)
- Cc: hardie@nasa.gov, http-caching@pa.dec.com
Jeffrey Mogul: > >After thinking about Ted's suggestion for a "Customizable Warning", >I decided to include this: > > 98 Customizable warning [...] > 99 Miscellaneous warning These semantics look good to me. But if you want to require caches to (not) take certain actions on getting a 98, even though a "Cache-control: no-cache" header is not present in the response, the header for sending the 98 code should not be called `warning'. To me, a warning message is something I may always choose to ignore. What about calling it 'cache-exception' or something? `The cache-exception response header field is used to signal exceptional situations in which the normal caching rules do not apply, or could not be applied, to clients in the response chain'. >-Jeff Koen.
Received on Thursday, 4 April 1996 11:49:40 UTC