Changeset 1092

Timestamp:

Nov 15, 2010, 12:20:16 AM (9 years ago)

Author:

julian.reschke@…

Message:

regen HTML for [1091]

File:

• draft-ietf-httpbis/latest/p6-cache.html (modified) (5 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-11-01">
+      <meta name="dct.issued" scheme="ISO8601" content="2010-11-15">
       <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: May 5, 2011</td>
+               <td class="left">Expires: May 19, 2011</td>
                <td class="right">J. Mogul</td>
             </tr>
@@ -489 +489 @@
             <tr>
                <td class="left"></td>
-               <td class="right">November 1, 2010</td>
+               <td class="right">November 15, 2010</td>
             </tr>
          </tbody>
@@ -515 +515 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on May 5, 2011.</p>
+      <p>This Internet-Draft will expire on May 19, 2011.</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>
@@ -996 +996 @@
       <h2 id="rfc.section.2.8"><a href="#rfc.section.2.8">2.8</a>&nbsp;<a id="combining.responses" href="#combining.responses">Combining Responses</a></h2>
       <p id="rfc.section.2.8.p.1">When a cache receives a 304 (Not Modified) response or a 206 (Partial Content) response (in this section, the "new" response"),
-         it needs to created an updated response by combining the stored response with the new one, so that the updated response can
+         it needs to create an updated response by combining the stored response with the new one, so that the updated response can
          be used to satisfy the request, and potentially update the cached response.
       </p>