Changeset 673 for draft-ietf-httpbis/latest/p3-payload.html
- Timestamp:
- 07/08/09 16:46:40 (13 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
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>
Note: See TracChangeset
for help on using the changeset viewer.