Changeset 943

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:

• draft-ietf-httpbis/latest/p6-cache.xml (modified) (2 diffs)

draft-ietf-httpbis/latest/p6-cache.xml

@@ -33 +33 @@
   <!ENTITY weak-and-strong             "<xref target='Part4' x:rel='#weak.and.strong.validators' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
   <!ENTITY status-codes                "<xref target='Part2' x:rel='#status.codes' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
+  <!ENTITY status.2xx                  "<xref target='Part2' x:rel='#status.2xx' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
 ]>
 <?rfc toc="yes" ?>
@@ -803 +804 @@
 </t>
 <t>
-  The following HTTP methods &MUST; cause a cache to invalidate the Effective Request URI (&effective-request-uri;) as well
+  In a succesful exchange (&status.2xx;), the following HTTP methods &MUST; cause a cache 
+  to invalidate the Effective Request URI (&effective-request-uri;) as well
   as the URI(s) in the Location and Content-Location headers (if present):
   <list style="symbols">