- From: Roy T. Fielding <fielding@avron.ICS.UCI.EDU>
- Date: Wed, 10 Jan 1996 02:59:36 -0800
- To: Koen Holtman <koen@win.tue.nl>
- Cc: http-caching@pa.dec.com
> Personally, I think that "no-cache" is much more clear than "reload".
> "reload" makes me think of reload buttons on browsers, and these have
> little to do with the caching of normal requests.
I was just about to say something about this as well, but different.
The current semantics of
Cache-Control: no-cache
are identical to that of
Pragma: no-cache
which is not the semantics of a "reload" action. "no-cache" means
no interference from the cache, such that
GET / HTTP/1.1
Cache-Control: no-cache
will indeed result in a "reload" action, but
GET / HTTP/1.1
If-Modified-Since: Wed, 10 Jan 1996 10:07:34 GMT
Cache-Control: no-cache
is only a conditional GET that is answered by the origin server
(i.e., a freshness check on the origin) which may still result in
a 304 response and thus is not considered a "reload" action.
.....Roy
Received on Wednesday, 10 January 1996 11:11:12 UTC