Changeset 943


Ignore:
Timestamp:
Jul 27, 2010, 6:20:49 AM (9 years ago)
Author:
ylafon@…
Message:

clarify that only successful exchanges (2xx) are mandating invalidation on caches for PUT/POST/DELETE and unknown methods.
(See #235)

File:
1 edited

Legend:

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

    r938 r943  
    3333  <!ENTITY weak-and-strong             "<xref target='Part4' x:rel='#weak.and.strong.validators' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    3434  <!ENTITY status-codes                "<xref target='Part2' x:rel='#status.codes' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     35  <!ENTITY status.2xx                  "<xref target='Part2' x:rel='#status.2xx' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    3536]>
    3637<?rfc toc="yes" ?>
     
    803804</t>
    804805<t>
    805   The following HTTP methods &MUST; cause a cache to invalidate the Effective Request URI (&effective-request-uri;) as well
     806  In a succesful exchange (&status.2xx;), the following HTTP methods &MUST; cause a cache
     807  to invalidate the Effective Request URI (&effective-request-uri;) as well
    806808  as the URI(s) in the Location and Content-Location headers (if present):
    807809  <list style="symbols">
Note: See TracChangeset for help on using the changeset viewer.