Changeset 827

Timestamp:

07/06/10 11:29:53 (12 years ago)

Author:

julian.reschke@…

Message:

Clarify differences between / requirements for request and response CC directives (see #168)

Location:

draft-ietf-httpbis/latest

Files:

• p6-cache.html (modified) (6 diffs)
• p6-cache.xml (modified) (2 diffs)

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

@@ -402 +402 @@
       <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="2010-06-02">
+      <meta name="dct.issued" scheme="ISO8601" content="2010-06-07">
       <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, hypermedia information systems. 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.">
@@ -428 +428 @@
             </tr>
             <tr>
-               <td class="left">Expires: December 4, 2010</td>
+               <td class="left">Expires: December 9, 2010</td>
                <td class="right">J. Mogul</td>
             </tr>
@@ -489 +489 @@
             <tr>
                <td class="left"></td>
-               <td class="right">June 2, 2010</td>
+               <td class="right">June 7, 2010</td>
             </tr>
          </tbody>
@@ -515 +515 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire in December 4, 2010.</p>
+      <p>This Internet-Draft will expire in December 9, 2010.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
@@ -1030 +1030 @@
       <div id="rfc.iref.h.3"></div>
       <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a id="header.cache-control" href="#header.cache-control">Cache-Control</a></h2>
-      <p id="rfc.section.3.2.p.1">The "Cache-Control" general-header field is used to specify directives that <em class="bcp14">MUST</em> be obeyed by all caches along the request/response chain. Such cache directives are unidirectional in that the presence of
-         a directive in a request does not imply that the same directive is to be given in the response.
-      </p>
-      <div class="note" id="rfc.section.3.2.p.2"> 
+      <p id="rfc.section.3.2.p.1">The "Cache-Control" general-header field is used to specify directives for caches along the request/response chain. Such cache
+         directives are unidirectional in that the presence of a directive in a request does not imply that the same directive is to
+         be given in the response.
+      </p>
+      <p id="rfc.section.3.2.p.2">HTTP/1.1 caches <em class="bcp14">MUST</em> obey the requirements of the Cache-Control directives defined in this section. See <a href="#cache.control.extensions" title="Cache Control Extensions">Section&nbsp;3.2.3</a> for information about how Cache-Control directives defined elsewhere are handled.
+      </p>
+      <div class="note" id="rfc.section.3.2.p.3"> 
          <p> <b>Note:</b> HTTP/1.0 caches might not implement Cache-Control and might only implement Pragma: no-cache (see <a href="#header.pragma" id="rfc.xref.header.pragma.2" title="Pragma">Section&nbsp;3.4</a>).
          </p> 
       </div>
-      <p id="rfc.section.3.2.p.3">Cache directives <em class="bcp14">MUST</em> be passed through by a proxy or gateway application, regardless of their significance to that application, since the directives
+      <p id="rfc.section.3.2.p.4">Cache directives <em class="bcp14">MUST</em> be passed through by a proxy or gateway application, regardless of their significance to that application, since the directives
          might be applicable to all recipients along the request/response chain. It is not possible to target a directive to a specific
          cache.
@@ -1883 +1886 @@
          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/29">http://tools.ietf.org/wg/httpbis/trac/ticket/29</a>&gt;: "Age calculation"
          </li>
+         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/168">http://tools.ietf.org/wg/httpbis/trac/ticket/168</a>&gt;: "Clarify differences between / requirements for request and response CC directives"
+         </li>
          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/208">http://tools.ietf.org/wg/httpbis/trac/ticket/208</a>&gt;: "IANA registry for cache-control directives"
          </li>

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

@@ -977 +977 @@
   <x:anchor-alias value="cache-response-directive"/>
 <t>
-  The "Cache-Control" general-header field is used to specify directives that
-  &MUST; be obeyed by all caches along the request/response chain. Such cache
-  directives are unidirectional in that the presence of a directive in a
-  request does not imply that the same directive is to be given in the
-  response.
+  The "Cache-Control" general-header field is used to specify directives for
+  caches along the request/response chain. Such cache directives are
+  unidirectional in that the presence of a directive in a request does not
+  imply that the same directive is to be given in the response.
+</t>
+<t>
+  HTTP/1.1 caches &MUST; obey the requirements of the Cache-Control directives
+  defined in this section. See <xref target="cache.control.extensions"/> for
+  information about how Cache-Control directives defined elsewhere are handled.
 </t>
 <x:note>
@@ -2463 +2467 @@
     </t>
     <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/168" />:
+      "Clarify differences between / requirements for request and response CC directives"
+    </t>
+    <t>
       <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/208" />:
       "IANA registry for cache-control directives"