Changeset 1991 for draft-ietf-httpbis

Timestamp:

12/11/12 09:14:42 (10 years ago)

Author:

julian.reschke@…

Message:

editorial clarification

Location:

draft-ietf-httpbis/latest

Files:

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

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

@@ -452 +452 @@
   } 
   @bottom-center {
-       content: "Expires May 10, 2013"; 
+       content: "Expires May 16, 2013"; 
   } 
   @bottom-right {
@@ -498 +498 @@
       <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-11-06">
+      <meta name="dct.issued" scheme="ISO8601" content="2012-11-12">
       <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. This document defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages.">
@@ -524 +524 @@
             </tr>
             <tr>
-               <td class="left">Expires: May 10, 2013</td>
+               <td class="left">Expires: May 16, 2013</td>
                <td class="right">J. Reschke, Editor</td>
             </tr>
@@ -533 +533 @@
             <tr>
                <td class="left"></td>
-               <td class="right">November 6, 2012</td>
+               <td class="right">November 12, 2012</td>
             </tr>
          </tbody>
@@ -559 +559 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on May 10, 2013.</p>
+      <p>This Internet-Draft will expire on May 16, 2013.</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>
@@ -905 +905 @@
       </p>
       <p id="rfc.section.4.1.p.3">If an origin server wishes to force a cache to validate every request, it can assign an explicit expiration time in the past
-         to indicate that the response is already stale. Compliant caches will normally validate the cached response before reusing
+         to indicate that the response is already stale. Compliant caches will normally validate a stale cached response before reusing
          it for subsequent requests (see <a href="#serving.stale.responses" title="Serving Stale Responses">Section&nbsp;4.1.4</a>).
       </p>

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

@@ -552 +552 @@
    If an origin server wishes to force a cache to validate every request, it
    can assign an explicit expiration time in the past to indicate that the
-   response is already stale. Compliant caches will normally validate the 
+   response is already stale. Compliant caches will normally validate a stale
    cached response before reusing it for subsequent requests (see <xref
    target="serving.stale.responses" />).