W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2003

Re: Expires header vs Vary header

From: Jeffrey Mogul <Jeff.Mogul@hp.com>
Date: Mon, 08 Dec 2003 11:59:31 -0800
Message-Id: <200312081959.hB8JxVjw024648@wera.hpl.hp.com>
To: Alex Rousskov <rousskov@measurement-factory.com>
Cc: ietf-http-wg@w3.org

    From: Alex Rousskov <rousskov@measurement-factory.com>
    I am not aware of such dependencies. I would have guessed that
    Mozilla does not update Expires header when receiving a 304
    response, but then it would probably not have worked without the
    Vary either.

If Mozilla is not updating the Expires header when it receives
a 304 response with a new value for that header (as in the
example in Julian Reschke's message), then it is violating
this MUST:

   If a cache uses a received 304 response to update a cache entry, the
   cache MUST update the entry to reflect any new field values given in
   the response.

in RFC2616 section 10.3.5 304 (Not Modified).  This is restated
in more detail in section 13.5.3.

Received on Monday, 8 December 2003 14:59:32 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:13:24 UTC