Changeset 497


Ignore:
Timestamp:
Mar 3, 2009, 10:59:01 PM (11 years ago)
Author:
mnot@…
Message:

clean up refs to unsafe methods

File:
1 edited

Legend:

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

    r496 r497  
    451451        <t>All responses satisfied from cache include an appropriate Age header field; see
    452452            <xref target="header.age" />. <cref>DISCUSS: this currently includes successfully validated responses.</cref></t>
    453         <t>Request methods that are unsafe (e.g., POST, PUT, DELETE) &MUST; be written through the cache to
     453        <t>Request methods that are unsafe (&safe-methods;) &MUST; be written through the cache to
    454454          the origin server; i.e., A cache must not reply to such a request before having forwarded the request and having received a
    455455   corresponding response.</t>
     
    660660      <section anchor="invalidation.after.updates.or.deletions"
    661661        title="Request Methods that Invalidate">
    662         <t>Because unsafe methods &safe-methods; have the potential for changing state on the
     662        <t>Because unsafe methods (&safe-methods;) have the potential for changing state on the
    663663          origin server, intervening caches can use them to keep their contents
    664664          up-to-date.</t>
Note: See TracChangeset for help on using the changeset viewer.