Ticket #167: 167.diff

p6-cache.xml

@@ -755 +755 @@
   respond. In the latter case, it &MAY; return a previously stored response (see <xref
   target="serving.stale.responses" />).
 </t>
-<t>
-  If a cache receives a successful response whose Content-Location field  
-  matches that of an existing stored response for the same Request-URI,  
-  whose entity-tag differs from that of the existing stored response,  
-  and whose Date is more recent than that of the existing response, the  
-  existing response &SHOULD-NOT; be returned in response to future  
-  requests and &SHOULD; be deleted from the cache. <cref>DISCUSS: Not  
-  sure if this is necessary.</cref>
-</t>
 </section>
 
 <section anchor="invalidation.after.updates.or.deletions" title="Request Methods that Invalidate">
@@ -2069 +2060 @@
 
 <section anchor="changes.from.rfc.2616" title="Changes from RFC 2616">
 <t>
+  Remove requirement to consider Content-Location in successful responses
+  in order to invalidate cached responses.
+  (<xref target="validation.model" />)
+</t>
+<t>
   Clarify denial of service attack avoidance requirement.
   (<xref target="invalidation.after.updates.or.deletions" />)
 </t>
@@ -2308 +2304 @@
   Closed issues:
   <list style="symbols"> 
     <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/167"/>:
+      "Content-Location on 304 responses"
+    </t>
+    <t>
       <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/187"/>:
       "RFC2047 and warn-text"
     </t>