Changeset 2035 for draft-ietf-httpbis/latest/p2-semantics.html
- Timestamp:
- 08/12/12 07:31:48 (9 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r2031 r2035 449 449 } 450 450 @bottom-center { 451 content: "Expires June 8, 2013";451 content: "Expires June 10, 2013"; 452 452 } 453 453 @bottom-right { … … 496 496 <meta name="dct.creator" content="Reschke, J. F."> 497 497 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 498 <meta name="dct.issued" scheme="ISO8601" content="2012-12-0 5">498 <meta name="dct.issued" scheme="ISO8601" content="2012-12-07"> 499 499 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 500 500 <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> 525 525 <td class="left">Intended status: Standards Track</td> 526 <td class="right">December 5, 2012</td>526 <td class="right">December 7, 2012</td> 527 527 </tr> 528 528 <tr> 529 <td class="left">Expires: June 8, 2013</td>529 <td class="left">Expires: June 10, 2013</td> 530 530 <td class="right"></td> 531 531 </tr> … … 555 555 in progress”. 556 556 </p> 557 <p>This Internet-Draft will expire on June 8, 2013.</p>557 <p>This Internet-Draft will expire on June 10, 2013.</p> 558 558 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 559 559 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 2393 2393 <div id="rfc.iref.71"></div> 2394 2394 <h3 id="rfc.section.7.2.2"><a href="#rfc.section.7.2.2">7.2.2</a> <a id="status.101" href="#status.101">101 Switching Protocols</a></h3> 2395 <p id="rfc.section.7.2.2.p.1">The server understands and is willing to comply with the client's request, via the <a href="p1-messaging.html#header.upgrade" class="smpl">Upgrade</a> message header field (<a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 6. 3</a> of <a href="#Part1" id="rfc.xref.Part1.22"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>), for a change in the application protocol being used on this connection. The server will switch protocols to those defined2395 <p id="rfc.section.7.2.2.p.1">The server understands and is willing to comply with the client's request, via the <a href="p1-messaging.html#header.upgrade" class="smpl">Upgrade</a> message header field (<a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 6.7</a> of <a href="#Part1" id="rfc.xref.Part1.22"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>), for a change in the application protocol being used on this connection. The server will switch protocols to those defined 2396 2396 by the response's Upgrade header field immediately after the empty line which terminates the 101 response. 2397 2397 </p> … … 2711 2711 <div id="rfc.iref.74"></div> 2712 2712 <h3 id="rfc.section.7.5.15"><a href="#rfc.section.7.5.15">7.5.15</a> <a id="status.426" href="#status.426">426 Upgrade Required</a></h3> 2713 <p id="rfc.section.7.5.15.p.1">The request can not be completed without a prior protocol upgrade. This response <em class="bcp14">MUST</em> include an <a href="p1-messaging.html#header.upgrade" class="smpl">Upgrade</a> header field (<a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 6. 3</a> of <a href="#Part1" id="rfc.xref.Part1.25"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) specifying the required protocols.2713 <p id="rfc.section.7.5.15.p.1">The request can not be completed without a prior protocol upgrade. This response <em class="bcp14">MUST</em> include an <a href="p1-messaging.html#header.upgrade" class="smpl">Upgrade</a> header field (<a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 6.7</a> of <a href="#Part1" id="rfc.xref.Part1.25"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) specifying the required protocols. 2714 2714 </p> 2715 2715 <div id="rfc.figure.u.42"></div> … … 4559 4559 <li><em>Section 5.7.1</em> <a href="#rfc.xref.Part1.17">5.3.8</a>, <a href="#rfc.xref.Part1.29">8.4.2</a>, <a href="#rfc.xref.Part1.44">C</a></li> 4560 4560 <li><em>Section 6.1</em> <a href="#rfc.xref.Part1.35">9.3.1</a></li> 4561 <li><em>Section 6. 3</em> <a href="#rfc.xref.Part1.22">7.2.2</a>, <a href="#rfc.xref.Part1.25">7.5.15</a></li>4561 <li><em>Section 6.7</em> <a href="#rfc.xref.Part1.22">7.2.2</a>, <a href="#rfc.xref.Part1.25">7.5.15</a></li> 4562 4562 <li><em>Section 7.3.1</em> <a href="#rfc.xref.Part1.18">5.3.8</a></li> 4563 4563 <li><em>Section 9</em> <a href="#rfc.xref.Part1.43">11</a></li>
Note: See TracChangeset
for help on using the changeset viewer.