Changeset 1976 for draft-ietf-httpbis

Timestamp:

06/11/12 07:47:35 (10 years ago)

Author:

julian.reschke@…

Message:

fix typo

Location:

draft-ietf-httpbis/latest

Files:

• p1-messaging.html (modified) (4 diffs)
• p2-semantics.html (modified) (4 diffs)
• p6-cache.html (modified) (6 diffs)
• p6-cache.xml (modified) (1 diff)

draft-ietf-httpbis/latest/p1-messaging.html

@@ -449 +449 @@
   } 
   @bottom-center {
-       content: "Expires May 8, 2013"; 
+       content: "Expires May 10, 2013"; 
   } 
   @bottom-right {
@@ -491 +491 @@
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2012-11-04">
+      <meta name="dct.issued" scheme="ISO8601" content="2012-11-06">
       <meta name="dct.replaces" content="urn:ietf:rfc:2145">
       <meta name="dct.replaces" content="urn:ietf:rfc:2616">
@@ -520 +520 @@
             <tr>
                <td class="left">Intended status: Standards Track</td>
-               <td class="right">November 4, 2012</td>
+               <td class="right">November 6, 2012</td>
             </tr>
             <tr>
-               <td class="left">Expires: May 8, 2013</td>
+               <td class="left">Expires: May 10, 2013</td>
                <td class="right"></td>
             </tr>
@@ -551 +551 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on May 8, 2013.</p>
+      <p>This Internet-Draft will expire on May 10, 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>

draft-ietf-httpbis/latest/p2-semantics.html

@@ -449 +449 @@
   } 
   @bottom-center {
-       content: "Expires May 9, 2013"; 
+       content: "Expires May 10, 2013"; 
   } 
   @bottom-right {
@@ -496 +496 @@
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2012-11-05">
+      <meta name="dct.issued" scheme="ISO8601" content="2012-11-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. This document defines the semantics of HTTP/1.1 messages, as expressed by request methods, request header fields, response status codes, and response header fields, along with the payload of messages (metadata and body content) and mechanisms for content negotiation.">
@@ -524 +524 @@
             <tr>
                <td class="left">Intended status: Standards Track</td>
-               <td class="right">November 5, 2012</td>
+               <td class="right">November 6, 2012</td>
             </tr>
             <tr>
-               <td class="left">Expires: May 9, 2013</td>
+               <td class="left">Expires: May 10, 2013</td>
                <td class="right"></td>
             </tr>
@@ -555 +555 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on May 9, 2013.</p>
+      <p>This Internet-Draft will expire on May 10, 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>

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

@@ -452 +452 @@
   } 
   @bottom-center {
-       content: "Expires May 8, 2013"; 
+       content: "Expires May 10, 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-04">
+      <meta name="dct.issued" scheme="ISO8601" content="2012-11-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. 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 8, 2013</td>
+               <td class="left">Expires: May 10, 2013</td>
                <td class="right">J. Reschke, Editor</td>
             </tr>
@@ -533 +533 @@
             <tr>
                <td class="left"></td>
-               <td class="right">November 4, 2012</td>
+               <td class="right">November 6, 2012</td>
             </tr>
          </tbody>
@@ -559 +559 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on May 8, 2013.</p>
+      <p>This Internet-Draft will expire on May 10, 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>
@@ -916 +916 @@
 </pre> <p id="rfc.section.4.1.p.6">The freshness_lifetime is defined in <a href="#calculating.freshness.lifetime" title="Calculating Freshness Lifetime">Section&nbsp;4.1.1</a>; the current_age is defined in <a href="#age.calculations" title="Calculating Age">Section&nbsp;4.1.3</a>.
       </p>
-      <p id="rfc.section.4.1.p.7">Additionally, clients can influence freshness calculation — either constraining it relaxing it — by using the max-age and
+      <p id="rfc.section.4.1.p.7">Additionally, clients can influence freshness calculation — either constraining or 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;7.2.1</a> for details.
       </p>

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

@@ -579 +579 @@
 <t>
    Additionally, clients can influence freshness calculation &mdash; either
-   constraining it relaxing it &mdash; by using the max-age and min-fresh
+   constraining or it relaxing it &mdash; by using the max-age and min-fresh
    request cache directives. See <xref target="cache-request-directive" /> 
    for details.