Changeset 1563 for draft-ietf-httpbis/latest/p6-cache.html

Timestamp:

Mar 5, 2012, 5:40:47 PM (8 years ago)

Author:

mnot@…

Message:

Adjust language around no-cache with arguments; #337

File:

• draft-ietf-httpbis/latest/p6-cache.html (modified) (7 diffs)

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

@@ -463 +463 @@
   } 
   @bottom-center {
-       content: "Expires September 5, 2012"; 
+       content: "Expires September 7, 2012"; 
   } 
   @bottom-right {
@@ -498 +498 @@
       <link href="p5-range.html" rel="prev">
       <link href="p7-auth.html" rel="next">
-      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.570, 2012-02-13 19:17:35, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
+      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.570, 2012-02-13 19:17:35, XSLT vendor: SAXON 9.1.0.8 from Saxonica http://www.saxonica.com/">
       <link rel="schema.dct" href="http://purl.org/dc/terms/">
       <meta name="dct.creator" content="Fielding, R.">
@@ -511 +511 @@
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2012-03-04">
+      <meta name="dct.issued" scheme="ISO8601" content="2012-03-06">
       <meta name="dct.replaces" content="urn:ietf:rfc:2616">
       <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 6 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 6 defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages.">
@@ -537 +537 @@
             </tr>
             <tr>
-               <td class="left">Expires: September 5, 2012</td>
+               <td class="left">Expires: September 7, 2012</td>
                <td class="right">J. Mogul</td>
             </tr>
@@ -602 +602 @@
             <tr>
                <td class="left"></td>
-               <td class="right">March 4, 2012</td>
+               <td class="right">March 6, 2012</td>
             </tr>
          </tbody>
@@ -632 +632 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on September 5, 2012.</p>
+      <p>This Internet-Draft will expire on September 7, 2012.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
@@ -1419 +1419 @@
             stale responses.
          </li>
-         <li>If the no-cache response directive specifies one or more field-names, this requirement is limited to the field-values associated
-            with the listed response header fields. That is, a cache <em class="bcp14">MUST NOT</em> send the specified field-name(s) in the response to a subsequent request without successful validation on the origin server.
-            This allows an origin server to prevent the re-use of certain header fields in a response, while still allowing caching of
-            the rest of the response.
+         <li>If the no-cache response directive specifies one or more field-names, then a cache MAY use the response to satisfy a subsequent
+            request, subject to any other restrictions on caching. However, any header fields in the response that have the field-name(s)
+            listed <em class="bcp14">MUST NOT</em> be sent in the response to a subsequent request without successful revalidation with the origin server. This allows an origin
+            server to prevent the re-use of certain header fields in a response, while still allowing caching of the rest of the response.
          </li>
          <li> <b>Note:</b> Most HTTP/1.0 caches will not recognize or obey this directive. Also, no-cache response directives with field-names are often