- From: Ari Luotonen <luotonen@netscape.com>
- Date: Fri, 29 Dec 1995 18:03:25 -0800 (PST)
- To: mogul@pa.dec.com (Jeffrey Mogul)
- Cc: http-caching@pa.dec.com
> So in summary I would say that it might well be sadly reasonable > to ignore "Expires:" today, since it's almost never used, and when > it is used, it is often clearly bogus. Aaargh, no! If it exists but is bogus (un-parseable) treat it as "expires now", and don't cache. It's true that most of the time it's not there, and we can't build on its existence -- but the times it _is_ there, there _is_ a reason for it. There may be software bugs that corrupt it in some cases, but those should be treated as "expires now", because the originator _was_ trying to tell something expiration related, and failing to do that properly, "expires now" is the only safe thing to do. Cheers, -- Ari Luotonen ari@netscape.com Netscape Communications Corp. http://home.netscape.com/people/ari/ 501 East Middlefield Road Mountain View, CA 94043, USA Netscape Server Development Team
Received on Saturday, 30 December 1995 02:37:31 UTC