Ignore:
Timestamp:
May 26, 2011, 9:06:18 PM (9 years ago)
Author:
mnot@…
Message:

Don't talk about "understanding" methods in invalidation; #289

File:
1 edited

Legend:

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

    r1289 r1290  
    870870   title="Request Methods that Invalidate">
    871871<t>
    872    Because unsafe request methods (&safe-methods;) have the potential for changing
    873    state on the origin server, intervening caches can use them to keep their
    874    contents up-to-date.
     872   Because unsafe request methods (&safe-methods;) such as PUT, POST or DELETE
     873   have the potential for changing state on the origin server, intervening
     874   caches can use them to keep their contents up-to-date.
    875875</t>
    876876<t>
    877877   A cache &MUST; invalidate the effective Request URI
    878878   (&effective-request-uri;) as well as the URI(s) in the Location
    879    and Content-Location header fields (if present) when the following
    880    request methods are received:
    881    <list style="symbols">
    882       <t>PUT</t>
    883       <t>DELETE</t>
    884       <t>POST</t>
    885    </list>
     879   and Content-Location header fields (if present) when requests with
     880   unsafe methods are received.
    886881</t>
    887882<t>
     
    892887</t>
    893888<t>
    894    A cache that passes through requests with methods it does not understand
    895    &SHOULD; invalidate the effective request URI (&effective-request-uri;).
     889         A cache &SHOULD; invalidate the effective request URI
     890         (&effective-request-uri;) when passing through requests with methods
     891         whose safety is unknown.
    896892</t>
    897893<t>
     
    27112707            "Mismatch Vary"
    27122708          </t>
     2709          <t>
     2710                  <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/289"/>:
     2711                  "Proxies don't 'understand' methods"
     2712                </t>
    27132713  </list>
    27142714</t>
Note: See TracChangeset for help on using the changeset viewer.