Changeset 2214 for draft-ietf-httpbis/latest/p1-messaging.html

Timestamp:

21/03/13 09:06:23 (10 years ago)

Author:

julian.reschke@…

Message:

editorial fixes (see #441)

File:

• draft-ietf-httpbis/latest/p1-messaging.html (modified) (6 diffs)

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

@@ -449 +449 @@
   } 
   @bottom-center {
-       content: "Expires September 20, 2013"; 
+       content: "Expires September 22, 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="2013-03-19">
+      <meta name="dct.issued" scheme="ISO8601" content="2013-03-21">
       <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">March 19, 2013</td>
+               <td class="right">March 21, 2013</td>
             </tr>
             <tr>
-               <td class="left">Expires: September 20, 2013</td>
+               <td class="left">Expires: September 22, 2013</td>
                <td class="right"></td>
             </tr>
@@ -551 +551 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on September 20, 2013.</p>
+      <p>This Internet-Draft will expire on September 22, 2013.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
@@ -1006 +1006 @@
          is introduced, and that the minor number will only be incremented when changes made to the protocol have the effect of adding
          to the message semantics or implying additional capabilities of the sender. However, the minor version was not incremented
-         for the changes introduced between <a href="#RFC2068" id="rfc.xref.RFC2068.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a> and <a href="#RFC2616" id="rfc.xref.RFC2616.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, and this revision has specifically avoiding any such changes to the protocol.
+         for the changes introduced between <a href="#RFC2068" id="rfc.xref.RFC2068.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a> and <a href="#RFC2616" id="rfc.xref.RFC2616.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, and this revision has specifically avoided any such changes to the protocol.
       </p>
       <div id="rfc.iref.r.5"></div>
@@ -2836 +2836 @@
       <p id="rfc.section.A.1.2.p.4">As a result, clients are encouraged not to send the Proxy-Connection header field in any requests.</p>
       <p id="rfc.section.A.1.2.p.5">Clients are also encouraged to consider the use of Connection: keep-alive in requests carefully; while they can enable persistent
-         connections with HTTP/1.0 servers, clients using them need will need to monitor the connection for "hung" requests (which
-         indicate that the client ought stop sending the header field), and this mechanism ought not be used by clients at all when
-         a proxy is being used.
+         connections with HTTP/1.0 servers, clients using them will need to monitor the connection for "hung" requests (which indicate
+         that the client ought stop sending the header field), and this mechanism ought not be used by clients at all when a proxy
+         is being used.
       </p>
       <h3 id="rfc.section.A.1.3"><a href="#rfc.section.A.1.3">A.1.3</a>&nbsp;<a id="introduction.of.transfer-encoding" href="#introduction.of.transfer-encoding">Introduction of Transfer-Encoding</a></h3>