- From: John Franks <john@math.nwu.edu>
- Date: Tue, 15 Aug 1995 23:50:03 -0500 (CDT)
- To: Lou Montulli <montulli@mozilla.com>
- Cc: john@math.nwu.edu, http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
According to Lou Montulli: > > I recently changed netscape to interpret "Pragma: no-cache" and not > cache the object. This is slightly different than a "Expires" header > because the object will not even be cached for history navigation. > (Documents that are expired are still shown when traversing the session > history). Haveing the client interpret "Pragma: no-cache" lets servers > tell the client that this information is highly sensitive or volitile > and should not be cached in any way. > Well, I find this reasonable. But, I believe that the latest version of the spec says the client should ignore Pragma: no-cache. What I think is important is that there be some way to stop the client from caching -- as apparently there now is with Netscape. :) I don't care if it is Pragma: no-cache or if there is a separate way (Pragma: no-local-cache ?) but apparently someone does since the spec wants the client to ignore Pragma: no-cache. Could someone explain the rationale for this? John Franks
Received on Tuesday, 15 August 1995 21:51:43 UTC