Changeset 673 for draft-ietf-httpbis/latest
- Timestamp:
- 07/08/09 16:46:40 (13 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 4 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r670 r673 574 574 <li class="tocline1">2.10.1 <a href="#date.time.formats.full.date">Date/Time Formats: Full Date</a></li> 575 575 <li class="tocline1">2.10.2 <a href="#transfer.codings">Transfer Codings</a><ul class="toc"> 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> 576 <li class="tocline1">2.10.2.1 <a href="#chunked.encoding">Chunked Transfer Coding</a></li> 577 <li class="tocline1">2.10.2.2 <a href="#compression.codings">Compression Codings</a><ul class="toc"> 578 <li class="tocline1">2.10.2.2.1 <a href="#compress.coding">Compress Coding</a></li> 579 <li class="tocline1">2.10.2.2.2 <a href="#deflate.coding">Deflate Coding</a></li> 580 <li class="tocline1">2.10.2.2.3 <a href="#gzip.coding">Gzip Coding</a></li> 581 </ul> 582 </li> 583 <li class="tocline1">2.10.2.3 <a href="#transfer.coding.registry">Transfer Coding Registry</a></li> 578 584 </ul> 579 585 </li> … … 1442 1448 is a property of the message, not of the original entity. 1443 1449 </p> 1444 <div id="rfc.figure.u.45"></div><pre class="inline"><span id="rfc.iref.g.70"></span><span id="rfc.iref.g.71"></span> <a href="#transfer.codings" class="smpl">transfer-coding</a> = "chunked" / <a href="#transfer.codings" class="smpl">transfer-extension</a> 1450 <div id="rfc.figure.u.45"></div><pre class="inline"><span id="rfc.iref.g.70"></span><span id="rfc.iref.g.71"></span> <a href="#transfer.codings" class="smpl">transfer-coding</a> = "chunked" ; <a href="#chunked.encoding" title="Chunked Transfer Coding">Section 2.10.2.1</a> 1451 / "compress" ; <a href="#compress.coding" title="Compress Coding">Section 2.10.2.2.1</a> 1452 / "deflate" ; <a href="#deflate.coding" title="Deflate Coding">Section 2.10.2.2.2</a> 1453 / "gzip" ; <a href="#gzip.coding" title="Gzip Coding">Section 2.10.2.2.3</a> 1454 / <a href="#transfer.codings" class="smpl">transfer-extension</a> 1445 1455 <a href="#transfer.codings" class="smpl">transfer-extension</a> = <a href="#rule.token.separators" class="smpl">token</a> *( <a href="#rule.whitespace" class="smpl">OWS</a> ";" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#rule.parameter" class="smpl">transfer-parameter</a> ) 1446 1456 </pre><div id="rule.parameter"> … … 1462 1472 <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. 1463 1473 </p> 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> 1474 <div id="rfc.iref.c.5"></div> 1475 <div id="rfc.iref.c.6"></div> 1476 <h4 id="rfc.section.2.10.2.1"><a href="#rfc.section.2.10.2.1">2.10.2.1</a> <a id="chunked.encoding" href="#chunked.encoding">Chunked Transfer Coding</a></h4> 1465 1477 <p id="rfc.section.2.10.2.1.p.1">The chunked encoding modifies the body of a message in order to transfer it as a series of chunks, each with its own size 1466 1478 indicator, followed by an <em class="bcp14">OPTIONAL</em> trailer containing entity-header fields. This allows dynamically produced content to be transferred along with the information 1467 1479 necessary for the recipient to verify that it has received the full message. 1468 1480 </p> 1469 <div id="rfc.figure.u.47"></div><pre class="inline"><span id="rfc.iref.g.77"></span><span id="rfc.iref.g.78"></span><span id="rfc.iref.g.79"></span><span id="rfc.iref.g.80"></span><span id="rfc.iref.g.81"></span><span id="rfc.iref.g.82"></span><span id="rfc.iref.g.83"></span><span id="rfc.iref.g.84"></span><span id="rfc.iref.g.85"></span> <a href="#chunked. transfer.encoding" class="smpl">Chunked-Body</a> = *<a href="#chunked.transfer.encoding" class="smpl">chunk</a>1470 <a href="#chunked. transfer.encoding" class="smpl">last-chunk</a>1471 <a href="#chunked. transfer.encoding" class="smpl">trailer-part</a>1481 <div id="rfc.figure.u.47"></div><pre class="inline"><span id="rfc.iref.g.77"></span><span id="rfc.iref.g.78"></span><span id="rfc.iref.g.79"></span><span id="rfc.iref.g.80"></span><span id="rfc.iref.g.81"></span><span id="rfc.iref.g.82"></span><span id="rfc.iref.g.83"></span><span id="rfc.iref.g.84"></span><span id="rfc.iref.g.85"></span> <a href="#chunked.encoding" class="smpl">Chunked-Body</a> = *<a href="#chunked.encoding" class="smpl">chunk</a> 1482 <a href="#chunked.encoding" class="smpl">last-chunk</a> 1483 <a href="#chunked.encoding" class="smpl">trailer-part</a> 1472 1484 <a href="#core.rules" class="smpl">CRLF</a> 1473 1485 1474 <a href="#chunked. transfer.encoding" class="smpl">chunk</a> = <a href="#chunked.transfer.encoding" class="smpl">chunk-size</a> *WSP [ <a href="#chunked.transfer.encoding" class="smpl">chunk-ext</a> ] <a href="#core.rules" class="smpl">CRLF</a>1475 <a href="#chunked. transfer.encoding" class="smpl">chunk-data</a> <a href="#core.rules" class="smpl">CRLF</a>1476 <a href="#chunked. transfer.encoding" class="smpl">chunk-size</a> = 1*<a href="#core.rules" class="smpl">HEXDIG</a>1477 <a href="#chunked. transfer.encoding" class="smpl">last-chunk</a> = 1*("0") *WSP [ <a href="#chunked.transfer.encoding" class="smpl">chunk-ext</a> ] <a href="#core.rules" class="smpl">CRLF</a>1486 <a href="#chunked.encoding" class="smpl">chunk</a> = <a href="#chunked.encoding" class="smpl">chunk-size</a> *WSP [ <a href="#chunked.encoding" class="smpl">chunk-ext</a> ] <a href="#core.rules" class="smpl">CRLF</a> 1487 <a href="#chunked.encoding" class="smpl">chunk-data</a> <a href="#core.rules" class="smpl">CRLF</a> 1488 <a href="#chunked.encoding" class="smpl">chunk-size</a> = 1*<a href="#core.rules" class="smpl">HEXDIG</a> 1489 <a href="#chunked.encoding" class="smpl">last-chunk</a> = 1*("0") *WSP [ <a href="#chunked.encoding" class="smpl">chunk-ext</a> ] <a href="#core.rules" class="smpl">CRLF</a> 1478 1490 1479 <a href="#chunked. transfer.encoding" class="smpl">chunk-ext</a> = *( ";" *WSP <a href="#chunked.transfer.encoding" class="smpl">chunk-ext-name</a>1480 [ "=" <a href="#chunked. transfer.encoding" class="smpl">chunk-ext-val</a> ] *WSP )1481 <a href="#chunked. transfer.encoding" class="smpl">chunk-ext-name</a> = <a href="#rule.token.separators" class="smpl">token</a>1482 <a href="#chunked. transfer.encoding" class="smpl">chunk-ext-val</a> = <a href="#rule.token.separators" class="smpl">token</a> / <a href="#rule.quoted-string" class="smpl">quoted-string</a>1483 <a href="#chunked. transfer.encoding" class="smpl">chunk-data</a> = 1*<a href="#core.rules" class="smpl">OCTET</a> ; a sequence of chunk-size octets1484 <a href="#chunked. transfer.encoding" class="smpl">trailer-part</a> = *( <a href="#abnf.dependencies" class="smpl">entity-header</a> <a href="#core.rules" class="smpl">CRLF</a> )1491 <a href="#chunked.encoding" class="smpl">chunk-ext</a> = *( ";" *WSP <a href="#chunked.encoding" class="smpl">chunk-ext-name</a> 1492 [ "=" <a href="#chunked.encoding" class="smpl">chunk-ext-val</a> ] *WSP ) 1493 <a href="#chunked.encoding" class="smpl">chunk-ext-name</a> = <a href="#rule.token.separators" class="smpl">token</a> 1494 <a href="#chunked.encoding" class="smpl">chunk-ext-val</a> = <a href="#rule.token.separators" class="smpl">token</a> / <a href="#rule.quoted-string" class="smpl">quoted-string</a> 1495 <a href="#chunked.encoding" class="smpl">chunk-data</a> = 1*<a href="#core.rules" class="smpl">OCTET</a> ; a sequence of chunk-size octets 1496 <a href="#chunked.encoding" class="smpl">trailer-part</a> = *( <a href="#abnf.dependencies" class="smpl">entity-header</a> <a href="#core.rules" class="smpl">CRLF</a> ) 1485 1497 </pre><p id="rfc.section.2.10.2.1.p.3">The chunk-size field is a string of hex digits indicating the size of the chunk-data in octets. The chunked encoding is ended 1486 1498 by any chunk whose size is zero, followed by the trailer, which is terminated by an empty line. … … 1522 1534 </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. 1523 1535 </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: 1536 <h4 id="rfc.section.2.10.2.2"><a href="#rfc.section.2.10.2.2">2.10.2.2</a> <a id="compression.codings" href="#compression.codings">Compression Codings</a></h4> 1537 <p id="rfc.section.2.10.2.2.p.1">The codings defined below can be used to compress the payload of a message.</p> 1538 <div class="note"> 1539 <p> <b>Note:</b> Use of program names for the identification of encoding formats is not desirable and is discouraged for future encodings. 1540 Their use here is representative of historical practice, not good design. 1541 </p> 1542 </div> 1543 <div class="note"> 1544 <p> <b>Note:</b> For compatibility with previous implementations of HTTP, applications <em class="bcp14">SHOULD</em> consider "x-gzip" and "x-compress" to be equivalent to "gzip" and "compress" respectively. 1545 </p> 1546 </div> 1547 <div id="rfc.iref.c.7"></div> 1548 <div id="rfc.iref.c.8"></div> 1549 <h5 id="rfc.section.2.10.2.2.1"><a href="#rfc.section.2.10.2.2.1">2.10.2.2.1</a> <a id="compress.coding" href="#compress.coding">Compress Coding</a></h5> 1550 <p id="rfc.section.2.10.2.2.1.p.1">The "compress" format is produced by the common UNIX file compression program "compress". This format is an adaptive Lempel-Ziv-Welch 1551 coding (LZW). 1552 </p> 1553 <div id="rfc.iref.d.2"></div> 1554 <div id="rfc.iref.c.9"></div> 1555 <h5 id="rfc.section.2.10.2.2.2"><a href="#rfc.section.2.10.2.2.2">2.10.2.2.2</a> <a id="deflate.coding" href="#deflate.coding">Deflate Coding</a></h5> 1556 <p id="rfc.section.2.10.2.2.2.p.1">The "zlib" format is defined in <a href="#RFC1950" id="rfc.xref.RFC1950.1"><cite title="ZLIB Compressed Data Format Specification version 3.3">[RFC1950]</cite></a> in combination with the "deflate" compression mechanism described in <a href="#RFC1951" id="rfc.xref.RFC1951.1"><cite title="DEFLATE Compressed Data Format Specification version 1.3">[RFC1951]</cite></a>. 1557 </p> 1558 <div id="rfc.iref.g.86"></div> 1559 <div id="rfc.iref.c.10"></div> 1560 <h5 id="rfc.section.2.10.2.2.3"><a href="#rfc.section.2.10.2.2.3">2.10.2.2.3</a> <a id="gzip.coding" href="#gzip.coding">Gzip Coding</a></h5> 1561 <p id="rfc.section.2.10.2.2.3.p.1">The "gzip" format is produced by the file compression program "gzip" (GNU zip), as described in <a href="#RFC1952" id="rfc.xref.RFC1952.1"><cite title="GZIP file format specification version 4.3">[RFC1952]</cite></a>. This format is a Lempel-Ziv coding (LZ77) with a 32 bit CRC. 1562 </p> 1563 <h4 id="rfc.section.2.10.2.3"><a href="#rfc.section.2.10.2.3">2.10.2.3</a> <a id="transfer.coding.registry" href="#transfer.coding.registry">Transfer Coding Registry</a></h4> 1564 <p id="rfc.section.2.10.2.3.p.1">The HTTP Transfer Coding Registry defines the name space for the transfer coding names.</p> 1565 <p id="rfc.section.2.10.2.3.p.2">Registrations <em class="bcp14">MUST</em> include the following fields: 1527 1566 </p> 1528 1567 <ul> … … 1531 1570 <li>Pointer to specification text</li> 1532 1571 </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"1572 <p id="rfc.section.2.10.2.3.p.3">Values to be added to this name space require expert review and a specification (see "Expert Review" and "Specification Required" 1534 1573 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 1574 </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>>.1575 <p id="rfc.section.2.10.2.3.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 1576 </p> 1538 1577 <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> … … 1541 1580 By convention, the products are listed in order of their significance for identifying the application. 1542 1581 </p> 1543 <div id="rfc.figure.u.49"></div><pre class="inline"><span id="rfc.iref.g.8 6"></span><span id="rfc.iref.g.87"></span> <a href="#product.tokens" class="smpl">product</a> = <a href="#rule.token.separators" class="smpl">token</a> ["/" <a href="#product.tokens" class="smpl">product-version</a>]1582 <div id="rfc.figure.u.49"></div><pre class="inline"><span id="rfc.iref.g.87"></span><span id="rfc.iref.g.88"></span> <a href="#product.tokens" class="smpl">product</a> = <a href="#rule.token.separators" class="smpl">token</a> ["/" <a href="#product.tokens" class="smpl">product-version</a>] 1544 1583 <a href="#product.tokens" class="smpl">product-version</a> = <a href="#rule.token.separators" class="smpl">token</a> 1545 1584 </pre><p id="rfc.section.2.10.3.p.3">Examples:</p> … … 1553 1592 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. 1554 1593 </p> 1555 <div id="rfc.figure.u.51"></div><pre class="inline"><span id="rfc.iref.g.8 8"></span> <a href="#quality.values" class="smpl">qvalue</a> = ( "0" [ "." 0*3<a href="#core.rules" class="smpl">DIGIT</a> ] )1594 <div id="rfc.figure.u.51"></div><pre class="inline"><span id="rfc.iref.g.89"></span> <a href="#quality.values" class="smpl">qvalue</a> = ( "0" [ "." 0*3<a href="#core.rules" class="smpl">DIGIT</a> ] ) 1556 1595 / ( "1" [ "." 0*3("0") ] ) 1557 1596 </pre><div class="note"> … … 1758 1797 receives the entity. 1759 1798 </p> 1760 <div id="rfc.iref.c. 5"></div>1799 <div id="rfc.iref.c.11"></div> 1761 1800 <div id="rfc.iref.h.6"></div> 1762 1801 <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a> <a id="header.connection" href="#header.connection">Connection</a></h2> … … 1765 1804 </p> 1766 1805 <p id="rfc.section.3.1.p.2">The Connection header's value has the following grammar:</p> 1767 <div id="rfc.figure.u.52"></div><pre class="inline"><span id="rfc.iref.g. 89"></span><span id="rfc.iref.g.90"></span><span id="rfc.iref.g.91"></span> <a href="#header.connection" class="smpl">Connection</a> = "Connection" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.connection" class="smpl">Connection-v</a>1806 <div id="rfc.figure.u.52"></div><pre class="inline"><span id="rfc.iref.g.90"></span><span id="rfc.iref.g.91"></span><span id="rfc.iref.g.92"></span> <a href="#header.connection" class="smpl">Connection</a> = "Connection" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.connection" class="smpl">Connection-v</a> 1768 1807 <a href="#header.connection" class="smpl">Connection-v</a> = 1#<a href="#header.connection" class="smpl">connection-token</a> 1769 1808 <a href="#header.connection" class="smpl">connection-token</a> = <a href="#rule.token.separators" class="smpl">token</a> … … 1788 1827 connection-token. This protects against mistaken forwarding of such header fields by pre-HTTP/1.1 proxies. See <a href="#compatibility.with.http.1.0.persistent.connections" title="Compatibility with HTTP/1.0 Persistent Connections">Appendix B.2</a>. 1789 1828 </p> 1790 <div id="rfc.iref.c. 6"></div>1829 <div id="rfc.iref.c.12"></div> 1791 1830 <div id="rfc.iref.h.7"></div> 1792 1831 <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a> <a id="header.content-length" href="#header.content-length">Content-Length</a></h2> … … 1794 1833 or, in the case of the HEAD method, the size of the entity-body that would have been sent had the request been a GET. 1795 1834 </p> 1796 <div id="rfc.figure.u.54"></div><pre class="inline"><span id="rfc.iref.g.9 2"></span><span id="rfc.iref.g.93"></span> <a href="#header.content-length" class="smpl">Content-Length</a> = "Content-Length" ":" <a href="#rule.whitespace" class="smpl">OWS</a> 1*<a href="#header.content-length" class="smpl">Content-Length-v</a>1835 <div id="rfc.figure.u.54"></div><pre class="inline"><span id="rfc.iref.g.93"></span><span id="rfc.iref.g.94"></span> <a href="#header.content-length" class="smpl">Content-Length</a> = "Content-Length" ":" <a href="#rule.whitespace" class="smpl">OWS</a> 1*<a href="#header.content-length" class="smpl">Content-Length-v</a> 1797 1836 <a href="#header.content-length" class="smpl">Content-Length-v</a> = 1*<a href="#core.rules" class="smpl">DIGIT</a> 1798 1837 </pre><p id="rfc.section.3.2.p.3">An example is</p> … … 1806 1845 in <a href="#message.length" title="Message Length">Section 2.7.4</a>. 1807 1846 </p> 1808 <div id="rfc.iref.d. 2"></div>1847 <div id="rfc.iref.d.3"></div> 1809 1848 <div id="rfc.iref.h.8"></div> 1810 1849 <h2 id="rfc.section.3.3"><a href="#rfc.section.3.3">3.3</a> <a id="header.date" href="#header.date">Date</a></h2> … … 1812 1851 as orig-date in <a href="http://tools.ietf.org/html/rfc5322#section-3.6.1">Section 3.6.1</a> of <a href="#RFC5322" id="rfc.xref.RFC5322.4"><cite title="Internet Message Format">[RFC5322]</cite></a>. The field value is an HTTP-date, as described in <a href="#date.time.formats.full.date" title="Date/Time Formats: Full Date">Section 2.10.1</a>; it <em class="bcp14">MUST</em> be sent in rfc1123-date format. 1813 1852 </p> 1814 <div id="rfc.figure.u.56"></div><pre class="inline"><span id="rfc.iref.g.9 4"></span><span id="rfc.iref.g.95"></span> <a href="#header.date" class="smpl">Date</a> = "Date" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.date" class="smpl">Date-v</a>1853 <div id="rfc.figure.u.56"></div><pre class="inline"><span id="rfc.iref.g.95"></span><span id="rfc.iref.g.96"></span> <a href="#header.date" class="smpl">Date</a> = "Date" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.date" class="smpl">Date-v</a> 1815 1854 <a href="#header.date" class="smpl">Date-v</a> = <a href="#date.time.formats.full.date" class="smpl">HTTP-date</a> 1816 1855 </pre><p id="rfc.section.3.3.p.3">An example is</p> … … 1851 1890 a single IP address. 1852 1891 </p> 1853 <div id="rfc.figure.u.58"></div><pre class="inline"><span id="rfc.iref.g.9 6"></span><span id="rfc.iref.g.97"></span> <a href="#header.host" class="smpl">Host</a> = "Host" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.host" class="smpl">Host-v</a>1892 <div id="rfc.figure.u.58"></div><pre class="inline"><span id="rfc.iref.g.97"></span><span id="rfc.iref.g.98"></span> <a href="#header.host" class="smpl">Host</a> = "Host" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.host" class="smpl">Host-v</a> 1854 1893 <a href="#header.host" class="smpl">Host-v</a> = <a href="#uri" class="smpl">uri-host</a> [ ":" <a href="#uri" class="smpl">port</a> ] ; <a href="#http.uri" title="http URI scheme">Section 2.6.1</a> 1855 1894 </pre><p id="rfc.section.3.4.p.3">A "host" without any trailing port information implies the default port for the service requested (e.g., "80" for an HTTP … … 1871 1910 and/or a comma-separated list of extension transfer-coding names with optional accept parameters (as described in <a href="#transfer.codings" title="Transfer Codings">Section 2.10.2</a>). 1872 1911 </p> 1873 <div id="rfc.figure.u.60"></div><pre class="inline"><span id="rfc.iref.g.9 8"></span><span id="rfc.iref.g.99"></span><span id="rfc.iref.g.100"></span><span id="rfc.iref.g.101"></span><span id="rfc.iref.g.102"></span> <a href="#header.te" class="smpl">TE</a> = "TE" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.te" class="smpl">TE-v</a>1912 <div id="rfc.figure.u.60"></div><pre class="inline"><span id="rfc.iref.g.99"></span><span id="rfc.iref.g.100"></span><span id="rfc.iref.g.101"></span><span id="rfc.iref.g.102"></span><span id="rfc.iref.g.103"></span> <a href="#header.te" class="smpl">TE</a> = "TE" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.te" class="smpl">TE-v</a> 1874 1913 <a href="#header.te" class="smpl">TE-v</a> = #<a href="#header.te" class="smpl">t-codings</a> 1875 1914 <a href="#header.te" class="smpl">t-codings</a> = "trailers" / ( <a href="#transfer.codings" class="smpl">transfer-extension</a> [ <a href="#header.te" class="smpl">te-params</a> ] ) … … 1877 1916 <a href="#header.te" class="smpl">te-ext</a> = <a href="#rule.whitespace" class="smpl">OWS</a> ";" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#rule.token.separators" class="smpl">token</a> [ "=" ( <a href="#rule.token.separators" class="smpl">token</a> / <a href="#rule.quoted-string" class="smpl">quoted-string</a> ) ] 1878 1917 </pre><p id="rfc.section.3.5.p.3">The presence of the keyword "trailers" indicates that the client is willing to accept trailer fields in a chunked transfer-coding, 1879 as defined in <a href="#chunked. transfer.encoding" title="Chunked Transfer Coding">Section 2.10.2.1</a>. This keyword is reserved for use with transfer-coding values even though it does not itself represent a transfer-coding.1918 as defined in <a href="#chunked.encoding" title="Chunked Transfer Coding">Section 2.10.2.1</a>. This keyword is reserved for use with transfer-coding values even though it does not itself represent a transfer-coding. 1880 1919 </p> 1881 1920 <p id="rfc.section.3.5.p.4">Examples of its use are:</p> … … 1917 1956 chunked transfer-coding. 1918 1957 </p> 1919 <div id="rfc.figure.u.62"></div><pre class="inline"><span id="rfc.iref.g.10 3"></span><span id="rfc.iref.g.104"></span> <a href="#header.trailer" class="smpl">Trailer</a> = "Trailer" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.trailer" class="smpl">Trailer-v</a>1958 <div id="rfc.figure.u.62"></div><pre class="inline"><span id="rfc.iref.g.104"></span><span id="rfc.iref.g.105"></span> <a href="#header.trailer" class="smpl">Trailer</a> = "Trailer" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.trailer" class="smpl">Trailer-v</a> 1920 1959 <a href="#header.trailer" class="smpl">Trailer-v</a> = 1#<a href="#header.fields" class="smpl">field-name</a> 1921 1960 </pre><p id="rfc.section.3.6.p.3">An HTTP/1.1 message <em class="bcp14">SHOULD</em> include a Trailer header field in a message using chunked transfer-coding with a non-empty trailer. Doing so allows the recipient 1922 1961 to know which header fields to expect in the trailer. 1923 1962 </p> 1924 <p id="rfc.section.3.6.p.4">If no Trailer header field is present, the trailer <em class="bcp14">SHOULD NOT</em> include any header fields. See <a href="#chunked. transfer.encoding" title="Chunked Transfer Coding">Section 2.10.2.1</a> for restrictions on the use of trailer fields in a "chunked" transfer-coding.1963 <p id="rfc.section.3.6.p.4">If no Trailer header field is present, the trailer <em class="bcp14">SHOULD NOT</em> include any header fields. See <a href="#chunked.encoding" title="Chunked Transfer Coding">Section 2.10.2.1</a> for restrictions on the use of trailer fields in a "chunked" transfer-coding. 1925 1964 </p> 1926 1965 <p id="rfc.section.3.6.p.5">Message header fields listed in the Trailer header field <em class="bcp14">MUST NOT</em> include the following header fields: … … 1938 1977 transfer-coding is a property of the message, not of the entity. 1939 1978 </p> 1940 <div id="rfc.figure.u.63"></div><pre class="inline"><span id="rfc.iref.g.10 5"></span><span id="rfc.iref.g.106"></span> <a href="#header.transfer-encoding" class="smpl">Transfer-Encoding</a> = "Transfer-Encoding" ":" <a href="#rule.whitespace" class="smpl">OWS</a>1979 <div id="rfc.figure.u.63"></div><pre class="inline"><span id="rfc.iref.g.106"></span><span id="rfc.iref.g.107"></span> <a href="#header.transfer-encoding" class="smpl">Transfer-Encoding</a> = "Transfer-Encoding" ":" <a href="#rule.whitespace" class="smpl">OWS</a> 1941 1980 <a href="#header.transfer-encoding" class="smpl">Transfer-Encoding-v</a> 1942 1981 <a href="#header.transfer-encoding" class="smpl">Transfer-Encoding-v</a> = 1#<a href="#transfer.codings" class="smpl">transfer-coding</a> … … 1953 1992 to use if the server finds it appropriate to switch protocols. The server <em class="bcp14">MUST</em> use the Upgrade header field within a 101 (Switching Protocols) response to indicate which protocol(s) are being switched. 1954 1993 </p> 1955 <div id="rfc.figure.u.65"></div><pre class="inline"><span id="rfc.iref.g.10 7"></span><span id="rfc.iref.g.108"></span> <a href="#header.upgrade" class="smpl">Upgrade</a> = "Upgrade" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.upgrade" class="smpl">Upgrade-v</a>1994 <div id="rfc.figure.u.65"></div><pre class="inline"><span id="rfc.iref.g.108"></span><span id="rfc.iref.g.109"></span> <a href="#header.upgrade" class="smpl">Upgrade</a> = "Upgrade" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.upgrade" class="smpl">Upgrade-v</a> 1956 1995 <a href="#header.upgrade" class="smpl">Upgrade-v</a> = 1#<a href="#product.tokens" class="smpl">product</a> 1957 1996 </pre><p id="rfc.section.3.8.p.3">For example,</p> … … 1985 2024 of all senders along the request/response chain. 1986 2025 </p> 1987 <div id="rfc.figure.u.67"></div><pre class="inline"><span id="rfc.iref.g.1 09"></span><span id="rfc.iref.g.110"></span><span id="rfc.iref.g.111"></span><span id="rfc.iref.g.112"></span><span id="rfc.iref.g.113"></span><span id="rfc.iref.g.114"></span><span id="rfc.iref.g.115"></span> <a href="#header.via" class="smpl">Via</a> = "Via" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.via" class="smpl">Via-v</a>2026 <div id="rfc.figure.u.67"></div><pre class="inline"><span id="rfc.iref.g.110"></span><span id="rfc.iref.g.111"></span><span id="rfc.iref.g.112"></span><span id="rfc.iref.g.113"></span><span id="rfc.iref.g.114"></span><span id="rfc.iref.g.115"></span><span id="rfc.iref.g.116"></span> <a href="#header.via" class="smpl">Via</a> = "Via" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.via" class="smpl">Via-v</a> 1988 2027 <a href="#header.via" class="smpl">Via-v</a> = 1#( <a href="#header.via" class="smpl">received-protocol</a> <a href="#rule.whitespace" class="smpl">RWS</a> <a href="#header.via" class="smpl">received-by</a> 1989 2028 [ <a href="#rule.whitespace" class="smpl">RWS</a> <a href="#rule.comment" class="smpl">comment</a> ] ) … … 2223 2262 </dl> 2224 2263 <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> 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.2226 </p> 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:2264 <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.3</a> of this document. 2265 </p> 2266 <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 registrations below: 2228 2267 </p> 2229 2268 <div id="rfc.table.2"> … … 2239 2278 <tbody> 2240 2279 <tr> 2241 <td> Chunked</td>2280 <td>chunked</td> 2242 2281 <td>Transfer in a series of chunks</td> 2243 <td> <a href="#chunked.transfer.encoding" title="Chunked Transfer Coding">Section 2.10.2.1</a> 2282 <td> <a href="#chunked.encoding" title="Chunked Transfer Coding">Section 2.10.2.1</a> 2283 </td> 2284 </tr> 2285 <tr> 2286 <td>compress</td> 2287 <td>UNIX "compress" program method</td> 2288 <td> <a href="#compress.coding" title="Compress Coding">Section 2.10.2.2.1</a> 2289 </td> 2290 </tr> 2291 <tr> 2292 <td>deflate</td> 2293 <td>"zlib" format <a href="#RFC1950" id="rfc.xref.RFC1950.2"><cite title="ZLIB Compressed Data Format Specification version 3.3">[RFC1950]</cite></a> with "deflate" compression 2294 </td> 2295 <td> <a href="#deflate.coding" title="Deflate Coding">Section 2.10.2.2.2</a> 2296 </td> 2297 </tr> 2298 <tr> 2299 <td>gzip</td> 2300 <td>Same as GNU zip <a href="#RFC1952" id="rfc.xref.RFC1952.2"><cite title="GZIP file format specification version 4.3">[RFC1952]</cite></a></td> 2301 <td> <a href="#gzip.coding" title="Gzip Coding">Section 2.10.2.2.3</a> 2244 2302 </td> 2245 2303 </tr> … … 2347 2405 <h2 id="rfc.references.1"><a href="#rfc.section.7.1" id="rfc.section.7.1">7.1</a> Normative References 2348 2406 </h2> 2349 <table summary="Normative References"> 2407 <table summary="Normative References"> 2350 2408 <tr> 2351 2409 <td class="reference"><b id="ISO-8859-1">[ISO-8859-1]</b></td> … … 2373 2431 </tr> 2374 2432 <tr> 2433 <td class="reference"><b id="RFC1950">[RFC1950]</b></td> 2434 <td class="top"><a title="Aladdin Enterprises">Deutsch, L.P.</a> and J-L. Gailly, “<a href="http://tools.ietf.org/html/rfc1950">ZLIB Compressed Data Format Specification version 3.3</a>”, RFC 1950, May 1996.<br>RFC 1950 is an Informational RFC, thus it may be less stable than this specification. On the other hand, this downward reference 2435 was present since the publication of RFC 2068 in 1997 (<a href="#RFC2068" id="rfc.xref.RFC2068.5"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>), therefore it is unlikely to cause problems in practice. See also <a href="#BCP97" id="rfc.xref.BCP97.1"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>. 2436 </td> 2437 </tr> 2438 <tr> 2439 <td class="reference"><b id="RFC1951">[RFC1951]</b></td> 2440 <td class="top"><a title="Aladdin Enterprises">Deutsch, P.</a>, “<a href="http://tools.ietf.org/html/rfc1951">DEFLATE Compressed Data Format Specification version 1.3</a>”, RFC 1951, May 1996.<br>RFC 1951 is an Informational RFC, thus it may be less stable than this specification. On the other hand, this downward reference 2441 was present since the publication of RFC 2068 in 1997 (<a href="#RFC2068" id="rfc.xref.RFC2068.6"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>), therefore it is unlikely to cause problems in practice. See also <a href="#BCP97" id="rfc.xref.BCP97.2"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>. 2442 </td> 2443 </tr> 2444 <tr> 2445 <td class="reference"><b id="RFC1952">[RFC1952]</b></td> 2446 <td class="top"><a title="Aladdin Enterprises">Deutsch, P.</a>, <a>Gailly, J-L.</a>, <a>Adler, M.</a>, <a>Deutsch, L.P.</a>, and <a>G. Randers-Pehrson</a>, “<a href="http://tools.ietf.org/html/rfc1952">GZIP file format specification version 4.3</a>”, RFC 1952, May 1996.<br>RFC 1952 is an Informational RFC, thus it may be less stable than this specification. On the other hand, this downward reference 2447 was present since the publication of RFC 2068 in 1997 (<a href="#RFC2068" id="rfc.xref.RFC2068.7"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>), therefore it is unlikely to cause problems in practice. See also <a href="#BCP97" id="rfc.xref.BCP97.3"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>. 2448 </td> 2449 </tr> 2450 <tr> 2375 2451 <td class="reference"><b id="RFC2119">[RFC2119]</b></td> 2376 2452 <td class="top"><a title="Harvard University">Bradner, S.</a>, “<a href="http://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>”, BCP 14, RFC 2119, March 1997. … … 2394 2470 <h2 id="rfc.references.2"><a href="#rfc.section.7.2" id="rfc.section.7.2">7.2</a> Informative References 2395 2471 </h2> 2396 <table summary="Informative References"> 2472 <table summary="Informative References"> 2473 <tr> 2474 <td class="reference"><b id="BCP97">[BCP97]</b></td> 2475 <td class="top"><a>Klensin, J.</a> and <a title="MIT">S. Hartman</a>, “<a href="http://tools.ietf.org/html/rfc4897">Handling Normative References to Standards-Track Documents</a>”, BCP 97, RFC 4897, June 2007. 2476 </td> 2477 </tr> 2397 2478 <tr> 2398 2479 <td class="reference"><b id="Kri2001">[Kri2001]</b></td> … … 2580 2661 <p id="rfc.section.B.p.5">For most implementations of HTTP/1.0, each connection is established by the client prior to the request and closed by the 2581 2662 server after sending the response. Some implementations implement the Keep-Alive version of persistent connections described 2582 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>.2663 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.8"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>. 2583 2664 </p> 2584 2665 <h2 id="rfc.section.B.1"><a href="#rfc.section.B.1">B.1</a> <a id="changes.from.1.0" href="#changes.from.1.0">Changes from HTTP/1.0</a></h2> … … 2620 2701 a new keyword (Connection: close) for declaring non-persistence. See <a href="#header.connection" id="rfc.xref.header.connection.7" title="Connection">Section 3.1</a>. 2621 2702 </p> 2622 <p id="rfc.section.B.2.p.3">The original HTTP/1.0 form of persistent connections (the Connection: Keep-Alive and Keep-Alive header) is documented 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. 6"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>.2703 <p id="rfc.section.B.2.p.3">The original HTTP/1.0 form of persistent connections (the Connection: Keep-Alive and Keep-Alive header) is documented 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.9"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>. 2623 2704 </p> 2624 2705 <h2 id="rfc.section.B.3"><a href="#rfc.section.B.3">B.3</a> <a id="changes.from.rfc.2068" href="#changes.from.rfc.2068">Changes from RFC 2068</a></h2> … … 2639 2720 codings), a new header field (TE) and enabling trailer headers in the future. Transfer encoding is a major performance benefit, 2640 2721 so it was worth fixing <a href="#Nie1997" id="rfc.xref.Nie1997.2"><cite title="Network Performance Effects of HTTP/1.1, CSS1, and PNG">[Nie1997]</cite></a>. TE also solves another, obscure, downward interoperability problem that could have occurred due to interactions between 2641 authentication trailers, chunked encoding and HTTP/1.0 clients.(Section <a href="#transfer.codings" title="Transfer Codings">2.10.2</a>, <a href="#chunked. transfer.encoding" title="Chunked Transfer Coding">2.10.2.1</a>, and <a href="#header.te" id="rfc.xref.header.te.5" title="TE">3.5</a>)2722 authentication trailers, chunked encoding and HTTP/1.0 clients.(Section <a href="#transfer.codings" title="Transfer Codings">2.10.2</a>, <a href="#chunked.encoding" title="Chunked Transfer Coding">2.10.2.1</a>, and <a href="#header.te" id="rfc.xref.header.te.5" title="TE">3.5</a>) 2642 2723 </p> 2643 2724 <h2 id="rfc.section.B.4"><a href="#rfc.section.B.4">B.4</a> <a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2> … … 2653 2734 <p id="rfc.section.B.4.p.4">Remove reference to non-existant identity transfer-coding value tokens. (Sections <a href="#transfer.codings" title="Transfer Codings">2.10.2</a> and <a href="#message.length" title="Message Length">2.7.4</a>) 2654 2735 </p> 2655 <p id="rfc.section.B.4.p.5">Clarification that the chunk length does not include the count of the octets in the chunk header and trailer. (<a href="#chunked. transfer.encoding" title="Chunked Transfer Coding">Section 2.10.2.1</a>)2736 <p id="rfc.section.B.4.p.5">Clarification that the chunk length does not include the count of the octets in the chunk header and trailer. (<a href="#chunked.encoding" title="Chunked Transfer Coding">Section 2.10.2.1</a>) 2656 2737 </p> 2657 2738 <p id="rfc.section.B.4.p.6">Require that invalid whitespace around field-names be rejected. (<a href="#header.fields" title="Header Fields">Section 2.7.2</a>) … … 2665 2746 2666 2747 <a href="#abnf.dependencies" class="smpl">Cache-Control</a> = <Cache-Control, defined in [Part6], Section 3.4> 2667 <a href="#chunked. transfer.encoding" class="smpl">Chunked-Body</a> = *chunk last-chunk trailer-part CRLF2748 <a href="#chunked.encoding" class="smpl">Chunked-Body</a> = *chunk last-chunk trailer-part CRLF 2668 2749 <a href="#header.connection" class="smpl">Connection</a> = "Connection:" OWS Connection-v 2669 2750 <a href="#header.connection" class="smpl">Connection-v</a> = *( "," OWS ) connection-token *( OWS "," [ OWS … … 2727 2808 <a href="#uri" class="smpl">authority</a> = <authority, defined in [RFC3986], Section 3.2> 2728 2809 2729 <a href="#chunked. transfer.encoding" class="smpl">chunk</a> = chunk-size *WSP [ chunk-ext ] CRLF chunk-data CRLF2730 <a href="#chunked. transfer.encoding" class="smpl">chunk-data</a> = 1*OCTET2731 <a href="#chunked. transfer.encoding" class="smpl">chunk-ext</a> = *( ";" *WSP chunk-ext-name [ "=" chunk-ext-val ] *WSP )2732 <a href="#chunked. transfer.encoding" class="smpl">chunk-ext-name</a> = token2733 <a href="#chunked. transfer.encoding" class="smpl">chunk-ext-val</a> = token / quoted-string2734 <a href="#chunked. transfer.encoding" class="smpl">chunk-size</a> = 1*HEXDIG2810 <a href="#chunked.encoding" class="smpl">chunk</a> = chunk-size *WSP [ chunk-ext ] CRLF chunk-data CRLF 2811 <a href="#chunked.encoding" class="smpl">chunk-data</a> = 1*OCTET 2812 <a href="#chunked.encoding" class="smpl">chunk-ext</a> = *( ";" *WSP chunk-ext-name [ "=" chunk-ext-val ] *WSP ) 2813 <a href="#chunked.encoding" class="smpl">chunk-ext-name</a> = token 2814 <a href="#chunked.encoding" class="smpl">chunk-ext-val</a> = token / quoted-string 2815 <a href="#chunked.encoding" class="smpl">chunk-size</a> = 1*HEXDIG 2735 2816 <a href="#rule.comment" class="smpl">comment</a> = "(" *( ctext / quoted-pair / comment ) ")" 2736 2817 <a href="#header.connection" class="smpl">connection-token</a> = token … … 2774 2855 <a href="#https.uri" class="smpl">https-URI</a> = "https://" authority path-abempty [ "?" query ] 2775 2856 2776 <a href="#chunked. transfer.encoding" class="smpl">last-chunk</a> = 1*"0" *WSP [ chunk-ext ] CRLF2857 <a href="#chunked.encoding" class="smpl">last-chunk</a> = 1*"0" *WSP [ chunk-ext ] CRLF 2777 2858 2778 2859 <a href="#message.body" class="smpl">message-body</a> = entity-body / … … 2835 2916 <a href="#preferred.date.format" class="smpl">time-of-day</a> = hour ":" minute ":" second 2836 2917 <a href="#rule.token.separators" class="smpl">token</a> = 1*tchar 2837 <a href="#chunked. transfer.encoding" class="smpl">trailer-part</a> = *( entity-header CRLF )2918 <a href="#chunked.encoding" class="smpl">trailer-part</a> = *( entity-header CRLF ) 2838 2919 <a href="#transfer.codings" class="smpl">transfer-coding</a> = "chunked" / transfer-extension 2839 2920 <a href="#transfer.codings" class="smpl">transfer-extension</a> = token *( OWS ";" OWS transfer-parameter ) … … 3058 3139 <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" 3059 3140 </li> 3141 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/189">http://tools.ietf.org/wg/httpbis/trac/ticket/189</a>>: "move definitions of gzip/deflate/compress to part 1" 3142 </li> 3060 3143 </ul> 3061 3144 <p id="rfc.section.D.9.p.2">Partly resolved issues: </p> … … 3065 3148 </ul> 3066 3149 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> 3067 <p class="noprint"><a href="#rfc.index.A">A</a> <a href="#rfc.index. C">C</a> <a href="#rfc.index.D">D</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.K">K</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.N">N</a> <a href="#rfc.index.O">O</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> <a href="#rfc.index.T">T</a> <a href="#rfc.index.U">U</a> <a href="#rfc.index.V">V</a>3150 <p class="noprint"><a href="#rfc.index.A">A</a> <a href="#rfc.index.B">B</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.D">D</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.K">K</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.N">N</a> <a href="#rfc.index.O">O</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> <a href="#rfc.index.T">T</a> <a href="#rfc.index.U">U</a> <a href="#rfc.index.V">V</a> 3068 3151 </p> 3069 3152 <div class="print2col"> … … 3073 3156 </ul> 3074 3157 </li> 3158 <li class="indline0"><a id="rfc.index.B" href="#rfc.index.B"><b>B</b></a><ul class="ind"> 3159 <li class="indline1"><em>BCP97</em> <a class="iref" href="#rfc.xref.BCP97.1">7.1</a>, <a class="iref" href="#rfc.xref.BCP97.2">7.1</a>, <a class="iref" href="#rfc.xref.BCP97.3">7.1</a>, <a class="iref" href="#BCP97"><b>7.2</b></a></li> 3160 </ul> 3161 </li> 3075 3162 <li class="indline0"><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul class="ind"> 3076 3163 <li class="indline1">cache <a class="iref" href="#rfc.iref.c.3">2.3</a></li> 3077 3164 <li class="indline1">cacheable <a class="iref" href="#rfc.iref.c.4">2.3</a></li> 3165 <li class="indline1">chunked (Coding Format) <a class="iref" href="#rfc.iref.c.5">2.10.2.1</a></li> 3078 3166 <li class="indline1">client <a class="iref" href="#rfc.iref.c.1">2.1</a></li> 3167 <li class="indline1">Coding Format 3168 <ul class="ind"> 3169 <li class="indline1">chunked <a class="iref" href="#rfc.iref.c.6">2.10.2.1</a></li> 3170 <li class="indline1">compress <a class="iref" href="#rfc.iref.c.8">2.10.2.2.1</a></li> 3171 <li class="indline1">deflate <a class="iref" href="#rfc.iref.c.9">2.10.2.2.2</a></li> 3172 <li class="indline1">gzip <a class="iref" href="#rfc.iref.c.10">2.10.2.2.3</a></li> 3173 </ul> 3174 </li> 3175 <li class="indline1">compress (Coding Format) <a class="iref" href="#rfc.iref.c.7">2.10.2.2.1</a></li> 3079 3176 <li class="indline1">connection <a class="iref" href="#rfc.iref.c.2">2.1</a></li> 3080 <li class="indline1">Connection header <a class="iref" href="#rfc.xref.header.connection.1">2.7.5</a>, <a class="iref" href="#rfc.xref.header.connection.2">2.11.1.2</a>, <a class="iref" href="#rfc.xref.header.connection.3">2.11.1.3</a>, <a class="iref" href="#rfc.iref.c. 5"><b>3.1</b></a>, <a class="iref" href="#rfc.xref.header.connection.4">3.5</a>, <a class="iref" href="#rfc.xref.header.connection.5">3.8</a>, <a class="iref" href="#rfc.xref.header.connection.6">4.1</a>, <a class="iref" href="#rfc.xref.header.connection.7">B.2</a>, <a class="iref" href="#rfc.xref.header.connection.8">B.4</a></li>3081 <li class="indline1">Content-Length header <a class="iref" href="#rfc.xref.header.content-length.1">2.7.4</a>, <a class="iref" href="#rfc.iref.c. 6"><b>3.2</b></a>, <a class="iref" href="#rfc.xref.header.content-length.2">4.1</a>, <a class="iref" href="#rfc.xref.header.content-length.3">B.3</a></li>3177 <li class="indline1">Connection header <a class="iref" href="#rfc.xref.header.connection.1">2.7.5</a>, <a class="iref" href="#rfc.xref.header.connection.2">2.11.1.2</a>, <a class="iref" href="#rfc.xref.header.connection.3">2.11.1.3</a>, <a class="iref" href="#rfc.iref.c.11"><b>3.1</b></a>, <a class="iref" href="#rfc.xref.header.connection.4">3.5</a>, <a class="iref" href="#rfc.xref.header.connection.5">3.8</a>, <a class="iref" href="#rfc.xref.header.connection.6">4.1</a>, <a class="iref" href="#rfc.xref.header.connection.7">B.2</a>, <a class="iref" href="#rfc.xref.header.connection.8">B.4</a></li> 3178 <li class="indline1">Content-Length header <a class="iref" href="#rfc.xref.header.content-length.1">2.7.4</a>, <a class="iref" href="#rfc.iref.c.12"><b>3.2</b></a>, <a class="iref" href="#rfc.xref.header.content-length.2">4.1</a>, <a class="iref" href="#rfc.xref.header.content-length.3">B.3</a></li> 3082 3179 </ul> 3083 3180 </li> 3084 3181 <li class="indline0"><a id="rfc.index.D" href="#rfc.index.D"><b>D</b></a><ul class="ind"> 3085 <li class="indline1">Date header <a class="iref" href="#rfc.xref.header.date.1">2.7.5</a>, <a class="iref" href="#rfc.iref.d.2"><b>3.3</b></a>, <a class="iref" href="#rfc.xref.header.date.2">4.1</a></li> 3182 <li class="indline1">Date header <a class="iref" href="#rfc.xref.header.date.1">2.7.5</a>, <a class="iref" href="#rfc.iref.d.3"><b>3.3</b></a>, <a class="iref" href="#rfc.xref.header.date.2">4.1</a></li> 3183 <li class="indline1">deflate (Coding Format) <a class="iref" href="#rfc.iref.d.2">2.10.2.2.2</a></li> 3086 3184 <li class="indline1">downstream <a class="iref" href="#rfc.iref.d.1">2.2</a></li> 3087 3185 </ul> … … 3105 3203 <li class="indline1"><tt>Chunked-Body</tt> <a class="iref" href="#rfc.iref.g.77"><b>2.10.2.1</b></a></li> 3106 3204 <li class="indline1"><tt>comment</tt> <a class="iref" href="#rfc.iref.g.40"><b>2.7.2</b></a></li> 3107 <li class="indline1"><tt>Connection</tt> <a class="iref" href="#rfc.iref.g. 89"><b>3.1</b></a></li>3108 <li class="indline1"><tt>connection-token</tt> <a class="iref" href="#rfc.iref.g.9 1"><b>3.1</b></a></li>3109 <li class="indline1"><tt>Connection-v</tt> <a class="iref" href="#rfc.iref.g.9 0"><b>3.1</b></a></li>3110 <li class="indline1"><tt>Content-Length</tt> <a class="iref" href="#rfc.iref.g.9 2"><b>3.2</b></a></li>3111 <li class="indline1"><tt>Content-Length-v</tt> <a class="iref" href="#rfc.iref.g.9 3"><b>3.2</b></a></li>3205 <li class="indline1"><tt>Connection</tt> <a class="iref" href="#rfc.iref.g.90"><b>3.1</b></a></li> 3206 <li class="indline1"><tt>connection-token</tt> <a class="iref" href="#rfc.iref.g.92"><b>3.1</b></a></li> 3207 <li class="indline1"><tt>Connection-v</tt> <a class="iref" href="#rfc.iref.g.91"><b>3.1</b></a></li> 3208 <li class="indline1"><tt>Content-Length</tt> <a class="iref" href="#rfc.iref.g.93"><b>3.2</b></a></li> 3209 <li class="indline1"><tt>Content-Length-v</tt> <a class="iref" href="#rfc.iref.g.94"><b>3.2</b></a></li> 3112 3210 <li class="indline1">CR <a class="iref" href="#rfc.iref.g.2"><b>1.2</b></a></li> 3113 3211 <li class="indline1">CRLF <a class="iref" href="#rfc.iref.g.3"><b>1.2</b></a></li> 3114 3212 <li class="indline1"><tt>ctext</tt> <a class="iref" href="#rfc.iref.g.41"><b>2.7.2</b></a></li> 3115 3213 <li class="indline1">CTL <a class="iref" href="#rfc.iref.g.4"><b>1.2</b></a></li> 3116 <li class="indline1"><tt>Date</tt> <a class="iref" href="#rfc.iref.g.9 4"><b>3.3</b></a></li>3117 <li class="indline1"><tt>Date-v</tt> <a class="iref" href="#rfc.iref.g.9 5"><b>3.3</b></a></li>3214 <li class="indline1"><tt>Date</tt> <a class="iref" href="#rfc.iref.g.95"><b>3.3</b></a></li> 3215 <li class="indline1"><tt>Date-v</tt> <a class="iref" href="#rfc.iref.g.96"><b>3.3</b></a></li> 3118 3216 <li class="indline1"><tt>date1</tt> <a class="iref" href="#rfc.iref.g.56"><b>2.10.1</b></a></li> 3119 3217 <li class="indline1"><tt>date2</tt> <a class="iref" href="#rfc.iref.g.75"><b>2.10.2</b></a></li> … … 3133 3231 <li class="indline1"><tt>header-field</tt> <a class="iref" href="#rfc.iref.g.36"><b>2.7.2</b></a></li> 3134 3232 <li class="indline1">HEXDIG <a class="iref" href="#rfc.iref.g.7"><b>1.2</b></a></li> 3135 <li class="indline1"><tt>Host</tt> <a class="iref" href="#rfc.iref.g.9 6"><b>3.4</b></a></li>3136 <li class="indline1"><tt>Host-v</tt> <a class="iref" href="#rfc.iref.g.9 7"><b>3.4</b></a></li>3233 <li class="indline1"><tt>Host</tt> <a class="iref" href="#rfc.iref.g.97"><b>3.4</b></a></li> 3234 <li class="indline1"><tt>Host-v</tt> <a class="iref" href="#rfc.iref.g.98"><b>3.4</b></a></li> 3137 3235 <li class="indline1"><tt>hour</tt> <a class="iref" href="#rfc.iref.g.58"><b>2.10.1</b></a></li> 3138 3236 <li class="indline1"><tt>HTTP-date</tt> <a class="iref" href="#rfc.iref.g.54"><b>2.10.1</b></a></li> … … 3154 3252 <li class="indline1"><tt>path-absolute</tt> <a class="iref" href="#rfc.iref.g.29"><b>2.6</b></a></li> 3155 3253 <li class="indline1"><tt>port</tt> <a class="iref" href="#rfc.iref.g.30"><b>2.6</b></a></li> 3156 <li class="indline1"><tt>product</tt> <a class="iref" href="#rfc.iref.g.8 6"><b>2.10.3</b></a></li>3157 <li class="indline1"><tt>product-version</tt> <a class="iref" href="#rfc.iref.g.8 7"><b>2.10.3</b></a></li>3158 <li class="indline1"><tt>protocol-name</tt> <a class="iref" href="#rfc.iref.g.11 2"><b>3.9</b></a></li>3159 <li class="indline1"><tt>protocol-version</tt> <a class="iref" href="#rfc.iref.g.11 3"><b>3.9</b></a></li>3160 <li class="indline1"><tt>pseudonym</tt> <a class="iref" href="#rfc.iref.g.11 5"><b>3.9</b></a></li>3254 <li class="indline1"><tt>product</tt> <a class="iref" href="#rfc.iref.g.87"><b>2.10.3</b></a></li> 3255 <li class="indline1"><tt>product-version</tt> <a class="iref" href="#rfc.iref.g.88"><b>2.10.3</b></a></li> 3256 <li class="indline1"><tt>protocol-name</tt> <a class="iref" href="#rfc.iref.g.113"><b>3.9</b></a></li> 3257 <li class="indline1"><tt>protocol-version</tt> <a class="iref" href="#rfc.iref.g.114"><b>3.9</b></a></li> 3258 <li class="indline1"><tt>pseudonym</tt> <a class="iref" href="#rfc.iref.g.116"><b>3.9</b></a></li> 3161 3259 <li class="indline1"><tt>qdtext</tt> <a class="iref" href="#rfc.iref.g.19"><b>1.2.2</b></a></li> 3162 3260 <li class="indline1"><tt>query</tt> <a class="iref" href="#rfc.iref.g.31"><b>2.6</b></a></li> … … 3164 3262 <li class="indline1"><tt>quoted-string</tt> <a class="iref" href="#rfc.iref.g.18"><b>1.2.2</b></a></li> 3165 3263 <li class="indline1"><tt>quoted-text</tt> <a class="iref" href="#rfc.iref.g.21"><b>1.2.2</b></a></li> 3166 <li class="indline1"><tt>qvalue</tt> <a class="iref" href="#rfc.iref.g.8 8"><b>2.10.4</b></a></li>3264 <li class="indline1"><tt>qvalue</tt> <a class="iref" href="#rfc.iref.g.89"><b>2.10.4</b></a></li> 3167 3265 <li class="indline1"><tt>Reason-Phrase</tt> <a class="iref" href="#rfc.iref.g.53"><b>2.9.1.1</b></a></li> 3168 <li class="indline1"><tt>received-by</tt> <a class="iref" href="#rfc.iref.g.11 4"><b>3.9</b></a></li>3169 <li class="indline1"><tt>received-protocol</tt> <a class="iref" href="#rfc.iref.g.11 1"><b>3.9</b></a></li>3266 <li class="indline1"><tt>received-by</tt> <a class="iref" href="#rfc.iref.g.115"><b>3.9</b></a></li> 3267 <li class="indline1"><tt>received-protocol</tt> <a class="iref" href="#rfc.iref.g.112"><b>3.9</b></a></li> 3170 3268 <li class="indline1"><tt>Request</tt> <a class="iref" href="#rfc.iref.g.44"><b>2.8</b></a></li> 3171 3269 <li class="indline1"><tt>Request-Line</tt> <a class="iref" href="#rfc.iref.g.45"><b>2.8.1</b></a></li> … … 3179 3277 <li class="indline1"><tt>Status-Code</tt> <a class="iref" href="#rfc.iref.g.51"><b>2.9.1.1</b></a></li> 3180 3278 <li class="indline1"><tt>Status-Line</tt> <a class="iref" href="#rfc.iref.g.50"><b>2.9.1</b></a></li> 3181 <li class="indline1"><tt>t-codings</tt> <a class="iref" href="#rfc.iref.g.10 0"><b>3.5</b></a></li>3279 <li class="indline1"><tt>t-codings</tt> <a class="iref" href="#rfc.iref.g.101"><b>3.5</b></a></li> 3182 3280 <li class="indline1"><tt>tchar</tt> <a class="iref" href="#rfc.iref.g.17"><b>1.2.2</b></a></li> 3183 <li class="indline1"><tt>TE</tt> <a class="iref" href="#rfc.iref.g.9 8"><b>3.5</b></a></li>3184 <li class="indline1"><tt>te-ext</tt> <a class="iref" href="#rfc.iref.g.10 2"><b>3.5</b></a></li>3185 <li class="indline1"><tt>te-params</tt> <a class="iref" href="#rfc.iref.g.10 1"><b>3.5</b></a></li>3186 <li class="indline1"><tt>TE-v</tt> <a class="iref" href="#rfc.iref.g. 99"><b>3.5</b></a></li>3281 <li class="indline1"><tt>TE</tt> <a class="iref" href="#rfc.iref.g.99"><b>3.5</b></a></li> 3282 <li class="indline1"><tt>te-ext</tt> <a class="iref" href="#rfc.iref.g.103"><b>3.5</b></a></li> 3283 <li class="indline1"><tt>te-params</tt> <a class="iref" href="#rfc.iref.g.102"><b>3.5</b></a></li> 3284 <li class="indline1"><tt>TE-v</tt> <a class="iref" href="#rfc.iref.g.100"><b>3.5</b></a></li> 3187 3285 <li class="indline1"><tt>time-of-day</tt> <a class="iref" href="#rfc.iref.g.57"><b>2.10.1</b></a></li> 3188 3286 <li class="indline1"><tt>token</tt> <a class="iref" href="#rfc.iref.g.16"><b>1.2.2</b></a></li> 3189 <li class="indline1"><tt>Trailer</tt> <a class="iref" href="#rfc.iref.g.10 3"><b>3.6</b></a></li>3287 <li class="indline1"><tt>Trailer</tt> <a class="iref" href="#rfc.iref.g.104"><b>3.6</b></a></li> 3190 3288 <li class="indline1"><tt>trailer-part</tt> <a class="iref" href="#rfc.iref.g.85"><b>2.10.2.1</b></a></li> 3191 <li class="indline1"><tt>Trailer-v</tt> <a class="iref" href="#rfc.iref.g.10 4"><b>3.6</b></a></li>3289 <li class="indline1"><tt>Trailer-v</tt> <a class="iref" href="#rfc.iref.g.105"><b>3.6</b></a></li> 3192 3290 <li class="indline1"><tt>transfer-coding</tt> <a class="iref" href="#rfc.iref.g.70"><b>2.10.2</b></a></li> 3193 <li class="indline1"><tt>Transfer-Encoding</tt> <a class="iref" href="#rfc.iref.g.10 5"><b>3.7</b></a></li>3194 <li class="indline1"><tt>Transfer-Encoding-v</tt> <a class="iref" href="#rfc.iref.g.10 6"><b>3.7</b></a></li>3291 <li class="indline1"><tt>Transfer-Encoding</tt> <a class="iref" href="#rfc.iref.g.106"><b>3.7</b></a></li> 3292 <li class="indline1"><tt>Transfer-Encoding-v</tt> <a class="iref" href="#rfc.iref.g.107"><b>3.7</b></a></li> 3195 3293 <li class="indline1"><tt>transfer-extension</tt> <a class="iref" href="#rfc.iref.g.71"><b>2.10.2</b></a></li> 3196 3294 <li class="indline1"><tt>transfer-parameter</tt> <a class="iref" href="#rfc.iref.g.72"><b>2.10.2</b></a></li> 3197 <li class="indline1"><tt>Upgrade</tt> <a class="iref" href="#rfc.iref.g.10 7"><b>3.8</b></a></li>3198 <li class="indline1"><tt>Upgrade-v</tt> <a class="iref" href="#rfc.iref.g.10 8"><b>3.8</b></a></li>3295 <li class="indline1"><tt>Upgrade</tt> <a class="iref" href="#rfc.iref.g.108"><b>3.8</b></a></li> 3296 <li class="indline1"><tt>Upgrade-v</tt> <a class="iref" href="#rfc.iref.g.109"><b>3.8</b></a></li> 3199 3297 <li class="indline1"><tt>uri-host</tt> <a class="iref" href="#rfc.iref.g.32"><b>2.6</b></a></li> 3200 3298 <li class="indline1"><tt>URI-reference</tt> <a class="iref" href="#rfc.iref.g.26"><b>2.6</b></a></li> 3201 3299 <li class="indline1"><tt>value</tt> <a class="iref" href="#rfc.iref.g.74"><b>2.10.2</b></a></li> 3202 3300 <li class="indline1">VCHAR <a class="iref" href="#rfc.iref.g.11"><b>1.2</b></a></li> 3203 <li class="indline1"><tt>Via</tt> <a class="iref" href="#rfc.iref.g.1 09"><b>3.9</b></a></li>3204 <li class="indline1"><tt>Via-v</tt> <a class="iref" href="#rfc.iref.g.11 0"><b>3.9</b></a></li>3301 <li class="indline1"><tt>Via</tt> <a class="iref" href="#rfc.iref.g.110"><b>3.9</b></a></li> 3302 <li class="indline1"><tt>Via-v</tt> <a class="iref" href="#rfc.iref.g.111"><b>3.9</b></a></li> 3205 3303 <li class="indline1">WSP <a class="iref" href="#rfc.iref.g.12"><b>1.2</b></a></li> 3206 3304 <li class="indline1"><tt>year</tt> <a class="iref" href="#rfc.iref.g.65"><b>2.10.1</b></a></li> 3207 3305 </ul> 3208 3306 </li> 3307 <li class="indline1">gzip (Coding Format) <a class="iref" href="#rfc.iref.g.86">2.10.2.2.3</a></li> 3209 3308 </ul> 3210 3309 </li> … … 3302 3401 <li class="indline1"><em>RFC1900</em> <a class="iref" href="#rfc.xref.RFC1900.1">5.4</a>, <a class="iref" href="#RFC1900"><b>7.2</b></a></li> 3303 3402 <li class="indline1"><em>RFC1945</em> <a class="iref" href="#RFC1945"><b>7.2</b></a>, <a class="iref" href="#rfc.xref.RFC1945.1">B</a></li> 3403 <li class="indline1"><em>RFC1950</em> <a class="iref" href="#rfc.xref.RFC1950.1">2.10.2.2.2</a>, <a class="iref" href="#rfc.xref.RFC1950.2">4.4</a>, <a class="iref" href="#RFC1950"><b>7.1</b></a></li> 3404 <li class="indline1"><em>RFC1951</em> <a class="iref" href="#rfc.xref.RFC1951.1">2.10.2.2.2</a>, <a class="iref" href="#RFC1951"><b>7.1</b></a></li> 3405 <li class="indline1"><em>RFC1952</em> <a class="iref" href="#rfc.xref.RFC1952.1">2.10.2.2.3</a>, <a class="iref" href="#rfc.xref.RFC1952.2">4.4</a>, <a class="iref" href="#RFC1952"><b>7.1</b></a></li> 3304 3406 <li class="indline1"><em>RFC2045</em> <a class="iref" href="#rfc.xref.RFC2045.1">1</a>, <a class="iref" href="#rfc.xref.RFC2045.2">2.10.2</a>, <a class="iref" href="#rfc.xref.RFC2045.3">6</a>, <a class="iref" href="#RFC2045"><b>7.2</b></a><ul class="ind"> 3305 3407 <li class="indline1"><em>Section 6</em> <a class="iref" href="#rfc.xref.RFC2045.2">2.10.2</a></li> … … 3307 3409 </li> 3308 3410 <li class="indline1"><em>RFC2047</em> <a class="iref" href="#rfc.xref.RFC2047.1">2.7.2</a>, <a class="iref" href="#RFC2047"><b>7.2</b></a></li> 3309 <li class="indline1"><em>RFC2068</em> <a class="iref" href="#rfc.xref.RFC2068.1">2.5</a>, <a class="iref" href="#rfc.xref.RFC2068.2">2.11.1.3</a>, <a class="iref" href="#rfc.xref.RFC2068.3">2.11.2.3</a>, <a class="iref" href="#rfc.xref.RFC2068.4">6</a>, <a class="iref" href="# RFC2068"><b>7.2</b></a>, <a class="iref" href="#rfc.xref.RFC2068.5">B</a>, <a class="iref" href="#rfc.xref.RFC2068.6">B.2</a><ul class="ind">3310 <li class="indline1"><em>Section 19.7.1</em> <a class="iref" href="#rfc.xref.RFC2068.2">2.11.1.3</a>, <a class="iref" href="#rfc.xref.RFC2068. 5">B</a>, <a class="iref" href="#rfc.xref.RFC2068.6">B.2</a></li>3411 <li class="indline1"><em>RFC2068</em> <a class="iref" href="#rfc.xref.RFC2068.1">2.5</a>, <a class="iref" href="#rfc.xref.RFC2068.2">2.11.1.3</a>, <a class="iref" href="#rfc.xref.RFC2068.3">2.11.2.3</a>, <a class="iref" href="#rfc.xref.RFC2068.4">6</a>, <a class="iref" href="#rfc.xref.RFC2068.5">7.1</a>, <a class="iref" href="#rfc.xref.RFC2068.6">7.1</a>, <a class="iref" href="#rfc.xref.RFC2068.7">7.1</a>, <a class="iref" href="#RFC2068"><b>7.2</b></a>, <a class="iref" href="#rfc.xref.RFC2068.8">B</a>, <a class="iref" href="#rfc.xref.RFC2068.9">B.2</a><ul class="ind"> 3412 <li class="indline1"><em>Section 19.7.1</em> <a class="iref" href="#rfc.xref.RFC2068.2">2.11.1.3</a>, <a class="iref" href="#rfc.xref.RFC2068.8">B</a>, <a class="iref" href="#rfc.xref.RFC2068.9">B.2</a></li> 3311 3413 </ul> 3312 3414 </li> … … 3334 3436 <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> 3335 3437 <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>3438 <li class="indline1"><em>RFC5226</em> <a class="iref" href="#rfc.xref.RFC5226.1">2.10.2.3</a>, <a class="iref" href="#RFC5226"><b>7.2</b></a><ul class="ind"> 3439 <li class="indline1"><em>Section 4.1</em> <a class="iref" href="#rfc.xref.RFC5226.1">2.10.2.3</a></li> 3338 3440 </ul> 3339 3441 </li> -
draft-ietf-httpbis/latest/p1-messaging.xml
r670 r673 1756 1756 </t> 1757 1757 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="transfer-coding"/><iref primary="true" item="Grammar" subitem="transfer-extension"/> 1758 <x:ref>transfer-coding</x:ref> = "chunked" / <x:ref>transfer-extension</x:ref> 1758 <x:ref>transfer-coding</x:ref> = "chunked" ; <xref target="chunked.encoding"/> 1759 / "compress" ; <xref target="compress.coding"/> 1760 / "deflate" ; <xref target="deflate.coding"/> 1761 / "gzip" ; <xref target="gzip.coding"/> 1762 / <x:ref>transfer-extension</x:ref> 1759 1763 <x:ref>transfer-extension</x:ref> = <x:ref>token</x:ref> *( <x:ref>OWS</x:ref> ";" <x:ref>OWS</x:ref> <x:ref>transfer-parameter</x:ref> ) 1760 1764 </artwork></figure> … … 1801 1805 </t> 1802 1806 1803 <section title="Chunked Transfer Coding" anchor="chunked.transfer.encoding"> 1807 <section title="Chunked Transfer Coding" anchor="chunked.encoding"> 1808 <iref item="chunked (Coding Format)"/> 1809 <iref item="Coding Format" subitem="chunked"/> 1804 1810 <x:anchor-alias value="chunk"/> 1805 1811 <x:anchor-alias value="Chunked-Body"/> … … 1898 1904 they do not understand. 1899 1905 </t> 1906 </section> 1907 1908 <section title="Compression Codings" anchor="compression.codings"> 1909 <t> 1910 The codings defined below can be used to compress the payload of a 1911 message. 1912 </t> 1913 <x:note><t> 1914 <x:h>Note:</x:h> Use of program names for the identification of encoding formats 1915 is not desirable and is discouraged for future encodings. Their 1916 use here is representative of historical practice, not good 1917 design. 1918 </t></x:note> 1919 <x:note><t> 1920 <x:h>Note:</x:h> For compatibility with previous implementations of HTTP, 1921 applications &SHOULD; consider "x-gzip" and "x-compress" to be 1922 equivalent to "gzip" and "compress" respectively. 1923 </t></x:note> 1924 1925 <section title="Compress Coding" anchor="compress.coding"> 1926 <iref item="compress (Coding Format)"/> 1927 <iref item="Coding Format" subitem="compress"/> 1928 <t> 1929 The "compress" format is produced by the common UNIX file compression 1930 program "compress". This format is an adaptive Lempel-Ziv-Welch 1931 coding (LZW). 1932 </t> 1933 </section> 1934 1935 <section title="Deflate Coding" anchor="deflate.coding"> 1936 <iref item="deflate (Coding Format)"/> 1937 <iref item="Coding Format" subitem="deflate"/> 1938 <t> 1939 The "zlib" format is defined in <xref target="RFC1950"/> in combination with 1940 the "deflate" compression mechanism described in <xref target="RFC1951"/>. 1941 </t> 1942 </section> 1943 1944 <section title="Gzip Coding" anchor="gzip.coding"> 1945 <iref item="gzip (Coding Format)"/> 1946 <iref item="Coding Format" subitem="gzip"/> 1947 <t> 1948 The "gzip" format is produced by the file compression program 1949 "gzip" (GNU zip), as described in <xref target="RFC1952"/>. This format is a 1950 Lempel-Ziv coding (LZ77) with a 32 bit CRC. 1951 </t> 1952 </section> 1953 1900 1954 </section> 1901 1955 … … 2683 2737 The presence of the keyword "trailers" indicates that the client is 2684 2738 willing to accept trailer fields in a chunked transfer-coding, as 2685 defined in <xref target="chunked. transfer.encoding"/>. This keyword is reserved for use with2739 defined in <xref target="chunked.encoding"/>. This keyword is reserved for use with 2686 2740 transfer-coding values even though it does not itself represent a 2687 2741 transfer-coding. … … 2761 2815 <t> 2762 2816 If no Trailer header field is present, the trailer &SHOULD-NOT; include 2763 any header fields. See <xref target="chunked. transfer.encoding"/> for restrictions on the use of2817 any header fields. See <xref target="chunked.encoding"/> for restrictions on the use of 2764 2818 trailer fields in a "chunked" transfer-coding. 2765 2819 </t> … … 3214 3268 <section title="Transfer Coding Registry" anchor="transfer.coding.registration"> 3215 3269 <t> 3216 The registration procedure for HTTP Transfer Codings is now defined 3217 by<xref target="transfer.coding.registry"/> of this document.3270 The registration procedure for HTTP Transfer Codings is now defined by 3271 <xref target="transfer.coding.registry"/> of this document. 3218 3272 </t> 3219 3273 <t> 3220 3274 The HTTP Transfer Codings Registry located at <eref target="http://www.iana.org/assignments/http-parameters"/> 3221 should be updated with the registration below:3275 should be updated with the registrations below: 3222 3276 </t> 3223 3277 <texttable align="left" suppress-title="true" anchor="iana.transfer.coding.registration.table"> … … 3225 3279 <ttcol>Description</ttcol> 3226 3280 <ttcol>Reference</ttcol> 3227 <c> Chunked</c>3281 <c>chunked</c> 3228 3282 <c>Transfer in a series of chunks</c> 3229 3283 <c> 3230 <xref target="chunked.transfer.encoding"/> 3284 <xref target="chunked.encoding"/> 3285 </c> 3286 <c>compress</c> 3287 <c>UNIX "compress" program method</c> 3288 <c> 3289 <xref target="compress.coding"/> 3290 </c> 3291 <c>deflate</c> 3292 <c>"zlib" format <xref target="RFC1950"/> with "deflate" compression</c> 3293 <c> 3294 <xref target="deflate.coding"/> 3295 </c> 3296 <c>gzip</c> 3297 <c>Same as GNU zip <xref target="RFC1952"/></c> 3298 <c> 3299 <xref target="gzip.coding"/> 3231 3300 </c> 3232 3301 </texttable> … … 3723 3792 </reference> 3724 3793 3794 <reference anchor="RFC1950"> 3795 <front> 3796 <title>ZLIB Compressed Data Format Specification version 3.3</title> 3797 <author initials="L.P." surname="Deutsch" fullname="L. Peter Deutsch"> 3798 <organization>Aladdin Enterprises</organization> 3799 <address><email>ghost@aladdin.com</email></address> 3800 </author> 3801 <author initials="J-L." surname="Gailly" fullname="Jean-Loup Gailly"> 3802 <organization/> 3803 </author> 3804 <date month="May" year="1996"/> 3805 </front> 3806 <seriesInfo name="RFC" value="1950"/> 3807 <annotation> 3808 RFC 1950 is an Informational RFC, thus it may be less stable than 3809 this specification. On the other hand, this downward reference was 3810 present since the publication of RFC 2068 in 1997 (<xref target="RFC2068"/>), 3811 therefore it is unlikely to cause problems in practice. See also 3812 <xref target="BCP97"/>. 3813 </annotation> 3814 </reference> 3815 3816 <reference anchor="RFC1951"> 3817 <front> 3818 <title>DEFLATE Compressed Data Format Specification version 1.3</title> 3819 <author initials="P." surname="Deutsch" fullname="L. Peter Deutsch"> 3820 <organization>Aladdin Enterprises</organization> 3821 <address><email>ghost@aladdin.com</email></address> 3822 </author> 3823 <date month="May" year="1996"/> 3824 </front> 3825 <seriesInfo name="RFC" value="1951"/> 3826 <annotation> 3827 RFC 1951 is an Informational RFC, thus it may be less stable than 3828 this specification. On the other hand, this downward reference was 3829 present since the publication of RFC 2068 in 1997 (<xref target="RFC2068"/>), 3830 therefore it is unlikely to cause problems in practice. See also 3831 <xref target="BCP97"/>. 3832 </annotation> 3833 </reference> 3834 3835 <reference anchor="RFC1952"> 3836 <front> 3837 <title>GZIP file format specification version 4.3</title> 3838 <author initials="P." surname="Deutsch" fullname="L. Peter Deutsch"> 3839 <organization>Aladdin Enterprises</organization> 3840 <address><email>ghost@aladdin.com</email></address> 3841 </author> 3842 <author initials="J-L." surname="Gailly" fullname="Jean-Loup Gailly"> 3843 <organization/> 3844 <address><email>gzip@prep.ai.mit.edu</email></address> 3845 </author> 3846 <author initials="M." surname="Adler" fullname="Mark Adler"> 3847 <organization/> 3848 <address><email>madler@alumni.caltech.edu</email></address> 3849 </author> 3850 <author initials="L.P." surname="Deutsch" fullname="L. Peter Deutsch"> 3851 <organization/> 3852 <address><email>ghost@aladdin.com</email></address> 3853 </author> 3854 <author initials="G." surname="Randers-Pehrson" fullname="Glenn Randers-Pehrson"> 3855 <organization/> 3856 <address><email>randeg@alumni.rpi.edu</email></address> 3857 </author> 3858 <date month="May" year="1996"/> 3859 </front> 3860 <seriesInfo name="RFC" value="1952"/> 3861 <annotation> 3862 RFC 1952 is an Informational RFC, thus it may be less stable than 3863 this specification. On the other hand, this downward reference was 3864 present since the publication of RFC 2068 in 1997 (<xref target="RFC2068"/>), 3865 therefore it is unlikely to cause problems in practice. See also 3866 <xref target="BCP97"/>. 3867 </annotation> 3868 </reference> 3869 3725 3870 </references> 3726 3871 … … 4080 4225 </front> 4081 4226 <seriesInfo name="RFC" value="5322"/> 4227 </reference> 4228 4229 <reference anchor='BCP97'> 4230 <front> 4231 <title>Handling Normative References to Standards-Track Documents</title> 4232 <author initials='J.' surname='Klensin' fullname='J. Klensin'> 4233 <organization /> 4234 <address> 4235 <email>klensin+ietf@jck.com</email> 4236 </address> 4237 </author> 4238 <author initials='S.' surname='Hartman' fullname='S. Hartman'> 4239 <organization>MIT</organization> 4240 <address> 4241 <email>hartmans-ietf@mit.edu</email> 4242 </address> 4243 </author> 4244 <date year='2007' month='June' /> 4245 </front> 4246 <seriesInfo name='BCP' value='97' /> 4247 <seriesInfo name='RFC' value='4897' /> 4082 4248 </reference> 4083 4249 … … 4345 4511 interoperability problem that could have occurred due to interactions 4346 4512 between authentication trailers, chunked encoding and HTTP/1.0 4347 clients.(Section <xref target="transfer.codings" format="counter"/>, <xref target="chunked. transfer.encoding" format="counter"/>,4513 clients.(Section <xref target="transfer.codings" format="counter"/>, <xref target="chunked.encoding" format="counter"/>, 4348 4514 and <xref target="header.te" format="counter"/>) 4349 4515 </t> … … 4376 4542 Clarification that the chunk length does not include 4377 4543 the count of the octets in the chunk header and trailer. 4378 (<xref target="chunked. transfer.encoding"/>)4544 (<xref target="chunked.encoding"/>) 4379 4545 </t> 4380 4546 <t> … … 5002 5168 "pick IANA policy (RFC5226) for Transfer Coding / Content Coding" 5003 5169 </t> 5170 <t> 5171 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/189"/>: 5172 "move definitions of gzip/deflate/compress to part 1" 5173 </t> 5004 5174 </list> 5005 5175 </t> -
draft-ietf-httpbis/latest/p3-payload.html
r671 r673 592 592 <li class="tocline0">6. <a href="#IANA.considerations">IANA Considerations</a><ul class="toc"> 593 593 <li class="tocline1">6.1 <a href="#message.header.registration">Message Header Registration</a></li> 594 <li class="tocline1">6.2 <a href="#transfer.coding.registration">Transfer Coding Registry</a></li> 595 <li class="tocline1">6.3 <a href="#content.coding.registration">Content Coding Registry</a></li> 594 <li class="tocline1">6.2 <a href="#content.coding.registration">Content Coding Registry</a></li> 596 595 </ul> 597 596 </li> … … 760 759 mechanism will be required to remove the encoding. 761 760 </p> 762 <p id="rfc.section.2.2.p.4">The Internet Assigned Numbers Authority (IANA) acts as a registry for content-coding value tokens. Initially, the registry 763 contains the following tokens: 764 </p> 765 <p id="rfc.section.2.2.p.5">gzip<span id="rfc.iref.g.3"></span> 761 <p id="rfc.section.2.2.p.4">compress<span id="rfc.iref.c.2"></span><span id="rfc.iref.c.3"></span> 766 762 </p> 767 763 <dl class="empty"> 768 <dd> An encoding format produced by the file compression program "gzip" (GNU zip) as described in <a href="#RFC1952" id="rfc.xref.RFC1952.1"><cite title="GZIP file format specification version 4.3">[RFC1952]</cite></a>. This format is a Lempel-Ziv coding (LZ77) with a 32 bit CRC.764 <dd>See <a href="p1-messaging.html#compress.coding" title="Compress Coding">Section 2.10.2.2.1</a> of <a href="#Part1" id="rfc.xref.Part1.11"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. 769 765 </dd> 770 766 </dl> 771 <p id="rfc.section.2.2.p. 6">compress<span id="rfc.iref.c.2"></span>767 <p id="rfc.section.2.2.p.5">deflate<span id="rfc.iref.d.1"></span><span id="rfc.iref.c.4"></span> 772 768 </p> 773 769 <dl class="empty"> 774 <dd>The encoding format produced by the common UNIX file compression program "compress". This format is an adaptive Lempel-Ziv-Welch 775 coding (LZW). 776 </dd> 777 <dd>Use of program names for the identification of encoding formats is not desirable and is discouraged for future encodings. 778 Their use here is representative of historical practice, not good design. For compatibility with previous implementations 779 of HTTP, applications <em class="bcp14">SHOULD</em> consider "x-gzip" and "x-compress" to be equivalent to "gzip" and "compress" respectively. 770 <dd>See <a href="p1-messaging.html#deflate.coding" title="Deflate Coding">Section 2.10.2.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.12"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. 780 771 </dd> 781 772 </dl> 782 <p id="rfc.section.2.2.p. 7">deflate<span id="rfc.iref.d.1"></span>773 <p id="rfc.section.2.2.p.6">gzip<span id="rfc.iref.g.3"></span><span id="rfc.iref.c.5"></span> 783 774 </p> 784 775 <dl class="empty"> 785 <dd> The "zlib" format defined in <a href="#RFC1950" id="rfc.xref.RFC1950.1"><cite title="ZLIB Compressed Data Format Specification version 3.3">[RFC1950]</cite></a> in combination with the "deflate" compression mechanism described in <a href="#RFC1951" id="rfc.xref.RFC1951.1"><cite title="DEFLATE Compressed Data Format Specification version 1.3">[RFC1951]</cite></a>.776 <dd>See <a href="p1-messaging.html#gzip.coding" title="Gzip Coding">Section 2.10.2.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. 786 777 </dd> 787 778 </dl> 788 <p id="rfc.section.2.2.p. 8">identity<span id="rfc.iref.i.1"></span>779 <p id="rfc.section.2.2.p.7">identity<span id="rfc.iref.i.1"></span><span id="rfc.iref.c.6"></span> 789 780 </p> 790 781 <dl class="empty"> … … 897 888 <div id="rfc.figure.u.12"></div><pre class="inline"><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span> <a href="#entity.header.fields" class="smpl">entity-header</a> = <a href="#header.content-encoding" class="smpl">Content-Encoding</a> ; <a href="#header.content-encoding" id="rfc.xref.header.content-encoding.2" title="Content-Encoding">Section 5.5</a> 898 889 / <a href="#header.content-language" class="smpl">Content-Language</a> ; <a href="#header.content-language" id="rfc.xref.header.content-language.1" title="Content-Language">Section 5.6</a> 899 / <a href="#abnf.dependencies" class="smpl">Content-Length</a> ; <a href="#Part1" id="rfc.xref.Part1.1 1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.content-length" title="Content-Length">Section 3.2</a>890 / <a href="#abnf.dependencies" class="smpl">Content-Length</a> ; <a href="#Part1" id="rfc.xref.Part1.14"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.content-length" title="Content-Length">Section 3.2</a> 900 891 / <a href="#header.content-location" class="smpl">Content-Location</a> ; <a href="#header.content-location" id="rfc.xref.header.content-location.1" title="Content-Location">Section 5.7</a> 901 892 / <a href="#header.content-md5" class="smpl">Content-MD5</a> ; <a href="#header.content-md5" id="rfc.xref.header.content-md5.1" title="Content-MD5">Section 5.8</a> … … 913 904 <p id="rfc.section.3.2.p.1">The entity-body (if any) sent with an HTTP request or response is in a format and encoding defined by the entity-header fields.</p> 914 905 <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.13"></span> <a href="#entity.body" class="smpl">entity-body</a> = *<a href="#notation" class="smpl">OCTET</a> 915 </pre><p id="rfc.section.3.2.p.3">An entity-body is only present in a message when a message-body is present, as described in <a href="p1-messaging.html#message.body" title="Message Body">Section 2.7.3</a> of <a href="#Part1" id="rfc.xref.Part1.1 2"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. The entity-body is obtained from the message-body by decoding any Transfer-Encoding that might have been applied to ensure906 </pre><p id="rfc.section.3.2.p.3">An entity-body is only present in a message when a message-body is present, as described in <a href="p1-messaging.html#message.body" title="Message Body">Section 2.7.3</a> of <a href="#Part1" id="rfc.xref.Part1.15"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. The entity-body is obtained from the message-body by decoding any Transfer-Encoding that might have been applied to ensure 916 907 safe and proper transfer of the message. 917 908 </p> … … 928 919 </p> 929 920 <h3 id="rfc.section.3.2.2"><a href="#rfc.section.3.2.2">3.2.2</a> <a id="entity.length" href="#entity.length">Entity Length</a></h3> 930 <p id="rfc.section.3.2.2.p.1">The entity-length of a message is the length of the message-body before any transfer-codings have been applied. <a href="p1-messaging.html#message.length" title="Message Length">Section 2.7.4</a> of <a href="#Part1" id="rfc.xref.Part1.1 3"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> defines how the transfer-length of a message-body is determined.921 <p id="rfc.section.3.2.2.p.1">The entity-length of a message is the length of the message-body before any transfer-codings have been applied. <a href="p1-messaging.html#message.length" title="Message Length">Section 2.7.4</a> of <a href="#Part1" id="rfc.xref.Part1.16"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> defines how the transfer-length of a message-body is determined. 931 922 </p> 932 923 <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a> <a id="content.negotiation" href="#content.negotiation">Content Negotiation</a></h1> … … 1037 1028 <p id="rfc.section.5.1.p.4">Each media-range <em class="bcp14">MAY</em> be followed by one or more accept-params, beginning with the "q" parameter for indicating a relative quality factor. The first 1038 1029 "q" parameter (if any) separates the media-range parameter(s) from the accept-params. Quality factors allow the user or user 1039 agent to indicate the relative degree of preference for that media-range, using the qvalue scale from 0 to 1 (<a href="p1-messaging.html#quality.values" title="Quality Values">Section 2.10.4</a> of <a href="#Part1" id="rfc.xref.Part1.1 4"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). The default value is q=1.1030 agent to indicate the relative degree of preference for that media-range, using the qvalue scale from 0 to 1 (<a href="p1-messaging.html#quality.values" title="Quality Values">Section 2.10.4</a> of <a href="#Part1" id="rfc.xref.Part1.17"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). The default value is q=1. 1040 1031 </p> 1041 1032 <div class="note"> … … 1161 1152 <ol> 1162 1153 <li>If the content-coding is one of the content-codings listed in the Accept-Encoding field, then it is acceptable, unless it 1163 is accompanied by a qvalue of 0. (As defined in <a href="p1-messaging.html#quality.values" title="Quality Values">Section 2.10.4</a> of <a href="#Part1" id="rfc.xref.Part1.1 5"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, a qvalue of 0 means "not acceptable.")1154 is accompanied by a qvalue of 0. (As defined in <a href="p1-messaging.html#quality.values" title="Quality Values">Section 2.10.4</a> of <a href="#Part1" id="rfc.xref.Part1.18"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, a qvalue of 0 means "not acceptable.") 1164 1155 </li> 1165 1156 <li>The special "*" symbol in an Accept-Encoding field matches any available content-coding not explicitly listed in the header … … 1242 1233 </p> 1243 1234 </div> 1244 <div id="rfc.iref.c. 3"></div>1235 <div id="rfc.iref.c.7"></div> 1245 1236 <div id="rfc.iref.h.5"></div> 1246 1237 <h2 id="rfc.section.5.5"><a href="#rfc.section.5.5">5.5</a> <a id="header.content-encoding" href="#header.content-encoding">Content-Encoding</a></h2> … … 1265 1256 <p id="rfc.section.5.5.p.8">If multiple encodings have been applied to an entity, the content codings <em class="bcp14">MUST</em> be listed in the order in which they were applied. Additional information about the encoding parameters <em class="bcp14">MAY</em> be provided by other entity-header fields not defined by this specification. 1266 1257 </p> 1267 <div id="rfc.iref.c. 4"></div>1258 <div id="rfc.iref.c.8"></div> 1268 1259 <div id="rfc.iref.h.6"></div> 1269 1260 <h2 id="rfc.section.5.6"><a href="#rfc.section.5.6">5.6</a> <a id="header.content-language" href="#header.content-language">Content-Language</a></h2> … … 1291 1282 <p id="rfc.section.5.6.p.9">Content-Language <em class="bcp14">MAY</em> be applied to any media type -- it is not limited to textual documents. 1292 1283 </p> 1293 <div id="rfc.iref.c. 5"></div>1284 <div id="rfc.iref.c.9"></div> 1294 1285 <div id="rfc.iref.h.7"></div> 1295 1286 <h2 id="rfc.section.5.7"><a href="#rfc.section.5.7">5.7</a> <a id="header.content-location" href="#header.content-location">Content-Location</a></h2> … … 1313 1304 <p id="rfc.section.5.7.p.6">If the Content-Location is a relative URI, the relative URI is interpreted relative to the request-target.</p> 1314 1305 <p id="rfc.section.5.7.p.7">The meaning of the Content-Location header in requests is undefined; servers are free to ignore it in those cases.</p> 1315 <div id="rfc.iref.c. 6"></div>1306 <div id="rfc.iref.c.10"></div> 1316 1307 <div id="rfc.iref.h.8"></div> 1317 1308 <h2 id="rfc.section.5.8"><a href="#rfc.section.5.8">5.8</a> <a id="header.content-md5" href="#header.content-md5">Content-MD5</a></h2> … … 1351 1342 </p> 1352 1343 </div> 1353 <div id="rfc.iref.c. 7"></div>1344 <div id="rfc.iref.c.11"></div> 1354 1345 <div id="rfc.iref.h.9"></div> 1355 1346 <h2 id="rfc.section.5.9"><a href="#rfc.section.5.9">5.9</a> <a id="header.content-type" href="#header.content-type">Content-Type</a></h2> … … 1461 1452 </div> 1462 1453 <p id="rfc.section.6.1.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p> 1463 <h2 id="rfc.section.6.2"><a href="#rfc.section.6.2">6.2</a> <a id="transfer.coding.registration" href="#transfer.coding.registration">Transfer Coding Registry</a></h2> 1464 <p id="rfc.section.6.2.p.1">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 registrations below: 1454 <h2 id="rfc.section.6.2"><a href="#rfc.section.6.2">6.2</a> <a id="content.coding.registration" href="#content.coding.registration">Content Coding Registry</a></h2> 1455 <p id="rfc.section.6.2.p.1">The registration procedure for HTTP Content Codings is now defined by <a href="#content.coding.registry" title="Content Coding Registry">Section 2.2.1</a> of this document. 1456 </p> 1457 <p id="rfc.section.6.2.p.2">The HTTP Content 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: 1465 1458 </p> 1466 1459 <div id="rfc.table.2"> 1467 <div id="iana. transfer.coding.registration.table"></div>1460 <div id="iana.content.coding.registration.table"></div> 1468 1461 <table class="tt full left" cellpadding="3" cellspacing="0"> 1469 1462 <thead> … … 1478 1471 <td>compress</td> 1479 1472 <td>UNIX "compress" program method</td> 1480 <td> <a href=" #content.codings" title="Content Codings">Section 2.2</a>1473 <td> <a href="p1-messaging.html#compress.coding" title="Compress Coding">Section 2.10.2.2.1</a> of <a href="#Part1" id="rfc.xref.Part1.19"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> 1481 1474 </td> 1482 1475 </tr> 1483 1476 <tr> 1484 1477 <td>deflate</td> 1485 <td>"zlib" format <a href="#RFC1950" id="rfc.xref.RFC1950. 2"><cite title="ZLIB Compressed Data Format Specification version 3.3">[RFC1950]</cite></a> with "deflate" compression1478 <td>"zlib" format <a href="#RFC1950" id="rfc.xref.RFC1950.1"><cite title="ZLIB Compressed Data Format Specification version 3.3">[RFC1950]</cite></a> with "deflate" compression 1486 1479 </td> 1487 <td> <a href=" #content.codings" title="Content Codings">Section 2.2</a>1480 <td> <a href="p1-messaging.html#deflate.coding" title="Deflate Coding">Section 2.10.2.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.20"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> 1488 1481 </td> 1489 1482 </tr> 1490 1483 <tr> 1491 1484 <td>gzip</td> 1492 <td>Same as GNU zip <a href="#RFC1952" id="rfc.xref.RFC1952.2"><cite title="GZIP file format specification version 4.3">[RFC1952]</cite></a></td> 1493 <td> <a href="#content.codings" title="Content Codings">Section 2.2</a> 1494 </td> 1495 </tr> 1496 </tbody> 1497 </table> 1498 </div> 1499 <h2 id="rfc.section.6.3"><a href="#rfc.section.6.3">6.3</a> <a id="content.coding.registration" href="#content.coding.registration">Content Coding Registry</a></h2> 1500 <p id="rfc.section.6.3.p.1">The registration procedure for HTTP Content Codings is now defined by <a href="#content.coding.registry" title="Content Coding Registry">Section 2.2.1</a> of this document. 1501 </p> 1502 <p id="rfc.section.6.3.p.2">The HTTP Content 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 registrations below: 1503 </p> 1504 <div id="rfc.table.3"> 1505 <div id="iana.content.coding.registration.table"></div> 1506 <table class="tt full left" cellpadding="3" cellspacing="0"> 1507 <thead> 1508 <tr> 1509 <th>Name</th> 1510 <th>Description</th> 1511 <th>Reference</th> 1512 </tr> 1513 </thead> 1514 <tbody> 1515 <tr> 1516 <td>compress</td> 1517 <td>UNIX "compress" program method</td> 1518 <td> <a href="#content.codings" title="Content Codings">Section 2.2</a> 1519 </td> 1520 </tr> 1521 <tr> 1522 <td>deflate</td> 1523 <td>"zlib" format <a href="#RFC1950" id="rfc.xref.RFC1950.3"><cite title="ZLIB Compressed Data Format Specification version 3.3">[RFC1950]</cite></a> with "deflate" compression 1524 </td> 1525 <td> <a href="#content.codings" title="Content Codings">Section 2.2</a> 1526 </td> 1527 </tr> 1528 <tr> 1529 <td>gzip</td> 1530 <td>Same as GNU zip <a href="#RFC1952" id="rfc.xref.RFC1952.3"><cite title="GZIP file format specification version 4.3">[RFC1952]</cite></a></td> 1531 <td> <a href="#content.codings" title="Content Codings">Section 2.2</a> 1485 <td>Same as GNU zip <a href="#RFC1952" id="rfc.xref.RFC1952.1"><cite title="GZIP file format specification version 4.3">[RFC1952]</cite></a></td> 1486 <td> <a href="p1-messaging.html#gzip.coding" title="Gzip Coding">Section 2.10.2.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.21"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> 1532 1487 </td> 1533 1488 </tr> … … 1574 1529 <h2 id="rfc.references.1"><a href="#rfc.section.9.1" id="rfc.section.9.1">9.1</a> Normative References 1575 1530 </h2> 1576 <table summary="Normative References"> 1531 <table summary="Normative References"> 1577 1532 <tr> 1578 1533 <td class="reference"><b id="ISO-8859-1">[ISO-8859-1]</b></td> … … 1616 1571 </tr> 1617 1572 <tr> 1618 <td class="reference"><b id="RFC1951">[RFC1951]</b></td>1619 <td class="top"><a title="Aladdin Enterprises">Deutsch, P.</a>, “<a href="http://tools.ietf.org/html/rfc1951">DEFLATE Compressed Data Format Specification version 1.3</a>”, RFC 1951, May 1996.<br>RFC 1951 is an Informational RFC, thus it may be less stable than this specification. On the other hand, this downward reference1620 was present since the publication of RFC 2068 in 1997 (<a href="#RFC2068" id="rfc.xref.RFC2068.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>), therefore it is unlikely to cause problems in practice. See also <a href="#BCP97" id="rfc.xref.BCP97.2"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>.1621 </td>1622 </tr>1623 <tr>1624 1573 <td class="reference"><b id="RFC1952">[RFC1952]</b></td> 1625 1574 <td class="top"><a title="Aladdin Enterprises">Deutsch, P.</a>, <a>Gailly, J-L.</a>, <a>Adler, M.</a>, <a>Deutsch, L.P.</a>, and <a>G. Randers-Pehrson</a>, “<a href="http://tools.ietf.org/html/rfc1952">GZIP file format specification version 4.3</a>”, RFC 1952, May 1996.<br>RFC 1952 is an Informational RFC, thus it may be less stable than this specification. On the other hand, this downward reference 1626 was present since the publication of RFC 2068 in 1997 (<a href="#RFC2068" id="rfc.xref.RFC2068. 3"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>), therefore it is unlikely to cause problems in practice. See also <a href="#BCP97" id="rfc.xref.BCP97.3"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>.1575 was present since the publication of RFC 2068 in 1997 (<a href="#RFC2068" id="rfc.xref.RFC2068.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>), therefore it is unlikely to cause problems in practice. See also <a href="#BCP97" id="rfc.xref.BCP97.2"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>. 1627 1576 </td> 1628 1577 </tr> … … 1791 1740 </p> 1792 1741 <h2 id="rfc.section.A.3"><a href="#rfc.section.A.3">A.3</a> <a id="conversion.of.date.formats" href="#conversion.of.date.formats">Conversion of Date Formats</a></h2> 1793 <p id="rfc.section.A.3.p.1">HTTP/1.1 uses a restricted set of date formats (<a href="p1-messaging.html#date.time.formats.full.date" title="Date/Time Formats: Full Date">Section 2.10.1</a> of <a href="#Part1" id="rfc.xref.Part1. 16"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) to simplify the process of date comparison. Proxies and gateways from other protocols <em class="bcp14">SHOULD</em> ensure that any Date header field present in a message conforms to one of the HTTP/1.1 formats and rewrite the date if necessary.1742 <p id="rfc.section.A.3.p.1">HTTP/1.1 uses a restricted set of date formats (<a href="p1-messaging.html#date.time.formats.full.date" title="Date/Time Formats: Full Date">Section 2.10.1</a> of <a href="#Part1" id="rfc.xref.Part1.22"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) to simplify the process of date comparison. Proxies and gateways from other protocols <em class="bcp14">SHOULD</em> ensure that any Date header field present in a message conforms to one of the HTTP/1.1 formats and rewrite the date if necessary. 1794 1743 </p> 1795 1744 <h2 id="rfc.section.A.4"><a href="#rfc.section.A.4">A.4</a> <a id="introduction.of.content-encoding" href="#introduction.of.content-encoding">Introduction of Content-Encoding</a></h2> … … 1808 1757 </p> 1809 1758 <h2 id="rfc.section.A.6"><a href="#rfc.section.A.6">A.6</a> <a id="introduction.of.transfer-encoding" href="#introduction.of.transfer-encoding">Introduction of Transfer-Encoding</a></h2> 1810 <p id="rfc.section.A.6.p.1">HTTP/1.1 introduces the Transfer-Encoding header field (<a href="p1-messaging.html#header.transfer-encoding" title="Transfer-Encoding">Section 3.7</a> of <a href="#Part1" id="rfc.xref.Part1. 17"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). Proxies/gateways <em class="bcp14">MUST</em> remove any transfer-coding prior to forwarding a message via a MIME-compliant protocol.1759 <p id="rfc.section.A.6.p.1">HTTP/1.1 introduces the Transfer-Encoding header field (<a href="p1-messaging.html#header.transfer-encoding" title="Transfer-Encoding">Section 3.7</a> of <a href="#Part1" id="rfc.xref.Part1.23"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). Proxies/gateways <em class="bcp14">MUST</em> remove any transfer-coding prior to forwarding a message via a MIME-compliant protocol. 1811 1760 </p> 1812 1761 <h2 id="rfc.section.A.7"><a href="#rfc.section.A.7">A.7</a> <a id="mhtml.line.length" href="#mhtml.line.length">MHTML and Line Length Limitations</a></h2> … … 1816 1765 </p> 1817 1766 <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a> <a id="additional.features" href="#additional.features">Additional Features</a></h1> 1818 <p id="rfc.section.B.p.1"> <a href="#RFC1945" id="rfc.xref.RFC1945.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.0">[RFC1945]</cite></a> and <a href="#RFC2068" id="rfc.xref.RFC2068. 4"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a> document protocol elements used by some existing HTTP implementations, but not consistently and correctly across most HTTP/1.11767 <p id="rfc.section.B.p.1"> <a href="#RFC1945" id="rfc.xref.RFC1945.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.0">[RFC1945]</cite></a> and <a href="#RFC2068" id="rfc.xref.RFC2068.3"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a> document protocol elements used by some existing HTTP implementations, but not consistently and correctly across most HTTP/1.1 1819 1768 applications. Implementors are advised to be aware of these features, but cannot rely upon their presence in, or interoperability 1820 1769 with, other HTTP/1.1 applications. Some of these describe proposed experimental features, and some describe features that … … 1824 1773 </p> 1825 1774 <div id="rfc.iref.h.11"></div> 1826 <div id="rfc.iref.c. 8"></div>1775 <div id="rfc.iref.c.12"></div> 1827 1776 <h2 id="rfc.section.B.1"><a href="#rfc.section.B.1">B.1</a> <a id="content-disposition" href="#content-disposition">Content-Disposition</a></h2> 1828 1777 <p id="rfc.section.B.1.p.1">The Content-Disposition response-header field has been proposed as a means for the origin server to suggest a default filename … … 1853 1802 <p id="rfc.section.C.1.p.1">Transfer-coding and message lengths all interact in ways that required fixing exactly when chunked encoding is used (to allow 1854 1803 for transfer encoding that may not be self delimiting); it was important to straighten out exactly how message lengths are 1855 computed. (<a href="#entity.length" title="Entity Length">Section 3.2.2</a>, see also <a href="#Part1" id="rfc.xref.Part1. 18"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="#Part5" id="rfc.xref.Part5.4"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a> and <a href="#Part6" id="rfc.xref.Part6.5"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).1804 computed. (<a href="#entity.length" title="Entity Length">Section 3.2.2</a>, see also <a href="#Part1" id="rfc.xref.Part1.24"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="#Part5" id="rfc.xref.Part5.4"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a> and <a href="#Part6" id="rfc.xref.Part6.5"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>). 1856 1805 </p> 1857 1806 <p id="rfc.section.C.1.p.2">Charset wildcarding is introduced to avoid explosion of character set names in accept headers. (<a href="#header.accept-charset" id="rfc.xref.header.accept-charset.3" title="Accept-Charset">Section 5.2</a>) … … 1862 1811 <p id="rfc.section.C.1.p.4">A content-coding of "identity" was introduced, to solve problems discovered in caching. (<a href="#content.codings" title="Content Codings">Section 2.2</a>) 1863 1812 </p> 1864 <p id="rfc.section.C.1.p.5">The Alternates<span id="rfc.iref.a.5"></span><span id="rfc.iref.h.12"></span>, Content-Version<span id="rfc.iref.c. 9"></span><span id="rfc.iref.h.13"></span>, Derived-From<span id="rfc.iref.d.2"></span><span id="rfc.iref.h.14"></span>, Link<span id="rfc.iref.l.1"></span><span id="rfc.iref.h.15"></span>, URI<span id="rfc.iref.u.1"></span><span id="rfc.iref.h.16"></span>, Public<span id="rfc.iref.p.1"></span><span id="rfc.iref.h.17"></span> and Content-Base<span id="rfc.iref.c.10"></span><span id="rfc.iref.h.18"></span> header fields were defined in previous versions of this specification, but not commonly implemented. See <a href="http://tools.ietf.org/html/rfc2068#section-19.6.2">Section 19.6.2</a> of <a href="#RFC2068" id="rfc.xref.RFC2068.5"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>.1813 <p id="rfc.section.C.1.p.5">The Alternates<span id="rfc.iref.a.5"></span><span id="rfc.iref.h.12"></span>, Content-Version<span id="rfc.iref.c.13"></span><span id="rfc.iref.h.13"></span>, Derived-From<span id="rfc.iref.d.2"></span><span id="rfc.iref.h.14"></span>, Link<span id="rfc.iref.l.1"></span><span id="rfc.iref.h.15"></span>, URI<span id="rfc.iref.u.1"></span><span id="rfc.iref.h.16"></span>, Public<span id="rfc.iref.p.1"></span><span id="rfc.iref.h.17"></span> and Content-Base<span id="rfc.iref.c.14"></span><span id="rfc.iref.h.18"></span> header fields were defined in previous versions of this specification, but not commonly implemented. See <a href="http://tools.ietf.org/html/rfc2068#section-19.6.2">Section 19.6.2</a> of <a href="#RFC2068" id="rfc.xref.RFC2068.4"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>. 1865 1814 </p> 1866 1815 <h2 id="rfc.section.C.2"><a href="#rfc.section.C.2">C.2</a> <a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2> … … 2031 1980 <p id="rfc.section.E.5.p.2">Other changes: </p> 2032 1981 <ul> 2033 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/68">http://tools.ietf.org/wg/httpbis/trac/ticket/68</a>>: "Encoding References Normative" -- rephrase the annotation and reference <a href="#BCP97" id="rfc.xref.BCP97. 4"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>.1982 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/68">http://tools.ietf.org/wg/httpbis/trac/ticket/68</a>>: "Encoding References Normative" -- rephrase the annotation and reference <a href="#BCP97" id="rfc.xref.BCP97.3"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>. 2034 1983 </li> 2035 1984 </ul> … … 2079 2028 <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" 2080 2029 </li> 2030 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/189">http://tools.ietf.org/wg/httpbis/trac/ticket/189</a>>: "move definitions of gzip/deflate/compress to part 1" 2031 </li> 2081 2032 </ul> 2082 2033 <p id="rfc.section.E.9.p.2">Partly resolved issues: </p> … … 2101 2052 </li> 2102 2053 <li class="indline0"><a id="rfc.index.B" href="#rfc.index.B"><b>B</b></a><ul class="ind"> 2103 <li class="indline1"><em>BCP97</em> <a class="iref" href="#rfc.xref.BCP97.1">9.1</a>, <a class="iref" href="#rfc.xref.BCP97.2">9.1</a>, <a class="iref" href="# rfc.xref.BCP97.3">9.1</a>, <a class="iref" href="#BCP97"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.BCP97.4">E.5</a></li>2054 <li class="indline1"><em>BCP97</em> <a class="iref" href="#rfc.xref.BCP97.1">9.1</a>, <a class="iref" href="#rfc.xref.BCP97.2">9.1</a>, <a class="iref" href="#BCP97"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.BCP97.3">E.5</a></li> 2104 2055 </ul> 2105 2056 </li> 2106 2057 <li class="indline0"><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul class="ind"> 2107 <li class="indline1">compress <a class="iref" href="#rfc.iref.c.2">2.2</a></li> 2058 <li class="indline1">Coding Format 2059 <ul class="ind"> 2060 <li class="indline1">compress <a class="iref" href="#rfc.iref.c.3">2.2</a></li> 2061 <li class="indline1">deflate <a class="iref" href="#rfc.iref.c.4">2.2</a></li> 2062 <li class="indline1">gzip <a class="iref" href="#rfc.iref.c.5">2.2</a></li> 2063 <li class="indline1">identity <a class="iref" href="#rfc.iref.c.6">2.2</a></li> 2064 </ul> 2065 </li> 2066 <li class="indline1">compress (Coding Format) <a class="iref" href="#rfc.iref.c.2">2.2</a></li> 2108 2067 <li class="indline1">content negotiation <a class="iref" href="#rfc.iref.c.1">1.1</a></li> 2109 <li class="indline1">Content-Base header <a class="iref" href="#rfc.iref.c.1 0"><b>C.1</b></a></li>2110 <li class="indline1">Content-Disposition header <a class="iref" href="#rfc.xref.content-disposition.1">6.1</a>, <a class="iref" href="#rfc.xref.content-disposition.2">7.2</a>, <a class="iref" href="#rfc.iref.c. 8"><b>B.1</b></a>, <a class="iref" href="#rfc.extref.c.32">B.1</a>, <a class="iref" href="#rfc.extref.c.50">D</a></li>2111 <li class="indline1">Content-Encoding header <a class="iref" href="#rfc.xref.header.content-encoding.1">2.2</a>, <a class="iref" href="#rfc.xref.header.content-encoding.2">3.1</a>, <a class="iref" href="#rfc.iref.c. 3"><b>5.5</b></a>, <a class="iref" href="#rfc.xref.header.content-encoding.3">5.5</a>, <a class="iref" href="#rfc.xref.header.content-encoding.4">6.1</a></li>2112 <li class="indline1">Content-Language header <a class="iref" href="#rfc.xref.header.content-language.1">3.1</a>, <a class="iref" href="#rfc.iref.c. 4"><b>5.6</b></a>, <a class="iref" href="#rfc.xref.header.content-language.2">6.1</a></li>2113 <li class="indline1">Content-Location header <a class="iref" href="#rfc.xref.header.content-location.1">3.1</a>, <a class="iref" href="#rfc.iref.c. 5"><b>5.7</b></a>, <a class="iref" href="#rfc.xref.header.content-location.2">6.1</a></li>2114 <li class="indline1">Content-MD5 header <a class="iref" href="#rfc.xref.header.content-md5.1">3.1</a>, <a class="iref" href="#rfc.iref.c. 6"><b>5.8</b></a>, <a class="iref" href="#rfc.xref.header.content-md5.2">6.1</a></li>2115 <li class="indline1">Content-Type header <a class="iref" href="#rfc.xref.header.content-type.1">2.3</a>, <a class="iref" href="#rfc.xref.header.content-type.2">3.1</a>, <a class="iref" href="#rfc.iref.c. 7"><b>5.9</b></a>, <a class="iref" href="#rfc.xref.header.content-type.3">6.1</a></li>2116 <li class="indline1">Content-Version header <a class="iref" href="#rfc.iref.c. 9"><b>C.1</b></a></li>2068 <li class="indline1">Content-Base header <a class="iref" href="#rfc.iref.c.14"><b>C.1</b></a></li> 2069 <li class="indline1">Content-Disposition header <a class="iref" href="#rfc.xref.content-disposition.1">6.1</a>, <a class="iref" href="#rfc.xref.content-disposition.2">7.2</a>, <a class="iref" href="#rfc.iref.c.12"><b>B.1</b></a>, <a class="iref" href="#rfc.extref.c.32">B.1</a>, <a class="iref" href="#rfc.extref.c.50">D</a></li> 2070 <li class="indline1">Content-Encoding header <a class="iref" href="#rfc.xref.header.content-encoding.1">2.2</a>, <a class="iref" href="#rfc.xref.header.content-encoding.2">3.1</a>, <a class="iref" href="#rfc.iref.c.7"><b>5.5</b></a>, <a class="iref" href="#rfc.xref.header.content-encoding.3">5.5</a>, <a class="iref" href="#rfc.xref.header.content-encoding.4">6.1</a></li> 2071 <li class="indline1">Content-Language header <a class="iref" href="#rfc.xref.header.content-language.1">3.1</a>, <a class="iref" href="#rfc.iref.c.8"><b>5.6</b></a>, <a class="iref" href="#rfc.xref.header.content-language.2">6.1</a></li> 2072 <li class="indline1">Content-Location header <a class="iref" href="#rfc.xref.header.content-location.1">3.1</a>, <a class="iref" href="#rfc.iref.c.9"><b>5.7</b></a>, <a class="iref" href="#rfc.xref.header.content-location.2">6.1</a></li> 2073 <li class="indline1">Content-MD5 header <a class="iref" href="#rfc.xref.header.content-md5.1">3.1</a>, <a class="iref" href="#rfc.iref.c.10"><b>5.8</b></a>, <a class="iref" href="#rfc.xref.header.content-md5.2">6.1</a></li> 2074 <li class="indline1">Content-Type header <a class="iref" href="#rfc.xref.header.content-type.1">2.3</a>, <a class="iref" href="#rfc.xref.header.content-type.2">3.1</a>, <a class="iref" href="#rfc.iref.c.11"><b>5.9</b></a>, <a class="iref" href="#rfc.xref.header.content-type.3">6.1</a></li> 2075 <li class="indline1">Content-Version header <a class="iref" href="#rfc.iref.c.13"><b>C.1</b></a></li> 2117 2076 </ul> 2118 2077 </li> 2119 2078 <li class="indline0"><a id="rfc.index.D" href="#rfc.index.D"><b>D</b></a><ul class="ind"> 2120 <li class="indline1">deflate <a class="iref" href="#rfc.iref.d.1">2.2</a></li>2079 <li class="indline1">deflate (Coding Format) <a class="iref" href="#rfc.iref.d.1">2.2</a></li> 2121 2080 <li class="indline1">Derived-From header <a class="iref" href="#rfc.iref.d.2"><b>C.1</b></a></li> 2122 2081 </ul> … … 2175 2134 </ul> 2176 2135 </li> 2177 <li class="indline1">gzip <a class="iref" href="#rfc.iref.g.3">2.2</a></li>2136 <li class="indline1">gzip (Coding Format) <a class="iref" href="#rfc.iref.g.3">2.2</a></li> 2178 2137 </ul> 2179 2138 </li> … … 2204 2163 </li> 2205 2164 <li class="indline0"><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul class="ind"> 2206 <li class="indline1">identity <a class="iref" href="#rfc.iref.i.1">2.2</a></li>2165 <li class="indline1">identity (Coding Format) <a class="iref" href="#rfc.iref.i.1">2.2</a></li> 2207 2166 <li class="indline1"><em>ISO-8859-1</em> <a class="iref" href="#rfc.xref.ISO-8859-1.1">2.1.1</a>, <a class="iref" href="#ISO-8859-1"><b>9.1</b></a></li> 2208 2167 </ul> … … 2217 2176 </li> 2218 2177 <li class="indline0"><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul class="ind"> 2219 <li class="indline1"><em>Part1</em> <a class="iref" href="#rfc.xref.Part1.1">1.3</a>, <a class="iref" href="#rfc.xref.Part1.2">1.3.1</a>, <a class="iref" href="#rfc.xref.Part1.3">1.3.1</a>, <a class="iref" href="#rfc.xref.Part1.4">1.3.1</a>, <a class="iref" href="#rfc.xref.Part1.5">1.3.1</a>, <a class="iref" href="#rfc.xref.Part1.6">1.3.2</a>, <a class="iref" href="#rfc.xref.Part1.7">1.3.2</a>, <a class="iref" href="#rfc.xref.Part1.8">1.3.2</a>, <a class="iref" href="#rfc.xref.Part1.9">1.3.2</a>, <a class="iref" href="#rfc.xref.Part1.10">1.3.2</a>, <a class="iref" href="#rfc.xref.Part1.11"> 3.1</a>, <a class="iref" href="#rfc.xref.Part1.12">3.2</a>, <a class="iref" href="#rfc.xref.Part1.13">3.2.2</a>, <a class="iref" href="#rfc.xref.Part1.14">5.1</a>, <a class="iref" href="#rfc.xref.Part1.15">5.3</a>, <a class="iref" href="#Part1"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.Part1.16">A.3</a>, <a class="iref" href="#rfc.xref.Part1.17">A.6</a>, <a class="iref" href="#rfc.xref.Part1.18">C.1</a><ul class="ind">2178 <li class="indline1"><em>Part1</em> <a class="iref" href="#rfc.xref.Part1.1">1.3</a>, <a class="iref" href="#rfc.xref.Part1.2">1.3.1</a>, <a class="iref" href="#rfc.xref.Part1.3">1.3.1</a>, <a class="iref" href="#rfc.xref.Part1.4">1.3.1</a>, <a class="iref" href="#rfc.xref.Part1.5">1.3.1</a>, <a class="iref" href="#rfc.xref.Part1.6">1.3.2</a>, <a class="iref" href="#rfc.xref.Part1.7">1.3.2</a>, <a class="iref" href="#rfc.xref.Part1.8">1.3.2</a>, <a class="iref" href="#rfc.xref.Part1.9">1.3.2</a>, <a class="iref" href="#rfc.xref.Part1.10">1.3.2</a>, <a class="iref" href="#rfc.xref.Part1.11">2.2</a>, <a class="iref" href="#rfc.xref.Part1.12">2.2</a>, <a class="iref" href="#rfc.xref.Part1.13">2.2</a>, <a class="iref" href="#rfc.xref.Part1.14">3.1</a>, <a class="iref" href="#rfc.xref.Part1.15">3.2</a>, <a class="iref" href="#rfc.xref.Part1.16">3.2.2</a>, <a class="iref" href="#rfc.xref.Part1.17">5.1</a>, <a class="iref" href="#rfc.xref.Part1.18">5.3</a>, <a class="iref" href="#rfc.xref.Part1.19">6.2</a>, <a class="iref" href="#rfc.xref.Part1.20">6.2</a>, <a class="iref" href="#rfc.xref.Part1.21">6.2</a>, <a class="iref" href="#Part1"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.Part1.22">A.3</a>, <a class="iref" href="#rfc.xref.Part1.23">A.6</a>, <a class="iref" href="#rfc.xref.Part1.24">C.1</a><ul class="ind"> 2220 2179 <li class="indline1"><em>Section 1.2</em> <a class="iref" href="#rfc.xref.Part1.1">1.3</a></li> 2221 2180 <li class="indline1"><em>Section 1.2.2</em> <a class="iref" href="#rfc.xref.Part1.2">1.3.1</a>, <a class="iref" href="#rfc.xref.Part1.3">1.3.1</a>, <a class="iref" href="#rfc.xref.Part1.4">1.3.1</a>, <a class="iref" href="#rfc.xref.Part1.5">1.3.1</a></li> 2222 2181 <li class="indline1"><em>Section 2.6</em> <a class="iref" href="#rfc.xref.Part1.6">1.3.2</a>, <a class="iref" href="#rfc.xref.Part1.9">1.3.2</a></li> 2223 2182 <li class="indline1"><em>Section 2.7.2</em> <a class="iref" href="#rfc.xref.Part1.8">1.3.2</a></li> 2224 <li class="indline1"><em>Section 2.7.3</em> <a class="iref" href="#rfc.xref.Part1.12">3.2</a></li> 2225 <li class="indline1"><em>Section 2.7.4</em> <a class="iref" href="#rfc.xref.Part1.13">3.2.2</a></li> 2226 <li class="indline1"><em>Section 2.10.1</em> <a class="iref" href="#rfc.xref.Part1.16">A.3</a></li> 2227 <li class="indline1"><em>Section 2.10.4</em> <a class="iref" href="#rfc.xref.Part1.10">1.3.2</a>, <a class="iref" href="#rfc.xref.Part1.14">5.1</a>, <a class="iref" href="#rfc.xref.Part1.15">5.3</a></li> 2228 <li class="indline1"><em>Section 3.2</em> <a class="iref" href="#rfc.xref.Part1.7">1.3.2</a>, <a class="iref" href="#rfc.xref.Part1.11">3.1</a></li> 2229 <li class="indline1"><em>Section 3.7</em> <a class="iref" href="#rfc.xref.Part1.17">A.6</a></li> 2183 <li class="indline1"><em>Section 2.7.3</em> <a class="iref" href="#rfc.xref.Part1.15">3.2</a></li> 2184 <li class="indline1"><em>Section 2.7.4</em> <a class="iref" href="#rfc.xref.Part1.16">3.2.2</a></li> 2185 <li class="indline1"><em>Section 2.10.1</em> <a class="iref" href="#rfc.xref.Part1.22">A.3</a></li> 2186 <li class="indline1"><em>Section 2.10.2.2.1</em> <a class="iref" href="#rfc.xref.Part1.11">2.2</a>, <a class="iref" href="#rfc.xref.Part1.19">6.2</a></li> 2187 <li class="indline1"><em>Section 2.10.2.2.2</em> <a class="iref" href="#rfc.xref.Part1.12">2.2</a>, <a class="iref" href="#rfc.xref.Part1.20">6.2</a></li> 2188 <li class="indline1"><em>Section 2.10.2.2.3</em> <a class="iref" href="#rfc.xref.Part1.13">2.2</a>, <a class="iref" href="#rfc.xref.Part1.21">6.2</a></li> 2189 <li class="indline1"><em>Section 2.10.4</em> <a class="iref" href="#rfc.xref.Part1.10">1.3.2</a>, <a class="iref" href="#rfc.xref.Part1.17">5.1</a>, <a class="iref" href="#rfc.xref.Part1.18">5.3</a></li> 2190 <li class="indline1"><em>Section 3.2</em> <a class="iref" href="#rfc.xref.Part1.7">1.3.2</a>, <a class="iref" href="#rfc.xref.Part1.14">3.1</a></li> 2191 <li class="indline1"><em>Section 3.7</em> <a class="iref" href="#rfc.xref.Part1.23">A.6</a></li> 2230 2192 </ul> 2231 2193 </li> … … 2256 2218 <li class="indline1"><em>RFC1864</em> <a class="iref" href="#rfc.xref.RFC1864.1">5.8</a>, <a class="iref" href="#rfc.xref.RFC1864.2">5.8</a>, <a class="iref" href="#RFC1864"><b>9.1</b></a></li> 2257 2219 <li class="indline1"><em>RFC1945</em> <a class="iref" href="#RFC1945"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC1945.1">B</a></li> 2258 <li class="indline1"><em>RFC1950</em> <a class="iref" href="#rfc.xref.RFC1950.1">2.2</a>, <a class="iref" href="#rfc.xref.RFC1950.2">6.2</a>, <a class="iref" href="#rfc.xref.RFC1950.3">6.3</a>, <a class="iref" href="#RFC1950"><b>9.1</b></a></li> 2259 <li class="indline1"><em>RFC1951</em> <a class="iref" href="#rfc.xref.RFC1951.1">2.2</a>, <a class="iref" href="#RFC1951"><b>9.1</b></a></li> 2260 <li class="indline1"><em>RFC1952</em> <a class="iref" href="#rfc.xref.RFC1952.1">2.2</a>, <a class="iref" href="#rfc.xref.RFC1952.2">6.2</a>, <a class="iref" href="#rfc.xref.RFC1952.3">6.3</a>, <a class="iref" href="#RFC1952"><b>9.1</b></a></li> 2220 <li class="indline1"><em>RFC1950</em> <a class="iref" href="#rfc.xref.RFC1950.1">6.2</a>, <a class="iref" href="#RFC1950"><b>9.1</b></a></li> 2221 <li class="indline1"><em>RFC1952</em> <a class="iref" href="#rfc.xref.RFC1952.1">6.2</a>, <a class="iref" href="#RFC1952"><b>9.1</b></a></li> 2261 2222 <li class="indline1"><em>RFC2045</em> <a class="iref" href="#RFC2045"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.RFC2045.1">A</a>, <a class="iref" href="#rfc.xref.RFC2045.2">A.1</a>, <a class="iref" href="#rfc.xref.RFC2045.3">A.2</a></li> 2262 2223 <li class="indline1"><em>RFC2046</em> <a class="iref" href="#rfc.xref.RFC2046.1">2.3</a>, <a class="iref" href="#rfc.xref.RFC2046.2">2.3.2</a>, <a class="iref" href="#rfc.xref.RFC2046.3">3.2.1</a>, <a class="iref" href="#RFC2046"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.RFC2046.4">A.2</a><ul class="ind"> … … 2269 2230 </ul> 2270 2231 </li> 2271 <li class="indline1"><em>RFC2068</em> <a class="iref" href="#rfc.xref.RFC2068.1">9.1</a>, <a class="iref" href="#rfc.xref.RFC2068.2">9.1</a>, <a class="iref" href="# rfc.xref.RFC2068.3">9.1</a>, <a class="iref" href="#RFC2068"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC2068.4">B</a>, <a class="iref" href="#rfc.xref.RFC2068.5">C.1</a><ul class="ind">2272 <li class="indline1"><em>Section 19.6.2</em> <a class="iref" href="#rfc.xref.RFC2068. 5">C.1</a></li>2232 <li class="indline1"><em>RFC2068</em> <a class="iref" href="#rfc.xref.RFC2068.1">9.1</a>, <a class="iref" href="#rfc.xref.RFC2068.2">9.1</a>, <a class="iref" href="#RFC2068"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC2068.3">B</a>, <a class="iref" href="#rfc.xref.RFC2068.4">C.1</a><ul class="ind"> 2233 <li class="indline1"><em>Section 19.6.2</em> <a class="iref" href="#rfc.xref.RFC2068.4">C.1</a></li> 2273 2234 </ul> 2274 2235 </li> -
draft-ietf-httpbis/latest/p3-payload.xml
r671 r673 33 33 <!ENTITY qvalue "<xref target='Part1' x:rel='#quality.values' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 34 34 <!ENTITY uri "<xref target='Part1' x:rel='#uri' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 35 <!ENTITY compress-coding "<xref target='Part1' x:rel='#compress.coding' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 36 <!ENTITY deflate-coding "<xref target='Part1' x:rel='#deflate.coding' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 37 <!ENTITY gzip-coding "<xref target='Part1' x:rel='#gzip.coding' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 35 38 ]> 36 39 <?rfc toc="yes" ?> … … 481 484 </t> 482 485 <t> 483 The Internet Assigned Numbers Authority (IANA) acts as a registry for 484 content-coding value tokens. Initially, the registry contains the 485 following tokens: 486 </t> 487 <t> 488 gzip<iref item="gzip"/> 486 compress<iref item="compress (Coding Format)"/><iref item="Coding Format" subitem="compress"/> 489 487 <list> 490 488 <t> 491 An encoding format produced by the file compression program 492 "gzip" (GNU zip) as described in <xref target="RFC1952"/>. This format is a 493 Lempel-Ziv coding (LZ77) with a 32 bit CRC. 489 See &compress-coding;. 494 490 </t> 495 491 </list> 496 492 </t> 497 493 <t> 498 compress<iref item="compress"/> 499 <list><t> 500 The encoding format produced by the common UNIX file compression 501 program "compress". This format is an adaptive Lempel-Ziv-Welch 502 coding (LZW). 503 </t><t> 504 Use of program names for the identification of encoding formats 505 is not desirable and is discouraged for future encodings. Their 506 use here is representative of historical practice, not good 507 design. For compatibility with previous implementations of HTTP, 508 applications &SHOULD; consider "x-gzip" and "x-compress" to be 509 equivalent to "gzip" and "compress" respectively. 510 </t></list> 511 </t> 512 <t> 513 deflate<iref item="deflate"/> 514 <list><t> 515 The "zlib" format defined in <xref target="RFC1950"/> in combination with 516 the "deflate" compression mechanism described in <xref target="RFC1951"/>. 517 </t></list> 518 </t> 519 <t> 520 identity<iref item="identity"/> 494 deflate<iref item="deflate (Coding Format)"/><iref item="Coding Format" subitem="deflate"/> 495 <list> 496 <t> 497 See &deflate-coding;. 498 </t> 499 </list> 500 </t> 501 <t> 502 gzip<iref item="gzip (Coding Format)"/><iref item="Coding Format" subitem="gzip"/> 503 <list> 504 <t> 505 See &gzip-coding;. 506 </t> 507 </list> 508 </t> 509 <t> 510 identity<iref item="identity (Coding Format)"/><iref item="Coding Format" subitem="identity"/> 521 511 <list><t> 522 512 The default (identity) encoding; the use of no transformation … … 1691 1681 </section> 1692 1682 1693 <section title="Transfer Coding Registry" anchor="transfer.coding.registration">1694 <t>1695 The HTTP Transfer Codings Registry located at <eref target="http://www.iana.org/assignments/http-parameters"/>1696 should be updated with the registrations below:1697 </t>1698 <texttable align="left" suppress-title="true" anchor="iana.transfer.coding.registration.table">1699 <ttcol>Name</ttcol>1700 <ttcol>Description</ttcol>1701 <ttcol>Reference</ttcol>1702 <c>compress</c>1703 <c>UNIX "compress" program method</c>1704 <c>1705 <xref target="content.codings"/>1706 </c>1707 <c>deflate</c>1708 <c>"zlib" format <xref target="RFC1950"/> with "deflate" compression</c>1709 <c>1710 <xref target="content.codings"/>1711 </c>1712 <c>gzip</c>1713 <c>Same as GNU zip <xref target="RFC1952"/></c>1714 <c>1715 <xref target="content.codings"/>1716 </c>1717 </texttable>1718 </section>1719 1720 1683 <section title="Content Coding Registry" anchor="content.coding.registration"> 1721 1684 <t> … … 1725 1688 <t> 1726 1689 The HTTP Content Codings Registry located at <eref target="http://www.iana.org/assignments/http-parameters"/> 1727 should be updated with the registration sbelow:1690 should be updated with the registration below: 1728 1691 </t> 1729 1692 <texttable align="left" suppress-title="true" anchor="iana.content.coding.registration.table"> … … 1734 1697 <c>UNIX "compress" program method</c> 1735 1698 <c> 1736 <xref target="content.codings"/>1699 &compress-coding; 1737 1700 </c> 1738 1701 <c>deflate</c> 1739 1702 <c>"zlib" format <xref target="RFC1950"/> with "deflate" compression</c> 1740 1703 <c> 1741 <xref target="content.codings"/>1704 &deflate-coding; 1742 1705 </c> 1743 1706 <c>gzip</c> 1744 1707 <c>Same as GNU zip <xref target="RFC1952"/></c> 1745 1708 <c> 1746 <xref target="content.codings"/>1709 &gzip-coding; 1747 1710 </c> 1748 1711 <c>identity</c> … … 2097 2060 <annotation> 2098 2061 RFC 1950 is an Informational RFC, thus it may be less stable than 2099 this specification. On the other hand, this downward reference was2100 present since the publication of RFC 2068 in 1997 (<xref target="RFC2068"/>),2101 therefore it is unlikely to cause problems in practice. See also2102 <xref target="BCP97"/>.2103 </annotation>2104 </reference>2105 2106 <reference anchor="RFC1951">2107 <front>2108 <title>DEFLATE Compressed Data Format Specification version 1.3</title>2109 <author initials="P." surname="Deutsch" fullname="L. Peter Deutsch">2110 <organization>Aladdin Enterprises</organization>2111 <address><email>ghost@aladdin.com</email></address>2112 </author>2113 <date month="May" year="1996"/>2114 </front>2115 <seriesInfo name="RFC" value="1951"/>2116 <annotation>2117 RFC 1951 is an Informational RFC, thus it may be less stable than2118 2062 this specification. On the other hand, this downward reference was 2119 2063 present since the publication of RFC 2068 in 1997 (<xref target="RFC2068"/>), … … 3135 3079 "pick IANA policy (RFC5226) for Transfer Coding / Content Coding" 3136 3080 </t> 3081 <t> 3082 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/189"/>: 3083 "move definitions of gzip/deflate/compress to part 1" 3084 </t> 3137 3085 </list> 3138 3086 </t>
Note: See TracChangeset
for help on using the changeset viewer.