- From: <jg@w3.org>
- Date: Fri, 07 Jun 96 11:55:30 -0400
- To: Jeffrey Mogul <mogul@pa.dec.com>
- Cc: http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
Here is the revised 10.3.5. - Jim 10.3.5 304 Not Modified If the client has performed a conditional GET request and access is allowed, but the document has not been modified, the server SHOULD respond with this status code. The response MUST NOT contain a message-body. 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. If a 304 response indicates an entity not currently cached, then the cache MUST disregard the response and repeat the request without the conditional. 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. The 304 response MUST NOT include an message-body, and thus is always terminated by the first empty line after the header fields.
Received on Friday, 7 June 1996 09:02:15 UTC