If-Modified-Since enhancement

luotonen@ptsun00.cern.ch (Ari Luotonen)

Mail folder: WWW Talk Jan 94-present
Next message: Rob Raisch, The Internet Company: "Re: Indexing the List of Lists"
Previous message: Kevin Altis: "Re: file://localhost => local: ?"
Maybe in reply to: Markus Stumpf: "Re: If-Modified-Since enhancement"
Reply: Ari Luotonen: "Re: If-Modified-Since enhancement"

Errors-To: listmaster@www0.cern.ch
Date: Mon, 21 Mar 1994 21:21:04 --100
Message-id: <9403212019.AA00845@ptsun03.cern.ch>
Errors-To: listmaster@www0.cern.ch
Reply-To: luotonen@ptsun00.cern.ch
Originator: www-talk@info.cern.ch
Sender: www-talk@www0.cern.ch
Precedence: bulk
From: luotonen@ptsun00.cern.ch (Ari Luotonen)
To: Multiple recipients of list <www-talk@www0.cern.ch>
Subject: If-Modified-Since enhancement
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
Content-Length: 710


Since nobody objected, and some gave me feedback saying it was
a good idea, the HTTP spec now says:


  NOT MODIFIED 304
 
       If the client has done a conditional GET and access is allowed, but
       the document has not been modified since the date and time specified
       in If-Modified-Since field, server responds with 304 status code, and
       does not send the document back to the client.
 
NEW:   Response headers are as if the client had originally sent a HEAD request.
NEW:   This way the server can upload a new expiry date and other necessary
NEW:   metainformation to the requesting client (often a caching proxy).
 
       This is to allow fast update of caches.
 
 
-- Cheers, Ari --