Changeset 1483 for draft-ietf-httpbis/latest

Timestamp:

05/12/11 03:17:47 (9 years ago)

Author:

mnot@…

Message:

Clarify effects of request Cache-Control; closes #293.

Location:

draft-ietf-httpbis/latest

Files:

• p6-cache.html (modified) (11 diffs)
• p6-cache.xml (modified) (3 diffs)

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

@@ -362 +362 @@
   } 
   @bottom-center {
-       content: "Expires June 3, 2012"; 
+       content: "Expires June 7, 2012"; 
   } 
   @bottom-right {
@@ -410 +410 @@
       <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="2011-12-01">
+      <meta name="dct.issued" scheme="ISO8601" content="2011-12-05">
       <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.">
@@ -436 +436 @@
             </tr>
             <tr>
-               <td class="left">Expires: June 3, 2012</td>
+               <td class="left">Expires: June 7, 2012</td>
                <td class="right">J. Mogul</td>
             </tr>
@@ -501 +501 @@
             <tr>
                <td class="left"></td>
-               <td class="right">December 1, 2011</td>
+               <td class="right">December 5, 2011</td>
             </tr>
          </tbody>
@@ -531 +531 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on June 3, 2012.</p>
+      <p>This Internet-Draft will expire on June 7, 2012.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
@@ -844 +844 @@
          <li>selecting header fields nominated by the stored response (if any) match those presented (see <a href="#caching.negotiated.responses" title="Caching Negotiated Responses">Section&nbsp;2.7</a>), and
          </li>
-         <li>the presented request and stored response are free from directives that would prevent its use (see <a href="#header.cache-control" id="rfc.xref.header.cache-control.2" title="Cache-Control">Section&nbsp;3.2</a> and <a href="#header.pragma" id="rfc.xref.header.pragma.1" title="Pragma">Section&nbsp;3.4</a>), and
+         <li>the presented request does not contain the no-cache pragma (<a href="#header.pragma" id="rfc.xref.header.pragma.1" title="Pragma">Section&nbsp;3.4</a>), nor the no-cache cache directive (<a href="#cache-request-directive" title="Request Cache-Control Directives">Section&nbsp;3.2.1</a>), unless the stored response is successfully validated (<a href="#validation.model" title="Validation Model">Section&nbsp;2.4</a>), and
+         </li>
+         <li>the stored response does not contain the no-cache cache directive (<a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a>), unless it is successfully validated (<a href="#validation.model" title="Validation Model">Section&nbsp;2.4</a>), and
          </li>
          <li>the stored response is either: 
@@ -891 +893 @@
 </pre> <p id="rfc.section.2.3.p.6">The freshness_lifetime is defined in <a href="#calculating.freshness.lifetime" title="Calculating Freshness Lifetime">Section&nbsp;2.3.1</a>; the current_age is defined in <a href="#age.calculations" title="Calculating Age">Section&nbsp;2.3.2</a>.
       </p>
-      <p id="rfc.section.2.3.p.7">Additionally, clients might need to influence freshness calculation. They can do this using several request cache directives,
-         with the effect of either increasing or loosening constraints on freshness. See <a href="#cache-request-directive" title="Request Cache-Control Directives">Section&nbsp;3.2.1</a>.
+      <p id="rfc.section.2.3.p.7">Additionally, clients can influence freshness calculation -- either constraining it relaxing it -- by using the max-age and
+         min-fresh request cache directives. See <a href="#cache-request-directive" title="Request Cache-Control Directives">Section&nbsp;3.2.1</a> for details.
       </p>
       <p id="rfc.section.2.3.p.8">Note that freshness applies only to cache operation; it cannot be used to force a user agent to refresh its display or reload
@@ -1674 +1676 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <td class="left"> <a href="#header.cache-control" id="rfc.xref.header.cache-control.3" title="Cache-Control">Section&nbsp;3.2</a> 
+                  <td class="left"> <a href="#header.cache-control" id="rfc.xref.header.cache-control.2" title="Cache-Control">Section&nbsp;3.2</a> 
                   </td>
                </tr>
@@ -2093 +2095 @@
       </ul>
       <h2 id="rfc.section.C.19"><a href="#rfc.section.C.19">C.19</a>&nbsp;<a id="changes.since.17" href="#changes.since.17">Since draft-ietf-httpbis-p6-cache-17</a></h2>
-      <p id="rfc.section.C.19.p.1">No changes yet.</p>
+      <p id="rfc.section.C.19.p.1">Closed issues: </p>
+      <ul>
+         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/293">http://tools.ietf.org/wg/httpbis/trac/ticket/293</a>&gt;: "Interaction of request and response Cache-Control"
+         </li>
+      </ul>
       <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
       <p class="noprint"><a href="#rfc.index.A">A</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.E">E</a> <a href="#rfc.index.F">F</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.N">N</a> <a href="#rfc.index.O">O</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> <a href="#rfc.index.V">V</a> <a href="#rfc.index.W">W</a> 
@@ -2124 +2130 @@
                   <li>cache entry&nbsp;&nbsp;<a href="#rfc.iref.c.4">2</a></li>
                   <li>cache key&nbsp;&nbsp;<a href="#rfc.iref.c.5">2</a></li>
-                  <li>Cache-Control header field&nbsp;&nbsp;<a href="#rfc.xref.header.cache-control.1">2.1</a>, <a href="#rfc.xref.header.cache-control.2">2.2</a>, <a href="#rfc.iref.c.6"><b>3.2</b></a>, <a href="#rfc.xref.header.cache-control.3">5.2</a></li>
+                  <li>Cache-Control header field&nbsp;&nbsp;<a href="#rfc.xref.header.cache-control.1">2.1</a>, <a href="#rfc.iref.c.6"><b>3.2</b></a>, <a href="#rfc.xref.header.cache-control.2">5.2</a></li>
                   <li>cacheable&nbsp;&nbsp;<a href="#rfc.iref.c.3">1.2</a></li>
                </ul>
@@ -2167 +2173 @@
                      <ul>
                         <li>Age&nbsp;&nbsp;<a href="#rfc.xref.header.age.1">2.2</a>, <a href="#rfc.xref.header.age.2">2.3.2</a>, <a href="#rfc.iref.h.2"><b>3.1</b></a>, <a href="#rfc.xref.header.age.3">5.2</a></li>
-                        <li>Cache-Control&nbsp;&nbsp;<a href="#rfc.xref.header.cache-control.1">2.1</a>, <a href="#rfc.xref.header.cache-control.2">2.2</a>, <a href="#rfc.iref.h.3"><b>3.2</b></a>, <a href="#rfc.xref.header.cache-control.3">5.2</a></li>
+                        <li>Cache-Control&nbsp;&nbsp;<a href="#rfc.xref.header.cache-control.1">2.1</a>, <a href="#rfc.iref.h.3"><b>3.2</b></a>, <a href="#rfc.xref.header.cache-control.2">5.2</a></li>
                         <li>Expires&nbsp;&nbsp;<a href="#rfc.xref.header.expires.1">2.1</a>, <a href="#rfc.xref.header.expires.2">2.3</a>, <a href="#rfc.xref.header.expires.3">2.3.1</a>, <a href="#rfc.iref.h.4"><b>3.3</b></a>, <a href="#rfc.xref.header.expires.4">5.2</a></li>
                         <li>Pragma&nbsp;&nbsp;<a href="#rfc.xref.header.pragma.1">2.2</a>, <a href="#rfc.xref.header.pragma.2">3.2</a>, <a href="#rfc.iref.h.5"><b>3.4</b></a>, <a href="#rfc.xref.header.pragma.3">5.2</a></li>

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

@@ -627 +627 @@
       match those presented (see <xref target="caching.negotiated.responses"
       />), and</t>
-      <t>the presented request and stored response are free from directives
-      that would prevent its use (see <xref target="header.cache-control" />
-      and <xref target="header.pragma"/>), and</t>
+      <t>the presented request does not contain the no-cache pragma (<xref
+      target="header.pragma"/>), nor the no-cache cache directive (<xref
+      target="cache-request-directive"/>), unless the stored response is
+      successfully validated (<xref target="validation.model"/>), and</t>
+      <t>the stored response does not contain the no-cache cache directive
+      (<xref target="cache-response-directive"/>), unless it is successfully
+      validated (<xref target="validation.model"/>), and</t>
       <t>the stored response is either:
          <list style="symbols">
@@ -720 +724 @@
 </t>
 <t>
-   Additionally, clients might need to influence freshness calculation. They
-   can do this using several request cache directives, with the effect of
-   either increasing or loosening constraints on freshness. See <xref
-   target="cache-request-directive" />.
+   Additionally, clients can influence freshness calculation -- either
+   constraining it relaxing it -- by using the max-age and min-fresh
+   request cache directives. See <xref target="cache-request-directive" /> 
+   for details.
 </t>
 <t>
@@ -2928 +2932 @@
 <section title="Since draft-ietf-httpbis-p6-cache-17" anchor="changes.since.17">
 <t>
-  No changes yet.
+  Closed issues:
+  <list style="symbols">
+    <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/293"/>:
+      "Interaction of request and response Cache-Control"
+    </t>
+  </list>
 </t>
 </section>