Changeset 526


Ignore:
Timestamp:
Mar 4, 2009, 10:23:23 PM (11 years ago)
Author:
mnot@…
Message:

clarify language in caching negotiated responses

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest-roy/p6-cache.xml

    r525 r526  
    683683      <section anchor="caching.negotiated.responses" title="Caching Negotiated Responses">
    684684        <t>Use of server-driven content negotiation (&server-driven-negotiation;) alters
    685           the conditions and procedure by which a cache can use the response for subsequent
     685          the conditions under which a cache can use the response for subsequent
    686686          requests.</t>
    687         <t>When the 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 the stored response to satisfy the request unless
    689           all of the selecting request-headers present in the new request match the corresponding
     687        <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
    690690          stored request-headers from the original request.</t>
    691691        <t>The selecting request-headers from two requests are defined to match if and only if the
     
    698698          resource can only be properly interpreted by the origin server.</t>
    699699        <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 with
     700          server in a conditional request, and &SHOULD; include all ETags stored with
    701701          potentially suitable responses in an If-None-Match request header. If the server responds with 304 (Not Modified) and
    702702          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.