Changeset 2214


Ignore:
Timestamp:
Mar 21, 2013, 2:06:23 AM (6 years ago)
Author:
julian.reschke@…
Message:

editorial fixes (see #441)

Location:
draft-ietf-httpbis/latest
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.html

    r2212 r2214  
    449449  }
    450450  @bottom-center {
    451        content: "Expires September 20, 2013";
     451       content: "Expires September 22, 2013";
    452452  }
    453453  @bottom-right {
     
    491491      <meta name="dct.creator" content="Reschke, J. F.">
    492492      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest">
    493       <meta name="dct.issued" scheme="ISO8601" content="2013-03-19">
     493      <meta name="dct.issued" scheme="ISO8601" content="2013-03-21">
    494494      <meta name="dct.replaces" content="urn:ietf:rfc:2145">
    495495      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
     
    520520            <tr>
    521521               <td class="left">Intended status: Standards Track</td>
    522                <td class="right">March 19, 2013</td>
     522               <td class="right">March 21, 2013</td>
    523523            </tr>
    524524            <tr>
    525                <td class="left">Expires: September 20, 2013</td>
     525               <td class="left">Expires: September 22, 2013</td>
    526526               <td class="right"></td>
    527527            </tr>
     
    551551         in progress”.
    552552      </p>
    553       <p>This Internet-Draft will expire on September 20, 2013.</p>
     553      <p>This Internet-Draft will expire on September 22, 2013.</p>
    554554      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    555555      <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    10061006         is introduced, and that the minor number will only be incremented when changes made to the protocol have the effect of adding
    10071007         to the message semantics or implying additional capabilities of the sender. However, the minor version was not incremented
    1008          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.
     1008         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.
    10091009      </p>
    10101010      <div id="rfc.iref.r.5"></div>
     
    28362836      <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>
    28372837      <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
    2838          connections with HTTP/1.0 servers, clients using them need will need to monitor the connection for "hung" requests (which
    2839          indicate that the client ought stop sending the header field), and this mechanism ought not be used by clients at all when
    2840          a proxy is being used.
     2838         connections with HTTP/1.0 servers, clients using them will need to monitor the connection for "hung" requests (which indicate
     2839         that the client ought stop sending the header field), and this mechanism ought not be used by clients at all when a proxy
     2840         is being used.
    28412841      </p>
    28422842      <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>
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r2212 r2214  
    765765   the minor version was not incremented for the changes introduced between
    766766   <xref target="RFC2068"/> and <xref target="RFC2616"/>, and this revision
    767    has specifically avoiding any such changes to the protocol.
     767   has specifically avoided any such changes to the protocol.
    768768</t>
    769769</section>
     
    47494749   Clients are also encouraged to consider the use of Connection: keep-alive
    47504750   in requests carefully; while they can enable persistent connections with
    4751    HTTP/1.0 servers, clients using them need will need to monitor the
     4751   HTTP/1.0 servers, clients using them will need to monitor the
    47524752   connection for "hung" requests (which indicate that the client ought stop
    47534753   sending the header field), and this mechanism ought not be used by clients
Note: See TracChangeset for help on using the changeset viewer.