Ignore:
Timestamp:
Mar 5, 2012, 5:40:47 PM (8 years ago)
Author:
mnot@…
Message:

Adjust language around no-cache with arguments; #337

File:
1 edited

Legend:

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

    r1560 r1563  
    14851485      have been configured to return stale responses.</t>
    14861486      <t>If the no-cache response directive specifies one or more field-names,
    1487       this requirement is limited to the field-values associated with the
    1488       listed response header fields. That is, a cache &MUST-NOT; send the
    1489       specified field-name(s) in the response to a subsequent request without successful
    1490       validation on the origin server. This allows an origin server to prevent
    1491       the re-use of certain header fields in a response, while still allowing
    1492       caching of the rest of the response.</t>
     1487      then a cache MAY use the response to satisfy a subsequent request,
     1488      subject to any other restrictions on caching. However, any header fields
     1489      in the response that have the field-name(s) listed &MUST-NOT; be sent
     1490      in the response to a subsequent request without successful revalidation
     1491      with the origin server. This allows an origin server to prevent the
     1492      re-use of certain header fields in a response, while still allowing
     1493      caching of the rest of the response.</t>
    14931494      <t> <x:h>Note:</x:h> Most HTTP/1.0 caches will not recognize or obey
    14941495      this directive. Also, no-cache response directives with field-names are
    14951496      often handled by implementations as if an unqualified no-cache directive
    14961497      was received; i.e., the special handling for the qualified form is not
    1497       widely implemented. </t>
     1498      widely implemented.</t>
    14981499   </list>
    14991500</t>
Note: See TracChangeset for help on using the changeset viewer.