W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > May to August 1996

Meaning of Last-Modified/I-M-S (was Re: Last gasp terminology issue)

From: Jeffrey Mogul <mogul@pa.dec.com>
Date: Tue, 04 Jun 96 14:51:17 MDT
Message-Id: <9606042151.AA09857@acetes.pa.dec.com>
To: "Roy T. Fielding" <fielding@liege.ICS.UCI.EDU>
Cc: http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/788
    > always assumed that
    > the Last-Modified header applied to the variant, not to the whole
    > resource.
    It applies to the resource as a whole, which explains why the definition
    was the way it was (i.e., specified in terms of how the recipient will
    interpret it) and should be.

I agree with Koen on this one.  At the very least, it should be at
the origin server's option to decide whether to keep distinct
Last-Modified dates for each variant, or to use the maximum
over all of the variants of a resource.

Whether or not this has been easy for the CERN and Apache servers
is basically irrelevant, since I see no reason why the protocol
specification should require it, and it might be much harder to
implement in other contexts.

Received on Tuesday, 4 June 1996 15:01:07 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:40:17 UTC