Re: If-Modified-Since enhancement

• Mail folder: WWW Talk Jan 94-present
• Next message: Jared Rhine: "SOAP Requirements"
• Previous message: Roy T. Fielding: "Re: If-Modified-Since enhancement "
• Maybe in reply to: Ari Luotonen: "Re: If-Modified-Since enhancement"

Errors-To: listmaster@www0.cern.ch
Date: Tue, 22 Mar 1994 13:03:13 --100
Message-id: <9403221201.AA01192@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: Re: If-Modified-Since enhancement
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
Content-Length: 1073

So I changed If-Modified-Since spec phrasing.  Essential content
is the same.  Thanks, Roy!

> 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 the If-Modified-Since field, the server responds with
> a 304 status code and does not send the document body to the client. 
> 
> Response headers are as if the client had sent a HEAD request, but 
> limited to only those headers which make sense in this context. This
> means only headers that are relevant to cache managers and which may
> have changed independently of the document's Last-modified date. 
> Examples include Date, Server, and Expires.
> 
> The purpose of this feature is to allow efficient updates of local
> cache information (including relevant metainformation) without requiring
> the overhead of multiple HTTP requests (e.g. a HEAD followed by a GET)
> and minimizing the transmittal of information already known by the
> requesting client (usually a caching proxy).

-- Cheers, Ari --