Changeset 1894 for draft-ietf-httpbis/latest/p1-messaging.html
- Timestamp:
- 15/09/12 08:06:47 (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r1891 r1894 449 449 } 450 450 @bottom-center { 451 content: "Expires March 1 7, 2013";451 content: "Expires March 19, 2013"; 452 452 } 453 453 @bottom-right { … … 492 492 <meta name="dct.creator" content="Reschke, J. F."> 493 493 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest"> 494 <meta name="dct.issued" scheme="ISO8601" content="2012-09-1 3">494 <meta name="dct.issued" scheme="ISO8601" content="2012-09-15"> 495 495 <meta name="dct.replaces" content="urn:ietf:rfc:2145"> 496 496 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> … … 524 524 </tr> 525 525 <tr> 526 <td class="left">Expires: March 1 7, 2013</td>526 <td class="left">Expires: March 19, 2013</td> 527 527 <td class="right">greenbytes</td> 528 528 </tr> 529 529 <tr> 530 530 <td class="left"></td> 531 <td class="right">September 1 3, 2012</td>531 <td class="right">September 15, 2012</td> 532 532 </tr> 533 533 </tbody> … … 556 556 in progress”. 557 557 </p> 558 <p>This Internet-Draft will expire on March 1 7, 2013.</p>558 <p>This Internet-Draft will expire on March 19, 2013.</p> 559 559 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 560 560 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1360 1360 </p> 1361 1361 <div id="rfc.iref.t.4"></div> 1362 <div id="rfc.iref.h.6"></div>1363 1362 <h3 id="rfc.section.3.3.1"><a href="#rfc.section.3.3.1">3.3.1</a> <a id="header.transfer-encoding" href="#header.transfer-encoding">Transfer-Encoding</a></h3> 1364 1363 <p id="rfc.section.3.3.1.p.1">When one or more transfer codings are applied to a payload body in order to form the message body, a Transfer-Encoding header … … 1396 1395 </p> 1397 1396 <div id="rfc.iref.c.6"></div> 1398 <div id="rfc.iref.h.7"></div>1399 1397 <h3 id="rfc.section.3.3.2"><a href="#rfc.section.3.3.2">3.3.2</a> <a id="header.content-length" href="#header.content-length">Content-Length</a></h3> 1400 1398 <p id="rfc.section.3.3.2.p.1">When a message does not have a <a href="#header.transfer-encoding" class="smpl">Transfer-Encoding</a> header field and the payload body length can be determined prior to being transferred, a Content-Length header field <em class="bcp14">SHOULD</em> be sent to indicate the length of the payload body that is either present as the message body, for requests and non-HEAD responses … … 1570 1568 </p> 1571 1569 <div id="rfc.iref.t.5"></div> 1572 <div id="rfc.iref.h.8"></div>1573 1570 <h3 id="rfc.section.4.1.1"><a href="#rfc.section.4.1.1">4.1.1</a> <a id="header.trailer" href="#header.trailer">Trailer</a></h3> 1574 1571 <p id="rfc.section.4.1.1.p.1">A trailer allows the sender to include additional fields at the end of a chunked message in order to supply metadata that … … 1640 1637 </p> 1641 1638 <div id="rfc.iref.t.6"></div> 1642 <div id="rfc.iref.h.9"></div>1643 1639 <h2 id="rfc.section.4.3"><a href="#rfc.section.4.3">4.3</a> <a id="header.te" href="#header.te">TE</a></h2> 1644 1640 <p id="rfc.section.4.3.p.1">The "TE" header field in a request indicates what transfer-codings, besides "chunked", the client is willing to accept in … … 1763 1759 Host: www.example.org:8001 1764 1760 </pre> <p>after connecting to port 8001 of host "www.example.org".</p> 1765 <div id="rfc.iref.h.10"></div> 1766 <div id="rfc.iref.h.11"></div> 1761 <div id="rfc.iref.h.6"></div> 1767 1762 <h2 id="rfc.section.5.4"><a href="#rfc.section.5.4">5.4</a> <a id="header.host" href="#header.host">Host</a></h2> 1768 1763 <p id="rfc.section.5.4.p.1">The "Host" header field in a request provides the host and port information from the target URI, enabling the origin server … … 1840 1835 </p> 1841 1836 <div id="rfc.iref.v.1"></div> 1842 <div id="rfc.iref.h.12"></div>1843 1837 <h2 id="rfc.section.5.7"><a href="#rfc.section.5.7">5.7</a> <a id="header.via" href="#header.via">Via</a></h2> 1844 1838 <p id="rfc.section.5.7.p.1">The "Via" header field <em class="bcp14">MUST</em> be sent by a proxy or gateway in forwarded messages to indicate the intermediate protocols and recipients between the user … … 1949 1943 </p> 1950 1944 <div id="rfc.iref.c.13"></div> 1951 <div id="rfc.iref.h.13"></div>1952 1945 <div id="rfc.iref.c.14"></div> 1953 1946 <h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a> <a id="header.connection" href="#header.connection">Connection</a></h2> … … 2119 2112 <p id="rfc.section.6.2.5.p.8">It is unknown whether the reset problem is exclusive to TCP or might also be found in other transport connection protocols.</p> 2120 2113 <div id="rfc.iref.u.5"></div> 2121 <div id="rfc.iref.h.14"></div>2122 2114 <h2 id="rfc.section.6.3"><a href="#rfc.section.6.3">6.3</a> <a id="header.upgrade" href="#header.upgrade">Upgrade</a></h2> 2123 2115 <p id="rfc.section.6.3.p.1">The "Upgrade" header field is intended to provide a simple mechanism for transitioning from HTTP/1.1 to some other protocol … … 3608 3600 <li><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul> 3609 3601 <li>header field <a href="#rfc.iref.h.5">3</a></li> 3610 <li>Header Fields 3611 <ul>3612 <li>Connection <a href="#rfc.xref.header.connection.1">2.3</a>, <a href="#rfc.xref.header.connection.2">2.6</a>, <a href="#rfc.xref.header.connection.3">3.2</a>, <a href="#rfc.xref.header.connection.4">4.3</a>, <a href="#rfc.xref.header.connection.5">5.6</a>, <a href="#rfc.iref.h.13"><b>6.1</b></a>, <a href="#rfc.xref.header.connection.6">6.2.5</a>, <a href="#rfc.xref.header.connection.7">6.3</a>, <a href="#rfc.xref.header.connection.8">7.1</a>, <a href="#rfc.xref.header.connection.9">7.1</a>, <a href="#rfc.xref.header.connection.10">A.2</a></li>3613 <li>Content-Length <a href="#rfc.iref.h.7"><b>3.3.2</b></a>, <a href="#rfc.xref.header.content-length.1">7.1</a></li>3614 <li>Host <a href="#rfc.xref.header.host.1">5.3</a>, <a href="#rfc.iref.h.11"><b>5.4</b></a>, <a href="#rfc.xref.header.host.2">7.1</a>, <a href="#rfc.xref.header.host.3">A.1.1</a></li>3615 <li>TE <a href="#rfc.xref.header.te.1">4</a>, <a href="#rfc.xref.header.te.2">4.1.1</a>, <a href="#rfc.iref.h.9"><b>4.3</b></a>, <a href="#rfc.xref.header.te.3">7.1</a></li>3616 <li>Trailer <a href="#rfc.iref.h.8"><b>4.1.1</b></a>, <a href="#rfc.xref.header.trailer.1">7.1</a></li>3617 <li>Transfer-Encoding <a href="#rfc.xref.header.transfer-encoding.1">3.3</a>, <a href="#rfc.iref.h.6"><b>3.3.1</b></a>, <a href="#rfc.xref.header.transfer-encoding.2">4</a>, <a href="#rfc.xref.header.transfer-encoding.3">7.1</a>, <a href="#rfc.xref.header.transfer-encoding.4">A.1.3</a></li>3618 <li>Upgrade <a href="#rfc.iref.h.14"><b>6.3</b></a>, <a href="#rfc.xref.header.upgrade.1">7.1</a>, <a href="#rfc.xref.header.upgrade.2">A.2</a></li>3619 <li>Via <a href="#rfc.xref.header.via.1">2.3</a>, <a href="#rfc.iref.h.12"><b>5.7</b></a>, <a href="#rfc.xref.header.via.2">7.1</a></li>3620 </ul>3621 </li>3622 3602 <li>header section <a href="#rfc.iref.h.3">3</a></li> 3623 3603 <li>headers <a href="#rfc.iref.h.4">3</a></li> 3624 <li>Host header field <a href="#rfc.xref.header.host.1">5.3</a>, <a href="#rfc.iref.h. 10"><b>5.4</b></a>, <a href="#rfc.xref.header.host.2">7.1</a>, <a href="#rfc.xref.header.host.3">A.1.1</a></li>3604 <li>Host header field <a href="#rfc.xref.header.host.1">5.3</a>, <a href="#rfc.iref.h.6"><b>5.4</b></a>, <a href="#rfc.xref.header.host.2">7.1</a>, <a href="#rfc.xref.header.host.3">A.1.1</a></li> 3625 3605 <li>http URI scheme <a href="#rfc.iref.h.1"><b>2.7.1</b></a></li> 3626 3606 <li>https URI scheme <a href="#rfc.iref.h.2">2.7.2</a></li>
Note: See TracChangeset
for help on using the changeset viewer.