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

Re: EDITs to 10.3.5 (304 Not Modified)

From: Robert S. Thau <rst@ai.mit.edu>
Date: Fri, 7 Jun 1996 10:14:48 -0400
Message-Id: <199606071414.KAA13807@volterra.ai.mit.edu>
To: http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com, mogul@pa.dec.com
Cc: jg@w3.org
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/857
    The response MUST include the following header fields:
        .   Date
        .   ETag and/or Content-Location, if the header would have been
                sent in a 200 response to the same request
        .   Expires, Cache-Control, and/or Vary, if the field-value
                might differ from that sent in any previous response
                for the same variant
    If the conditional GET used a strong cache validator (see section
    13.3.3), the response SHOULD NOT include other entity-headers.
    Otherwise (i.e., the conditional GET used a weak validator),
    the response MUST NOT include other entity-headers; this prevents
    inconsistencies between cached entity-bodies and updated headers.

Thanks... this language is an *enormous* improvement.  I'm not sure
I'm fully enough clued in to the constraints on cache behavior to be
absolutely certain that this provides enough information on that end,
but at the very least, I'm no longer wondering what an origin server
is supposed to do.  

I notice that this change has not yet appeared in the (preliminary?)
draft 05 text on the W3C HTTP issues page... is it planned for inclusion
in the final submission?

Received on Friday, 7 June 1996 07:18:16 UTC

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