Changeset 526
- Timestamp:
- 05/03/09 06:23:23 (13 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest-roy/p6-cache.xml
r525 r526 683 683 <section anchor="caching.negotiated.responses" title="Caching Negotiated Responses"> 684 684 <t>Use of server-driven content negotiation (&server-driven-negotiation;) alters 685 the conditions and procedure bywhich a cache can use the response for subsequent685 the conditions under which a cache can use the response for subsequent 686 686 requests.</t> 687 <t>When thecache receives a request which may be satisfied by a stored response688 that includes a Vary header field (<xref target="header.vary"/>), it &MUST-NOT; use th e stored response to satisfy the requestunless689 all of the selecting request-headers present in the newrequest match the corresponding687 <t>When a cache receives a request which may be satisfied by a stored response 688 that includes a Vary header field (<xref target="header.vary"/>), it &MUST-NOT; use that response unless 689 all of the selecting request-headers in the presented request match the corresponding 690 690 stored request-headers from the original request.</t> 691 691 <t>The selecting request-headers from two requests are defined to match if and only if the … … 698 698 resource can only be properly interpreted by the origin server.</t> 699 699 <t>If no stored response matches, the cache &MAY; forward the presented request to the origin 700 server in a conditional request, which&SHOULD; include all ETags stored with700 server in a conditional request, and &SHOULD; include all ETags stored with 701 701 potentially suitable responses in an If-None-Match request header. If the server responds with 304 (Not Modified) and 702 702 includes an entity tag or Content-Location that indicates the entity to be used, that
Note: See TracChangeset
for help on using the changeset viewer.