Changeset 2529
- Timestamp:
- 03/01/14 15:12:58 (8 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r2528 r2529 448 448 } 449 449 @bottom-center { 450 content: "Expires July 6, 2014";450 content: "Expires July 7, 2014"; 451 451 } 452 452 @bottom-right { … … 490 490 <meta name="dct.creator" content="Reschke, J. F."> 491 491 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest"> 492 <meta name="dct.issued" scheme="ISO8601" content="2014-01-0 2">492 <meta name="dct.issued" scheme="ISO8601" content="2014-01-03"> 493 493 <meta name="dct.replaces" content="urn:ietf:rfc:2145"> 494 494 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> … … 519 519 <tr> 520 520 <td class="left">Intended status: Standards Track</td> 521 <td class="right">January 2, 2014</td>521 <td class="right">January 3, 2014</td> 522 522 </tr> 523 523 <tr> 524 <td class="left">Expires: July 6, 2014</td>524 <td class="left">Expires: July 7, 2014</td> 525 525 <td class="right"></td> 526 526 </tr> … … 551 551 in progress”. 552 552 </p> 553 <p>This Internet-Draft will expire on July 6, 2014.</p>553 <p>This Internet-Draft will expire on July 7, 2014.</p> 554 554 </div> 555 555 <div id="rfc.copyrightnotice"> … … 737 737 </li> 738 738 </ul> 739 <p id="rfc.section.1.p.2">This HTTP/1.1 specification obsoletes and moves to historic status <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2616.1">RFC 2616</cite>, its predecessor <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2068.1">RFC 2068</cite>,and <cite title="Use and Interpretation of HTTP Version Numbers" id="rfc.xref.RFC2145.1">RFC 2145</cite> (on HTTP versioning). This specification also updates the use of CONNECT to establish a tunnel, previously defined in <cite title="Upgrading to TLS Within HTTP/1.1" id="rfc.xref.RFC2817.1">RFC 2817</cite>, and defines the "https" URI scheme that was described informally in <cite title="HTTP Over TLS" id="rfc.xref.RFC2818.1">RFC 2818</cite>.739 <p id="rfc.section.1.p.2">This HTTP/1.1 specification obsoletes <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2616.1">RFC 2616</cite> and <cite title="Use and Interpretation of HTTP Version Numbers" id="rfc.xref.RFC2145.1">RFC 2145</cite> (on HTTP versioning). This specification also updates the use of CONNECT to establish a tunnel, previously defined in <cite title="Upgrading to TLS Within HTTP/1.1" id="rfc.xref.RFC2817.1">RFC 2817</cite>, and defines the "https" URI scheme that was described informally in <cite title="HTTP Over TLS" id="rfc.xref.RFC2818.1">RFC 2818</cite>. 740 740 </p> 741 741 <p id="rfc.section.1.p.3">HTTP is a generic interface protocol for information systems. It is designed to hide the details of how a service is implemented … … 1056 1056 is introduced, and that the minor number will only be incremented when changes made to the protocol have the effect of adding 1057 1057 to the message semantics or implying additional capabilities of the sender. However, the minor version was not incremented 1058 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.1058 for the changes introduced between <a href="#RFC2068" id="rfc.xref.RFC2068.1"><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. 1059 1059 </p> 1060 1060 <p id="rfc.section.2.6.p.14">When an HTTP message is received with a major version number that the recipient implements, but a higher minor version number … … 2180 2180 on a persistent connection would be misinterpreted as the next request. Likewise, a client <em class="bcp14">MUST</em> read the entire response message body if it intends to reuse the same connection for a subsequent request. 2181 2181 </p> 2182 <p id="rfc.section.6.3.p.6">A proxy server <em class="bcp14">MUST NOT</em> maintain a persistent connection with an HTTP/1.0 client (see <a href="http://tools.ietf.org/html/rfc2068#section-19.7.1">Section 19.7.1</a> of <a href="#RFC2068" id="rfc.xref.RFC2068. 3"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a> for information and discussion of the problems with the Keep-Alive header field implemented by many HTTP/1.0 clients).2182 <p id="rfc.section.6.3.p.6">A proxy server <em class="bcp14">MUST NOT</em> maintain a persistent connection with an HTTP/1.0 client (see <a href="http://tools.ietf.org/html/rfc2068#section-19.7.1">Section 19.7.1</a> of <a href="#RFC2068" id="rfc.xref.RFC2068.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a> for information and discussion of the problems with the Keep-Alive header field implemented by many HTTP/1.0 clients). 2183 2183 </p> 2184 2184 <p id="rfc.section.6.3.p.7">Clients and servers <em class="bcp14">SHOULD NOT</em> assume that a persistent connection is maintained for HTTP versions less than 1.1 unless it is explicitly signaled. See <a href="#compatibility.with.http.1.0.persistent.connections" title="Keep-Alive Connections">Appendix A.1.2</a> for more information on backward compatibility with HTTP/1.0 clients. … … 2920 2920 <div id="acks"> 2921 2921 <h1 id="rfc.section.10"><a href="#rfc.section.10">10.</a> <a href="#acks">Acknowledgments</a></h1> 2922 <p id="rfc.section.10.p.1">This edition of HTTP/1.1 builds on the many contributions that went into <a href="#RFC1945" id="rfc.xref.RFC1945.2">RFC 1945</a>, <a href="#RFC2068" id="rfc.xref.RFC2068. 4">RFC 2068</a>, <a href="#RFC2145" id="rfc.xref.RFC2145.2">RFC 2145</a>, and <a href="#RFC2616" id="rfc.xref.RFC2616.3">RFC 2616</a>, including substantial contributions made by the previous authors, editors, and working group chairs: Tim Berners-Lee, Ari2922 <p id="rfc.section.10.p.1">This edition of HTTP/1.1 builds on the many contributions that went into <a href="#RFC1945" id="rfc.xref.RFC1945.2">RFC 1945</a>, <a href="#RFC2068" id="rfc.xref.RFC2068.3">RFC 2068</a>, <a href="#RFC2145" id="rfc.xref.RFC2145.2">RFC 2145</a>, and <a href="#RFC2616" id="rfc.xref.RFC2616.3">RFC 2616</a>, including substantial contributions made by the previous authors, editors, and working group chairs: Tim Berners-Lee, Ari 2923 2923 Luotonen, Roy T. Fielding, Henrik Frystyk Nielsen, Jim Gettys, Jeffrey C. Mogul, Larry Masinter, and Paul J. Leach. Mark Nottingham 2924 2924 oversaw this effort as working group chair. … … 3204 3204 <p id="rfc.section.A.1.2.p.1">In HTTP/1.0, each connection is established by the client prior to the request and closed by the server after sending the 3205 3205 response. However, some implementations implement the explicitly negotiated ("Keep-Alive") version of persistent connections 3206 described in <a href="http://tools.ietf.org/html/rfc2068#section-19.7.1">Section 19.7.1</a> of <a href="#RFC2068" id="rfc.xref.RFC2068. 5"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>.3206 described in <a href="http://tools.ietf.org/html/rfc2068#section-19.7.1">Section 19.7.1</a> of <a href="#RFC2068" id="rfc.xref.RFC2068.4"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>. 3207 3207 </p> 3208 3208 <p id="rfc.section.A.1.2.p.2">Some clients and servers might wish to be compatible with these previous approaches to persistent connections, by explicitly … … 3447 3447 </li> 3448 3448 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/542">http://tools.ietf.org/wg/httpbis/trac/ticket/542</a>>: "improve introduction of list rule" 3449 </li> 3450 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/544">http://tools.ietf.org/wg/httpbis/trac/ticket/544</a>>: "moving 2616/2068/2145 to historic" 3449 3451 </li> 3450 3452 </ul> … … 3689 3691 </li> 3690 3692 <li><em>RFC2047</em> <a href="#rfc.xref.RFC2047.1">3.2.4</a>, <a href="#RFC2047"><b>11.2</b></a></li> 3691 <li><em>RFC2068</em> <a href="#rfc.xref.RFC2068.1"> 1</a>, <a href="#rfc.xref.RFC2068.2">2.6</a>, <a href="#rfc.xref.RFC2068.3">6.3</a>, <a href="#rfc.xref.RFC2068.4">10</a>, <a href="#RFC2068"><b>11.2</b></a>, <a href="#rfc.xref.RFC2068.5">A.1.2</a><ul>3692 <li><em>Section 19.7.1</em> <a href="#rfc.xref.RFC2068. 3">6.3</a>, <a href="#rfc.xref.RFC2068.5">A.1.2</a></li>3693 <li><em>RFC2068</em> <a href="#rfc.xref.RFC2068.1">2.6</a>, <a href="#rfc.xref.RFC2068.2">6.3</a>, <a href="#rfc.xref.RFC2068.3">10</a>, <a href="#RFC2068"><b>11.2</b></a>, <a href="#rfc.xref.RFC2068.4">A.1.2</a><ul> 3694 <li><em>Section 19.7.1</em> <a href="#rfc.xref.RFC2068.2">6.3</a>, <a href="#rfc.xref.RFC2068.4">A.1.2</a></li> 3693 3695 </ul> 3694 3696 </li> -
draft-ietf-httpbis/latest/p1-messaging.xml
r2528 r2529 158 158 </t> 159 159 <t> 160 This HTTP/1.1 specification obsoletes and moves to historic status 161 <xref target="RFC2616" x:fmt="none">RFC 2616</xref>, its predecessor 162 <xref target="RFC2068" x:fmt="none">RFC 2068</xref>, and 160 This HTTP/1.1 specification obsoletes 161 <xref target="RFC2616" x:fmt="none">RFC 2616</xref> and 163 162 <xref target="RFC2145" x:fmt="none">RFC 2145</xref> (on HTTP versioning). 164 163 This specification also updates the use of CONNECT to establish a tunnel, … … 5443 5442 "improve introduction of list rule" 5444 5443 </t> 5444 <t> 5445 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/544"/>: 5446 "moving 2616/2068/2145 to historic" 5447 </t> 5445 5448 </list> 5446 5449 </t>
Note: See TracChangeset
for help on using the changeset viewer.