last-seen & server ability to indicate "Never cache"?

Matt Heffron <heffron@falstaff.css.beckman.com>
Errors-To: listmaster@www0.cern.ch
Date: Thu, 10 Mar 1994 20:55:38 --100
Message-id: <9403101945.AA09226@dxmint.cern.ch>
Errors-To: listmaster@www0.cern.ch
Reply-To: heffron@falstaff.css.beckman.com
Originator: www-talk@info.cern.ch
Sender: www-talk@www0.cern.ch
Precedence: bulk
From: Matt Heffron <heffron@falstaff.css.beckman.com>
To: Multiple recipients of list <www-talk@www0.cern.ch>
Subject: last-seen & server ability to indicate "Never cache"?
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
Content-Length: 851
Larry Masinter <masinter@parc.xerox.com> asks:

>a) If the server has a file with an EARLIER date, do you want that too?

>From Ari's description of "If-Modified-Since: date" I'd say NO. 
return the 304 status code

>b) is the date in GMT?

It better be, or include the offset from GMT.

---
If we want to do caching well, we also need some way to indicate
that a document should never be cached, e.g. the output from some
scripts will ALWAYS be new documents.  There's no point
cluttering the cache with things that will never be served again.

Matt Heffron

PS.  Where is the latest HTTP spec available from?

--
Matt Heffron                      heffron@falstaff.css.beckman.com
Beckman Instruments, Inc.         voice: (714) 961-3128
2500 N. Harbor Blvd. MS X-10, Fullerton, CA 92634-3100
I don't speak for Beckman Instruments unless they say so.