Re: If-Modified-Since enhancement

• Mail folder: WWW Talk Jan 94-present
• Next message: Roy T. Fielding: "Re: Future of meta-indices: site indexing proposal and Perl script "
• Previous message: Roy T. Fielding: "Re: forwarding cache requests "
• Maybe in reply to: Ari Luotonen: "If-Modified-Since enhancement"
• Reply: Ari Luotonen: "Re: If-Modified-Since enhancement"

Errors-To: listmaster@www0.cern.ch
Date: Tue, 22 Mar 1994 10:33:56 --100
Message-id: <9403220932.AA01014@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: 831

> Sorry for the late response (it's Monday here in California)

Sorry, I lost my sense of time 'cause I was working the whole weekend
and didn't realize it was only the first working day after my original
message.

> The only headers which should be sent are
> 
>     Date:
>     Server:
>     Expires:

You're right.  How about saying:

  Response headers are as if the client had originally sent a HEAD
  request, but not all the headers need to be present, only the ones
  that make sense in this context.  That means all the headers that
  are relevant to cache managers, like Expires: and Date:.

  The purpose of this feature is that the server can upload a new expiry
  date and other necessary metainformation to the requesting client
  (often a caching proxy). This is to allow fast update of caches.

-- Cheers, Ari --