![(please configure the [header_logo] section in trac.ini)](https://www.ietf.org/images/ietflogotrans.gif)
Changeset 670 for draft-ietf-httpbis/latest/p1-messaging.html
- Timestamp:
- 07/08/09 14:18:03 (13 years ago)
- File:
-
- 1 edited
-
draft-ietf-httpbis/latest/p1-messaging.html (modified) (17 diffs)
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r664 r670 394 394 <meta name="DC.Creator" content="Reschke, J. F."> 395 395 <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest"> 396 <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-08-0 6">396 <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-08-07"> 397 397 <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616"> 398 398 <meta name="DC.Description.Abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 1 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 1 provides an overview of HTTP and its associated terminology, defines the "http" and "https" Uniform Resource Identifier (URI) schemes, defines the generic message syntax and parsing requirements for HTTP message frames, and describes general security concerns for implementations."> … … 425 425 </tr> 426 426 <tr> 427 <td class="header left">Expires: February 7, 2010</td>427 <td class="header left">Expires: February 8, 2010</td> 428 428 <td class="header right">HP</td> 429 429 </tr> … … 478 478 <tr> 479 479 <td class="header left"></td> 480 <td class="header right">August 6, 2009</td>480 <td class="header right">August 7, 2009</td> 481 481 </tr> 482 482 </table> … … 502 502 <p>The list of Internet-Draft Shadow Directories can be accessed at <<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>>. 503 503 </p> 504 <p>This Internet-Draft will expire in February 7, 2010.</p>504 <p>This Internet-Draft will expire in February 8, 2010.</p> 505 505 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 506 506 <p>Copyright © 2009 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 575 575 <li class="tocline1">2.10.2 <a href="#transfer.codings">Transfer Codings</a><ul class="toc"> 576 576 <li class="tocline1">2.10.2.1 <a href="#chunked.transfer.encoding">Chunked Transfer Coding</a></li> 577 <li class="tocline1">2.10.2.2 <a href="#transfer.coding.registry">Transfer Coding Registry</a></li> 577 578 </ul> 578 579 </li> … … 1459 1460 of message-bodies is the difficulty in determining the exact body length (<a href="#message.length" title="Message Length">Section 2.7.4</a>), or the desire to encrypt data over a shared transport. 1460 1461 </p> 1461 <p id="rfc.section.2.10.2.p.8">The Internet Assigned Numbers Authority (IANA) acts as a registry for transfer-coding value tokens. Initially, the registry 1462 contains the following tokens: "chunked" (<a href="#chunked.transfer.encoding" title="Chunked Transfer Coding">Section 2.10.2.1</a>), "gzip", "compress", and "deflate" (<a href="p3-payload.html#content.codings" title="Content Codings">Section 2.2</a> of <a href="#Part3" id="rfc.xref.Part3.7"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>). 1463 </p> 1464 <p id="rfc.section.2.10.2.p.9">New transfer-coding value tokens <em class="bcp14">SHOULD</em> be registered in the same way as new content-coding value tokens (<a href="p3-payload.html#content.codings" title="Content Codings">Section 2.2</a> of <a href="#Part3" id="rfc.xref.Part3.8"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>). 1465 </p> 1466 <p id="rfc.section.2.10.2.p.10">A server which receives an entity-body with a transfer-coding it does not understand <em class="bcp14">SHOULD</em> return 501 (Not Implemented), and close the connection. A server <em class="bcp14">MUST NOT</em> send transfer-codings to an HTTP/1.0 client. 1462 <p id="rfc.section.2.10.2.p.8">A server which receives an entity-body with a transfer-coding it does not understand <em class="bcp14">SHOULD</em> return 501 (Not Implemented), and close the connection. A server <em class="bcp14">MUST NOT</em> send transfer-codings to an HTTP/1.0 client. 1467 1463 </p> 1468 1464 <h4 id="rfc.section.2.10.2.1"><a href="#rfc.section.2.10.2.1">2.10.2.1</a> <a id="chunked.transfer.encoding" href="#chunked.transfer.encoding">Chunked Transfer Coding</a></h4> … … 1526 1522 </pre><p id="rfc.section.2.10.2.1.p.9">All HTTP/1.1 applications <em class="bcp14">MUST</em> be able to receive and decode the "chunked" transfer-coding, and <em class="bcp14">MUST</em> ignore chunk-ext extensions they do not understand. 1527 1523 </p> 1524 <h4 id="rfc.section.2.10.2.2"><a href="#rfc.section.2.10.2.2">2.10.2.2</a> <a id="transfer.coding.registry" href="#transfer.coding.registry">Transfer Coding Registry</a></h4> 1525 <p id="rfc.section.2.10.2.2.p.1">The HTTP Transfer Coding Registry defines the name space for the transfer coding names.</p> 1526 <p id="rfc.section.2.10.2.2.p.2">Registrations <em class="bcp14">MUST</em> include the following fields: 1527 </p> 1528 <ul> 1529 <li>Name</li> 1530 <li>Description</li> 1531 <li>Pointer to specification text</li> 1532 </ul> 1533 <p id="rfc.section.2.10.2.2.p.3">Values to be added to this name space require expert review and a specification (see "Expert Review" and "Specification Required" 1534 in <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a> of <a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>), and <em class="bcp14">MUST</em> conform to the purpose of transfer coding defined in this section. 1535 </p> 1536 <p id="rfc.section.2.10.2.2.p.4">The registry itself is maintained at <<a href="http://www.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http-parameters</a>>. 1537 </p> 1528 1538 <h3 id="rfc.section.2.10.3"><a href="#rfc.section.2.10.3">2.10.3</a> <a id="product.tokens" href="#product.tokens">Product Tokens</a></h3> 1529 1539 <p id="rfc.section.2.10.3.p.1">Product tokens are used to allow communicating applications to identify themselves by software name and version. Most fields … … 1539 1549 </p> 1540 1550 <h3 id="rfc.section.2.10.4"><a href="#rfc.section.2.10.4">2.10.4</a> <a id="quality.values" href="#quality.values">Quality Values</a></h3> 1541 <p id="rfc.section.2.10.4.p.1">Both transfer codings (TE request header, <a href="#header.te" id="rfc.xref.header.te.3" title="TE">Section 3.5</a>) and content negotiation (<a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 4</a> of <a href="#Part3" id="rfc.xref.Part3. 9"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) use short "floating point" numbers to indicate the relative importance ("weight") of various negotiable parameters. A weight1551 <p id="rfc.section.2.10.4.p.1">Both transfer codings (TE request header, <a href="#header.te" id="rfc.xref.header.te.3" title="TE">Section 3.5</a>) and content negotiation (<a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 4</a> of <a href="#Part3" id="rfc.xref.Part3.7"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) use short "floating point" numbers to indicate the relative importance ("weight") of various negotiable parameters. A weight 1542 1552 is normalized to a real number in the range 0 through 1, where 0 is the minimum and 1 the maximum value. If a parameter has 1543 1553 a quality value of 0, then content with this parameter is `not acceptable' for the client. HTTP/1.1 applications <em class="bcp14">MUST NOT</em> generate more than three digits after the decimal point. User configuration of these values <em class="bcp14">SHOULD</em> also be limited in this fashion. … … 2213 2223 </dl> 2214 2224 <h2 id="rfc.section.4.4"><a href="#rfc.section.4.4">4.4</a> <a id="transfer.coding.registration" href="#transfer.coding.registration">Transfer Coding Registry</a></h2> 2215 <p id="rfc.section.4.4.p.1">The registration procedure for HTTP Transfer Codings is now defined by <a href="#transfer.coding s" title="Transfer Codings">Section 2.10.2</a> of this document.2225 <p id="rfc.section.4.4.p.1">The registration procedure for HTTP Transfer Codings is now defined by <a href="#transfer.coding.registry" title="Transfer Coding Registry">Section 2.10.2.2</a> of this document. 2216 2226 </p> 2217 2227 <p id="rfc.section.4.4.p.2">The HTTP Transfer Codings Registry located at <<a href="http://www.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http-parameters</a>> should be updated with the registration below: … … 2222 2232 <thead> 2223 2233 <tr> 2224 <th> RegistryName</th>2234 <th>Name</th> 2225 2235 <th>Description</th> 2226 2236 <th>Reference</th> … … 2384 2394 <h2 id="rfc.references.2"><a href="#rfc.section.7.2" id="rfc.section.7.2">7.2</a> Informative References 2385 2395 </h2> 2386 <table summary="Informative References"> 2396 <table summary="Informative References"> 2387 2397 <tr> 2388 2398 <td class="reference"><b id="Kri2001">[Kri2001]</b></td> … … 2474 2484 <td class="reference"><b id="RFC4395">[RFC4395]</b></td> 2475 2485 <td class="top"><a title="AT&T Laboratories">Hansen, T.</a>, <a title="Qualcomm, Inc.">Hardie, T.</a>, and <a title="Adobe Systems">L. Masinter</a>, “<a href="http://tools.ietf.org/html/rfc4395">Guidelines and Registration Procedures for New URI Schemes</a>”, BCP 115, RFC 4395, February 2006. 2486 </td> 2487 </tr> 2488 <tr> 2489 <td class="reference"><b id="RFC5226">[RFC5226]</b></td> 2490 <td class="top"><a title="IBM">Narten, T.</a> and <a title="Google">H. Alvestrand</a>, “<a href="http://tools.ietf.org/html/rfc5226">Guidelines for Writing an IANA Considerations Section in RFCs</a>”, BCP 26, RFC 5226, May 2008. 2476 2491 </td> 2477 2492 </tr> … … 2521 2536 </p> 2522 2537 <p id="rfc.section.A.p.4">The character set of an entity-body <em class="bcp14">SHOULD</em> be labeled as the lowest common denominator of the character codes used within that body, with the exception that not labeling 2523 the entity is preferred over labeling the entity with the labels US-ASCII or ISO-8859-1. See <a href="#Part3" id="rfc.xref.Part3. 10"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>.2538 the entity is preferred over labeling the entity with the labels US-ASCII or ISO-8859-1. See <a href="#Part3" id="rfc.xref.Part3.8"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>. 2524 2539 </p> 2525 2540 <p id="rfc.section.A.p.5">Additional rules for requirements on parsing and encoding of dates and other potential problems with date encodings include:</p> … … 2613 2628 <p id="rfc.section.B.3.p.2">Transfer-coding and message lengths all interact in ways that required fixing exactly when chunked encoding is used (to allow 2614 2629 for transfer encoding that may not be self delimiting); it was important to straighten out exactly how message lengths are 2615 computed. (Sections <a href="#transfer.codings" title="Transfer Codings">2.10.2</a>, <a href="#message.length" title="Message Length">2.7.4</a>, <a href="#header.content-length" id="rfc.xref.header.content-length.3" title="Content-Length">3.2</a>, see also <a href="#Part3" id="rfc.xref.Part3. 11"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="#Part5" id="rfc.xref.Part5.1"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a> and <a href="#Part6" id="rfc.xref.Part6.8"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>)2630 computed. (Sections <a href="#transfer.codings" title="Transfer Codings">2.10.2</a>, <a href="#message.length" title="Message Length">2.7.4</a>, <a href="#header.content-length" id="rfc.xref.header.content-length.3" title="Content-Length">3.2</a>, see also <a href="#Part3" id="rfc.xref.Part3.9"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="#Part5" id="rfc.xref.Part5.1"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a> and <a href="#Part6" id="rfc.xref.Part6.8"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) 2616 2631 </p> 2617 2632 <p id="rfc.section.B.3.p.3">The use and interpretation of HTTP version numbers has been clarified by <a href="#RFC2145" id="rfc.xref.RFC2145.3"><cite title="Use and Interpretation of HTTP Version Numbers">[RFC2145]</cite></a>. Require proxies to upgrade requests to highest protocol version they support to deal with problems discovered in HTTP/1.0 … … 3040 3055 </li> 3041 3056 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/157">http://tools.ietf.org/wg/httpbis/trac/ticket/157</a>>: "IP addresses in URLs" 3057 </li> 3058 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/188">http://tools.ietf.org/wg/httpbis/trac/ticket/188</a>>: "pick IANA policy (RFC5226) for Transfer Coding / Content Coding" 3042 3059 </li> 3043 3060 </ul> … … 3257 3274 </ul> 3258 3275 </li> 3259 <li class="indline1"><em>Part3</em> <a class="iref" href="#rfc.xref.Part3.1">1</a>, <a class="iref" href="#rfc.xref.Part3.2">1.2.2</a>, <a class="iref" href="#rfc.xref.Part3.3">1.2.3</a>, <a class="iref" href="#rfc.xref.Part3.4">1.2.3</a>, <a class="iref" href="#rfc.xref.Part3.5">2.8</a>, <a class="iref" href="#rfc.xref.Part3.6">2.9</a>, <a class="iref" href="#rfc.xref.Part3.7">2.10.2</a>, <a class="iref" href="#rfc.xref.Part3.8">2.10.2</a>, <a class="iref" href="#rfc.xref.Part3.9">2.10.4</a>, <a class="iref" href="#Part3"><b>7.1</b></a>, <a class="iref" href="#rfc.xref.Part3.10">A</a>, <a class="iref" href="#rfc.xref.Part3.11">B.3</a><ul class="ind"> 3260 <li class="indline1"><em>Section 2.2</em> <a class="iref" href="#rfc.xref.Part3.7">2.10.2</a>, <a class="iref" href="#rfc.xref.Part3.8">2.10.2</a></li> 3276 <li class="indline1"><em>Part3</em> <a class="iref" href="#rfc.xref.Part3.1">1</a>, <a class="iref" href="#rfc.xref.Part3.2">1.2.2</a>, <a class="iref" href="#rfc.xref.Part3.3">1.2.3</a>, <a class="iref" href="#rfc.xref.Part3.4">1.2.3</a>, <a class="iref" href="#rfc.xref.Part3.5">2.8</a>, <a class="iref" href="#rfc.xref.Part3.6">2.9</a>, <a class="iref" href="#rfc.xref.Part3.7">2.10.4</a>, <a class="iref" href="#Part3"><b>7.1</b></a>, <a class="iref" href="#rfc.xref.Part3.8">A</a>, <a class="iref" href="#rfc.xref.Part3.9">B.3</a><ul class="ind"> 3261 3277 <li class="indline1"><em>Section 2.3</em> <a class="iref" href="#rfc.xref.Part3.2">1.2.2</a></li> 3262 3278 <li class="indline1"><em>Section 3.1</em> <a class="iref" href="#rfc.xref.Part3.4">1.2.3</a>, <a class="iref" href="#rfc.xref.Part3.5">2.8</a>, <a class="iref" href="#rfc.xref.Part3.6">2.9</a></li> 3263 3279 <li class="indline1"><em>Section 3.2</em> <a class="iref" href="#rfc.xref.Part3.3">1.2.3</a></li> 3264 <li class="indline1"><em>Section 4</em> <a class="iref" href="#rfc.xref.Part3. 9">2.10.4</a></li>3280 <li class="indline1"><em>Section 4</em> <a class="iref" href="#rfc.xref.Part3.7">2.10.4</a></li> 3265 3281 <li class="indline1"><em>Appendix A</em> <a class="iref" href="#rfc.xref.Part3.1">1</a></li> 3266 3282 </ul> … … 3318 3334 <li class="indline1"><em>RFC4288</em> <a class="iref" href="#rfc.xref.RFC4288.1">4.3</a>, <a class="iref" href="#RFC4288"><b>7.2</b></a></li> 3319 3335 <li class="indline1"><em>RFC4395</em> <a class="iref" href="#rfc.xref.RFC4395.1">4.2</a>, <a class="iref" href="#RFC4395"><b>7.2</b></a></li> 3336 <li class="indline1"><em>RFC5226</em> <a class="iref" href="#rfc.xref.RFC5226.1">2.10.2.2</a>, <a class="iref" href="#RFC5226"><b>7.2</b></a><ul class="ind"> 3337 <li class="indline1"><em>Section 4.1</em> <a class="iref" href="#rfc.xref.RFC5226.1">2.10.2.2</a></li> 3338 </ul> 3339 </li> 3320 3340 <li class="indline1"><em>RFC5234</em> <a class="iref" href="#rfc.xref.RFC5234.1">1.2</a>, <a class="iref" href="#rfc.xref.RFC5234.2">1.2</a>, <a class="iref" href="#rfc.xref.RFC5234.3">1.2.1</a>, <a class="iref" href="#rfc.xref.RFC5234.4">6</a>, <a class="iref" href="#RFC5234"><b>7.1</b></a><ul class="ind"> 3321 3341 <li class="indline1"><em>Appendix B.1</em> <a class="iref" href="#rfc.xref.RFC5234.2">1.2</a></li>
Note: See TracChangeset
for help on using the changeset viewer.
