![(please configure the [header_logo] section in trac.ini)](https://www.ietf.org/images/ietflogotrans.gif)
Changeset 1647 for draft-ietf-httpbis/latest/p2-semantics.html
- Timestamp:
- Mar 30, 2012, 8:57:47 AM (8 years ago)
- File:
-
- 1 edited
-
draft-ietf-httpbis/latest/p2-semantics.html (modified) (78 diffs)
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r1646 r1647 493 493 <link rel="Chapter" title="10 Acknowledgments" href="#rfc.section.10"> 494 494 <link rel="Chapter" href="#rfc.section.11" title="11 References"> 495 <link rel="Appendix" title="A Changes from RFC 2616" href="#rfc.section.A"> 496 <link rel="Appendix" title="B Collected ABNF" href="#rfc.section.B"> 497 <link rel="Appendix" title="C Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.C"> 498 <link rel="Appendix" title="D THE TEXT FORMERLY KNOWN AS PART3" href="#rfc.section.D"> 495 <link rel="Appendix" title="A Differences between HTTP and MIME" href="#rfc.section.A"> 496 <link rel="Appendix" title="B Additional Features" href="#rfc.section.B"> 497 <link rel="Appendix" title="C Changes from RFC 2616" href="#rfc.section.C"> 498 <link rel="Appendix" title="D Collected ABNF" href="#rfc.section.D"> 499 <link rel="Appendix" title="E Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.E"> 500 <link rel="Appendix" title="F THE TEXT FORMERLY KNOWN AS PART3" href="#rfc.section.F"> 499 501 <link href="p1-messaging.html" rel="prev"> 500 502 <link href="p3-payload.html" rel="next"> … … 560 562 <p>The current issues list is at <<a href="http://tools.ietf.org/wg/httpbis/trac/report/3">http://tools.ietf.org/wg/httpbis/trac/report/3</a>> and related documents (including fancy diffs) can be found at <<a href="http://tools.ietf.org/wg/httpbis/">http://tools.ietf.org/wg/httpbis/</a>>. 561 563 </p> 562 <p>The changes in this draft are summarized in <a href="#changes.since.19" title="Since draft-ietf-httpbis-p2-semantics-19">Appendix C.21</a>.564 <p>The changes in this draft are summarized in <a href="#changes.since.19" title="Since draft-ietf-httpbis-p2-semantics-19">Appendix E.21</a>. 563 565 </p> 564 566 <h1><a id="rfc.status" href="#rfc.status">Status of This Memo</a></h1> … … 750 752 </li> 751 753 <li><a href="#rfc.authors">Authors' Addresses</a></li> 752 <li>A. <a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li> 753 <li>B. <a href="#collected.abnf">Collected ABNF</a></li> 754 <li>C. <a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul> 755 <li>C.1 <a href="#rfc.section.C.1">Since RFC 2616</a></li> 756 <li>C.2 <a href="#rfc.section.C.2">Since draft-ietf-httpbis-p2-semantics-00</a></li> 757 <li>C.3 <a href="#rfc.section.C.3">Since draft-ietf-httpbis-p2-semantics-01</a></li> 758 <li>C.4 <a href="#changes.since.02">Since draft-ietf-httpbis-p2-semantics-02</a></li> 759 <li>C.5 <a href="#changes.since.03">Since draft-ietf-httpbis-p2-semantics-03</a></li> 760 <li>C.6 <a href="#changes.since.04">Since draft-ietf-httpbis-p2-semantics-04</a></li> 761 <li>C.7 <a href="#changes.since.05">Since draft-ietf-httpbis-p2-semantics-05</a></li> 762 <li>C.8 <a href="#changes.since.06">Since draft-ietf-httpbis-p2-semantics-06</a></li> 763 <li>C.9 <a href="#changes.since.07">Since draft-ietf-httpbis-p2-semantics-07</a></li> 764 <li>C.10 <a href="#changes.since.08">Since draft-ietf-httpbis-p2-semantics-08</a></li> 765 <li>C.11 <a href="#changes.since.09">Since draft-ietf-httpbis-p2-semantics-09</a></li> 766 <li>C.12 <a href="#changes.since.10">Since draft-ietf-httpbis-p2-semantics-10</a></li> 767 <li>C.13 <a href="#changes.since.11">Since draft-ietf-httpbis-p2-semantics-11</a></li> 768 <li>C.14 <a href="#changes.since.12">Since draft-ietf-httpbis-p2-semantics-12</a></li> 769 <li>C.15 <a href="#changes.since.13">Since draft-ietf-httpbis-p2-semantics-13</a></li> 770 <li>C.16 <a href="#changes.since.14">Since draft-ietf-httpbis-p2-semantics-14</a></li> 771 <li>C.17 <a href="#changes.since.15">Since draft-ietf-httpbis-p2-semantics-15</a></li> 772 <li>C.18 <a href="#changes.since.16">Since draft-ietf-httpbis-p2-semantics-16</a></li> 773 <li>C.19 <a href="#changes.since.17">Since draft-ietf-httpbis-p2-semantics-17</a></li> 774 <li>C.20 <a href="#changes.since.18">Since draft-ietf-httpbis-p2-semantics-18</a></li> 775 <li>C.21 <a href="#changes.since.19">Since draft-ietf-httpbis-p2-semantics-19</a></li> 754 <li>A. <a href="#differences.between.http.and.mime">Differences between HTTP and MIME</a><ul> 755 <li>A.1 <a href="#mime-version">MIME-Version</a></li> 756 <li>A.2 <a href="#conversion.to.canonical.form">Conversion to Canonical Form</a></li> 757 <li>A.3 <a href="#conversion.of.date.formats">Conversion of Date Formats</a></li> 758 <li>A.4 <a href="#introduction.of.content-encoding">Introduction of Content-Encoding</a></li> 759 <li>A.5 <a href="#no.content-transfer-encoding">No Content-Transfer-Encoding</a></li> 760 <li>A.6 <a href="#introduction.of.transfer-encoding">Introduction of Transfer-Encoding</a></li> 761 <li>A.7 <a href="#mhtml.line.length">MHTML and Line Length Limitations</a></li> 776 762 </ul> 777 763 </li> 778 <li>D. <a href="#rfc.section.D">THE TEXT FORMERLY KNOWN AS PART3</a><ul> 779 <li>D.1 <a href="#payload">Payload</a><ul> 780 <li>D.1.1 <a href="#payload.header.fields">Payload Header Fields</a></li> 781 <li>D.1.2 <a href="#payload.body">Payload Body</a></li> 764 <li>B. <a href="#additional.features">Additional Features</a></li> 765 <li>C. <a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li> 766 <li>D. <a href="#collected.abnf">Collected ABNF</a></li> 767 <li>E. <a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul> 768 <li>E.1 <a href="#rfc.section.E.1">Since RFC 2616</a></li> 769 <li>E.2 <a href="#rfc.section.E.2">Since draft-ietf-httpbis-p2-semantics-00</a></li> 770 <li>E.3 <a href="#rfc.section.E.3">Since draft-ietf-httpbis-p2-semantics-01</a></li> 771 <li>E.4 <a href="#changes.since.02">Since draft-ietf-httpbis-p2-semantics-02</a></li> 772 <li>E.5 <a href="#changes.since.03">Since draft-ietf-httpbis-p2-semantics-03</a></li> 773 <li>E.6 <a href="#changes.since.04">Since draft-ietf-httpbis-p2-semantics-04</a></li> 774 <li>E.7 <a href="#changes.since.05">Since draft-ietf-httpbis-p2-semantics-05</a></li> 775 <li>E.8 <a href="#changes.since.06">Since draft-ietf-httpbis-p2-semantics-06</a></li> 776 <li>E.9 <a href="#changes.since.07">Since draft-ietf-httpbis-p2-semantics-07</a></li> 777 <li>E.10 <a href="#changes.since.08">Since draft-ietf-httpbis-p2-semantics-08</a></li> 778 <li>E.11 <a href="#changes.since.09">Since draft-ietf-httpbis-p2-semantics-09</a></li> 779 <li>E.12 <a href="#changes.since.10">Since draft-ietf-httpbis-p2-semantics-10</a></li> 780 <li>E.13 <a href="#changes.since.11">Since draft-ietf-httpbis-p2-semantics-11</a></li> 781 <li>E.14 <a href="#changes.since.12">Since draft-ietf-httpbis-p2-semantics-12</a></li> 782 <li>E.15 <a href="#changes.since.13">Since draft-ietf-httpbis-p2-semantics-13</a></li> 783 <li>E.16 <a href="#changes.since.14">Since draft-ietf-httpbis-p2-semantics-14</a></li> 784 <li>E.17 <a href="#changes.since.15">Since draft-ietf-httpbis-p2-semantics-15</a></li> 785 <li>E.18 <a href="#changes.since.16">Since draft-ietf-httpbis-p2-semantics-16</a></li> 786 <li>E.19 <a href="#changes.since.17">Since draft-ietf-httpbis-p2-semantics-17</a></li> 787 <li>E.20 <a href="#changes.since.18">Since draft-ietf-httpbis-p2-semantics-18</a></li> 788 <li>E.21 <a href="#changes.since.19">Since draft-ietf-httpbis-p2-semantics-19</a></li> 789 </ul> 790 </li> 791 <li>F. <a href="#rfc.section.F">THE TEXT FORMERLY KNOWN AS PART3</a><ul> 792 <li>F.1 <a href="#payload">Payload</a><ul> 793 <li>F.1.1 <a href="#payload.header.fields">Payload Header Fields</a></li> 794 <li>F.1.2 <a href="#payload.body">Payload Body</a></li> 782 795 </ul> 783 796 </li> 784 <li> D.2 <a href="#representation3">Representation</a><ul>785 <li> D.2.1 <a href="#representation.header.fields">Representation Header Fields</a></li>786 <li> D.2.2 <a href="#representation.data">Representation Data</a></li>797 <li>F.2 <a href="#representation3">Representation</a><ul> 798 <li>F.2.1 <a href="#representation.header.fields">Representation Header Fields</a></li> 799 <li>F.2.2 <a href="#representation.data">Representation Data</a></li> 787 800 </ul> 788 801 </li> 789 <li> D.3 <a href="#content.negotiation">Content Negotiation</a><ul>790 <li> D.3.1 <a href="#server-driven.negotiation">Server-driven Negotiation</a></li>791 <li> D.3.2 <a href="#agent-driven.negotiation">Agent-driven Negotiation</a></li>802 <li>F.3 <a href="#content.negotiation">Content Negotiation</a><ul> 803 <li>F.3.1 <a href="#server-driven.negotiation">Server-driven Negotiation</a></li> 804 <li>F.3.2 <a href="#agent-driven.negotiation">Agent-driven Negotiation</a></li> 792 805 </ul> 793 806 </li> 794 <li>D.4 <a href="#differences.between.http.and.mime">Differences between HTTP and MIME</a><ul> 795 <li>D.4.1 <a href="#mime-version">MIME-Version</a></li> 796 <li>D.4.2 <a href="#conversion.to.canonical.form">Conversion to Canonical Form</a></li> 797 <li>D.4.3 <a href="#conversion.of.date.formats">Conversion of Date Formats</a></li> 798 <li>D.4.4 <a href="#introduction.of.content-encoding">Introduction of Content-Encoding</a></li> 799 <li>D.4.5 <a href="#no.content-transfer-encoding">No Content-Transfer-Encoding</a></li> 800 <li>D.4.6 <a href="#introduction.of.transfer-encoding">Introduction of Transfer-Encoding</a></li> 801 <li>D.4.7 <a href="#mhtml.line.length">MHTML and Line Length Limitations</a></li> 802 </ul> 803 </li> 804 <li>D.5 <a href="#additional.features">Additional Features</a></li> 805 <li>D.6 <a href="#changes.from.rfc.2616-3">Changes from RFC 2616</a></li> 806 <li>D.7 <a href="#change.log3">Change Log (to be removed by RFC Editor before publication)</a><ul> 807 <li>D.7.1 <a href="#rfc.section.D.7.1">Since RFC 2616</a></li> 808 <li>D.7.2 <a href="#rfc.section.D.7.2">Since draft-ietf-httpbis-p3-payload-00</a></li> 809 <li>D.7.3 <a href="#rfc.section.D.7.3">Since draft-ietf-httpbis-p3-payload-01</a></li> 810 <li>D.7.4 <a href="#changes.3.since.02">Since draft-ietf-httpbis-p3-payload-02</a></li> 811 <li>D.7.5 <a href="#changes.3.since.03">Since draft-ietf-httpbis-p3-payload-03</a></li> 812 <li>D.7.6 <a href="#changes.3.since.04">Since draft-ietf-httpbis-p3-payload-04</a></li> 813 <li>D.7.7 <a href="#changes.3.since.05">Since draft-ietf-httpbis-p3-payload-05</a></li> 814 <li>D.7.8 <a href="#changes.3.since.06">Since draft-ietf-httpbis-p3-payload-06</a></li> 815 <li>D.7.9 <a href="#changes.3.since.07">Since draft-ietf-httpbis-p3-payload-07</a></li> 816 <li>D.7.10 <a href="#changes.3.since.08">Since draft-ietf-httpbis-p3-payload-08</a></li> 817 <li>D.7.11 <a href="#changes.3.since.09">Since draft-ietf-httpbis-p3-payload-09</a></li> 818 <li>D.7.12 <a href="#changes.3.since.10">Since draft-ietf-httpbis-p3-payload-10</a></li> 819 <li>D.7.13 <a href="#changes.3.since.11">Since draft-ietf-httpbis-p3-payload-11</a></li> 820 <li>D.7.14 <a href="#changes.3.since.12">Since draft-ietf-httpbis-p3-payload-12</a></li> 821 <li>D.7.15 <a href="#changes.3.since.13">Since draft-ietf-httpbis-p3-payload-13</a></li> 822 <li>D.7.16 <a href="#changes.3.since.14">Since draft-ietf-httpbis-p3-payload-14</a></li> 823 <li>D.7.17 <a href="#changes.3.since.15">Since draft-ietf-httpbis-p3-payload-15</a></li> 824 <li>D.7.18 <a href="#changes.3.since.16">Since draft-ietf-httpbis-p3-payload-16</a></li> 825 <li>D.7.19 <a href="#changes.3.since.17">Since draft-ietf-httpbis-p3-payload-17</a></li> 826 <li>D.7.20 <a href="#changes.3.since.18">Since draft-ietf-httpbis-p3-payload-18</a></li> 827 <li>D.7.21 <a href="#changes.3.since.19">Since draft-ietf-httpbis-p3-payload-19</a></li> 807 <li>F.4 <a href="#change.log3">Change Log (to be removed by RFC Editor before publication)</a><ul> 808 <li>F.4.1 <a href="#rfc.section.F.4.1">Since RFC 2616</a></li> 809 <li>F.4.2 <a href="#rfc.section.F.4.2">Since draft-ietf-httpbis-p3-payload-00</a></li> 810 <li>F.4.3 <a href="#rfc.section.F.4.3">Since draft-ietf-httpbis-p3-payload-01</a></li> 811 <li>F.4.4 <a href="#changes.3.since.02">Since draft-ietf-httpbis-p3-payload-02</a></li> 812 <li>F.4.5 <a href="#changes.3.since.03">Since draft-ietf-httpbis-p3-payload-03</a></li> 813 <li>F.4.6 <a href="#changes.3.since.04">Since draft-ietf-httpbis-p3-payload-04</a></li> 814 <li>F.4.7 <a href="#changes.3.since.05">Since draft-ietf-httpbis-p3-payload-05</a></li> 815 <li>F.4.8 <a href="#changes.3.since.06">Since draft-ietf-httpbis-p3-payload-06</a></li> 816 <li>F.4.9 <a href="#changes.3.since.07">Since draft-ietf-httpbis-p3-payload-07</a></li> 817 <li>F.4.10 <a href="#changes.3.since.08">Since draft-ietf-httpbis-p3-payload-08</a></li> 818 <li>F.4.11 <a href="#changes.3.since.09">Since draft-ietf-httpbis-p3-payload-09</a></li> 819 <li>F.4.12 <a href="#changes.3.since.10">Since draft-ietf-httpbis-p3-payload-10</a></li> 820 <li>F.4.13 <a href="#changes.3.since.11">Since draft-ietf-httpbis-p3-payload-11</a></li> 821 <li>F.4.14 <a href="#changes.3.since.12">Since draft-ietf-httpbis-p3-payload-12</a></li> 822 <li>F.4.15 <a href="#changes.3.since.13">Since draft-ietf-httpbis-p3-payload-13</a></li> 823 <li>F.4.16 <a href="#changes.3.since.14">Since draft-ietf-httpbis-p3-payload-14</a></li> 824 <li>F.4.17 <a href="#changes.3.since.15">Since draft-ietf-httpbis-p3-payload-15</a></li> 825 <li>F.4.18 <a href="#changes.3.since.16">Since draft-ietf-httpbis-p3-payload-16</a></li> 826 <li>F.4.19 <a href="#changes.3.since.17">Since draft-ietf-httpbis-p3-payload-17</a></li> 827 <li>F.4.20 <a href="#changes.3.since.18">Since draft-ietf-httpbis-p3-payload-18</a></li> 828 <li>F.4.21 <a href="#changes.3.since.19">Since draft-ietf-httpbis-p3-payload-19</a></li> 828 829 </ul> 829 830 </li> … … 883 884 </p> 884 885 <h2 id="rfc.section.1.3"><a href="#rfc.section.1.3">1.3</a> <a id="notation" href="#notation">Syntax Notation</a></h2> 885 <p id="rfc.section.1.3.p.1">This specification uses the Augmented Backus-Naur Form (ABNF) notation of <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with the list rule extension defined in <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#Part1" id="rfc.xref.Part1.3"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. <a href="#collected.abnf" title="Collected ABNF">Appendix B</a> shows the collected ABNF with the list rule expanded.886 <p id="rfc.section.1.3.p.1">This specification uses the Augmented Backus-Naur Form (ABNF) notation of <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with the list rule extension defined in <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#Part1" id="rfc.xref.Part1.3"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. <a href="#collected.abnf" title="Collected ABNF">Appendix D</a> shows the collected ABNF with the list rule expanded. 886 887 </p> 887 888 <p id="rfc.section.1.3.p.2">The following core rules are included by reference, as defined in <a href="#RFC5234" id="rfc.xref.RFC5234.2"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>, <a href="http://tools.ietf.org/html/rfc5234#appendix-B.1">Appendix B.1</a>: ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double quote), HEXDIG … … 1804 1805 </li> 1805 1806 <li> 1806 <p>Redirection offering a choice of matching resources for use by agent-driven content negotiation (<a href="#agent-driven.negotiation" title="Agent-driven Negotiation">Appendix D.3.2</a>). This is status code 300 (Multiple Choices).1807 <p>Redirection offering a choice of matching resources for use by agent-driven content negotiation (<a href="#agent-driven.negotiation" title="Agent-driven Negotiation">Appendix F.3.2</a>). This is status code 300 (Multiple Choices). 1807 1808 </p> 1808 1809 </li> … … 1836 1837 <h3 id="rfc.section.4.5.1"><a href="#rfc.section.4.5.1">4.5.1</a> <a id="status.300" href="#status.300">300 Multiple Choices</a></h3> 1837 1838 <p id="rfc.section.4.5.1.p.1">The target resource has more than one representation, each with its own specific location, and agent-driven negotiation information 1838 (<a href="#content.negotiation" title="Content Negotiation">Appendix D.3</a>) is being provided so that the user (or user agent) can select a preferred representation by redirecting its request to that1839 (<a href="#content.negotiation" title="Content Negotiation">Appendix F.3</a>) is being provided so that the user (or user agent) can select a preferred representation by redirecting its request to that 1839 1840 location. 1840 1841 </p> … … 1900 1901 <div id="rfc.iref.s.15"></div> 1901 1902 <h3 id="rfc.section.4.5.5"><a href="#rfc.section.4.5.5">4.5.5</a> <a id="status.305" href="#status.305">305 Use Proxy</a></h3> 1902 <p id="rfc.section.4.5.5.p.1">The 305 status code was defined in a previous version of this specification (see <a href="#changes.from.rfc.2616" title="Changes from RFC 2616">Appendix A</a>), and is now deprecated.1903 <p id="rfc.section.4.5.5.p.1">The 305 status code was defined in a previous version of this specification (see <a href="#changes.from.rfc.2616" title="Changes from RFC 2616">Appendix C</a>), and is now deprecated. 1903 1904 </p> 1904 1905 <div id="rfc.iref.34"></div> … … 2692 2693 </p> 2693 2694 <div id="rfc.figure.u.43"></div><pre class="text"> Content-Type: text/html; charset=ISO-8859-4 2694 </pre><p id="rfc.section.7.9.p.5">Further discussion of Content-Type is provided in <a href="#representation.data" title="Representation Data">Appendix D.2.2</a>.2695 </pre><p id="rfc.section.7.9.p.5">Further discussion of Content-Type is provided in <a href="#representation.data" title="Representation Data">Appendix F.2.2</a>. 2695 2696 </p> 2696 2697 <div id="rfc.iref.d.3"></div> … … 3304 3305 <td class="left">http</td> 3305 3306 <td class="left">standard</td> 3306 <td class="left"> <a href="#mime-version" id="rfc.xref.mime-version.1" title="MIME-Version">Appendix D.4.1</a>3307 <td class="left"> <a href="#mime-version" id="rfc.xref.mime-version.1" title="MIME-Version">Appendix A.1</a> 3307 3308 </td> 3308 3309 </tr> … … 3677 3678 <span class="n hidden"><span class="family-name">Reschke</span><span class="given-name">Julian F.</span></span></span><span class="org vcardline">greenbytes GmbH</span><span class="adr"><span class="street-address vcardline">Hafenweg 16</span><span class="vcardline"><span class="locality">Muenster</span>, <span class="region">NW</span> <span class="postal-code">48155</span></span><span class="country-name vcardline">Germany</span></span><span class="vcardline tel">Phone: <a href="tel:+492512807760"><span class="value">+49 251 2807760</span></a></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+492512807761"><span class="value">+49 251 2807761</span></a></span><span class="vcardline">Email: <a href="mailto:julian.reschke@greenbytes.de"><span class="email">julian.reschke@greenbytes.de</span></a></span><span class="vcardline">URI: <a href="http://greenbytes.de/tech/webdav/" class="url">http://greenbytes.de/tech/webdav/</a></span></address> 3678 3679 </div> 3679 <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a> <a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h1> 3680 <p id="rfc.section.A.p.1">Clarify definition of POST. (<a href="#POST" id="rfc.xref.POST.2" title="POST">Section 2.3.4</a>) 3681 </p> 3682 <p id="rfc.section.A.p.2">Remove requirement to handle all Content-* header fields; ban use of Content-Range with PUT. (<a href="#PUT" id="rfc.xref.PUT.2" title="PUT">Section 2.3.5</a>) 3683 </p> 3684 <p id="rfc.section.A.p.3">Take over definition of CONNECT method from <a href="#RFC2817" id="rfc.xref.RFC2817.2"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>. (<a href="#CONNECT" id="rfc.xref.CONNECT.2" title="CONNECT">Section 2.3.8</a>) 3685 </p> 3686 <p id="rfc.section.A.p.4">This document takes over the Status Code Registry, previously defined in <a href="http://tools.ietf.org/html/rfc2817#section-7.1">Section 7.1</a> of <a href="#RFC2817" id="rfc.xref.RFC2817.3"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>. (<a href="#status.code.registry" title="Status Code Registry">Section 4.2</a>) 3687 </p> 3688 <p id="rfc.section.A.p.5">Broadened the definition of 203 (Non-Authoritative Information) to include cases of payload transformations as well. (<a href="#status.203" id="rfc.xref.status.203.3" title="203 Non-Authoritative Information">Section 4.4.4</a>) 3689 </p> 3690 <p id="rfc.section.A.p.6">Status codes 301, 302, and 307: removed the normative requirements on both response payloads and user interaction. (<a href="#status.3xx" title="Redirection 3xx">Section 4.5</a>) 3691 </p> 3692 <p id="rfc.section.A.p.7">Failed to consider that there are many other request methods that are safe to automatically redirect, and further that the 3680 <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a> <a id="differences.between.http.and.mime" href="#differences.between.http.and.mime">Differences between HTTP and MIME</a></h1> 3681 <p id="rfc.section.A.p.1">HTTP/1.1 uses many of the constructs defined for Internet Mail (<a href="#RFC5322" id="rfc.xref.RFC5322.5"><cite title="Internet Message Format">[RFC5322]</cite></a>) and the Multipurpose Internet Mail Extensions (MIME <a href="#RFC2045" id="rfc.xref.RFC2045.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies">[RFC2045]</cite></a>) to allow a message body to be transmitted in an open variety of representations and with extensible mechanisms. However, 3682 RFC 2045 discusses mail, and HTTP has a few features that are different from those described in MIME. These differences were 3683 carefully chosen to optimize performance over binary connections, to allow greater freedom in the use of new media types, 3684 to make date comparisons easier, and to acknowledge the practice of some early HTTP servers and clients. 3685 </p> 3686 <p id="rfc.section.A.p.2">This appendix describes specific areas where HTTP differs from MIME. Proxies and gateways to strict MIME environments <em class="bcp14">SHOULD</em> be aware of these differences and provide the appropriate conversions where necessary. Proxies and gateways from MIME environments 3687 to HTTP also need to be aware of the differences because some conversions might be required. 3688 </p> 3689 <div id="rfc.iref.m.10"></div> 3690 <div id="rfc.iref.h.20"></div> 3691 <h2 id="rfc.section.A.1"><a href="#rfc.section.A.1">A.1</a> <a id="mime-version" href="#mime-version">MIME-Version</a></h2> 3692 <p id="rfc.section.A.1.p.1">HTTP is not a MIME-compliant protocol. However, HTTP/1.1 messages <em class="bcp14">MAY</em> include a single MIME-Version header field to indicate what version of the MIME protocol was used to construct the message. 3693 Use of the MIME-Version header field indicates that the message is in full conformance with the MIME protocol (as defined 3694 in <a href="#RFC2045" id="rfc.xref.RFC2045.2"><cite title="Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies">[RFC2045]</cite></a>). Proxies/gateways are responsible for ensuring full conformance (where possible) when exporting HTTP messages to strict 3695 MIME environments. 3696 </p> 3697 <div id="rfc.figure.u.62"></div><pre class="inline"><span id="rfc.iref.g.59"></span> <a href="#mime-version" class="smpl">MIME-Version</a> = 1*<a href="#notation" class="smpl">DIGIT</a> "." 1*<a href="#notation" class="smpl">DIGIT</a> 3698 </pre><p id="rfc.section.A.1.p.3">MIME version "1.0" is the default for use in HTTP/1.1. However, HTTP/1.1 message parsing and semantics are defined by this 3699 document and not the MIME specification. 3700 </p> 3701 <h2 id="rfc.section.A.2"><a href="#rfc.section.A.2">A.2</a> <a id="conversion.to.canonical.form" href="#conversion.to.canonical.form">Conversion to Canonical Form</a></h2> 3702 <p id="rfc.section.A.2.p.1">MIME requires that an Internet mail body-part be converted to canonical form prior to being transferred, as described in <a href="http://tools.ietf.org/html/rfc2049#section-4">Section 4</a> of <a href="#RFC2049" id="rfc.xref.RFC2049.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples">[RFC2049]</cite></a>. <a href="#canonicalization.and.text.defaults" title="Canonicalization and Text Defaults">Section 6.5.1</a> of this document describes the forms allowed for subtypes of the "text" media type when transmitted over HTTP. <a href="#RFC2046" id="rfc.xref.RFC2046.3"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a> requires that content with a type of "text" represent line breaks as CRLF and forbids the use of CR or LF outside of line 3703 break sequences. HTTP allows CRLF, bare CR, and bare LF to indicate a line break within text content when a message is transmitted 3704 over HTTP. 3705 </p> 3706 <p id="rfc.section.A.2.p.2">Where it is possible, a proxy or gateway from HTTP to a strict MIME environment <em class="bcp14">SHOULD</em> translate all line breaks within the text media types described in <a href="#canonicalization.and.text.defaults" title="Canonicalization and Text Defaults">Section 6.5.1</a> of this document to the RFC 2049 canonical form of CRLF. Note, however, that this might be complicated by the presence of 3707 a Content-Encoding and by the fact that HTTP allows the use of some character encodings which do not use octets 13 and 10 3708 to represent CR and LF, respectively, as is the case for some multi-byte character encodings. 3709 </p> 3710 <p id="rfc.section.A.2.p.3">Conversion will break any cryptographic checksums applied to the original content unless the original content is already in 3711 canonical form. Therefore, the canonical form is recommended for any content that uses such checksums in HTTP. 3712 </p> 3713 <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> 3714 <p id="rfc.section.A.3.p.1">HTTP/1.1 uses a restricted set of date formats (<a href="#http.date" title="Date/Time Formats">Section 6.1</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. 3715 </p> 3716 <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> 3717 <p id="rfc.section.A.4.p.1">MIME does not include any concept equivalent to HTTP/1.1's Content-Encoding header field. Since this acts as a modifier on 3718 the media type, proxies and gateways from HTTP to MIME-compliant protocols <em class="bcp14">MUST</em> either change the value of the Content-Type header field or decode the representation before forwarding the message. (Some 3719 experimental applications of Content-Type for Internet mail have used a media-type parameter of ";conversions=<content-coding>" 3720 to perform a function equivalent to Content-Encoding. However, this parameter is not part of the MIME standards). 3721 </p> 3722 <div id="rfc.iref.c.11"></div> 3723 <div id="rfc.iref.h.21"></div> 3724 <h2 id="rfc.section.A.5"><a href="#rfc.section.A.5">A.5</a> <a id="no.content-transfer-encoding" href="#no.content-transfer-encoding">No Content-Transfer-Encoding</a></h2> 3725 <p id="rfc.section.A.5.p.1">HTTP does not use the Content-Transfer-Encoding field of MIME. Proxies and gateways from MIME-compliant protocols to HTTP <em class="bcp14">MUST</em> remove any Content-Transfer-Encoding prior to delivering the response message to an HTTP client. 3726 </p> 3727 <p id="rfc.section.A.5.p.2">Proxies and gateways from HTTP to MIME-compliant protocols are responsible for ensuring that the message is in the correct 3728 format and encoding for safe transport on that protocol, where "safe transport" is defined by the limitations of the protocol 3729 being used. Such a proxy or gateway <em class="bcp14">SHOULD</em> label the data with an appropriate Content-Transfer-Encoding if doing so will improve the likelihood of safe transport over 3730 the destination protocol. 3731 </p> 3732 <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> 3733 <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.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.55"><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. 3734 </p> 3735 <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> 3736 <p id="rfc.section.A.7.p.1">HTTP implementations which share code with MHTML <a href="#RFC2557" id="rfc.xref.RFC2557.2"><cite title="MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)">[RFC2557]</cite></a> implementations need to be aware of MIME line length limitations. Since HTTP does not have this limitation, HTTP does not 3737 fold long lines. MHTML messages being transported by HTTP follow all conventions of MHTML, including line length limitations 3738 and folding, canonicalization, etc., since HTTP transports all message-bodies as payload (see <a href="#multipart.types" title="Multipart Types">Section 6.5.2</a>) and does not interpret the content or any MIME header lines that might be contained therein. 3739 </p> 3740 <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a> <a id="additional.features" href="#additional.features">Additional Features</a></h1> 3741 <p id="rfc.section.B.p.1"> <a href="#RFC1945" id="rfc.xref.RFC1945.2"><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 3742 applications. Implementors are advised to be aware of these features, but cannot rely upon their presence in, or interoperability 3743 with, other HTTP/1.1 applications. Some of these describe proposed experimental features, and some describe features that 3744 experimental deployment found lacking that are now addressed in the base HTTP/1.1 specification. 3745 </p> 3746 <p id="rfc.section.B.p.2">A number of other header fields, such as Content-Disposition and Title, from SMTP and MIME are also often implemented (see <a href="#RFC6266" id="rfc.xref.RFC6266.1"><cite title="Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)">[RFC6266]</cite></a> and <a href="#RFC2076" id="rfc.xref.RFC2076.1"><cite title="Common Internet Message Headers">[RFC2076]</cite></a>). 3747 </p> 3748 <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a> <a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h1> 3749 <p id="rfc.section.C.p.1">Clarify definition of POST. (<a href="#POST" id="rfc.xref.POST.2" title="POST">Section 2.3.4</a>) 3750 </p> 3751 <p id="rfc.section.C.p.2">Remove requirement to handle all Content-* header fields; ban use of Content-Range with PUT. (<a href="#PUT" id="rfc.xref.PUT.2" title="PUT">Section 2.3.5</a>) 3752 </p> 3753 <p id="rfc.section.C.p.3">Take over definition of CONNECT method from <a href="#RFC2817" id="rfc.xref.RFC2817.2"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>. (<a href="#CONNECT" id="rfc.xref.CONNECT.2" title="CONNECT">Section 2.3.8</a>) 3754 </p> 3755 <p id="rfc.section.C.p.4">This document takes over the Status Code Registry, previously defined in <a href="http://tools.ietf.org/html/rfc2817#section-7.1">Section 7.1</a> of <a href="#RFC2817" id="rfc.xref.RFC2817.3"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>. (<a href="#status.code.registry" title="Status Code Registry">Section 4.2</a>) 3756 </p> 3757 <p id="rfc.section.C.p.5">Broadened the definition of 203 (Non-Authoritative Information) to include cases of payload transformations as well. (<a href="#status.203" id="rfc.xref.status.203.3" title="203 Non-Authoritative Information">Section 4.4.4</a>) 3758 </p> 3759 <p id="rfc.section.C.p.6">Status codes 301, 302, and 307: removed the normative requirements on both response payloads and user interaction. (<a href="#status.3xx" title="Redirection 3xx">Section 4.5</a>) 3760 </p> 3761 <p id="rfc.section.C.p.7">Failed to consider that there are many other request methods that are safe to automatically redirect, and further that the 3693 3762 user agent is able to make that determination based on the request method semantics. Furthermore, allow user agents to rewrite 3694 3763 the method from POST to GET for status codes 301 and 302. (Sections <a href="#status.301" id="rfc.xref.status.301.3" title="301 Moved Permanently">4.5.2</a>, <a href="#status.302" id="rfc.xref.status.302.3" title="302 Found">4.5.3</a> and <a href="#status.307" id="rfc.xref.status.307.3" title="307 Temporary Redirect">4.5.7</a>) 3695 3764 </p> 3696 <p id="rfc.section. A.p.8">Deprecate 305 Use Proxy status code, because user agents did not implement it. It used to indicate that the target resource3765 <p id="rfc.section.C.p.8">Deprecate 305 Use Proxy status code, because user agents did not implement it. It used to indicate that the target resource 3697 3766 needs to be accessed through the proxy given by the Location field. The Location field gave the URI of the proxy. The recipient 3698 3767 was expected to repeat this single request via the proxy. (<a href="#status.305" id="rfc.xref.status.305.3" title="305 Use Proxy">Section 4.5.5</a>) 3699 3768 </p> 3700 <p id="rfc.section. A.p.9">Define status 426 (Upgrade Required) (this was incorporated from <a href="#RFC2817" id="rfc.xref.RFC2817.4"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>). (<a href="#status.426" id="rfc.xref.status.426.3" title="426 Upgrade Required">Section 4.6.15</a>)3701 </p> 3702 <p id="rfc.section. A.p.10">Change ABNF productions for header fields to only define the field value. (<a href="#header.field.definitions" title="Header Field Definitions">Section 7</a>)3703 </p> 3704 <p id="rfc.section. A.p.11">Reclassify "Allow" as response header field, removing the option to specify it in a PUT request. Relax the server requirement3769 <p id="rfc.section.C.p.9">Define status 426 (Upgrade Required) (this was incorporated from <a href="#RFC2817" id="rfc.xref.RFC2817.4"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>). (<a href="#status.426" id="rfc.xref.status.426.3" title="426 Upgrade Required">Section 4.6.15</a>) 3770 </p> 3771 <p id="rfc.section.C.p.10">Change ABNF productions for header fields to only define the field value. (<a href="#header.field.definitions" title="Header Field Definitions">Section 7</a>) 3772 </p> 3773 <p id="rfc.section.C.p.11">Reclassify "Allow" as response header field, removing the option to specify it in a PUT request. Relax the server requirement 3705 3774 on the contents of the Allow header field and remove requirement on clients to always trust the header field value. (<a href="#header.allow" id="rfc.xref.header.allow.4" title="Allow">Section 7.5</a>) 3706 3775 </p> 3707 <p id="rfc.section. A.p.12">The ABNF for the Expect header field has been both fixed (allowing parameters for value-less expectations as well) and simplified3776 <p id="rfc.section.C.p.12">The ABNF for the Expect header field has been both fixed (allowing parameters for value-less expectations as well) and simplified 3708 3777 (allowing trailing semicolons after "100-continue" when they were invalid before). (<a href="#header.expect" id="rfc.xref.header.expect.4" title="Expect">Section 7.11</a>) 3709 3778 </p> 3710 <p id="rfc.section. A.p.13">Correct syntax of Location header field to allow URI references (including relative references and fragments), as referred3779 <p id="rfc.section.C.p.13">Correct syntax of Location header field to allow URI references (including relative references and fragments), as referred 3711 3780 symbol "absoluteURI" wasn't what was expected, and add some clarifications as to when use of fragments would not be appropriate. 3712 3781 (<a href="#header.location" id="rfc.xref.header.location.5" title="Location">Section 7.13</a>) 3713 3782 </p> 3714 <p id="rfc.section.A.p.14">Restrict Max-Forwards header field to OPTIONS and TRACE (previously, extension methods could have used it as well). (<a href="#header.max-forwards" id="rfc.xref.header.max-forwards.5" title="Max-Forwards">Section 7.14</a>) 3715 </p> 3716 <p id="rfc.section.A.p.15">Allow Referer field value of "about:blank" as alternative to not specifying it. (<a href="#header.referer" id="rfc.xref.header.referer.3" title="Referer">Section 7.15</a>) 3717 </p> 3718 <p id="rfc.section.A.p.16">In the description of the Server header field, the Via field was described as a SHOULD. The requirement was and is stated 3719 correctly in the description of the Via header field in <a href="p1-messaging.html#header.via" title="Via">Section 6.2</a> of <a href="#Part1" id="rfc.xref.Part1.55"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. (<a href="#header.server" id="rfc.xref.header.server.4" title="Server">Section 7.17</a>) 3720 </p> 3721 <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a> <a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1> 3722 <div id="rfc.figure.u.62"></div> <pre class="inline"><a href="#header.accept" class="smpl">Accept</a> = [ ( "," / ( media-range [ accept-params ] ) ) *( OWS "," [ 3783 <p id="rfc.section.C.p.14">Restrict Max-Forwards header field to OPTIONS and TRACE (previously, extension methods could have used it as well). (<a href="#header.max-forwards" id="rfc.xref.header.max-forwards.5" title="Max-Forwards">Section 7.14</a>) 3784 </p> 3785 <p id="rfc.section.C.p.15">Allow Referer field value of "about:blank" as alternative to not specifying it. (<a href="#header.referer" id="rfc.xref.header.referer.3" title="Referer">Section 7.15</a>) 3786 </p> 3787 <p id="rfc.section.C.p.16">In the description of the Server header field, the Via field was described as a SHOULD. The requirement was and is stated 3788 correctly in the description of the Via header field in <a href="p1-messaging.html#header.via" title="Via">Section 6.2</a> of <a href="#Part1" id="rfc.xref.Part1.56"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. (<a href="#header.server" id="rfc.xref.header.server.4" title="Server">Section 7.17</a>) 3789 </p> 3790 <p id="rfc.section.C.p.17">Clarify contexts that charset is used in. (<a href="#character.sets" title="Character Encodings (charset)">Section 6.3</a>) 3791 </p> 3792 <p id="rfc.section.C.p.18">Registration of Content Codings now requires IETF Review (<a href="#content.coding.registry" title="Content Coding Registry">Section 6.4.1</a>) 3793 </p> 3794 <p id="rfc.section.C.p.19">Remove the default character encoding for text media types; the default now is whatever the media type definition says. (<a href="#canonicalization.and.text.defaults" title="Canonicalization and Text Defaults">Section 6.5.1</a>) 3795 </p> 3796 <p id="rfc.section.C.p.20">Change ABNF productions for header fields to only define the field value. (<a href="#header.field.definitions" title="Header Field Definitions">Section 7</a>) 3797 </p> 3798 <p id="rfc.section.C.p.21">Remove definition of Content-MD5 header field because it was inconsistently implemented with respect to partial responses, 3799 and also because of known deficiencies in the hash algorithm itself (see <a href="#RFC6151" id="rfc.xref.RFC6151.1"><cite title="Updated Security Considerations for the MD5 Message-Digest and the HMAC-MD5 Algorithms">[RFC6151]</cite></a> for details). (<a href="#header.field.definitions" title="Header Field Definitions">Section 7</a>) 3800 </p> 3801 <p id="rfc.section.C.p.22">Remove ISO-8859-1 special-casing in Accept-Charset. (<a href="#header.accept-charset" id="rfc.xref.header.accept-charset.3" title="Accept-Charset">Section 7.2</a>) 3802 </p> 3803 <p id="rfc.section.C.p.23">Remove base URI setting semantics for Content-Location due to poor implementation support, which was caused by too many broken 3804 servers emitting bogus Content-Location header fields, and also the potentially undesirable effect of potentially breaking 3805 relative links in content-negotiated resources. (<a href="#header.content-location" id="rfc.xref.header.content-location.4" title="Content-Location">Section 7.8</a>) 3806 </p> 3807 <p id="rfc.section.C.p.24">Remove reference to non-existant identity transfer-coding value tokens. (<a href="#no.content-transfer-encoding" id="rfc.xref.no.content-transfer-encoding.1" title="No Content-Transfer-Encoding">Appendix A.5</a>) 3808 </p> 3809 <p id="rfc.section.C.p.25">Remove discussion of Content-Disposition header field, it is now defined by <a href="#RFC6266" id="rfc.xref.RFC6266.2"><cite title="Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)">[RFC6266]</cite></a>. (<a href="#additional.features" title="Additional Features">Appendix B</a>) 3810 </p> 3811 <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a> <a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1> 3812 <div id="rfc.figure.u.63"></div> <pre class="inline"><a href="#header.accept" class="smpl">Accept</a> = [ ( "," / ( media-range [ accept-params ] ) ) *( OWS "," [ 3723 3813 OWS media-range [ accept-params ] ] ) ] 3724 3814 <a href="#header.accept-charset" class="smpl">Accept-Charset</a> = *( "," OWS ) ( charset / "*" ) [ OWS ";" OWS "q=" … … 3867 3957 3868 3958 <a href="#preferred.date.format" class="smpl">year</a> = 4DIGIT 3869 </pre> <div id="rfc.figure.u.6 3"></div>3959 </pre> <div id="rfc.figure.u.64"></div> 3870 3960 <p>ABNF diagnostics:</p><pre class="inline">; qvalue UNDEFINED 3871 3961 ; Accept defined but not used … … 3889 3979 ; User-Agent defined but not used 3890 3980 ; obs-text defined but not used 3891 </pre><h1 id="rfc.section. C"><a href="#rfc.section.C">C.</a> <a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>3892 <h2 id="rfc.section. C.1"><a href="#rfc.section.C.1">C.1</a> Since RFC 26163981 </pre><h1 id="rfc.section.E"><a href="#rfc.section.E">E.</a> <a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1> 3982 <h2 id="rfc.section.E.1"><a href="#rfc.section.E.1">E.1</a> Since RFC 2616 3893 3983 </h2> 3894 <p id="rfc.section. C.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.4"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.3895 </p> 3896 <h2 id="rfc.section. C.2"><a href="#rfc.section.C.2">C.2</a> Since draft-ietf-httpbis-p2-semantics-003984 <p id="rfc.section.E.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.4"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>. 3985 </p> 3986 <h2 id="rfc.section.E.2"><a href="#rfc.section.E.2">E.2</a> Since draft-ietf-httpbis-p2-semantics-00 3897 3987 </h2> 3898 <p id="rfc.section. C.2.p.1">Closed issues: </p>3988 <p id="rfc.section.E.2.p.1">Closed issues: </p> 3899 3989 <ul> 3900 3990 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/5">http://tools.ietf.org/wg/httpbis/trac/ticket/5</a>>: "Via is a MUST" (<<a href="http://purl.org/NET/http-errata#via-must">http://purl.org/NET/http-errata#via-must</a>>) … … 3915 4005 </li> 3916 4006 </ul> 3917 <p id="rfc.section. C.2.p.2">Other changes: </p>4007 <p id="rfc.section.E.2.p.2">Other changes: </p> 3918 4008 <ul> 3919 4009 <li>Move definitions of 304 and 412 condition codes to <a href="#Part4" id="rfc.xref.Part4.11"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a> 3920 4010 </li> 3921 4011 </ul> 3922 <h2 id="rfc.section. C.3"><a href="#rfc.section.C.3">C.3</a> Since draft-ietf-httpbis-p2-semantics-014012 <h2 id="rfc.section.E.3"><a href="#rfc.section.E.3">E.3</a> Since draft-ietf-httpbis-p2-semantics-01 3923 4013 </h2> 3924 <p id="rfc.section. C.3.p.1">Closed issues: </p>4014 <p id="rfc.section.E.3.p.1">Closed issues: </p> 3925 4015 <ul> 3926 4016 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/21">http://tools.ietf.org/wg/httpbis/trac/ticket/21</a>>: "PUT side effects" … … 3929 4019 </li> 3930 4020 </ul> 3931 <p id="rfc.section. C.3.p.2">Ongoing work on ABNF conversion (<<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>>):4021 <p id="rfc.section.E.3.p.2">Ongoing work on ABNF conversion (<<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>>): 3932 4022 </p> 3933 4023 <ul> … … 3936 4026 <li>Copy definition of delta-seconds from Part6 instead of referencing it.</li> 3937 4027 </ul> 3938 <h2 id="rfc.section. C.4"><a href="#rfc.section.C.4">C.4</a> <a id="changes.since.02" href="#changes.since.02">Since draft-ietf-httpbis-p2-semantics-02</a></h2>3939 <p id="rfc.section. C.4.p.1">Closed issues: </p>4028 <h2 id="rfc.section.E.4"><a href="#rfc.section.E.4">E.4</a> <a id="changes.since.02" href="#changes.since.02">Since draft-ietf-httpbis-p2-semantics-02</a></h2> 4029 <p id="rfc.section.E.4.p.1">Closed issues: </p> 3940 4030 <ul> 3941 4031 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/24">http://tools.ietf.org/wg/httpbis/trac/ticket/24</a>>: "Requiring Allow in 405 responses" … … 3954 4044 </li> 3955 4045 </ul> 3956 <p id="rfc.section. C.4.p.2">Ongoing work on IANA Message Header Field Registration (<<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/40">http://tools.ietf.org/wg/httpbis/trac/ticket/40</a>>):4046 <p id="rfc.section.E.4.p.2">Ongoing work on IANA Message Header Field Registration (<<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/40">http://tools.ietf.org/wg/httpbis/trac/ticket/40</a>>): 3957 4047 </p> 3958 4048 <ul> 3959 4049 <li>Reference RFC 3984, and update header field registrations for headers defined in this document.</li> 3960 4050 </ul> 3961 <p id="rfc.section. C.4.p.3">Ongoing work on ABNF conversion (<<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>>):4051 <p id="rfc.section.E.4.p.3">Ongoing work on ABNF conversion (<<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>>): 3962 4052 </p> 3963 4053 <ul> 3964 4054 <li>Replace string literals when the string really is case-sensitive (method).</li> 3965 4055 </ul> 3966 <h2 id="rfc.section. C.5"><a href="#rfc.section.C.5">C.5</a> <a id="changes.since.03" href="#changes.since.03">Since draft-ietf-httpbis-p2-semantics-03</a></h2>3967 <p id="rfc.section. C.5.p.1">Closed issues: </p>4056 <h2 id="rfc.section.E.5"><a href="#rfc.section.E.5">E.5</a> <a id="changes.since.03" href="#changes.since.03">Since draft-ietf-httpbis-p2-semantics-03</a></h2> 4057 <p id="rfc.section.E.5.p.1">Closed issues: </p> 3968 4058 <ul> 3969 4059 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/98">http://tools.ietf.org/wg/httpbis/trac/ticket/98</a>>: "OPTIONS request bodies" … … 3974 4064 </li> 3975 4065 </ul> 3976 <p id="rfc.section. C.5.p.2">Ongoing work on Method Registry (<<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/72">http://tools.ietf.org/wg/httpbis/trac/ticket/72</a>>):4066 <p id="rfc.section.E.5.p.2">Ongoing work on Method Registry (<<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/72">http://tools.ietf.org/wg/httpbis/trac/ticket/72</a>>): 3977 4067 </p> 3978 4068 <ul> 3979 4069 <li>Added initial proposal for registration process, plus initial content (non-HTTP/1.1 methods to be added by a separate specification).</li> 3980 4070 </ul> 3981 <h2 id="rfc.section. C.6"><a href="#rfc.section.C.6">C.6</a> <a id="changes.since.04" href="#changes.since.04">Since draft-ietf-httpbis-p2-semantics-04</a></h2>3982 <p id="rfc.section. C.6.p.1">Closed issues: </p>4071 <h2 id="rfc.section.E.6"><a href="#rfc.section.E.6">E.6</a> <a id="changes.since.04" href="#changes.since.04">Since draft-ietf-httpbis-p2-semantics-04</a></h2> 4072 <p id="rfc.section.E.6.p.1">Closed issues: </p> 3983 4073 <ul> 3984 4074 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/103">http://tools.ietf.org/wg/httpbis/trac/ticket/103</a>>: "Content-*" … … 3987 4077 </li> 3988 4078 </ul> 3989 <p id="rfc.section. C.6.p.2">Ongoing work on ABNF conversion (<<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>>):4079 <p id="rfc.section.E.6.p.2">Ongoing work on ABNF conversion (<<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>>): 3990 4080 </p> 3991 4081 <ul> … … 3994 4084 <li>Rewrite ABNFs to spell out whitespace rules, factor out header field value format definitions.</li> 3995 4085 </ul> 3996 <h2 id="rfc.section. C.7"><a href="#rfc.section.C.7">C.7</a> <a id="changes.since.05" href="#changes.since.05">Since draft-ietf-httpbis-p2-semantics-05</a></h2>3997 <p id="rfc.section. C.7.p.1">Closed issues: </p>4086 <h2 id="rfc.section.E.7"><a href="#rfc.section.E.7">E.7</a> <a id="changes.since.05" href="#changes.since.05">Since draft-ietf-httpbis-p2-semantics-05</a></h2> 4087 <p id="rfc.section.E.7.p.1">Closed issues: </p> 3998 4088 <ul> 3999 4089 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/94">http://tools.ietf.org/wg/httpbis/trac/ticket/94</a>>: "reason-phrase BNF" 4000 4090 </li> 4001 4091 </ul> 4002 <p id="rfc.section. C.7.p.2">Final work on ABNF conversion (<<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>>):4092 <p id="rfc.section.E.7.p.2">Final work on ABNF conversion (<<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>>): 4003 4093 </p> 4004 4094 <ul> 4005 4095 <li>Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.</li> 4006 4096 </ul> 4007 <h2 id="rfc.section. C.8"><a href="#rfc.section.C.8">C.8</a> <a id="changes.since.06" href="#changes.since.06">Since draft-ietf-httpbis-p2-semantics-06</a></h2>4008 <p id="rfc.section. C.8.p.1">Closed issues: </p>4097 <h2 id="rfc.section.E.8"><a href="#rfc.section.E.8">E.8</a> <a id="changes.since.06" href="#changes.since.06">Since draft-ietf-httpbis-p2-semantics-06</a></h2> 4098 <p id="rfc.section.E.8.p.1">Closed issues: </p> 4009 4099 <ul> 4010 4100 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/144">http://tools.ietf.org/wg/httpbis/trac/ticket/144</a>>: "Clarify when Referer is sent" … … 4015 4105 </li> 4016 4106 </ul> 4017 <h2 id="rfc.section. C.9"><a href="#rfc.section.C.9">C.9</a> <a id="changes.since.07" href="#changes.since.07">Since draft-ietf-httpbis-p2-semantics-07</a></h2>4018 <p id="rfc.section. C.9.p.1">Closed issues: </p>4107 <h2 id="rfc.section.E.9"><a href="#rfc.section.E.9">E.9</a> <a id="changes.since.07" href="#changes.since.07">Since draft-ietf-httpbis-p2-semantics-07</a></h2> 4108 <p id="rfc.section.E.9.p.1">Closed issues: </p> 4019 4109 <ul> 4020 4110 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/27">http://tools.ietf.org/wg/httpbis/trac/ticket/27</a>>: "Idempotency" … … 4035 4125 </li> 4036 4126 </ul> 4037 <p id="rfc.section. C.9.p.2">Partly resolved issues: </p>4127 <p id="rfc.section.E.9.p.2">Partly resolved issues: </p> 4038 4128 <ul> 4039 4129 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/171">http://tools.ietf.org/wg/httpbis/trac/ticket/171</a>>: "Are OPTIONS and TRACE safe?" 4040 4130 </li> 4041 4131 </ul> 4042 <h2 id="rfc.section. C.10"><a href="#rfc.section.C.10">C.10</a> <a id="changes.since.08" href="#changes.since.08">Since draft-ietf-httpbis-p2-semantics-08</a></h2>4043 <p id="rfc.section. C.10.p.1">Closed issues: </p>4132 <h2 id="rfc.section.E.10"><a href="#rfc.section.E.10">E.10</a> <a id="changes.since.08" href="#changes.since.08">Since draft-ietf-httpbis-p2-semantics-08</a></h2> 4133 <p id="rfc.section.E.10.p.1">Closed issues: </p> 4044 4134 <ul> 4045 4135 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/10">http://tools.ietf.org/wg/httpbis/trac/ticket/10</a>>: "Safe Methods vs Redirection" (we missed the introduction to the 3xx status codes when fixing this previously) 4046 4136 </li> 4047 4137 </ul> 4048 <h2 id="rfc.section. C.11"><a href="#rfc.section.C.11">C.11</a> <a id="changes.since.09" href="#changes.since.09">Since draft-ietf-httpbis-p2-semantics-09</a></h2>4049 <p id="rfc.section. C.11.p.1">Closed issues: </p>4138 <h2 id="rfc.section.E.11"><a href="#rfc.section.E.11">E.11</a> <a id="changes.since.09" href="#changes.since.09">Since draft-ietf-httpbis-p2-semantics-09</a></h2> 4139 <p id="rfc.section.E.11.p.1">Closed issues: </p> 4050 4140 <ul> 4051 4141 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/43">http://tools.ietf.org/wg/httpbis/trac/ticket/43</a>>: "Fragment combination / precedence during redirects" 4052 4142 </li> 4053 4143 </ul> 4054 <p id="rfc.section. C.11.p.2">Partly resolved issues: </p>4144 <p id="rfc.section.E.11.p.2">Partly resolved issues: </p> 4055 4145 <ul> 4056 4146 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/185">http://tools.ietf.org/wg/httpbis/trac/ticket/185</a>>: "Location header payload handling" … … 4059 4149 </li> 4060 4150 </ul> 4061 <h2 id="rfc.section. C.12"><a href="#rfc.section.C.12">C.12</a> <a id="changes.since.10" href="#changes.since.10">Since draft-ietf-httpbis-p2-semantics-10</a></h2>4062 <p id="rfc.section. C.12.p.1">Closed issues: </p>4151 <h2 id="rfc.section.E.12"><a href="#rfc.section.E.12">E.12</a> <a id="changes.since.10" href="#changes.since.10">Since draft-ietf-httpbis-p2-semantics-10</a></h2> 4152 <p id="rfc.section.E.12.p.1">Closed issues: </p> 4063 4153 <ul> 4064 4154 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/69">http://tools.ietf.org/wg/httpbis/trac/ticket/69</a>>: "Clarify 'Requested Variant'" … … 4075 4165 </li> 4076 4166 </ul> 4077 <h2 id="rfc.section. C.13"><a href="#rfc.section.C.13">C.13</a> <a id="changes.since.11" href="#changes.since.11">Since draft-ietf-httpbis-p2-semantics-11</a></h2>4078 <p id="rfc.section. C.13.p.1">Closed issues: </p>4167 <h2 id="rfc.section.E.13"><a href="#rfc.section.E.13">E.13</a> <a id="changes.since.11" href="#changes.since.11">Since draft-ietf-httpbis-p2-semantics-11</a></h2> 4168 <p id="rfc.section.E.13.p.1">Closed issues: </p> 4079 4169 <ul> 4080 4170 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/229">http://tools.ietf.org/wg/httpbis/trac/ticket/229</a>>: "Considerations for new status codes" … … 4085 4175 </li> 4086 4176 </ul> 4087 <h2 id="rfc.section. C.14"><a href="#rfc.section.C.14">C.14</a> <a id="changes.since.12" href="#changes.since.12">Since draft-ietf-httpbis-p2-semantics-12</a></h2>4088 <p id="rfc.section. C.14.p.1">Closed issues: </p>4177 <h2 id="rfc.section.E.14"><a href="#rfc.section.E.14">E.14</a> <a id="changes.since.12" href="#changes.since.12">Since draft-ietf-httpbis-p2-semantics-12</a></h2> 4178 <p id="rfc.section.E.14.p.1">Closed issues: </p> 4089 4179 <ul> 4090 4180 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/43">http://tools.ietf.org/wg/httpbis/trac/ticket/43</a>>: "Fragment combination / precedence during redirects" (added warning about having a fragid on the redirect may cause inconvenience … … 4128 4218 </li> 4129 4219 </ul> 4130 <h2 id="rfc.section. C.15"><a href="#rfc.section.C.15">C.15</a> <a id="changes.since.13" href="#changes.since.13">Since draft-ietf-httpbis-p2-semantics-13</a></h2>4131 <p id="rfc.section. C.15.p.1">Closed issues: </p>4220 <h2 id="rfc.section.E.15"><a href="#rfc.section.E.15">E.15</a> <a id="changes.since.13" href="#changes.since.13">Since draft-ietf-httpbis-p2-semantics-13</a></h2> 4221 <p id="rfc.section.E.15.p.1">Closed issues: </p> 4132 4222 <ul> 4133 4223 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/276">http://tools.ietf.org/wg/httpbis/trac/ticket/276</a>>: "untangle ABNFs for header fields" … … 4136 4226 </li> 4137 4227 </ul> 4138 <h2 id="rfc.section. C.16"><a href="#rfc.section.C.16">C.16</a> <a id="changes.since.14" href="#changes.since.14">Since draft-ietf-httpbis-p2-semantics-14</a></h2>4139 <p id="rfc.section. C.16.p.1">Closed issues: </p>4228 <h2 id="rfc.section.E.16"><a href="#rfc.section.E.16">E.16</a> <a id="changes.since.14" href="#changes.since.14">Since draft-ietf-httpbis-p2-semantics-14</a></h2> 4229 <p id="rfc.section.E.16.p.1">Closed issues: </p> 4140 4230 <ul> 4141 4231 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/255">http://tools.ietf.org/wg/httpbis/trac/ticket/255</a>>: "Clarify status code for rate limiting" … … 4148 4238 </li> 4149 4239 </ul> 4150 <h2 id="rfc.section. C.17"><a href="#rfc.section.C.17">C.17</a> <a id="changes.since.15" href="#changes.since.15">Since draft-ietf-httpbis-p2-semantics-15</a></h2>4151 <p id="rfc.section. C.17.p.1">Closed issues: </p>4240 <h2 id="rfc.section.E.17"><a href="#rfc.section.E.17">E.17</a> <a id="changes.since.15" href="#changes.since.15">Since draft-ietf-httpbis-p2-semantics-15</a></h2> 4241 <p id="rfc.section.E.17.p.1">Closed issues: </p> 4152 4242 <ul> 4153 4243 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/285">http://tools.ietf.org/wg/httpbis/trac/ticket/285</a>>: "Strength of requirements on Accept re: 406" … … 4156 4246 </li> 4157 4247 </ul> 4158 <h2 id="rfc.section. C.18"><a href="#rfc.section.C.18">C.18</a> <a id="changes.since.16" href="#changes.since.16">Since draft-ietf-httpbis-p2-semantics-16</a></h2>4159 <p id="rfc.section. C.18.p.1">Closed issues: </p>4248 <h2 id="rfc.section.E.18"><a href="#rfc.section.E.18">E.18</a> <a id="changes.since.16" href="#changes.since.16">Since draft-ietf-httpbis-p2-semantics-16</a></h2> 4249 <p id="rfc.section.E.18.p.1">Closed issues: </p> 4160 4250 <ul> 4161 4251 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/160">http://tools.ietf.org/wg/httpbis/trac/ticket/160</a>>: "Redirects and non-GET methods" … … 4168 4258 </li> 4169 4259 </ul> 4170 <h2 id="rfc.section. C.19"><a href="#rfc.section.C.19">C.19</a> <a id="changes.since.17" href="#changes.since.17">Since draft-ietf-httpbis-p2-semantics-17</a></h2>4171 <p id="rfc.section. C.19.p.1">Closed issues: </p>4260 <h2 id="rfc.section.E.19"><a href="#rfc.section.E.19">E.19</a> <a id="changes.since.17" href="#changes.since.17">Since draft-ietf-httpbis-p2-semantics-17</a></h2> 4261 <p id="rfc.section.E.19.p.1">Closed issues: </p> 4172 4262 <ul> 4173 4263 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/185">http://tools.ietf.org/wg/httpbis/trac/ticket/185</a>>: "Location header payload handling" … … 4184 4274 </li> 4185 4275 </ul> 4186 <h2 id="rfc.section. C.20"><a href="#rfc.section.C.20">C.20</a> <a id="changes.since.18" href="#changes.since.18">Since draft-ietf-httpbis-p2-semantics-18</a></h2>4187 <p id="rfc.section. C.20.p.1">Closed issues: </p>4276 <h2 id="rfc.section.E.20"><a href="#rfc.section.E.20">E.20</a> <a id="changes.since.18" href="#changes.since.18">Since draft-ietf-httpbis-p2-semantics-18</a></h2> 4277 <p id="rfc.section.E.20.p.1">Closed issues: </p> 4188 4278 <ul> 4189 4279 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/227">http://tools.ietf.org/wg/httpbis/trac/ticket/227</a>>: "Combining HEAD responses" … … 4206 4296 </li> 4207 4297 </ul> 4208 <h2 id="rfc.section. C.21"><a href="#rfc.section.C.21">C.21</a> <a id="changes.since.19" href="#changes.since.19">Since draft-ietf-httpbis-p2-semantics-19</a></h2>4209 <p id="rfc.section. C.21.p.1">Closed issues: </p>4298 <h2 id="rfc.section.E.21"><a href="#rfc.section.E.21">E.21</a> <a id="changes.since.19" href="#changes.since.19">Since draft-ietf-httpbis-p2-semantics-19</a></h2> 4299 <p id="rfc.section.E.21.p.1">Closed issues: </p> 4210 4300 <ul> 4211 4301 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/312">http://tools.ietf.org/wg/httpbis/trac/ticket/312</a>>: "should there be a permanent variant of 307" 4212 4302 </li> 4213 4303 </ul> 4214 <h1 id="rfc.section. D"><a href="#rfc.section.D">D.</a> THE TEXT FORMERLY KNOWN AS PART34304 <h1 id="rfc.section.F"><a href="#rfc.section.F">F.</a> THE TEXT FORMERLY KNOWN AS PART3 4215 4305 </h1> 4216 <h2 id="rfc.section. D.1"><a href="#rfc.section.D.1">D.1</a> <a id="payload" href="#payload">Payload</a></h2>4217 <p id="rfc.section. D.1.p.1">HTTP messages <em class="bcp14">MAY</em> transfer a payload if not otherwise restricted by the request method or response status code. The payload consists of metadata,4306 <h2 id="rfc.section.F.1"><a href="#rfc.section.F.1">F.1</a> <a id="payload" href="#payload">Payload</a></h2> 4307 <p id="rfc.section.F.1.p.1">HTTP messages <em class="bcp14">MAY</em> transfer a payload if not otherwise restricted by the request method or response status code. The payload consists of metadata, 4218 4308 in the form of header fields, and data, in the form of the sequence of octets in the message body after any transfer-coding 4219 4309 has been decoded. 4220 4310 </p> 4221 4311 <div id="rfc.iref.p.3"></div> 4222 <p id="rfc.section. D.1.p.2">A "<dfn>payload</dfn>" in HTTP is always a partial or complete representation of some resource. We use separate terms for payload and representation4312 <p id="rfc.section.F.1.p.2">A "<dfn>payload</dfn>" in HTTP is always a partial or complete representation of some resource. We use separate terms for payload and representation 4223 4313 because some messages contain only the associated representation's header fields (e.g., responses to HEAD) or only some part(s) 4224 4314 of the representation (e.g., the 206 status code). 4225 4315 </p> 4226 <h3 id="rfc.section. D.1.1"><a href="#rfc.section.D.1.1">D.1.1</a> <a id="payload.header.fields" href="#payload.header.fields">Payload Header Fields</a></h3>4227 <p id="rfc.section. D.1.1.p.1">HTTP header fields that specifically define the payload, rather than the associated representation, are referred to as "payload4316 <h3 id="rfc.section.F.1.1"><a href="#rfc.section.F.1.1">F.1.1</a> <a id="payload.header.fields" href="#payload.header.fields">Payload Header Fields</a></h3> 4317 <p id="rfc.section.F.1.1.p.1">HTTP header fields that specifically define the payload, rather than the associated representation, are referred to as "payload 4228 4318 header fields". The following payload header fields are defined by HTTP/1.1: 4229 4319 </p> … … 4239 4329 <tr> 4240 4330 <td class="left">Content-Length</td> 4241 <td class="left"><a href="p1-messaging.html#header.content-length" title="Content-Length">Section 3.3.2</a> of <a href="#Part1" id="rfc.xref.Part1.5 6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a></td>4331 <td class="left"><a href="p1-messaging.html#header.content-length" title="Content-Length">Section 3.3.2</a> of <a href="#Part1" id="rfc.xref.Part1.57"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a></td> 4242 4332 </tr> 4243 4333 <tr> … … 4248 4338 </table> 4249 4339 </div> 4250 <h3 id="rfc.section. D.1.2"><a href="#rfc.section.D.1.2">D.1.2</a> <a id="payload.body" href="#payload.body">Payload Body</a></h3>4251 <p id="rfc.section. D.1.2.p.1">A payload 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 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.57"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. The payload body is obtained from the message body by decoding any Transfer-Encoding that might have been applied to ensure4340 <h3 id="rfc.section.F.1.2"><a href="#rfc.section.F.1.2">F.1.2</a> <a id="payload.body" href="#payload.body">Payload Body</a></h3> 4341 <p id="rfc.section.F.1.2.p.1">A payload 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 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.58"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. The payload body is obtained from the message body by decoding any Transfer-Encoding that might have been applied to ensure 4252 4342 safe and proper transfer of the message. 4253 4343 </p> 4254 4344 <div id="rfc.iref.r.3"></div> 4255 <h2 id="rfc.section. D.2"><a href="#rfc.section.D.2">D.2</a> <a id="representation3" href="#representation3">Representation</a></h2>4256 <p id="rfc.section. D.2.p.1">A "<dfn>representation</dfn>" is information in a format that can be readily communicated from one party to another. A resource representation is information4345 <h2 id="rfc.section.F.2"><a href="#rfc.section.F.2">F.2</a> <a id="representation3" href="#representation3">Representation</a></h2> 4346 <p id="rfc.section.F.2.p.1">A "<dfn>representation</dfn>" is information in a format that can be readily communicated from one party to another. A resource representation is information 4257 4347 that reflects the state of that resource, as observed at some point in the past (e.g., in a response to GET) or to be desired 4258 4348 at some point in the future (e.g., in a PUT request). 4259 4349 </p> 4260 <p id="rfc.section. D.2.p.2">Most, but not all, representations transferred via HTTP are intended to be a representation of the target resource (the resource4350 <p id="rfc.section.F.2.p.2">Most, but not all, representations transferred via HTTP are intended to be a representation of the target resource (the resource 4261 4351 identified by the effective request URI). The precise semantics of a representation are determined by the type of message 4262 4352 (request or response), the request method, the response status code, and the representation metadata. For example, the above … … 4267 4357 next steps are suggested for resolving it. 4268 4358 </p> 4269 <h3 id="rfc.section. D.2.1"><a href="#rfc.section.D.2.1">D.2.1</a> <a id="representation.header.fields" href="#representation.header.fields">Representation Header Fields</a></h3>4270 <p id="rfc.section. D.2.1.p.1">Representation header fields define metadata about the representation data enclosed in the message body or, if no message4359 <h3 id="rfc.section.F.2.1"><a href="#rfc.section.F.2.1">F.2.1</a> <a id="representation.header.fields" href="#representation.header.fields">Representation Header Fields</a></h3> 4360 <p id="rfc.section.F.2.1.p.1">Representation header fields define metadata about the representation data enclosed in the message body or, if no message 4271 4361 body is present, about the representation that would have been transferred in a 200 response to a simultaneous GET request 4272 4362 with the same effective request URI. 4273 4363 </p> 4274 <p id="rfc.section. D.2.1.p.2">The following header fields are defined as representation metadata:</p>4364 <p id="rfc.section.F.2.1.p.2">The following header fields are defined as representation metadata:</p> 4275 4365 <div id="rfc.table.u.6"> 4276 4366 <table class="tt full left" cellpadding="3" cellspacing="0"> … … 4292 4382 <tr> 4293 4383 <td class="left">Content-Location</td> 4294 <td class="left"><a href="#header.content-location" id="rfc.xref.header.content-location. 4" title="Content-Location">Section 7.8</a></td>4384 <td class="left"><a href="#header.content-location" id="rfc.xref.header.content-location.5" title="Content-Location">Section 7.8</a></td> 4295 4385 </tr> 4296 4386 <tr> … … 4305 4395 </table> 4306 4396 </div> 4307 <p id="rfc.section. D.2.1.p.3">Additional header fields define metadata about the selected representation, which might differ from the representation included4397 <p id="rfc.section.F.2.1.p.3">Additional header fields define metadata about the selected representation, which might differ from the representation included 4308 4398 in the message for responses to some state-changing methods. The following header fields are defined as selected representation 4309 4399 metadata: … … 4329 4419 </table> 4330 4420 </div> 4331 <h3 id="rfc.section. D.2.2"><a href="#rfc.section.D.2.2">D.2.2</a> <a id="representation.data" href="#representation.data">Representation Data</a></h3>4332 <p id="rfc.section. D.2.2.p.1">The representation body associated with an HTTP message is either provided as the payload body of the message or referred4421 <h3 id="rfc.section.F.2.2"><a href="#rfc.section.F.2.2">F.2.2</a> <a id="representation.data" href="#representation.data">Representation Data</a></h3> 4422 <p id="rfc.section.F.2.2.p.1">The representation body associated with an HTTP message is either provided as the payload body of the message or referred 4333 4423 to by the message semantics and the effective request URI. The representation data is in a format and encoding defined by 4334 4424 the representation metadata header fields. 4335 4425 </p> 4336 <p id="rfc.section. D.2.2.p.2">The data type of the representation data is determined via the header fields Content-Type and Content-Encoding. These define4426 <p id="rfc.section.F.2.2.p.2">The data type of the representation data is determined via the header fields Content-Type and Content-Encoding. These define 4337 4427 a two-layer, ordered encoding model: 4338 4428 </p> 4339 <div id="rfc.figure.u.6 4"></div><pre class="text"> representation-data := Content-Encoding( Content-Type( bits ) )4340 </pre><p id="rfc.section. D.2.2.p.4">Content-Type specifies the media type of the underlying data, which defines both the data format and how that data <em class="bcp14">SHOULD</em> be processed by the recipient (within the scope of the request method semantics). Any HTTP/1.1 message containing a payload4429 <div id="rfc.figure.u.65"></div><pre class="text"> representation-data := Content-Encoding( Content-Type( bits ) ) 4430 </pre><p id="rfc.section.F.2.2.p.4">Content-Type specifies the media type of the underlying data, which defines both the data format and how that data <em class="bcp14">SHOULD</em> be processed by the recipient (within the scope of the request method semantics). Any HTTP/1.1 message containing a payload 4341 4431 body <em class="bcp14">SHOULD</em> include a Content-Type header field defining the media type of the associated representation unless that metadata is unknown 4342 4432 to the sender. If the Content-Type header field is not present, it indicates that the sender does not know the media type 4343 of the representation; recipients <em class="bcp14">MAY</em> either assume that the media type is "application/octet-stream" (<a href="#RFC2046" id="rfc.xref.RFC2046. 3"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a>, <a href="http://tools.ietf.org/html/rfc2046#section-4.5.1">Section 4.5.1</a>) or examine the content to determine its type.4344 </p> 4345 <p id="rfc.section. D.2.2.p.5">In practice, resource owners do not always properly configure their origin server to provide the correct Content-Type for4433 of the representation; recipients <em class="bcp14">MAY</em> either assume that the media type is "application/octet-stream" (<a href="#RFC2046" id="rfc.xref.RFC2046.4"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a>, <a href="http://tools.ietf.org/html/rfc2046#section-4.5.1">Section 4.5.1</a>) or examine the content to determine its type. 4434 </p> 4435 <p id="rfc.section.F.2.2.p.5">In practice, resource owners do not always properly configure their origin server to provide the correct Content-Type for 4346 4436 a given representation, with the result that some clients will examine a response body's content and override the specified 4347 4437 type. Clients that do so risk drawing incorrect conclusions, which might expose additional security risks (e.g., "privilege … … 4350 4440 such "content sniffing" when it is used. 4351 4441 </p> 4352 <p id="rfc.section. D.2.2.p.6">Content-Encoding is used to indicate any additional content codings applied to the data, usually for the purpose of data compression,4442 <p id="rfc.section.F.2.2.p.6">Content-Encoding is used to indicate any additional content codings applied to the data, usually for the purpose of data compression, 4353 4443 that are a property of the representation. If Content-Encoding is not present, then there is no additional encoding beyond 4354 4444 that defined by the Content-Type. 4355 4445 </p> 4356 <h2 id="rfc.section. D.3"><a href="#rfc.section.D.3">D.3</a> <a id="content.negotiation" href="#content.negotiation">Content Negotiation</a></h2>4357 <p id="rfc.section. D.3.p.1">HTTP responses include a representation which contains information for interpretation, whether by a human user or for further4446 <h2 id="rfc.section.F.3"><a href="#rfc.section.F.3">F.3</a> <a id="content.negotiation" href="#content.negotiation">Content Negotiation</a></h2> 4447 <p id="rfc.section.F.3.p.1">HTTP responses include a representation which contains information for interpretation, whether by a human user or for further 4358 4448 processing. Often, the server has different ways of representing the same information; for example, in different formats, 4359 4449 languages, or using different character encodings. 4360 4450 </p> 4361 <p id="rfc.section. D.3.p.2">HTTP clients and their users might have different or variable capabilities, characteristics or preferences which would influence4451 <p id="rfc.section.F.3.p.2">HTTP clients and their users might have different or variable capabilities, characteristics or preferences which would influence 4362 4452 which representation, among those available from the server, would be best for the server to deliver. For this reason, HTTP 4363 4453 provides mechanisms for "content negotiation" — a process of allowing selection of a representation of a given resource, when 4364 4454 more than one is available. 4365 4455 </p> 4366 <p id="rfc.section. D.3.p.3">This specification defines two patterns of content negotiation; "server-driven", where the server selects the representation4456 <p id="rfc.section.F.3.p.3">This specification defines two patterns of content negotiation; "server-driven", where the server selects the representation 4367 4457 based upon the client's stated preferences, and "agent-driven" negotiation, where the server provides a list of representations 4368 4458 for the client to choose from, based upon their metadata. In addition, there are other patterns: some applications use an … … 4370 4460 parameters, selects additional resources to invoke. "Transparent Content Negotiation" (<a href="#RFC2295" id="rfc.xref.RFC2295.1"><cite title="Transparent Content Negotiation in HTTP">[RFC2295]</cite></a>) has also been proposed. 4371 4461 </p> 4372 <p id="rfc.section. D.3.p.4">These patterns are all widely used, and have trade-offs in applicability and practicality. In particular, when the number4462 <p id="rfc.section.F.3.p.4">These patterns are all widely used, and have trade-offs in applicability and practicality. In particular, when the number 4373 4463 of preferences or capabilities to be expressed by a client are large (such as when many different formats are supported by 4374 4464 a user-agent), server-driven negotiation becomes unwieldy, and might not be appropriate. Conversely, when the number of representations 4375 4465 to choose from is very large, agent-driven negotiation might not be appropriate. 4376 4466 </p> 4377 <p id="rfc.section. D.3.p.5">Note that in all cases, the supplier of representations has the responsibility for determining which representations might4467 <p id="rfc.section.F.3.p.5">Note that in all cases, the supplier of representations has the responsibility for determining which representations might 4378 4468 be considered to be the "same information". 4379 4469 </p> 4380 <h3 id="rfc.section. D.3.1"><a href="#rfc.section.D.3.1">D.3.1</a> <a id="server-driven.negotiation" href="#server-driven.negotiation">Server-driven Negotiation</a></h3>4381 <p id="rfc.section. D.3.1.p.1">If the selection of the best representation for a response is made by an algorithm located at the server, it is called server-driven4470 <h3 id="rfc.section.F.3.1"><a href="#rfc.section.F.3.1">F.3.1</a> <a id="server-driven.negotiation" href="#server-driven.negotiation">Server-driven Negotiation</a></h3> 4471 <p id="rfc.section.F.3.1.p.1">If the selection of the best representation for a response is made by an algorithm located at the server, it is called server-driven 4382 4472 negotiation. Selection is based on the available representations of the response (the dimensions over which it can vary; e.g., 4383 4473 language, content-coding, etc.) and the contents of particular header fields in the request message or on other information 4384 4474 pertaining to the request (such as the network address of the client). 4385 4475 </p> 4386 <p id="rfc.section. D.3.1.p.2">Server-driven negotiation is advantageous when the algorithm for selecting from among the available representations is difficult4476 <p id="rfc.section.F.3.1.p.2">Server-driven negotiation is advantageous when the algorithm for selecting from among the available representations is difficult 4387 4477 to describe to the user agent, or when the server desires to send its "best guess" to the client along with the first response 4388 4478 (hoping to avoid the round-trip delay of a subsequent request if the "best guess" is good enough for the user). In order to 4389 4479 improve the server's guess, the user agent <em class="bcp14">MAY</em> include request header fields (Accept, Accept-Language, Accept-Encoding, etc.) which describe its preferences for such a response. 4390 4480 </p> 4391 <p id="rfc.section. D.3.1.p.3">Server-driven negotiation has disadvantages: </p>4481 <p id="rfc.section.F.3.1.p.3">Server-driven negotiation has disadvantages: </p> 4392 4482 <ol> 4393 4483 <li>It is impossible for the server to accurately determine what might be "best" for any given user, since that would require … … 4401 4491 <li>It might limit a public cache's ability to use the same response for multiple user's requests.</li> 4402 4492 </ol> 4403 <p id="rfc.section. D.3.1.p.4">Server-driven negotiation allows the user agent to specify its preferences, but it cannot expect responses to always honor4493 <p id="rfc.section.F.3.1.p.4">Server-driven negotiation allows the user agent to specify its preferences, but it cannot expect responses to always honor 4404 4494 them. For example, the origin server might not implement server-driven negotiation, or it might decide that sending a response 4405 4495 that doesn't conform to them is better than sending a 406 (Not Acceptable) response. 4406 4496 </p> 4407 <p id="rfc.section. D.3.1.p.5">Many of the mechanisms for expressing preferences use quality values to declare relative preference. See <a href="p1-messaging.html#quality.values" title="Quality Values">Section 4.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.58"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for more information.4408 </p> 4409 <p id="rfc.section. D.3.1.p.6">HTTP/1.1 includes the following header fields for enabling server-driven negotiation through description of user agent capabilities4410 and user preferences: Accept (<a href="#header.accept" id="rfc.xref.header.accept.4" title="Accept">Section 7.1</a>), Accept-Charset (<a href="#header.accept-charset" id="rfc.xref.header.accept-charset. 3" title="Accept-Charset">Section 7.2</a>), Accept-Encoding (<a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.5" title="Accept-Encoding">Section 7.3</a>), Accept-Language (<a href="#header.accept-language" id="rfc.xref.header.accept-language.3" title="Accept-Language">Section 7.4</a>), and User-Agent (<a href="#header.user-agent" id="rfc.xref.header.user-agent.4" title="User-Agent">Section 7.18</a>). However, an origin server is not limited to these dimensions and <em class="bcp14">MAY</em> vary the response based on any aspect of the request, including aspects of the connection (e.g., IP address) or information4497 <p id="rfc.section.F.3.1.p.5">Many of the mechanisms for expressing preferences use quality values to declare relative preference. See <a href="p1-messaging.html#quality.values" title="Quality Values">Section 4.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.59"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for more information. 4498 </p> 4499 <p id="rfc.section.F.3.1.p.6">HTTP/1.1 includes the following header fields for enabling server-driven negotiation through description of user agent capabilities 4500 and user preferences: Accept (<a href="#header.accept" id="rfc.xref.header.accept.4" title="Accept">Section 7.1</a>), Accept-Charset (<a href="#header.accept-charset" id="rfc.xref.header.accept-charset.4" title="Accept-Charset">Section 7.2</a>), Accept-Encoding (<a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.5" title="Accept-Encoding">Section 7.3</a>), Accept-Language (<a href="#header.accept-language" id="rfc.xref.header.accept-language.3" title="Accept-Language">Section 7.4</a>), and User-Agent (<a href="#header.user-agent" id="rfc.xref.header.user-agent.4" title="User-Agent">Section 7.18</a>). However, an origin server is not limited to these dimensions and <em class="bcp14">MAY</em> vary the response based on any aspect of the request, including aspects of the connection (e.g., IP address) or information 4411 4501 within extension header fields not defined by this specification. 4412 4502 </p> 4413 <div class="note" id="rfc.section. D.3.1.p.7">4503 <div class="note" id="rfc.section.F.3.1.p.7"> 4414 4504 <p> <b>Note:</b> In practice, User-Agent based negotiation is fragile, because new clients might not be recognized. 4415 4505 </p> 4416 4506 </div> 4417 <p id="rfc.section. D.3.1.p.8">The Vary header field (<a href="p6-cache.html#header.vary" title="Vary">Section 3.5</a> of <a href="#Part6" id="rfc.xref.Part6.19"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) can be used to express the parameters the server uses to select a representation that is subject to server-driven negotiation.4418 </p> 4419 <h3 id="rfc.section. D.3.2"><a href="#rfc.section.D.3.2">D.3.2</a> <a id="agent-driven.negotiation" href="#agent-driven.negotiation">Agent-driven Negotiation</a></h3>4420 <p id="rfc.section. D.3.2.p.1">With agent-driven negotiation, selection of the best representation for a response is performed by the user agent after receiving4507 <p id="rfc.section.F.3.1.p.8">The Vary header field (<a href="p6-cache.html#header.vary" title="Vary">Section 3.5</a> of <a href="#Part6" id="rfc.xref.Part6.19"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) can be used to express the parameters the server uses to select a representation that is subject to server-driven negotiation. 4508 </p> 4509 <h3 id="rfc.section.F.3.2"><a href="#rfc.section.F.3.2">F.3.2</a> <a id="agent-driven.negotiation" href="#agent-driven.negotiation">Agent-driven Negotiation</a></h3> 4510 <p id="rfc.section.F.3.2.p.1">With agent-driven negotiation, selection of the best representation for a response is performed by the user agent after receiving 4421 4511 an initial response from the origin server. Selection is based on a list of the available representations of the response 4422 4512 included within the header fields or body of the initial response, with each representation identified by its own URI. Selection … … 4424 4514 user selecting from a generated (possibly hypertext) menu. 4425 4515 </p> 4426 <p id="rfc.section. D.3.2.p.2">Agent-driven negotiation is advantageous when the response would vary over commonly-used dimensions (such as type, language,4516 <p id="rfc.section.F.3.2.p.2">Agent-driven negotiation is advantageous when the response would vary over commonly-used dimensions (such as type, language, 4427 4517 or encoding), when the origin server is unable to determine a user agent's capabilities from examining the request, and generally 4428 4518 when public caches are used to distribute server load and reduce network usage. 4429 4519 </p> 4430 <p id="rfc.section. D.3.2.p.3">Agent-driven negotiation suffers from the disadvantage of needing a second request to obtain the best alternate representation.4520 <p id="rfc.section.F.3.2.p.3">Agent-driven negotiation suffers from the disadvantage of needing a second request to obtain the best alternate representation. 4431 4521 This second request is only efficient when caching is used. In addition, this specification does not define any mechanism 4432 4522 for supporting automatic selection, though it also does not prevent any such mechanism from being developed as an extension 4433 4523 and used within HTTP/1.1. 4434 4524 </p> 4435 <p id="rfc.section. D.3.2.p.4">This specification defines the 300 (Multiple Choices) and 406 (Not Acceptable) status codes for enabling agent-driven negotiation4525 <p id="rfc.section.F.3.2.p.4">This specification defines the 300 (Multiple Choices) and 406 (Not Acceptable) status codes for enabling agent-driven negotiation 4436 4526 when the server is unwilling or unable to provide a varying response using server-driven negotiation. 4437 4527 </p> 4438 <h2 id="rfc.section.D.4"><a href="#rfc.section.D.4">D.4</a> <a id="differences.between.http.and.mime" href="#differences.between.http.and.mime">Differences between HTTP and MIME</a></h2> 4439 <p id="rfc.section.D.4.p.1">HTTP/1.1 uses many of the constructs defined for Internet Mail (<a href="#RFC5322" id="rfc.xref.RFC5322.5"><cite title="Internet Message Format">[RFC5322]</cite></a>) and the Multipurpose Internet Mail Extensions (MIME <a href="#RFC2045" id="rfc.xref.RFC2045.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies">[RFC2045]</cite></a>) to allow a message body to be transmitted in an open variety of representations and with extensible mechanisms. However, 4440 RFC 2045 discusses mail, and HTTP has a few features that are different from those described in MIME. These differences were 4441 carefully chosen to optimize performance over binary connections, to allow greater freedom in the use of new media types, 4442 to make date comparisons easier, and to acknowledge the practice of some early HTTP servers and clients. 4443 </p> 4444 <p id="rfc.section.D.4.p.2">This appendix describes specific areas where HTTP differs from MIME. Proxies and gateways to strict MIME environments <em class="bcp14">SHOULD</em> be aware of these differences and provide the appropriate conversions where necessary. Proxies and gateways from MIME environments 4445 to HTTP also need to be aware of the differences because some conversions might be required. 4446 </p> 4447 <div id="rfc.iref.m.10"></div> 4448 <div id="rfc.iref.h.20"></div> 4449 <h3 id="rfc.section.D.4.1"><a href="#rfc.section.D.4.1">D.4.1</a> <a id="mime-version" href="#mime-version">MIME-Version</a></h3> 4450 <p id="rfc.section.D.4.1.p.1">HTTP is not a MIME-compliant protocol. However, HTTP/1.1 messages <em class="bcp14">MAY</em> include a single MIME-Version header field to indicate what version of the MIME protocol was used to construct the message. 4451 Use of the MIME-Version header field indicates that the message is in full conformance with the MIME protocol (as defined 4452 in <a href="#RFC2045" id="rfc.xref.RFC2045.2"><cite title="Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies">[RFC2045]</cite></a>). Proxies/gateways are responsible for ensuring full conformance (where possible) when exporting HTTP messages to strict 4453 MIME environments. 4454 </p> 4455 <div id="rfc.figure.u.65"></div><pre class="inline"><span id="rfc.iref.g.59"></span> <a href="#mime-version" class="smpl">MIME-Version</a> = 1*<a href="#notation" class="smpl">DIGIT</a> "." 1*<a href="#notation" class="smpl">DIGIT</a> 4456 </pre><p id="rfc.section.D.4.1.p.3">MIME version "1.0" is the default for use in HTTP/1.1. However, HTTP/1.1 message parsing and semantics are defined by this 4457 document and not the MIME specification. 4458 </p> 4459 <h3 id="rfc.section.D.4.2"><a href="#rfc.section.D.4.2">D.4.2</a> <a id="conversion.to.canonical.form" href="#conversion.to.canonical.form">Conversion to Canonical Form</a></h3> 4460 <p id="rfc.section.D.4.2.p.1">MIME requires that an Internet mail body-part be converted to canonical form prior to being transferred, as described in <a href="http://tools.ietf.org/html/rfc2049#section-4">Section 4</a> of <a href="#RFC2049" id="rfc.xref.RFC2049.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples">[RFC2049]</cite></a>. <a href="#canonicalization.and.text.defaults" title="Canonicalization and Text Defaults">Section 6.5.1</a> of this document describes the forms allowed for subtypes of the "text" media type when transmitted over HTTP. <a href="#RFC2046" id="rfc.xref.RFC2046.4"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a> requires that content with a type of "text" represent line breaks as CRLF and forbids the use of CR or LF outside of line 4461 break sequences. HTTP allows CRLF, bare CR, and bare LF to indicate a line break within text content when a message is transmitted 4462 over HTTP. 4463 </p> 4464 <p id="rfc.section.D.4.2.p.2">Where it is possible, a proxy or gateway from HTTP to a strict MIME environment <em class="bcp14">SHOULD</em> translate all line breaks within the text media types described in <a href="#canonicalization.and.text.defaults" title="Canonicalization and Text Defaults">Section 6.5.1</a> of this document to the RFC 2049 canonical form of CRLF. Note, however, that this might be complicated by the presence of 4465 a Content-Encoding and by the fact that HTTP allows the use of some character encodings which do not use octets 13 and 10 4466 to represent CR and LF, respectively, as is the case for some multi-byte character encodings. 4467 </p> 4468 <p id="rfc.section.D.4.2.p.3">Conversion will break any cryptographic checksums applied to the original content unless the original content is already in 4469 canonical form. Therefore, the canonical form is recommended for any content that uses such checksums in HTTP. 4470 </p> 4471 <h3 id="rfc.section.D.4.3"><a href="#rfc.section.D.4.3">D.4.3</a> <a id="conversion.of.date.formats" href="#conversion.of.date.formats">Conversion of Date Formats</a></h3> 4472 <p id="rfc.section.D.4.3.p.1">HTTP/1.1 uses a restricted set of date formats (<a href="#http.date" title="Date/Time Formats">Section 6.1</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. 4473 </p> 4474 <h3 id="rfc.section.D.4.4"><a href="#rfc.section.D.4.4">D.4.4</a> <a id="introduction.of.content-encoding" href="#introduction.of.content-encoding">Introduction of Content-Encoding</a></h3> 4475 <p id="rfc.section.D.4.4.p.1">MIME does not include any concept equivalent to HTTP/1.1's Content-Encoding header field. Since this acts as a modifier on 4476 the media type, proxies and gateways from HTTP to MIME-compliant protocols <em class="bcp14">MUST</em> either change the value of the Content-Type header field or decode the representation before forwarding the message. (Some 4477 experimental applications of Content-Type for Internet mail have used a media-type parameter of ";conversions=<content-coding>" 4478 to perform a function equivalent to Content-Encoding. However, this parameter is not part of the MIME standards). 4479 </p> 4480 <div id="rfc.iref.c.11"></div> 4481 <div id="rfc.iref.h.21"></div> 4482 <h3 id="rfc.section.D.4.5"><a href="#rfc.section.D.4.5">D.4.5</a> <a id="no.content-transfer-encoding" href="#no.content-transfer-encoding">No Content-Transfer-Encoding</a></h3> 4483 <p id="rfc.section.D.4.5.p.1">HTTP does not use the Content-Transfer-Encoding field of MIME. Proxies and gateways from MIME-compliant protocols to HTTP <em class="bcp14">MUST</em> remove any Content-Transfer-Encoding prior to delivering the response message to an HTTP client. 4484 </p> 4485 <p id="rfc.section.D.4.5.p.2">Proxies and gateways from HTTP to MIME-compliant protocols are responsible for ensuring that the message is in the correct 4486 format and encoding for safe transport on that protocol, where "safe transport" is defined by the limitations of the protocol 4487 being used. Such a proxy or gateway <em class="bcp14">SHOULD</em> label the data with an appropriate Content-Transfer-Encoding if doing so will improve the likelihood of safe transport over 4488 the destination protocol. 4489 </p> 4490 <h3 id="rfc.section.D.4.6"><a href="#rfc.section.D.4.6">D.4.6</a> <a id="introduction.of.transfer-encoding" href="#introduction.of.transfer-encoding">Introduction of Transfer-Encoding</a></h3> 4491 <p id="rfc.section.D.4.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.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.59"><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. 4492 </p> 4493 <h3 id="rfc.section.D.4.7"><a href="#rfc.section.D.4.7">D.4.7</a> <a id="mhtml.line.length" href="#mhtml.line.length">MHTML and Line Length Limitations</a></h3> 4494 <p id="rfc.section.D.4.7.p.1">HTTP implementations which share code with MHTML <a href="#RFC2557" id="rfc.xref.RFC2557.2"><cite title="MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)">[RFC2557]</cite></a> implementations need to be aware of MIME line length limitations. Since HTTP does not have this limitation, HTTP does not 4495 fold long lines. MHTML messages being transported by HTTP follow all conventions of MHTML, including line length limitations 4496 and folding, canonicalization, etc., since HTTP transports all message-bodies as payload (see <a href="#multipart.types" title="Multipart Types">Section 6.5.2</a>) and does not interpret the content or any MIME header lines that might be contained therein. 4497 </p> 4498 <h2 id="rfc.section.D.5"><a href="#rfc.section.D.5">D.5</a> <a id="additional.features" href="#additional.features">Additional Features</a></h2> 4499 <p id="rfc.section.D.5.p.1"> <a href="#RFC1945" id="rfc.xref.RFC1945.2"><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 4500 applications. Implementors are advised to be aware of these features, but cannot rely upon their presence in, or interoperability 4501 with, other HTTP/1.1 applications. Some of these describe proposed experimental features, and some describe features that 4502 experimental deployment found lacking that are now addressed in the base HTTP/1.1 specification. 4503 </p> 4504 <p id="rfc.section.D.5.p.2">A number of other header fields, such as Content-Disposition and Title, from SMTP and MIME are also often implemented (see <a href="#RFC6266" id="rfc.xref.RFC6266.1"><cite title="Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)">[RFC6266]</cite></a> and <a href="#RFC2076" id="rfc.xref.RFC2076.1"><cite title="Common Internet Message Headers">[RFC2076]</cite></a>). 4505 </p> 4506 <h2 id="rfc.section.D.6"><a href="#rfc.section.D.6">D.6</a> <a id="changes.from.rfc.2616-3" href="#changes.from.rfc.2616-3">Changes from RFC 2616</a></h2> 4507 <p id="rfc.section.D.6.p.1">Clarify contexts that charset is used in. (<a href="#character.sets" title="Character Encodings (charset)">Section 6.3</a>) 4508 </p> 4509 <p id="rfc.section.D.6.p.2">Registration of Content Codings now requires IETF Review (<a href="#content.coding.registry" title="Content Coding Registry">Section 6.4.1</a>) 4510 </p> 4511 <p id="rfc.section.D.6.p.3">Remove the default character encoding for text media types; the default now is whatever the media type definition says. (<a href="#canonicalization.and.text.defaults" title="Canonicalization and Text Defaults">Section 6.5.1</a>) 4512 </p> 4513 <p id="rfc.section.D.6.p.4">Change ABNF productions for header fields to only define the field value. (<a href="#header.field.definitions" title="Header Field Definitions">Section 7</a>) 4514 </p> 4515 <p id="rfc.section.D.6.p.5">Remove definition of Content-MD5 header field because it was inconsistently implemented with respect to partial responses, 4516 and also because of known deficiencies in the hash algorithm itself (see <a href="#RFC6151" id="rfc.xref.RFC6151.1"><cite title="Updated Security Considerations for the MD5 Message-Digest and the HMAC-MD5 Algorithms">[RFC6151]</cite></a> for details). (<a href="#header.field.definitions" title="Header Field Definitions">Section 7</a>) 4517 </p> 4518 <p id="rfc.section.D.6.p.6">Remove ISO-8859-1 special-casing in Accept-Charset. (<a href="#header.accept-charset" id="rfc.xref.header.accept-charset.4" title="Accept-Charset">Section 7.2</a>) 4519 </p> 4520 <p id="rfc.section.D.6.p.7">Remove base URI setting semantics for Content-Location due to poor implementation support, which was caused by too many broken 4521 servers emitting bogus Content-Location header fields, and also the potentially undesirable effect of potentially breaking 4522 relative links in content-negotiated resources. (<a href="#header.content-location" id="rfc.xref.header.content-location.5" title="Content-Location">Section 7.8</a>) 4523 </p> 4524 <p id="rfc.section.D.6.p.8">Remove reference to non-existant identity transfer-coding value tokens. (<a href="#no.content-transfer-encoding" id="rfc.xref.no.content-transfer-encoding.1" title="No Content-Transfer-Encoding">Appendix D.4.5</a>) 4525 </p> 4526 <p id="rfc.section.D.6.p.9">Remove discussion of Content-Disposition header field, it is now defined by <a href="#RFC6266" id="rfc.xref.RFC6266.2"><cite title="Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)">[RFC6266]</cite></a>. (<a href="#additional.features" title="Additional Features">Appendix D.5</a>) 4527 </p> 4528 <h2 id="rfc.section.D.7"><a href="#rfc.section.D.7">D.7</a> <a id="change.log3" href="#change.log3">Change Log (to be removed by RFC Editor before publication)</a></h2> 4529 <h3 id="rfc.section.D.7.1"><a href="#rfc.section.D.7.1">D.7.1</a> Since RFC 2616 4528 <h2 id="rfc.section.F.4"><a href="#rfc.section.F.4">F.4</a> <a id="change.log3" href="#change.log3">Change Log (to be removed by RFC Editor before publication)</a></h2> 4529 <h3 id="rfc.section.F.4.1"><a href="#rfc.section.F.4.1">F.4.1</a> Since RFC 2616 4530 4530 </h3> 4531 <p id="rfc.section. D.7.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.5"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.4532 </p> 4533 <h3 id="rfc.section. D.7.2"><a href="#rfc.section.D.7.2">D.7.2</a> Since draft-ietf-httpbis-p3-payload-004531 <p id="rfc.section.F.4.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.5"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>. 4532 </p> 4533 <h3 id="rfc.section.F.4.2"><a href="#rfc.section.F.4.2">F.4.2</a> Since draft-ietf-httpbis-p3-payload-00 4534 4534 </h3> 4535 <p id="rfc.section. D.7.2.p.1">Closed issues: </p>4535 <p id="rfc.section.F.4.2.p.1">Closed issues: </p> 4536 4536 <ul> 4537 4537 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/8">http://tools.ietf.org/wg/httpbis/trac/ticket/8</a>>: "Media Type Registrations" (<<a href="http://purl.org/NET/http-errata#media-reg">http://purl.org/NET/http-errata#media-reg</a>>) … … 4558 4558 </li> 4559 4559 </ul> 4560 <h3 id="rfc.section. D.7.3"><a href="#rfc.section.D.7.3">D.7.3</a> Since draft-ietf-httpbis-p3-payload-014560 <h3 id="rfc.section.F.4.3"><a href="#rfc.section.F.4.3">F.4.3</a> Since draft-ietf-httpbis-p3-payload-01 4561 4561 </h3> 4562 <p id="rfc.section. D.7.3.p.1">Ongoing work on ABNF conversion (<<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>>):4562 <p id="rfc.section.F.4.3.p.1">Ongoing work on ABNF conversion (<<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>>): 4563 4563 </p> 4564 4564 <ul> 4565 4565 <li>Add explicit references to BNF syntax and rules imported from other parts of the specification.</li> 4566 4566 </ul> 4567 <h3 id="rfc.section. D.7.4"><a href="#rfc.section.D.7.4">D.7.4</a> <a id="changes.3.since.02" href="#changes.3.since.02">Since draft-ietf-httpbis-p3-payload-02</a></h3>4568 <p id="rfc.section. D.7.4.p.1">Closed issues: </p>4567 <h3 id="rfc.section.F.4.4"><a href="#rfc.section.F.4.4">F.4.4</a> <a id="changes.3.since.02" href="#changes.3.since.02">Since draft-ietf-httpbis-p3-payload-02</a></h3> 4568 <p id="rfc.section.F.4.4.p.1">Closed issues: </p> 4569 4569 <ul> 4570 4570 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/67">http://tools.ietf.org/wg/httpbis/trac/ticket/67</a>>: "Quoting Charsets" … … 4575 4575 </li> 4576 4576 </ul> 4577 <p id="rfc.section. D.7.4.p.2">Ongoing work on IANA Message Header Field Registration (<<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/40">http://tools.ietf.org/wg/httpbis/trac/ticket/40</a>>):4577 <p id="rfc.section.F.4.4.p.2">Ongoing work on IANA Message Header Field Registration (<<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/40">http://tools.ietf.org/wg/httpbis/trac/ticket/40</a>>): 4578 4578 </p> 4579 4579 <ul> 4580 4580 <li>Reference RFC 3984, and update header field registrations for headers defined in this document.</li> 4581 4581 </ul> 4582 <h3 id="rfc.section. D.7.5"><a href="#rfc.section.D.7.5">D.7.5</a> <a id="changes.3.since.03" href="#changes.3.since.03">Since draft-ietf-httpbis-p3-payload-03</a></h3>4583 <p id="rfc.section. D.7.5.p.1">Closed issues: </p>4582 <h3 id="rfc.section.F.4.5"><a href="#rfc.section.F.4.5">F.4.5</a> <a id="changes.3.since.03" href="#changes.3.since.03">Since draft-ietf-httpbis-p3-payload-03</a></h3> 4583 <p id="rfc.section.F.4.5.p.1">Closed issues: </p> 4584 4584 <ul> 4585 4585 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/67">http://tools.ietf.org/wg/httpbis/trac/ticket/67</a>>: "Quoting Charsets" … … 4590 4590 </li> 4591 4591 </ul> 4592 <p id="rfc.section. D.7.5.p.2">Other changes: </p>4592 <p id="rfc.section.F.4.5.p.2">Other changes: </p> 4593 4593 <ul> 4594 4594 <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 BCP97. 4595 4595 </li> 4596 4596 </ul> 4597 <h3 id="rfc.section. D.7.6"><a href="#rfc.section.D.7.6">D.7.6</a> <a id="changes.3.since.04" href="#changes.3.since.04">Since draft-ietf-httpbis-p3-payload-04</a></h3>4598 <p id="rfc.section. D.7.6.p.1">Closed issues: </p>4597 <h3 id="rfc.section.F.4.6"><a href="#rfc.section.F.4.6">F.4.6</a> <a id="changes.3.since.04" href="#changes.3.since.04">Since draft-ietf-httpbis-p3-payload-04</a></h3> 4598 <p id="rfc.section.F.4.6.p.1">Closed issues: </p> 4599 4599 <ul> 4600 4600 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/132">http://tools.ietf.org/wg/httpbis/trac/ticket/132</a>>: "RFC 2822 is updated by RFC 5322" 4601 4601 </li> 4602 4602 </ul> 4603 <p id="rfc.section. D.7.6.p.2">Ongoing work on ABNF conversion (<<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>>):4603 <p id="rfc.section.F.4.6.p.2">Ongoing work on ABNF conversion (<<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>>): 4604 4604 </p> 4605 4605 <ul> … … 4608 4608 <li>Rewrite ABNFs to spell out whitespace rules, factor out header field value format definitions.</li> 4609 4609 </ul> 4610 <h3 id="rfc.section. D.7.7"><a href="#rfc.section.D.7.7">D.7.7</a> <a id="changes.3.since.05" href="#changes.3.since.05">Since draft-ietf-httpbis-p3-payload-05</a></h3>4611 <p id="rfc.section. D.7.7.p.1">Closed issues: </p>4610 <h3 id="rfc.section.F.4.7"><a href="#rfc.section.F.4.7">F.4.7</a> <a id="changes.3.since.05" href="#changes.3.since.05">Since draft-ietf-httpbis-p3-payload-05</a></h3> 4611 <p id="rfc.section.F.4.7.p.1">Closed issues: </p> 4612 4612 <ul> 4613 4613 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/118">http://tools.ietf.org/wg/httpbis/trac/ticket/118</a>>: "Join "Differences Between HTTP Entities and RFC 2045 Entities"?" 4614 4614 </li> 4615 4615 </ul> 4616 <p id="rfc.section. D.7.7.p.2">Final work on ABNF conversion (<<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>>):4616 <p id="rfc.section.F.4.7.p.2">Final work on ABNF conversion (<<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>>): 4617 4617 </p> 4618 4618 <ul> 4619 4619 <li>Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.</li> 4620 4620 </ul> 4621 <p id="rfc.section. D.7.7.p.3">Other changes: </p>4621 <p id="rfc.section.F.4.7.p.3">Other changes: </p> 4622 4622 <ul> 4623 4623 <li>Move definition of quality values into Part 1.</li> 4624 4624 </ul> 4625 <h3 id="rfc.section. D.7.8"><a href="#rfc.section.D.7.8">D.7.8</a> <a id="changes.3.since.06" href="#changes.3.since.06">Since draft-ietf-httpbis-p3-payload-06</a></h3>4626 <p id="rfc.section. D.7.8.p.1">Closed issues: </p>4625 <h3 id="rfc.section.F.4.8"><a href="#rfc.section.F.4.8">F.4.8</a> <a id="changes.3.since.06" href="#changes.3.since.06">Since draft-ietf-httpbis-p3-payload-06</a></h3> 4626 <p id="rfc.section.F.4.8.p.1">Closed issues: </p> 4627 4627 <ul> 4628 4628 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/80">http://tools.ietf.org/wg/httpbis/trac/ticket/80</a>>: "Content-Location isn't special" … … 4631 4631 </li> 4632 4632 </ul> 4633 <h3 id="rfc.section. D.7.9"><a href="#rfc.section.D.7.9">D.7.9</a> <a id="changes.3.since.07" href="#changes.3.since.07">Since draft-ietf-httpbis-p3-payload-07</a></h3>4634 <p id="rfc.section. D.7.9.p.1">Closed issues: </p>4633 <h3 id="rfc.section.F.4.9"><a href="#rfc.section.F.4.9">F.4.9</a> <a id="changes.3.since.07" href="#changes.3.since.07">Since draft-ietf-httpbis-p3-payload-07</a></h3> 4634 <p id="rfc.section.F.4.9.p.1">Closed issues: </p> 4635 4635 <ul> 4636 4636 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/13">http://tools.ietf.org/wg/httpbis/trac/ticket/13</a>>: "Updated reference for language tags" … … 4647 4647 </li> 4648 4648 </ul> 4649 <p id="rfc.section. D.7.9.p.2">Partly resolved issues: </p>4649 <p id="rfc.section.F.4.9.p.2">Partly resolved issues: </p> 4650 4650 <ul> 4651 4651 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/148">http://tools.ietf.org/wg/httpbis/trac/ticket/148</a>>: "update IANA requirements wrt Transfer-Coding values" (add the IANA Considerations subsection) … … 4654 4654 </li> 4655 4655 </ul> 4656 <h3 id="rfc.section. D.7.10"><a href="#rfc.section.D.7.10">D.7.10</a> <a id="changes.3.since.08" href="#changes.3.since.08">Since draft-ietf-httpbis-p3-payload-08</a></h3>4657 <p id="rfc.section. D.7.10.p.1">Closed issues: </p>4656 <h3 id="rfc.section.F.4.10"><a href="#rfc.section.F.4.10">F.4.10</a> <a id="changes.3.since.08" href="#changes.3.since.08">Since draft-ietf-httpbis-p3-payload-08</a></h3> 4657 <p id="rfc.section.F.4.10.p.1">Closed issues: </p> 4658 4658 <ul> 4659 4659 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/81">http://tools.ietf.org/wg/httpbis/trac/ticket/81</a>>: "Content Negotiation for media types" … … 4662 4662 </li> 4663 4663 </ul> 4664 <h3 id="rfc.section. D.7.11"><a href="#rfc.section.D.7.11">D.7.11</a> <a id="changes.3.since.09" href="#changes.3.since.09">Since draft-ietf-httpbis-p3-payload-09</a></h3>4665 <p id="rfc.section. D.7.11.p.1">Closed issues: </p>4664 <h3 id="rfc.section.F.4.11"><a href="#rfc.section.F.4.11">F.4.11</a> <a id="changes.3.since.09" href="#changes.3.since.09">Since draft-ietf-httpbis-p3-payload-09</a></h3> 4665 <p id="rfc.section.F.4.11.p.1">Closed issues: </p> 4666 4666 <ul> 4667 4667 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/122">http://tools.ietf.org/wg/httpbis/trac/ticket/122</a>>: "MIME-Version not listed in P1, general header fields" … … 4674 4674 </li> 4675 4675 </ul> 4676 <p id="rfc.section. D.7.11.p.2">Partly resolved issues: </p>4676 <p id="rfc.section.F.4.11.p.2">Partly resolved issues: </p> 4677 4677 <ul> 4678 4678 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/196">http://tools.ietf.org/wg/httpbis/trac/ticket/196</a>>: "Term for the requested resource's URI" 4679 4679 </li> 4680 4680 </ul> 4681 <h3 id="rfc.section. D.7.12"><a href="#rfc.section.D.7.12">D.7.12</a> <a id="changes.3.since.10" href="#changes.3.since.10">Since draft-ietf-httpbis-p3-payload-10</a></h3>4682 <p id="rfc.section. D.7.12.p.1">Closed issues: </p>4681 <h3 id="rfc.section.F.4.12"><a href="#rfc.section.F.4.12">F.4.12</a> <a id="changes.3.since.10" href="#changes.3.since.10">Since draft-ietf-httpbis-p3-payload-10</a></h3> 4682 <p id="rfc.section.F.4.12.p.1">Closed issues: </p> 4683 4683 <ul> 4684 4684 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/69">http://tools.ietf.org/wg/httpbis/trac/ticket/69</a>>: "Clarify 'Requested Variant'" … … 4699 4699 </li> 4700 4700 </ul> 4701 <p id="rfc.section. D.7.12.p.2">Partly resolved issues: </p>4701 <p id="rfc.section.F.4.12.p.2">Partly resolved issues: </p> 4702 4702 <ul> 4703 4703 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/178">http://tools.ietf.org/wg/httpbis/trac/ticket/178</a>>: "Content-MD5 and partial responses" 4704 4704 </li> 4705 4705 </ul> 4706 <h3 id="rfc.section. D.7.13"><a href="#rfc.section.D.7.13">D.7.13</a> <a id="changes.3.since.11" href="#changes.3.since.11">Since draft-ietf-httpbis-p3-payload-11</a></h3>4707 <p id="rfc.section. D.7.13.p.1">Closed issues: </p>4706 <h3 id="rfc.section.F.4.13"><a href="#rfc.section.F.4.13">F.4.13</a> <a id="changes.3.since.11" href="#changes.3.since.11">Since draft-ietf-httpbis-p3-payload-11</a></h3> 4707 <p id="rfc.section.F.4.13.p.1">Closed issues: </p> 4708 4708 <ul> 4709 4709 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/123">http://tools.ietf.org/wg/httpbis/trac/ticket/123</a>>: "Factor out Content-Disposition" 4710 4710 </li> 4711 4711 </ul> 4712 <h3 id="rfc.section. D.7.14"><a href="#rfc.section.D.7.14">D.7.14</a> <a id="changes.3.since.12" href="#changes.3.since.12">Since draft-ietf-httpbis-p3-payload-12</a></h3>4713 <p id="rfc.section. D.7.14.p.1">Closed issues: </p>4712 <h3 id="rfc.section.F.4.14"><a href="#rfc.section.F.4.14">F.4.14</a> <a id="changes.3.since.12" href="#changes.3.since.12">Since draft-ietf-httpbis-p3-payload-12</a></h3> 4713 <p id="rfc.section.F.4.14.p.1">Closed issues: </p> 4714 4714 <ul> 4715 4715 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/224">http://tools.ietf.org/wg/httpbis/trac/ticket/224</a>>: "Header Classification" … … 4720 4720 </li> 4721 4721 </ul> 4722 <h3 id="rfc.section. D.7.15"><a href="#rfc.section.D.7.15">D.7.15</a> <a id="changes.3.since.13" href="#changes.3.since.13">Since draft-ietf-httpbis-p3-payload-13</a></h3>4723 <p id="rfc.section. D.7.15.p.1">Closed issues: </p>4722 <h3 id="rfc.section.F.4.15"><a href="#rfc.section.F.4.15">F.4.15</a> <a id="changes.3.since.13" href="#changes.3.since.13">Since draft-ietf-httpbis-p3-payload-13</a></h3> 4723 <p id="rfc.section.F.4.15.p.1">Closed issues: </p> 4724 4724 <ul> 4725 4725 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/20">http://tools.ietf.org/wg/httpbis/trac/ticket/20</a>>: "Default charsets for text media types" … … 4732 4732 </li> 4733 4733 </ul> 4734 <h3 id="rfc.section. D.7.16"><a href="#rfc.section.D.7.16">D.7.16</a> <a id="changes.3.since.14" href="#changes.3.since.14">Since draft-ietf-httpbis-p3-payload-14</a></h3>4735 <p id="rfc.section. D.7.16.p.1">None.</p>4736 <h3 id="rfc.section. D.7.17"><a href="#rfc.section.D.7.17">D.7.17</a> <a id="changes.3.since.15" href="#changes.3.since.15">Since draft-ietf-httpbis-p3-payload-15</a></h3>4737 <p id="rfc.section. D.7.17.p.1">Closed issues: </p>4734 <h3 id="rfc.section.F.4.16"><a href="#rfc.section.F.4.16">F.4.16</a> <a id="changes.3.since.14" href="#changes.3.since.14">Since draft-ietf-httpbis-p3-payload-14</a></h3> 4735 <p id="rfc.section.F.4.16.p.1">None.</p> 4736 <h3 id="rfc.section.F.4.17"><a href="#rfc.section.F.4.17">F.4.17</a> <a id="changes.3.since.15" href="#changes.3.since.15">Since draft-ietf-httpbis-p3-payload-15</a></h3> 4737 <p id="rfc.section.F.4.17.p.1">Closed issues: </p> 4738 4738 <ul> 4739 4739 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/285">http://tools.ietf.org/wg/httpbis/trac/ticket/285</a>>: "Strength of requirements on Accept re: 406" 4740 4740 </li> 4741 4741 </ul> 4742 <h3 id="rfc.section. D.7.18"><a href="#rfc.section.D.7.18">D.7.18</a> <a id="changes.3.since.16" href="#changes.3.since.16">Since draft-ietf-httpbis-p3-payload-16</a></h3>4743 <p id="rfc.section. D.7.18.p.1">Closed issues: </p>4742 <h3 id="rfc.section.F.4.18"><a href="#rfc.section.F.4.18">F.4.18</a> <a id="changes.3.since.16" href="#changes.3.since.16">Since draft-ietf-httpbis-p3-payload-16</a></h3> 4743 <p id="rfc.section.F.4.18.p.1">Closed issues: </p> 4744 4744 <ul> 4745 4745 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/186">http://tools.ietf.org/wg/httpbis/trac/ticket/186</a>>: "Document HTTP's error-handling philosophy" 4746 4746 </li> 4747 4747 </ul> 4748 <h3 id="rfc.section. D.7.19"><a href="#rfc.section.D.7.19">D.7.19</a> <a id="changes.3.since.17" href="#changes.3.since.17">Since draft-ietf-httpbis-p3-payload-17</a></h3>4749 <p id="rfc.section. D.7.19.p.1">Closed issues: </p>4748 <h3 id="rfc.section.F.4.19"><a href="#rfc.section.F.4.19">F.4.19</a> <a id="changes.3.since.17" href="#changes.3.since.17">Since draft-ietf-httpbis-p3-payload-17</a></h3> 4749 <p id="rfc.section.F.4.19.p.1">Closed issues: </p> 4750 4750 <ul> 4751 4751 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/323">http://tools.ietf.org/wg/httpbis/trac/ticket/323</a>>: "intended maturity level vs normative references" 4752 4752 </li> 4753 4753 </ul> 4754 <h3 id="rfc.section. D.7.20"><a href="#rfc.section.D.7.20">D.7.20</a> <a id="changes.3.since.18" href="#changes.3.since.18">Since draft-ietf-httpbis-p3-payload-18</a></h3>4755 <p id="rfc.section. D.7.20.p.1">Closed issues: </p>4754 <h3 id="rfc.section.F.4.20"><a href="#rfc.section.F.4.20">F.4.20</a> <a id="changes.3.since.18" href="#changes.3.since.18">Since draft-ietf-httpbis-p3-payload-18</a></h3> 4755 <p id="rfc.section.F.4.20.p.1">Closed issues: </p> 4756 4756 <ul> 4757 4757 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/330">http://tools.ietf.org/wg/httpbis/trac/ticket/330</a>>: "is ETag a representation header field?" … … 4762 4762 </li> 4763 4763 </ul> 4764 <h3 id="rfc.section. D.7.21"><a href="#rfc.section.D.7.21">D.7.21</a> <a id="changes.3.since.19" href="#changes.3.since.19">Since draft-ietf-httpbis-p3-payload-19</a></h3>4765 <p id="rfc.section. D.7.21.p.1">None yet.</p>4764 <h3 id="rfc.section.F.4.21"><a href="#rfc.section.F.4.21">F.4.21</a> <a id="changes.3.since.19" href="#changes.3.since.19">Since draft-ietf-httpbis-p3-payload-19</a></h3> 4765 <p id="rfc.section.F.4.21.p.1">None yet.</p> 4766 4766 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> 4767 4767 <p class="noprint"><a href="#rfc.index.1">1</a> <a href="#rfc.index.2">2</a> <a href="#rfc.index.3">3</a> <a href="#rfc.index.4">4</a> <a href="#rfc.index.5">5</a> <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.E">E</a> <a href="#rfc.index.F">F</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.L">L</a> <a href="#rfc.index.M">M</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> … … 4779 4779 <li>201 Created (status code) <a href="#rfc.xref.status.201.1">4.1</a>, <a href="#rfc.iref.24"><b>4.4.2</b></a>, <a href="#rfc.xref.status.201.2">8.2</a></li> 4780 4780 <li>202 Accepted (status code) <a href="#rfc.xref.status.202.1">4.1</a>, <a href="#rfc.iref.25"><b>4.4.3</b></a>, <a href="#rfc.xref.status.202.2">8.2</a></li> 4781 <li>203 Non-Authoritative Information (status code) <a href="#rfc.xref.status.203.1">4.1</a>, <a href="#rfc.iref.26"><b>4.4.4</b></a>, <a href="#rfc.xref.status.203.2">8.2</a>, <a href="#rfc.xref.status.203.3"> A</a></li>4781 <li>203 Non-Authoritative Information (status code) <a href="#rfc.xref.status.203.1">4.1</a>, <a href="#rfc.iref.26"><b>4.4.4</b></a>, <a href="#rfc.xref.status.203.2">8.2</a>, <a href="#rfc.xref.status.203.3">C</a></li> 4782 4782 <li>204 No Content (status code) <a href="#rfc.xref.status.204.1">4.1</a>, <a href="#rfc.iref.27"><b>4.4.5</b></a>, <a href="#rfc.xref.status.204.2">8.2</a></li> 4783 4783 <li>205 Reset Content (status code) <a href="#rfc.xref.status.205.1">4.1</a>, <a href="#rfc.iref.28"><b>4.4.6</b></a>, <a href="#rfc.xref.status.205.2">8.2</a></li> … … 4786 4786 <li><a id="rfc.index.3" href="#rfc.index.3"><b>3</b></a><ul> 4787 4787 <li>300 Multiple Choices (status code) <a href="#rfc.xref.status.300.1">4.1</a>, <a href="#rfc.iref.29"><b>4.5.1</b></a>, <a href="#rfc.xref.status.300.2">8.2</a></li> 4788 <li>301 Moved Permanently (status code) <a href="#rfc.xref.status.301.1">4.1</a>, <a href="#rfc.iref.30"><b>4.5.2</b></a>, <a href="#rfc.xref.status.301.2">8.2</a>, <a href="#rfc.xref.status.301.3"> A</a></li>4789 <li>302 Found (status code) <a href="#rfc.xref.status.302.1">4.1</a>, <a href="#rfc.iref.31"><b>4.5.3</b></a>, <a href="#rfc.xref.status.302.2">8.2</a>, <a href="#rfc.xref.status.302.3"> A</a></li>4788 <li>301 Moved Permanently (status code) <a href="#rfc.xref.status.301.1">4.1</a>, <a href="#rfc.iref.30"><b>4.5.2</b></a>, <a href="#rfc.xref.status.301.2">8.2</a>, <a href="#rfc.xref.status.301.3">C</a></li> 4789 <li>302 Found (status code) <a href="#rfc.xref.status.302.1">4.1</a>, <a href="#rfc.iref.31"><b>4.5.3</b></a>, <a href="#rfc.xref.status.302.2">8.2</a>, <a href="#rfc.xref.status.302.3">C</a></li> 4790 4790 <li>303 See Other (status code) <a href="#rfc.xref.status.303.1">4.1</a>, <a href="#rfc.iref.32"><b>4.5.4</b></a>, <a href="#rfc.xref.status.303.2">8.2</a></li> 4791 <li>305 Use Proxy (status code) <a href="#rfc.xref.status.305.1">4.1</a>, <a href="#rfc.iref.33"><b>4.5.5</b></a>, <a href="#rfc.xref.status.305.2">8.2</a>, <a href="#rfc.xref.status.305.3"> A</a></li>4791 <li>305 Use Proxy (status code) <a href="#rfc.xref.status.305.1">4.1</a>, <a href="#rfc.iref.33"><b>4.5.5</b></a>, <a href="#rfc.xref.status.305.2">8.2</a>, <a href="#rfc.xref.status.305.3">C</a></li> 4792 4792 <li>306 (Unused) (status code) <a href="#rfc.iref.34"><b>4.5.6</b></a>, <a href="#rfc.xref.status.306.1">8.2</a></li> 4793 <li>307 Temporary Redirect (status code) <a href="#rfc.xref.status.307.1">4.1</a>, <a href="#rfc.iref.35"><b>4.5.7</b></a>, <a href="#rfc.xref.status.307.2">8.2</a>, <a href="#rfc.xref.status.307.3"> A</a></li>4793 <li>307 Temporary Redirect (status code) <a href="#rfc.xref.status.307.1">4.1</a>, <a href="#rfc.iref.35"><b>4.5.7</b></a>, <a href="#rfc.xref.status.307.2">8.2</a>, <a href="#rfc.xref.status.307.3">C</a></li> 4794 4794 </ul> 4795 4795 </li> … … 4809 4809 <li>415 Unsupported Media Type (status code) <a href="#rfc.xref.status.415.1">4.1</a>, <a href="#rfc.iref.48"><b>4.6.13</b></a>, <a href="#rfc.xref.status.415.2">8.2</a></li> 4810 4810 <li>417 Expectation Failed (status code) <a href="#rfc.xref.status.417.1">4.1</a>, <a href="#rfc.iref.49"><b>4.6.14</b></a>, <a href="#rfc.xref.status.417.2">8.2</a></li> 4811 <li>426 Upgrade Required (status code) <a href="#rfc.xref.status.426.1">4.1</a>, <a href="#rfc.iref.50"><b>4.6.15</b></a>, <a href="#rfc.xref.status.426.2">8.2</a>, <a href="#rfc.xref.status.426.3"> A</a></li>4811 <li>426 Upgrade Required (status code) <a href="#rfc.xref.status.426.1">4.1</a>, <a href="#rfc.iref.50"><b>4.6.15</b></a>, <a href="#rfc.xref.status.426.2">8.2</a>, <a href="#rfc.xref.status.426.3">C</a></li> 4812 4812 </ul> 4813 4813 </li> … … 4822 4822 </li> 4823 4823 <li><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul> 4824 <li>Accept header field <a href="#rfc.xref.header.accept.1">3.2</a>, <a href="#rfc.xref.header.accept.2">6.5</a>, <a href="#rfc.iref.a.1"><b>7.1</b></a>, <a href="#rfc.xref.header.accept.3">8.3</a>, <a href="#rfc.xref.header.accept.4"> D.3.1</a></li>4825 <li>Accept-Charset header field <a href="#rfc.xref.header.accept-charset.1">3.2</a>, <a href="#rfc.iref.a.2"><b>7.2</b></a>, <a href="#rfc.xref.header.accept-charset.2">8.3</a>, <a href="#rfc.xref.header.accept-charset.3"> D.3.1</a>, <a href="#rfc.xref.header.accept-charset.4">D.6</a></li>4826 <li>Accept-Encoding header field <a href="#rfc.xref.header.accept-encoding.1">3.2</a>, <a href="#rfc.xref.header.accept-encoding.2">6.4</a>, <a href="#rfc.iref.a.3"><b>7.3</b></a>, <a href="#rfc.xref.header.accept-encoding.3">8.3</a>, <a href="#rfc.xref.header.accept-encoding.4">8.4</a>, <a href="#rfc.xref.header.accept-encoding.5"> D.3.1</a></li>4827 <li>Accept-Language header field <a href="#rfc.xref.header.accept-language.1">3.2</a>, <a href="#rfc.iref.a.4"><b>7.4</b></a>, <a href="#rfc.xref.header.accept-language.2">8.3</a>, <a href="#rfc.xref.header.accept-language.3"> D.3.1</a></li>4828 <li>Allow header field <a href="#rfc.xref.header.allow.1">2</a>, <a href="#rfc.xref.header.allow.2">3.3</a>, <a href="#rfc.iref.a.5"><b>7.5</b></a>, <a href="#rfc.xref.header.allow.3">8.3</a>, <a href="#rfc.xref.header.allow.4"> A</a></li>4824 <li>Accept header field <a href="#rfc.xref.header.accept.1">3.2</a>, <a href="#rfc.xref.header.accept.2">6.5</a>, <a href="#rfc.iref.a.1"><b>7.1</b></a>, <a href="#rfc.xref.header.accept.3">8.3</a>, <a href="#rfc.xref.header.accept.4">F.3.1</a></li> 4825 <li>Accept-Charset header field <a href="#rfc.xref.header.accept-charset.1">3.2</a>, <a href="#rfc.iref.a.2"><b>7.2</b></a>, <a href="#rfc.xref.header.accept-charset.2">8.3</a>, <a href="#rfc.xref.header.accept-charset.3">C</a>, <a href="#rfc.xref.header.accept-charset.4">F.3.1</a></li> 4826 <li>Accept-Encoding header field <a href="#rfc.xref.header.accept-encoding.1">3.2</a>, <a href="#rfc.xref.header.accept-encoding.2">6.4</a>, <a href="#rfc.iref.a.3"><b>7.3</b></a>, <a href="#rfc.xref.header.accept-encoding.3">8.3</a>, <a href="#rfc.xref.header.accept-encoding.4">8.4</a>, <a href="#rfc.xref.header.accept-encoding.5">F.3.1</a></li> 4827 <li>Accept-Language header field <a href="#rfc.xref.header.accept-language.1">3.2</a>, <a href="#rfc.iref.a.4"><b>7.4</b></a>, <a href="#rfc.xref.header.accept-language.2">8.3</a>, <a href="#rfc.xref.header.accept-language.3">F.3.1</a></li> 4828 <li>Allow header field <a href="#rfc.xref.header.allow.1">2</a>, <a href="#rfc.xref.header.allow.2">3.3</a>, <a href="#rfc.iref.a.5"><b>7.5</b></a>, <a href="#rfc.xref.header.allow.3">8.3</a>, <a href="#rfc.xref.header.allow.4">C</a></li> 4829 4829 </ul> 4830 4830 </li> … … 4838 4838 </li> 4839 4839 <li>compress (Coding Format) <a href="#rfc.iref.c.3">6.4</a></li> 4840 <li>CONNECT method <a href="#rfc.iref.c.2"><b>2.3.8</b></a>, <a href="#rfc.xref.CONNECT.1">8.1</a>, <a href="#rfc.xref.CONNECT.2"> A</a></li>4840 <li>CONNECT method <a href="#rfc.iref.c.2"><b>2.3.8</b></a>, <a href="#rfc.xref.CONNECT.1">8.1</a>, <a href="#rfc.xref.CONNECT.2">C</a></li> 4841 4841 <li>content negotiation <a href="#rfc.iref.c.1">1.1</a></li> 4842 <li>Content-Encoding header field <a href="#rfc.xref.header.content-encoding.1">6.4</a>, <a href="#rfc.iref.c.7"><b>7.6</b></a>, <a href="#rfc.xref.header.content-encoding.2">7.6</a>, <a href="#rfc.xref.header.content-encoding.3">8.3</a>, <a href="#rfc.xref.header.content-encoding.4"> D.2.1</a></li>4843 <li>Content-Language header field <a href="#rfc.iref.c.8"><b>7.7</b></a>, <a href="#rfc.xref.header.content-language.1">8.3</a>, <a href="#rfc.xref.header.content-language.2"> D.2.1</a></li>4844 <li>Content-Location header field <a href="#rfc.xref.header.content-location.1">2.3.4</a>, <a href="#rfc.iref.c.9"><b>7.8</b></a>, <a href="#rfc.xref.header.content-location.2">7.13</a>, <a href="#rfc.xref.header.content-location.3">8.3</a>, <a href="#rfc.xref.header.content-location.4"> D.2.1</a>, <a href="#rfc.xref.header.content-location.5">D.6</a></li>4845 <li>Content-Transfer-Encoding header field <a href="#rfc.iref.c.11"> D.4.5</a>, <a href="#rfc.xref.no.content-transfer-encoding.1">D.6</a></li>4846 <li>Content-Type header field <a href="#rfc.xref.header.content-type.1">3.1</a>, <a href="#rfc.xref.header.content-type.2">4</a>, <a href="#rfc.xref.header.content-type.3">6.5</a>, <a href="#rfc.iref.c.10"><b>7.9</b></a>, <a href="#rfc.xref.header.content-type.4">8.3</a>, <a href="#rfc.xref.header.content-type.5"> D.2.1</a></li>4842 <li>Content-Encoding header field <a href="#rfc.xref.header.content-encoding.1">6.4</a>, <a href="#rfc.iref.c.7"><b>7.6</b></a>, <a href="#rfc.xref.header.content-encoding.2">7.6</a>, <a href="#rfc.xref.header.content-encoding.3">8.3</a>, <a href="#rfc.xref.header.content-encoding.4">F.2.1</a></li> 4843 <li>Content-Language header field <a href="#rfc.iref.c.8"><b>7.7</b></a>, <a href="#rfc.xref.header.content-language.1">8.3</a>, <a href="#rfc.xref.header.content-language.2">F.2.1</a></li> 4844 <li>Content-Location header field <a href="#rfc.xref.header.content-location.1">2.3.4</a>, <a href="#rfc.iref.c.9"><b>7.8</b></a>, <a href="#rfc.xref.header.content-location.2">7.13</a>, <a href="#rfc.xref.header.content-location.3">8.3</a>, <a href="#rfc.xref.header.content-location.4">C</a>, <a href="#rfc.xref.header.content-location.5">F.2.1</a></li> 4845 <li>Content-Transfer-Encoding header field <a href="#rfc.iref.c.11">A.5</a>, <a href="#rfc.xref.no.content-transfer-encoding.1">C</a></li> 4846 <li>Content-Type header field <a href="#rfc.xref.header.content-type.1">3.1</a>, <a href="#rfc.xref.header.content-type.2">4</a>, <a href="#rfc.xref.header.content-type.3">6.5</a>, <a href="#rfc.iref.c.10"><b>7.9</b></a>, <a href="#rfc.xref.header.content-type.4">8.3</a>, <a href="#rfc.xref.header.content-type.5">F.2.1</a></li> 4847 4847 </ul> 4848 4848 </li> … … 4855 4855 </li> 4856 4856 <li><a id="rfc.index.E" href="#rfc.index.E"><b>E</b></a><ul> 4857 <li>Expect header field <a href="#rfc.xref.header.expect.1">3.2</a>, <a href="#rfc.xref.header.expect.2">4.6.14</a>, <a href="#rfc.iref.e.1"><b>7.11</b></a>, <a href="#rfc.xref.header.expect.3">8.3</a>, <a href="#rfc.xref.header.expect.4"> A</a></li>4857 <li>Expect header field <a href="#rfc.xref.header.expect.1">3.2</a>, <a href="#rfc.xref.header.expect.2">4.6.14</a>, <a href="#rfc.iref.e.1"><b>7.11</b></a>, <a href="#rfc.xref.header.expect.3">8.3</a>, <a href="#rfc.xref.header.expect.4">C</a></li> 4858 4858 <li>Expect Values 4859 4859 <ul> … … 4909 4909 <li><tt>media-type</tt> <a href="#rfc.iref.g.24"><b>6.5</b></a></li> 4910 4910 <li><tt>method</tt> <a href="#rfc.iref.g.1"><b>2</b></a></li> 4911 <li><tt>MIME-Version</tt> <a href="#rfc.iref.g.59"><b> D.4.1</b></a></li>4911 <li><tt>MIME-Version</tt> <a href="#rfc.iref.g.59"><b>A.1</b></a></li> 4912 4912 <li><tt>minute</tt> <a href="#rfc.iref.g.8"><b>6.1</b></a></li> 4913 4913 <li><tt>month</tt> <a href="#rfc.iref.g.13"><b>6.1</b></a></li> … … 4937 4937 <li>Header Fields 4938 4938 <ul> 4939 <li>Accept <a href="#rfc.xref.header.accept.1">3.2</a>, <a href="#rfc.xref.header.accept.2">6.5</a>, <a href="#rfc.iref.h.2"><b>7.1</b></a>, <a href="#rfc.xref.header.accept.3">8.3</a>, <a href="#rfc.xref.header.accept.4"> D.3.1</a></li>4940 <li>Accept-Charset <a href="#rfc.xref.header.accept-charset.1">3.2</a>, <a href="#rfc.iref.h.3"><b>7.2</b></a>, <a href="#rfc.xref.header.accept-charset.2">8.3</a>, <a href="#rfc.xref.header.accept-charset.3"> D.3.1</a>, <a href="#rfc.xref.header.accept-charset.4">D.6</a></li>4941 <li>Accept-Encoding <a href="#rfc.xref.header.accept-encoding.1">3.2</a>, <a href="#rfc.xref.header.accept-encoding.2">6.4</a>, <a href="#rfc.iref.h.4"><b>7.3</b></a>, <a href="#rfc.xref.header.accept-encoding.3">8.3</a>, <a href="#rfc.xref.header.accept-encoding.4">8.4</a>, <a href="#rfc.xref.header.accept-encoding.5"> D.3.1</a></li>4942 <li>Accept-Language <a href="#rfc.xref.header.accept-language.1">3.2</a>, <a href="#rfc.iref.h.5"><b>7.4</b></a>, <a href="#rfc.xref.header.accept-language.2">8.3</a>, <a href="#rfc.xref.header.accept-language.3"> D.3.1</a></li>4943 <li>Allow <a href="#rfc.xref.header.allow.1">2</a>, <a href="#rfc.xref.header.allow.2">3.3</a>, <a href="#rfc.iref.h.6"><b>7.5</b></a>, <a href="#rfc.xref.header.allow.3">8.3</a>, <a href="#rfc.xref.header.allow.4"> A</a></li>4944 <li>Content-Encoding <a href="#rfc.xref.header.content-encoding.1">6.4</a>, <a href="#rfc.iref.h.7"><b>7.6</b></a>, <a href="#rfc.xref.header.content-encoding.2">7.6</a>, <a href="#rfc.xref.header.content-encoding.3">8.3</a>, <a href="#rfc.xref.header.content-encoding.4"> D.2.1</a></li>4945 <li>Content-Language <a href="#rfc.iref.h.8"><b>7.7</b></a>, <a href="#rfc.xref.header.content-language.1">8.3</a>, <a href="#rfc.xref.header.content-language.2"> D.2.1</a></li>4946 <li>Content-Location <a href="#rfc.xref.header.content-location.1">2.3.4</a>, <a href="#rfc.iref.h.9"><b>7.8</b></a>, <a href="#rfc.xref.header.content-location.2">7.13</a>, <a href="#rfc.xref.header.content-location.3">8.3</a>, <a href="#rfc.xref.header.content-location.4"> D.2.1</a>, <a href="#rfc.xref.header.content-location.5">D.6</a></li>4947 <li>Content-Transfer-Encoding <a href="#rfc.iref.h.21"> D.4.5</a>, <a href="#rfc.xref.no.content-transfer-encoding.1">D.6</a></li>4948 <li>Content-Type <a href="#rfc.xref.header.content-type.1">3.1</a>, <a href="#rfc.xref.header.content-type.2">4</a>, <a href="#rfc.xref.header.content-type.3">6.5</a>, <a href="#rfc.iref.h.10"><b>7.9</b></a>, <a href="#rfc.xref.header.content-type.4">8.3</a>, <a href="#rfc.xref.header.content-type.5"> D.2.1</a></li>4939 <li>Accept <a href="#rfc.xref.header.accept.1">3.2</a>, <a href="#rfc.xref.header.accept.2">6.5</a>, <a href="#rfc.iref.h.2"><b>7.1</b></a>, <a href="#rfc.xref.header.accept.3">8.3</a>, <a href="#rfc.xref.header.accept.4">F.3.1</a></li> 4940 <li>Accept-Charset <a href="#rfc.xref.header.accept-charset.1">3.2</a>, <a href="#rfc.iref.h.3"><b>7.2</b></a>, <a href="#rfc.xref.header.accept-charset.2">8.3</a>, <a href="#rfc.xref.header.accept-charset.3">C</a>, <a href="#rfc.xref.header.accept-charset.4">F.3.1</a></li> 4941 <li>Accept-Encoding <a href="#rfc.xref.header.accept-encoding.1">3.2</a>, <a href="#rfc.xref.header.accept-encoding.2">6.4</a>, <a href="#rfc.iref.h.4"><b>7.3</b></a>, <a href="#rfc.xref.header.accept-encoding.3">8.3</a>, <a href="#rfc.xref.header.accept-encoding.4">8.4</a>, <a href="#rfc.xref.header.accept-encoding.5">F.3.1</a></li> 4942 <li>Accept-Language <a href="#rfc.xref.header.accept-language.1">3.2</a>, <a href="#rfc.iref.h.5"><b>7.4</b></a>, <a href="#rfc.xref.header.accept-language.2">8.3</a>, <a href="#rfc.xref.header.accept-language.3">F.3.1</a></li> 4943 <li>Allow <a href="#rfc.xref.header.allow.1">2</a>, <a href="#rfc.xref.header.allow.2">3.3</a>, <a href="#rfc.iref.h.6"><b>7.5</b></a>, <a href="#rfc.xref.header.allow.3">8.3</a>, <a href="#rfc.xref.header.allow.4">C</a></li> 4944 <li>Content-Encoding <a href="#rfc.xref.header.content-encoding.1">6.4</a>, <a href="#rfc.iref.h.7"><b>7.6</b></a>, <a href="#rfc.xref.header.content-encoding.2">7.6</a>, <a href="#rfc.xref.header.content-encoding.3">8.3</a>, <a href="#rfc.xref.header.content-encoding.4">F.2.1</a></li> 4945 <li>Content-Language <a href="#rfc.iref.h.8"><b>7.7</b></a>, <a href="#rfc.xref.header.content-language.1">8.3</a>, <a href="#rfc.xref.header.content-language.2">F.2.1</a></li> 4946 <li>Content-Location <a href="#rfc.xref.header.content-location.1">2.3.4</a>, <a href="#rfc.iref.h.9"><b>7.8</b></a>, <a href="#rfc.xref.header.content-location.2">7.13</a>, <a href="#rfc.xref.header.content-location.3">8.3</a>, <a href="#rfc.xref.header.content-location.4">C</a>, <a href="#rfc.xref.header.content-location.5">F.2.1</a></li> 4947 <li>Content-Transfer-Encoding <a href="#rfc.iref.h.21">A.5</a>, <a href="#rfc.xref.no.content-transfer-encoding.1">C</a></li> 4948 <li>Content-Type <a href="#rfc.xref.header.content-type.1">3.1</a>, <a href="#rfc.xref.header.content-type.2">4</a>, <a href="#rfc.xref.header.content-type.3">6.5</a>, <a href="#rfc.iref.h.10"><b>7.9</b></a>, <a href="#rfc.xref.header.content-type.4">8.3</a>, <a href="#rfc.xref.header.content-type.5">F.2.1</a></li> 4949 4949 <li>Date <a href="#rfc.xref.header.date.1">3.3</a>, <a href="#rfc.iref.h.11"><b>7.10</b></a>, <a href="#rfc.xref.header.date.2">8.3</a></li> 4950 <li>Expect <a href="#rfc.xref.header.expect.1">3.2</a>, <a href="#rfc.xref.header.expect.2">4.6.14</a>, <a href="#rfc.iref.h.12"><b>7.11</b></a>, <a href="#rfc.xref.header.expect.3">8.3</a>, <a href="#rfc.xref.header.expect.4"> A</a></li>4950 <li>Expect <a href="#rfc.xref.header.expect.1">3.2</a>, <a href="#rfc.xref.header.expect.2">4.6.14</a>, <a href="#rfc.iref.h.12"><b>7.11</b></a>, <a href="#rfc.xref.header.expect.3">8.3</a>, <a href="#rfc.xref.header.expect.4">C</a></li> 4951 4951 <li>From <a href="#rfc.xref.header.from.1">3.2</a>, <a href="#rfc.iref.h.13"><b>7.12</b></a>, <a href="#rfc.xref.header.from.2">8.3</a></li> 4952 <li>Location <a href="#rfc.xref.header.location.1">2.3.4</a>, <a href="#rfc.xref.header.location.2">3.3</a>, <a href="#rfc.xref.header.location.3">4.5</a>, <a href="#rfc.iref.h.14"><b>7.13</b></a>, <a href="#rfc.xref.header.location.4">8.3</a>, <a href="#rfc.xref.header.location.5"> A</a></li>4953 <li>Max-Forwards <a href="#rfc.xref.header.max-forwards.1">2.3.1</a>, <a href="#rfc.xref.header.max-forwards.2">2.3.7</a>, <a href="#rfc.xref.header.max-forwards.3">3.2</a>, <a href="#rfc.iref.h.15"><b>7.14</b></a>, <a href="#rfc.xref.header.max-forwards.4">8.3</a>, <a href="#rfc.xref.header.max-forwards.5"> A</a></li>4954 <li>MIME-Version <a href="#rfc.xref.mime-version.1">8.3</a>, <a href="#rfc.iref.h.20"><b> D.4.1</b></a></li>4955 <li>Referer <a href="#rfc.xref.header.referer.1">3.2</a>, <a href="#rfc.iref.h.16"><b>7.15</b></a>, <a href="#rfc.xref.header.referer.2">8.3</a>, <a href="#rfc.xref.header.referer.3"> A</a></li>4952 <li>Location <a href="#rfc.xref.header.location.1">2.3.4</a>, <a href="#rfc.xref.header.location.2">3.3</a>, <a href="#rfc.xref.header.location.3">4.5</a>, <a href="#rfc.iref.h.14"><b>7.13</b></a>, <a href="#rfc.xref.header.location.4">8.3</a>, <a href="#rfc.xref.header.location.5">C</a></li> 4953 <li>Max-Forwards <a href="#rfc.xref.header.max-forwards.1">2.3.1</a>, <a href="#rfc.xref.header.max-forwards.2">2.3.7</a>, <a href="#rfc.xref.header.max-forwards.3">3.2</a>, <a href="#rfc.iref.h.15"><b>7.14</b></a>, <a href="#rfc.xref.header.max-forwards.4">8.3</a>, <a href="#rfc.xref.header.max-forwards.5">C</a></li> 4954 <li>MIME-Version <a href="#rfc.xref.mime-version.1">8.3</a>, <a href="#rfc.iref.h.20"><b>A.1</b></a></li> 4955 <li>Referer <a href="#rfc.xref.header.referer.1">3.2</a>, <a href="#rfc.iref.h.16"><b>7.15</b></a>, <a href="#rfc.xref.header.referer.2">8.3</a>, <a href="#rfc.xref.header.referer.3">C</a></li> 4956 4956 <li>Retry-After <a href="#rfc.xref.header.retry-after.1">3.3</a>, <a href="#rfc.xref.header.retry-after.2">4.7.4</a>, <a href="#rfc.iref.h.17"><b>7.16</b></a>, <a href="#rfc.xref.header.retry-after.3">8.3</a></li> 4957 <li>Server <a href="#rfc.xref.header.server.1">3.3</a>, <a href="#rfc.iref.h.18"><b>7.17</b></a>, <a href="#rfc.xref.header.server.2">8.3</a>, <a href="#rfc.xref.header.server.3">9.1</a>, <a href="#rfc.xref.header.server.4"> A</a></li>4958 <li>User-Agent <a href="#rfc.xref.header.user-agent.1">3.2</a>, <a href="#rfc.iref.h.19"><b>7.18</b></a>, <a href="#rfc.xref.header.user-agent.2">8.3</a>, <a href="#rfc.xref.header.user-agent.3">9.1</a>, <a href="#rfc.xref.header.user-agent.4"> D.3.1</a></li>4957 <li>Server <a href="#rfc.xref.header.server.1">3.3</a>, <a href="#rfc.iref.h.18"><b>7.17</b></a>, <a href="#rfc.xref.header.server.2">8.3</a>, <a href="#rfc.xref.header.server.3">9.1</a>, <a href="#rfc.xref.header.server.4">C</a></li> 4958 <li>User-Agent <a href="#rfc.xref.header.user-agent.1">3.2</a>, <a href="#rfc.iref.h.19"><b>7.18</b></a>, <a href="#rfc.xref.header.user-agent.2">8.3</a>, <a href="#rfc.xref.header.user-agent.3">9.1</a>, <a href="#rfc.xref.header.user-agent.4">F.3.1</a></li> 4959 4959 </ul> 4960 4960 </li> … … 4966 4966 </li> 4967 4967 <li><a id="rfc.index.L" href="#rfc.index.L"><b>L</b></a><ul> 4968 <li>Location header field <a href="#rfc.xref.header.location.1">2.3.4</a>, <a href="#rfc.xref.header.location.2">3.3</a>, <a href="#rfc.xref.header.location.3">4.5</a>, <a href="#rfc.iref.l.1"><b>7.13</b></a>, <a href="#rfc.xref.header.location.4">8.3</a>, <a href="#rfc.xref.header.location.5"> A</a></li>4968 <li>Location header field <a href="#rfc.xref.header.location.1">2.3.4</a>, <a href="#rfc.xref.header.location.2">3.3</a>, <a href="#rfc.xref.header.location.3">4.5</a>, <a href="#rfc.iref.l.1"><b>7.13</b></a>, <a href="#rfc.xref.header.location.4">8.3</a>, <a href="#rfc.xref.header.location.5">C</a></li> 4969 4969 </ul> 4970 4970 </li> 4971 4971 <li><a id="rfc.index.M" href="#rfc.index.M"><b>M</b></a><ul> 4972 <li>Max-Forwards header field <a href="#rfc.xref.header.max-forwards.1">2.3.1</a>, <a href="#rfc.xref.header.max-forwards.2">2.3.7</a>, <a href="#rfc.xref.header.max-forwards.3">3.2</a>, <a href="#rfc.iref.m.9"><b>7.14</b></a>, <a href="#rfc.xref.header.max-forwards.4">8.3</a>, <a href="#rfc.xref.header.max-forwards.5"> A</a></li>4972 <li>Max-Forwards header field <a href="#rfc.xref.header.max-forwards.1">2.3.1</a>, <a href="#rfc.xref.header.max-forwards.2">2.3.7</a>, <a href="#rfc.xref.header.max-forwards.3">3.2</a>, <a href="#rfc.iref.m.9"><b>7.14</b></a>, <a href="#rfc.xref.header.max-forwards.4">8.3</a>, <a href="#rfc.xref.header.max-forwards.5">C</a></li> 4973 4973 <li>Methods 4974 4974 <ul> 4975 <li>CONNECT <a href="#rfc.iref.m.8"><b>2.3.8</b></a>, <a href="#rfc.xref.CONNECT.1">8.1</a>, <a href="#rfc.xref.CONNECT.2"> A</a></li>4975 <li>CONNECT <a href="#rfc.iref.m.8"><b>2.3.8</b></a>, <a href="#rfc.xref.CONNECT.1">8.1</a>, <a href="#rfc.xref.CONNECT.2">C</a></li> 4976 4976 <li>DELETE <a href="#rfc.iref.m.6"><b>2.3.6</b></a>, <a href="#rfc.xref.DELETE.1">8.1</a></li> 4977 4977 <li>GET <a href="#rfc.iref.m.2"><b>2.3.2</b></a>, <a href="#rfc.xref.GET.1">8.1</a></li> 4978 4978 <li>HEAD <a href="#rfc.iref.m.3"><b>2.3.3</b></a>, <a href="#rfc.xref.HEAD.1">8.1</a></li> 4979 4979 <li>OPTIONS <a href="#rfc.iref.m.1"><b>2.3.1</b></a>, <a href="#rfc.xref.OPTIONS.1">7.14</a>, <a href="#rfc.xref.OPTIONS.2">8.1</a></li> 4980 <li>POST <a href="#rfc.iref.m.4"><b>2.3.4</b></a>, <a href="#rfc.xref.POST.1">8.1</a>, <a href="#rfc.xref.POST.2"> A</a></li>4981 <li>PUT <a href="#rfc.iref.m.5"><b>2.3.5</b></a>, <a href="#rfc.xref.PUT.1">8.1</a>, <a href="#rfc.xref.PUT.2"> A</a></li>4980 <li>POST <a href="#rfc.iref.m.4"><b>2.3.4</b></a>, <a href="#rfc.xref.POST.1">8.1</a>, <a href="#rfc.xref.POST.2">C</a></li> 4981 <li>PUT <a href="#rfc.iref.m.5"><b>2.3.5</b></a>, <a href="#rfc.xref.PUT.1">8.1</a>, <a href="#rfc.xref.PUT.2">C</a></li> 4982 4982 <li>TRACE <a href="#rfc.iref.m.7"><b>2.3.7</b></a>, <a href="#rfc.xref.TRACE.1">7.14</a>, <a href="#rfc.xref.TRACE.2">8.1</a>, <a href="#rfc.xref.TRACE.3">9.1</a></li> 4983 4983 </ul> 4984 4984 </li> 4985 <li>MIME-Version header field <a href="#rfc.xref.mime-version.1">8.3</a>, <a href="#rfc.iref.m.10"><b> D.4.1</b></a></li>4985 <li>MIME-Version header field <a href="#rfc.xref.mime-version.1">8.3</a>, <a href="#rfc.iref.m.10"><b>A.1</b></a></li> 4986 4986 </ul> 4987 4987 </li> … … 4991 4991 </li> 4992 4992 <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul> 4993 <li><em>Part1</em> <a href="#rfc.xref.Part1.1">1</a>, <a href="#rfc.xref.Part1.2">1.2</a>, <a href="#rfc.xref.Part1.3">1.3</a>, <a href="#rfc.xref.Part1.4">1.3.1</a>, <a href="#rfc.xref.Part1.5">1.3.1</a>, <a href="#rfc.xref.Part1.6">1.3.1</a>, <a href="#rfc.xref.Part1.7">1.3.1</a>, <a href="#rfc.xref.Part1.8">1.3.1</a>, <a href="#rfc.xref.Part1.9">1.3.1</a>, <a href="#rfc.xref.Part1.10">1.3.1</a>, <a href="#rfc.xref.Part1.11">1.3.1</a>, <a href="#rfc.xref.Part1.12">1.3.2</a>, <a href="#rfc.xref.Part1.13">1.3.2</a>, <a href="#rfc.xref.Part1.14">1.3.2</a>, <a href="#rfc.xref.Part1.15">1.3.2</a>, <a href="#rfc.xref.Part1.16">2</a>, <a href="#rfc.xref.Part1.17">2.2.1</a>, <a href="#rfc.xref.Part1.18">2.3.1</a>, <a href="#rfc.xref.Part1.19">2.3.7</a>, <a href="#rfc.xref.Part1.20">2.3.7</a>, <a href="#rfc.xref.Part1.21">2.3.8</a>, <a href="#rfc.xref.Part1.22">3</a>, <a href="#rfc.xref.Part1.23">3.1</a>, <a href="#rfc.xref.Part1.24">3.1</a>, <a href="#rfc.xref.Part1.25">3.1</a>, <a href="#rfc.xref.Part1.26">3.1</a>, <a href="#rfc.xref.Part1.27">3.1</a>, <a href="#rfc.xref.Part1.28">3.2</a>, <a href="#rfc.xref.Part1.29">3.2</a>, <a href="#rfc.xref.Part1.30">3.3</a>, <a href="#rfc.xref.Part1.31">4.3.1</a>, <a href="#rfc.xref.Part1.32">4.3.2</a>, <a href="#rfc.xref.Part1.33">4.4.4</a>, <a href="#rfc.xref.Part1.34">4.4.6</a>, <a href="#rfc.xref.Part1.35">4.6.15</a>, <a href="#rfc.xref.Part1.36">4.7.6</a>, <a href="#rfc.xref.Part1.37">5</a>, <a href="#rfc.xref.Part1.38">5.1</a>, <a href="#rfc.xref.Part1.39">6.4</a>, <a href="#rfc.xref.Part1.40">6.4</a>, <a href="#rfc.xref.Part1.41">6.4</a>, <a href="#rfc.xref.Part1.42">6.4.1</a>, <a href="#rfc.xref.Part1.43">6.4.1</a>, <a href="#rfc.xref.Part1.44">7.1</a>, <a href="#rfc.xref.Part1.45">7.3</a>, <a href="#rfc.xref.Part1.46">7.8</a>, <a href="#rfc.xref.Part1.47">7.11</a>, <a href="#rfc.xref.Part1.48">7.17</a>, <a href="#rfc.xref.Part1.49">7.17</a>, <a href="#rfc.xref.Part1.50">7.18</a>, <a href="#rfc.xref.Part1.51">8.4</a>, <a href="#rfc.xref.Part1.52">8.4</a>, <a href="#rfc.xref.Part1.53">8.4</a>, <a href="#rfc.xref.Part1.54">10</a>, <a href="#Part1"><b>11.1</b></a>, <a href="#rfc.xref.Part1.55">A </a>, <a href="#rfc.xref.Part1.56">D.1.1</a>, <a href="#rfc.xref.Part1.57">D.1.2</a>, <a href="#rfc.xref.Part1.58">D.3.1</a>, <a href="#rfc.xref.Part1.59">D.4.6</a><ul>4993 <li><em>Part1</em> <a href="#rfc.xref.Part1.1">1</a>, <a href="#rfc.xref.Part1.2">1.2</a>, <a href="#rfc.xref.Part1.3">1.3</a>, <a href="#rfc.xref.Part1.4">1.3.1</a>, <a href="#rfc.xref.Part1.5">1.3.1</a>, <a href="#rfc.xref.Part1.6">1.3.1</a>, <a href="#rfc.xref.Part1.7">1.3.1</a>, <a href="#rfc.xref.Part1.8">1.3.1</a>, <a href="#rfc.xref.Part1.9">1.3.1</a>, <a href="#rfc.xref.Part1.10">1.3.1</a>, <a href="#rfc.xref.Part1.11">1.3.1</a>, <a href="#rfc.xref.Part1.12">1.3.2</a>, <a href="#rfc.xref.Part1.13">1.3.2</a>, <a href="#rfc.xref.Part1.14">1.3.2</a>, <a href="#rfc.xref.Part1.15">1.3.2</a>, <a href="#rfc.xref.Part1.16">2</a>, <a href="#rfc.xref.Part1.17">2.2.1</a>, <a href="#rfc.xref.Part1.18">2.3.1</a>, <a href="#rfc.xref.Part1.19">2.3.7</a>, <a href="#rfc.xref.Part1.20">2.3.7</a>, <a href="#rfc.xref.Part1.21">2.3.8</a>, <a href="#rfc.xref.Part1.22">3</a>, <a href="#rfc.xref.Part1.23">3.1</a>, <a href="#rfc.xref.Part1.24">3.1</a>, <a href="#rfc.xref.Part1.25">3.1</a>, <a href="#rfc.xref.Part1.26">3.1</a>, <a href="#rfc.xref.Part1.27">3.1</a>, <a href="#rfc.xref.Part1.28">3.2</a>, <a href="#rfc.xref.Part1.29">3.2</a>, <a href="#rfc.xref.Part1.30">3.3</a>, <a href="#rfc.xref.Part1.31">4.3.1</a>, <a href="#rfc.xref.Part1.32">4.3.2</a>, <a href="#rfc.xref.Part1.33">4.4.4</a>, <a href="#rfc.xref.Part1.34">4.4.6</a>, <a href="#rfc.xref.Part1.35">4.6.15</a>, <a href="#rfc.xref.Part1.36">4.7.6</a>, <a href="#rfc.xref.Part1.37">5</a>, <a href="#rfc.xref.Part1.38">5.1</a>, <a href="#rfc.xref.Part1.39">6.4</a>, <a href="#rfc.xref.Part1.40">6.4</a>, <a href="#rfc.xref.Part1.41">6.4</a>, <a href="#rfc.xref.Part1.42">6.4.1</a>, <a href="#rfc.xref.Part1.43">6.4.1</a>, <a href="#rfc.xref.Part1.44">7.1</a>, <a href="#rfc.xref.Part1.45">7.3</a>, <a href="#rfc.xref.Part1.46">7.8</a>, <a href="#rfc.xref.Part1.47">7.11</a>, <a href="#rfc.xref.Part1.48">7.17</a>, <a href="#rfc.xref.Part1.49">7.17</a>, <a href="#rfc.xref.Part1.50">7.18</a>, <a href="#rfc.xref.Part1.51">8.4</a>, <a href="#rfc.xref.Part1.52">8.4</a>, <a href="#rfc.xref.Part1.53">8.4</a>, <a href="#rfc.xref.Part1.54">10</a>, <a href="#Part1"><b>11.1</b></a>, <a href="#rfc.xref.Part1.55">A.6</a>, <a href="#rfc.xref.Part1.56">C</a>, <a href="#rfc.xref.Part1.57">F.1.1</a>, <a href="#rfc.xref.Part1.58">F.1.2</a>, <a href="#rfc.xref.Part1.59">F.3.1</a><ul> 4994 4994 <li><em>Section 1.2</em> <a href="#rfc.xref.Part1.3">1.3</a></li> 4995 4995 <li><em>Section 2</em> <a href="#rfc.xref.Part1.2">1.2</a></li> … … 5001 5001 <li><em>Section 3.2.4</em> <a href="#rfc.xref.Part1.8">1.3.1</a>, <a href="#rfc.xref.Part1.9">1.3.1</a>, <a href="#rfc.xref.Part1.10">1.3.1</a>, <a href="#rfc.xref.Part1.11">1.3.1</a>, <a href="#rfc.xref.Part1.13">1.3.2</a>, <a href="#rfc.xref.Part1.24">3.1</a></li> 5002 5002 <li><em>Section 3.2.5</em> <a href="#rfc.xref.Part1.23">3.1</a></li> 5003 <li><em>Section 3.3</em> <a href="#rfc.xref.Part1.17">2.2.1</a>, <a href="#rfc.xref.Part1.34">4.4.6</a>, <a href="#rfc.xref.Part1.37">5</a>, <a href="#rfc.xref.Part1.5 7">D.1.2</a></li>5004 <li><em>Section 3.3.1</em> <a href="#rfc.xref.Part1.5 9">D.4.6</a></li>5005 <li><em>Section 3.3.2</em> <a href="#rfc.xref.Part1.5 6">D.1.1</a></li>5003 <li><em>Section 3.3</em> <a href="#rfc.xref.Part1.17">2.2.1</a>, <a href="#rfc.xref.Part1.34">4.4.6</a>, <a href="#rfc.xref.Part1.37">5</a>, <a href="#rfc.xref.Part1.58">F.1.2</a></li> 5004 <li><em>Section 3.3.1</em> <a href="#rfc.xref.Part1.55">A.6</a></li> 5005 <li><em>Section 3.3.2</em> <a href="#rfc.xref.Part1.57">F.1.1</a></li> 5006 5006 <li><em>Section 4</em> <a href="#rfc.xref.Part1.42">6.4.1</a></li> 5007 5007 <li><em>Section 4.1</em> <a href="#rfc.xref.Part1.27">3.1</a></li> … … 5011 5011 <li><em>Section 4.2.3</em> <a href="#rfc.xref.Part1.41">6.4</a>, <a href="#rfc.xref.Part1.53">8.4</a></li> 5012 5012 <li><em>Section 4.3</em> <a href="#rfc.xref.Part1.29">3.2</a></li> 5013 <li><em>Section 4.3.1</em> <a href="#rfc.xref.Part1.44">7.1</a>, <a href="#rfc.xref.Part1.45">7.3</a>, <a href="#rfc.xref.Part1.5 8">D.3.1</a></li>5013 <li><em>Section 4.3.1</em> <a href="#rfc.xref.Part1.44">7.1</a>, <a href="#rfc.xref.Part1.45">7.3</a>, <a href="#rfc.xref.Part1.59">F.3.1</a></li> 5014 5014 <li><em>Section 5.3</em> <a href="#rfc.xref.Part1.18">2.3.1</a>, <a href="#rfc.xref.Part1.21">2.3.8</a></li> 5015 5015 <li><em>Section 5.4</em> <a href="#rfc.xref.Part1.28">3.2</a></li> 5016 5016 <li><em>Section 5.5</em> <a href="#rfc.xref.Part1.16">2</a>, <a href="#rfc.xref.Part1.30">3.3</a>, <a href="#rfc.xref.Part1.38">5.1</a>, <a href="#rfc.xref.Part1.46">7.8</a></li> 5017 5017 <li><em>Section 6.1</em> <a href="#rfc.xref.Part1.26">3.1</a></li> 5018 <li><em>Section 6.2</em> <a href="#rfc.xref.Part1.19">2.3.7</a>, <a href="#rfc.xref.Part1.49">7.17</a>, <a href="#rfc.xref.Part1.5 5">A</a></li>5018 <li><em>Section 6.2</em> <a href="#rfc.xref.Part1.19">2.3.7</a>, <a href="#rfc.xref.Part1.49">7.17</a>, <a href="#rfc.xref.Part1.56">C</a></li> 5019 5019 <li><em>Section 6.4.3</em> <a href="#rfc.xref.Part1.31">4.3.1</a>, <a href="#rfc.xref.Part1.47">7.11</a></li> 5020 5020 <li><em>Section 6.5</em> <a href="#rfc.xref.Part1.32">4.3.2</a>, <a href="#rfc.xref.Part1.35">4.6.15</a></li> … … 5023 5023 </ul> 5024 5024 </li> 5025 <li><em>Part4</em> <a href="#rfc.xref.Part4.1">3.2</a>, <a href="#rfc.xref.Part4.2">3.2</a>, <a href="#rfc.xref.Part4.3">3.2</a>, <a href="#rfc.xref.Part4.4">3.2</a>, <a href="#rfc.xref.Part4.5">3.3</a>, <a href="#rfc.xref.Part4.6">4.1</a>, <a href="#rfc.xref.Part4.7">4.1</a>, <a href="#rfc.xref.Part4.8">4.1</a>, <a href="#rfc.xref.Part4.9">4.4.2</a>, <a href="#rfc.xref.Part4.10">4.5</a>, <a href="#Part4"><b>11.1</b></a>, <a href="#rfc.xref.Part4.11"> C.2</a>, <a href="#rfc.xref.Part4.12">D.2.1</a>, <a href="#rfc.xref.Part4.13">D.2.1</a><ul>5026 <li><em>Section 2.2</em> <a href="#rfc.xref.Part4.13"> D.2.1</a></li>5027 <li><em>Section 2.3</em> <a href="#rfc.xref.Part4.5">3.3</a>, <a href="#rfc.xref.Part4.9">4.4.2</a>, <a href="#rfc.xref.Part4.12"> D.2.1</a></li>5025 <li><em>Part4</em> <a href="#rfc.xref.Part4.1">3.2</a>, <a href="#rfc.xref.Part4.2">3.2</a>, <a href="#rfc.xref.Part4.3">3.2</a>, <a href="#rfc.xref.Part4.4">3.2</a>, <a href="#rfc.xref.Part4.5">3.3</a>, <a href="#rfc.xref.Part4.6">4.1</a>, <a href="#rfc.xref.Part4.7">4.1</a>, <a href="#rfc.xref.Part4.8">4.1</a>, <a href="#rfc.xref.Part4.9">4.4.2</a>, <a href="#rfc.xref.Part4.10">4.5</a>, <a href="#Part4"><b>11.1</b></a>, <a href="#rfc.xref.Part4.11">E.2</a>, <a href="#rfc.xref.Part4.12">F.2.1</a>, <a href="#rfc.xref.Part4.13">F.2.1</a><ul> 5026 <li><em>Section 2.2</em> <a href="#rfc.xref.Part4.13">F.2.1</a></li> 5027 <li><em>Section 2.3</em> <a href="#rfc.xref.Part4.5">3.3</a>, <a href="#rfc.xref.Part4.9">4.4.2</a>, <a href="#rfc.xref.Part4.12">F.2.1</a></li> 5028 5028 <li><em>Section 3.1</em> <a href="#rfc.xref.Part4.1">3.2</a></li> 5029 5029 <li><em>Section 3.2</em> <a href="#rfc.xref.Part4.3">3.2</a></li> … … 5035 5035 </ul> 5036 5036 </li> 5037 <li><em>Part5</em> <a href="#rfc.xref.Part5.1">2.3.2</a>, <a href="#rfc.xref.Part5.2">3.2</a>, <a href="#rfc.xref.Part5.3">3.2</a>, <a href="#rfc.xref.Part5.4">3.3</a>, <a href="#rfc.xref.Part5.5">4.1</a>, <a href="#rfc.xref.Part5.6">4.1</a>, <a href="#rfc.xref.Part5.7">4.1</a>, <a href="#Part5"><b>11.1</b></a>, <a href="#rfc.xref.Part5.8"> D.1.1</a><ul>5037 <li><em>Part5</em> <a href="#rfc.xref.Part5.1">2.3.2</a>, <a href="#rfc.xref.Part5.2">3.2</a>, <a href="#rfc.xref.Part5.3">3.2</a>, <a href="#rfc.xref.Part5.4">3.3</a>, <a href="#rfc.xref.Part5.5">4.1</a>, <a href="#rfc.xref.Part5.6">4.1</a>, <a href="#rfc.xref.Part5.7">4.1</a>, <a href="#Part5"><b>11.1</b></a>, <a href="#rfc.xref.Part5.8">F.1.1</a><ul> 5038 5038 <li><em>Section 3</em> <a href="#rfc.xref.Part5.5">4.1</a></li> 5039 5039 <li><em>Section 3.1</em> <a href="#rfc.xref.Part5.6">4.1</a></li> 5040 5040 <li><em>Section 3.2</em> <a href="#rfc.xref.Part5.7">4.1</a></li> 5041 5041 <li><em>Section 5.1</em> <a href="#rfc.xref.Part5.4">3.3</a></li> 5042 <li><em>Section 5.2</em> <a href="#rfc.xref.Part5.8"> D.1.1</a></li>5042 <li><em>Section 5.2</em> <a href="#rfc.xref.Part5.8">F.1.1</a></li> 5043 5043 <li><em>Section 5.3</em> <a href="#rfc.xref.Part5.2">3.2</a></li> 5044 5044 <li><em>Section 5.4</em> <a href="#rfc.xref.Part5.1">2.3.2</a>, <a href="#rfc.xref.Part5.3">3.2</a></li> 5045 5045 </ul> 5046 5046 </li> 5047 <li><em>Part6</em> <a href="#rfc.xref.Part6.1">2.2.1</a>, <a href="#rfc.xref.Part6.2">2.3.2</a>, <a href="#rfc.xref.Part6.3">2.3.3</a>, <a href="#rfc.xref.Part6.4">2.3.4</a>, <a href="#rfc.xref.Part6.5">2.3.5</a>, <a href="#rfc.xref.Part6.6">2.3.6</a>, <a href="#rfc.xref.Part6.7">3.1</a>, <a href="#rfc.xref.Part6.8">3.3</a>, <a href="#rfc.xref.Part6.9">3.3</a>, <a href="#rfc.xref.Part6.10">4.2.1</a>, <a href="#rfc.xref.Part6.11">4.4.1</a>, <a href="#rfc.xref.Part6.12">4.4.4</a>, <a href="#rfc.xref.Part6.13">4.4.4</a>, <a href="#rfc.xref.Part6.14">4.4.4</a>, <a href="#rfc.xref.Part6.15">4.5.1</a>, <a href="#rfc.xref.Part6.16">4.5.2</a>, <a href="#rfc.xref.Part6.17">4.6.9</a>, <a href="#Part6"><b>11.1</b></a>, <a href="#rfc.xref.Part6.18"> D.2.1</a>, <a href="#rfc.xref.Part6.19">D.3.1</a><ul>5047 <li><em>Part6</em> <a href="#rfc.xref.Part6.1">2.2.1</a>, <a href="#rfc.xref.Part6.2">2.3.2</a>, <a href="#rfc.xref.Part6.3">2.3.3</a>, <a href="#rfc.xref.Part6.4">2.3.4</a>, <a href="#rfc.xref.Part6.5">2.3.5</a>, <a href="#rfc.xref.Part6.6">2.3.6</a>, <a href="#rfc.xref.Part6.7">3.1</a>, <a href="#rfc.xref.Part6.8">3.3</a>, <a href="#rfc.xref.Part6.9">3.3</a>, <a href="#rfc.xref.Part6.10">4.2.1</a>, <a href="#rfc.xref.Part6.11">4.4.1</a>, <a href="#rfc.xref.Part6.12">4.4.4</a>, <a href="#rfc.xref.Part6.13">4.4.4</a>, <a href="#rfc.xref.Part6.14">4.4.4</a>, <a href="#rfc.xref.Part6.15">4.5.1</a>, <a href="#rfc.xref.Part6.16">4.5.2</a>, <a href="#rfc.xref.Part6.17">4.6.9</a>, <a href="#Part6"><b>11.1</b></a>, <a href="#rfc.xref.Part6.18">F.2.1</a>, <a href="#rfc.xref.Part6.19">F.3.1</a><ul> 5048 5048 <li><em>Section 2.3.1</em> <a href="#rfc.xref.Part6.4">2.3.4</a></li> 5049 5049 <li><em>Section 2.3.1.1</em> <a href="#rfc.xref.Part6.11">4.4.1</a>, <a href="#rfc.xref.Part6.14">4.4.4</a>, <a href="#rfc.xref.Part6.15">4.5.1</a>, <a href="#rfc.xref.Part6.16">4.5.2</a>, <a href="#rfc.xref.Part6.17">4.6.9</a></li> … … 5052 5052 <li><em>Section 3.1</em> <a href="#rfc.xref.Part6.8">3.3</a></li> 5053 5053 <li><em>Section 3.2</em> <a href="#rfc.xref.Part6.12">4.4.4</a></li> 5054 <li><em>Section 3.3</em> <a href="#rfc.xref.Part6.18"> D.2.1</a></li>5055 <li><em>Section 3.5</em> <a href="#rfc.xref.Part6.9">3.3</a>, <a href="#rfc.xref.Part6.19"> D.3.1</a></li>5054 <li><em>Section 3.3</em> <a href="#rfc.xref.Part6.18">F.2.1</a></li> 5055 <li><em>Section 3.5</em> <a href="#rfc.xref.Part6.9">3.3</a>, <a href="#rfc.xref.Part6.19">F.3.1</a></li> 5056 5056 <li><em>Section 3.6</em> <a href="#rfc.xref.Part6.13">4.4.4</a></li> 5057 5057 </ul> … … 5067 5067 </ul> 5068 5068 </li> 5069 <li>payload <a href="#rfc.iref.p.3"> D.1</a></li>5070 <li>POST method <a href="#rfc.iref.p.1"><b>2.3.4</b></a>, <a href="#rfc.xref.POST.1">8.1</a>, <a href="#rfc.xref.POST.2"> A</a></li>5071 <li>PUT method <a href="#rfc.iref.p.2"><b>2.3.5</b></a>, <a href="#rfc.xref.PUT.1">8.1</a>, <a href="#rfc.xref.PUT.2"> A</a></li>5069 <li>payload <a href="#rfc.iref.p.3">F.1</a></li> 5070 <li>POST method <a href="#rfc.iref.p.1"><b>2.3.4</b></a>, <a href="#rfc.xref.POST.1">8.1</a>, <a href="#rfc.xref.POST.2">C</a></li> 5071 <li>PUT method <a href="#rfc.iref.p.2"><b>2.3.5</b></a>, <a href="#rfc.xref.PUT.1">8.1</a>, <a href="#rfc.xref.PUT.2">C</a></li> 5072 5072 </ul> 5073 5073 </li> 5074 5074 <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul> 5075 <li>Referer header field <a href="#rfc.xref.header.referer.1">3.2</a>, <a href="#rfc.iref.r.1"><b>7.15</b></a>, <a href="#rfc.xref.header.referer.2">8.3</a>, <a href="#rfc.xref.header.referer.3"> A</a></li>5076 <li>representation <a href="#rfc.iref.r.3"> D.2</a></li>5075 <li>Referer header field <a href="#rfc.xref.header.referer.1">3.2</a>, <a href="#rfc.iref.r.1"><b>7.15</b></a>, <a href="#rfc.xref.header.referer.2">8.3</a>, <a href="#rfc.xref.header.referer.3">C</a></li> 5076 <li>representation <a href="#rfc.iref.r.3">F.2</a></li> 5077 5077 <li>Retry-After header field <a href="#rfc.xref.header.retry-after.1">3.3</a>, <a href="#rfc.xref.header.retry-after.2">4.7.4</a>, <a href="#rfc.iref.r.2"><b>7.16</b></a>, <a href="#rfc.xref.header.retry-after.3">8.3</a></li> 5078 5078 <li><em>RFC1123</em> <a href="#rfc.xref.RFC1123.1">6.1</a>, <a href="#rfc.xref.RFC1123.2">6.1</a>, <a href="#RFC1123"><b>11.2</b></a><ul> … … 5080 5080 </ul> 5081 5081 </li> 5082 <li><em>RFC1945</em> <a href="#rfc.xref.RFC1945.1">4.5</a>, <a href="#RFC1945"><b>11.2</b></a>, <a href="#rfc.xref.RFC1945.2"> D.5</a><ul>5082 <li><em>RFC1945</em> <a href="#rfc.xref.RFC1945.1">4.5</a>, <a href="#RFC1945"><b>11.2</b></a>, <a href="#rfc.xref.RFC1945.2">B</a><ul> 5083 5083 <li><em>Section 9.3</em> <a href="#rfc.xref.RFC1945.1">4.5</a></li> 5084 5084 </ul> … … 5087 5087 <li><em>RFC1951</em> <a href="#rfc.xref.RFC1951.1">8.4</a>, <a href="#RFC1951"><b>11.1</b></a></li> 5088 5088 <li><em>RFC1952</em> <a href="#rfc.xref.RFC1952.1">8.4</a>, <a href="#RFC1952"><b>11.1</b></a></li> 5089 <li><em>RFC2045</em> <a href="#RFC2045"><b>11.1</b></a>, <a href="#rfc.xref.RFC2045.1"> D.4</a>, <a href="#rfc.xref.RFC2045.2">D.4.1</a></li>5090 <li><em>RFC2046</em> <a href="#rfc.xref.RFC2046.1">6.5</a>, <a href="#rfc.xref.RFC2046.2">6.5.2</a>, <a href="#RFC2046"><b>11.1</b></a>, <a href="#rfc.xref.RFC2046.3"> D.2.2</a>, <a href="#rfc.xref.RFC2046.4">D.4.2</a><ul>5091 <li><em>Section 4.5.1</em> <a href="#rfc.xref.RFC2046. 3">D.2.2</a></li>5089 <li><em>RFC2045</em> <a href="#RFC2045"><b>11.1</b></a>, <a href="#rfc.xref.RFC2045.1">A</a>, <a href="#rfc.xref.RFC2045.2">A.1</a></li> 5090 <li><em>RFC2046</em> <a href="#rfc.xref.RFC2046.1">6.5</a>, <a href="#rfc.xref.RFC2046.2">6.5.2</a>, <a href="#RFC2046"><b>11.1</b></a>, <a href="#rfc.xref.RFC2046.3">A.2</a>, <a href="#rfc.xref.RFC2046.4">F.2.2</a><ul> 5091 <li><em>Section 4.5.1</em> <a href="#rfc.xref.RFC2046.4">F.2.2</a></li> 5092 5092 <li><em>Section 5.1.1</em> <a href="#rfc.xref.RFC2046.2">6.5.2</a></li> 5093 5093 </ul> 5094 5094 </li> 5095 <li><em>RFC2049</em> <a href="#RFC2049"><b>11.2</b></a>, <a href="#rfc.xref.RFC2049.1"> D.4.2</a><ul>5096 <li><em>Section 4</em> <a href="#rfc.xref.RFC2049.1"> D.4.2</a></li>5095 <li><em>RFC2049</em> <a href="#RFC2049"><b>11.2</b></a>, <a href="#rfc.xref.RFC2049.1">A.2</a><ul> 5096 <li><em>Section 4</em> <a href="#rfc.xref.RFC2049.1">A.2</a></li> 5097 5097 </ul> 5098 5098 </li> 5099 <li><em>RFC2068</em> <a href="#rfc.xref.RFC2068.1">4.5</a>, <a href="#rfc.xref.RFC2068.2">4.5</a>, <a href="#RFC2068"><b>11.2</b></a>, <a href="#rfc.xref.RFC2068.3"> D.5</a><ul>5099 <li><em>RFC2068</em> <a href="#rfc.xref.RFC2068.1">4.5</a>, <a href="#rfc.xref.RFC2068.2">4.5</a>, <a href="#RFC2068"><b>11.2</b></a>, <a href="#rfc.xref.RFC2068.3">B</a><ul> 5100 5100 <li><em>Section 10.3</em> <a href="#rfc.xref.RFC2068.2">4.5</a></li> 5101 5101 <li><em>Section 10.3.4</em> <a href="#rfc.xref.RFC2068.1">4.5</a></li> 5102 5102 </ul> 5103 5103 </li> 5104 <li><em>RFC2076</em> <a href="#RFC2076"><b>11.2</b></a>, <a href="#rfc.xref.RFC2076.1"> D.5</a></li>5104 <li><em>RFC2076</em> <a href="#RFC2076"><b>11.2</b></a>, <a href="#rfc.xref.RFC2076.1">B</a></li> 5105 5105 <li><em>RFC2119</em> <a href="#rfc.xref.RFC2119.1">1.2</a>, <a href="#RFC2119"><b>11.1</b></a></li> 5106 5106 <li><em>RFC2277</em> <a href="#rfc.xref.RFC2277.1">6.3</a>, <a href="#RFC2277"><b>11.2</b></a></li> 5107 <li><em>RFC2295</em> <a href="#RFC2295"><b>11.2</b></a>, <a href="#rfc.xref.RFC2295.1"> D.3</a></li>5107 <li><em>RFC2295</em> <a href="#RFC2295"><b>11.2</b></a>, <a href="#rfc.xref.RFC2295.1">F.3</a></li> 5108 5108 <li><em>RFC2388</em> <a href="#rfc.xref.RFC2388.1">6.5.2</a>, <a href="#RFC2388"><b>11.2</b></a></li> 5109 <li><em>RFC2557</em> <a href="#rfc.xref.RFC2557.1">7.8</a>, <a href="#RFC2557"><b>11.2</b></a>, <a href="#rfc.xref.RFC2557.2"> D.4.7</a><ul>5109 <li><em>RFC2557</em> <a href="#rfc.xref.RFC2557.1">7.8</a>, <a href="#RFC2557"><b>11.2</b></a>, <a href="#rfc.xref.RFC2557.2">A.7</a><ul> 5110 5110 <li><em>Section 4</em> <a href="#rfc.xref.RFC2557.1">7.8</a></li> 5111 5111 </ul> 5112 5112 </li> 5113 <li><em>RFC2616</em> <a href="#rfc.xref.RFC2616.1">1</a>, <a href="#rfc.xref.RFC2616.2">4.5</a>, <a href="#rfc.xref.RFC2616.3">7.4</a>, <a href="#RFC2616"><b>11.2</b></a>, <a href="#rfc.xref.RFC2616.4"> C.1</a>, <a href="#rfc.xref.RFC2616.5">D.7.1</a><ul>5113 <li><em>RFC2616</em> <a href="#rfc.xref.RFC2616.1">1</a>, <a href="#rfc.xref.RFC2616.2">4.5</a>, <a href="#rfc.xref.RFC2616.3">7.4</a>, <a href="#RFC2616"><b>11.2</b></a>, <a href="#rfc.xref.RFC2616.4">E.1</a>, <a href="#rfc.xref.RFC2616.5">F.4.1</a><ul> 5114 5114 <li><em>Section 10.3.8</em> <a href="#rfc.xref.RFC2616.2">4.5</a></li> 5115 5115 <li><em>Section 14.4</em> <a href="#rfc.xref.RFC2616.3">7.4</a></li> 5116 5116 </ul> 5117 5117 </li> 5118 <li><em>RFC2817</em> <a href="#rfc.xref.RFC2817.1">8.2</a>, <a href="#RFC2817"><b>11.2</b></a>, <a href="#rfc.xref.RFC2817.2"> A</a>, <a href="#rfc.xref.RFC2817.3">A</a>, <a href="#rfc.xref.RFC2817.4">A</a><ul>5119 <li><em>Section 7.1</em> <a href="#rfc.xref.RFC2817.1">8.2</a>, <a href="#rfc.xref.RFC2817.3"> A</a></li>5118 <li><em>RFC2817</em> <a href="#rfc.xref.RFC2817.1">8.2</a>, <a href="#RFC2817"><b>11.2</b></a>, <a href="#rfc.xref.RFC2817.2">C</a>, <a href="#rfc.xref.RFC2817.3">C</a>, <a href="#rfc.xref.RFC2817.4">C</a><ul> 5119 <li><em>Section 7.1</em> <a href="#rfc.xref.RFC2817.1">8.2</a>, <a href="#rfc.xref.RFC2817.3">C</a></li> 5120 5120 </ul> 5121 5121 </li> … … 5146 5146 </ul> 5147 5147 </li> 5148 <li><em>RFC5322</em> <a href="#rfc.xref.RFC5322.1">6.1</a>, <a href="#rfc.xref.RFC5322.2">7.10</a>, <a href="#rfc.xref.RFC5322.3">7.12</a>, <a href="#rfc.xref.RFC5322.4">7.12</a>, <a href="#RFC5322"><b>11.2</b></a>, <a href="#rfc.xref.RFC5322.5"> D.4</a><ul>5148 <li><em>RFC5322</em> <a href="#rfc.xref.RFC5322.1">6.1</a>, <a href="#rfc.xref.RFC5322.2">7.10</a>, <a href="#rfc.xref.RFC5322.3">7.12</a>, <a href="#rfc.xref.RFC5322.4">7.12</a>, <a href="#RFC5322"><b>11.2</b></a>, <a href="#rfc.xref.RFC5322.5">A</a><ul> 5149 5149 <li><em>Section 3.3</em> <a href="#rfc.xref.RFC5322.1">6.1</a></li> 5150 5150 <li><em>Section 3.4</em> <a href="#rfc.xref.RFC5322.3">7.12</a>, <a href="#rfc.xref.RFC5322.4">7.12</a></li> … … 5158 5158 <li><em>RFC5789</em> <a href="#rfc.xref.RFC5789.1">2.3.5</a>, <a href="#RFC5789"><b>11.2</b></a></li> 5159 5159 <li><em>RFC5987</em> <a href="#rfc.xref.RFC5987.1">3.1</a>, <a href="#RFC5987"><b>11.2</b></a></li> 5160 <li><em>RFC6151</em> <a href="#RFC6151"><b>11.2</b></a>, <a href="#rfc.xref.RFC6151.1"> D.6</a></li>5161 <li><em>RFC6266</em> <a href="#RFC6266"><b>11.2</b></a>, <a href="#rfc.xref.RFC6266.1"> D.5</a>, <a href="#rfc.xref.RFC6266.2">D.6</a></li>5160 <li><em>RFC6151</em> <a href="#RFC6151"><b>11.2</b></a>, <a href="#rfc.xref.RFC6151.1">C</a></li> 5161 <li><em>RFC6266</em> <a href="#RFC6266"><b>11.2</b></a>, <a href="#rfc.xref.RFC6266.1">B</a>, <a href="#rfc.xref.RFC6266.2">C</a></li> 5162 5162 </ul> 5163 5163 </li> … … 5165 5165 <li>Safe Methods <a href="#rfc.iref.s.2"><b>2.1.1</b></a></li> 5166 5166 <li>selected representation <a href="#rfc.iref.s.1"><b>1.1</b></a></li> 5167 <li>Server header field <a href="#rfc.xref.header.server.1">3.3</a>, <a href="#rfc.iref.s.39"><b>7.17</b></a>, <a href="#rfc.xref.header.server.2">8.3</a>, <a href="#rfc.xref.header.server.3">9.1</a>, <a href="#rfc.xref.header.server.4"> A</a></li>5167 <li>Server header field <a href="#rfc.xref.header.server.1">3.3</a>, <a href="#rfc.iref.s.39"><b>7.17</b></a>, <a href="#rfc.xref.header.server.2">8.3</a>, <a href="#rfc.xref.header.server.3">9.1</a>, <a href="#rfc.xref.header.server.4">C</a></li> 5168 5168 <li>Status Codes 5169 5169 <ul> … … 5173 5173 <li>201 Created <a href="#rfc.xref.status.201.1">4.1</a>, <a href="#rfc.iref.s.6"><b>4.4.2</b></a>, <a href="#rfc.xref.status.201.2">8.2</a></li> 5174 5174 <li>202 Accepted <a href="#rfc.xref.status.202.1">4.1</a>, <a href="#rfc.iref.s.7"><b>4.4.3</b></a>, <a href="#rfc.xref.status.202.2">8.2</a></li> 5175 <li>203 Non-Authoritative Information <a href="#rfc.xref.status.203.1">4.1</a>, <a href="#rfc.iref.s.8"><b>4.4.4</b></a>, <a href="#rfc.xref.status.203.2">8.2</a>, <a href="#rfc.xref.status.203.3"> A</a></li>5175 <li>203 Non-Authoritative Information <a href="#rfc.xref.status.203.1">4.1</a>, <a href="#rfc.iref.s.8"><b>4.4.4</b></a>, <a href="#rfc.xref.status.203.2">8.2</a>, <a href="#rfc.xref.status.203.3">C</a></li> 5176 5176 <li>204 No Content <a href="#rfc.xref.status.204.1">4.1</a>, <a href="#rfc.iref.s.9"><b>4.4.5</b></a>, <a href="#rfc.xref.status.204.2">8.2</a></li> 5177 5177 <li>205 Reset Content <a href="#rfc.xref.status.205.1">4.1</a>, <a href="#rfc.iref.s.10"><b>4.4.6</b></a>, <a href="#rfc.xref.status.205.2">8.2</a></li> 5178 5178 <li>300 Multiple Choices <a href="#rfc.xref.status.300.1">4.1</a>, <a href="#rfc.iref.s.11"><b>4.5.1</b></a>, <a href="#rfc.xref.status.300.2">8.2</a></li> 5179 <li>301 Moved Permanently <a href="#rfc.xref.status.301.1">4.1</a>, <a href="#rfc.iref.s.12"><b>4.5.2</b></a>, <a href="#rfc.xref.status.301.2">8.2</a>, <a href="#rfc.xref.status.301.3"> A</a></li>5180 <li>302 Found <a href="#rfc.xref.status.302.1">4.1</a>, <a href="#rfc.iref.s.13"><b>4.5.3</b></a>, <a href="#rfc.xref.status.302.2">8.2</a>, <a href="#rfc.xref.status.302.3"> A</a></li>5179 <li>301 Moved Permanently <a href="#rfc.xref.status.301.1">4.1</a>, <a href="#rfc.iref.s.12"><b>4.5.2</b></a>, <a href="#rfc.xref.status.301.2">8.2</a>, <a href="#rfc.xref.status.301.3">C</a></li> 5180 <li>302 Found <a href="#rfc.xref.status.302.1">4.1</a>, <a href="#rfc.iref.s.13"><b>4.5.3</b></a>, <a href="#rfc.xref.status.302.2">8.2</a>, <a href="#rfc.xref.status.302.3">C</a></li> 5181 5181 <li>303 See Other <a href="#rfc.xref.status.303.1">4.1</a>, <a href="#rfc.iref.s.14"><b>4.5.4</b></a>, <a href="#rfc.xref.status.303.2">8.2</a></li> 5182 <li>305 Use Proxy <a href="#rfc.xref.status.305.1">4.1</a>, <a href="#rfc.iref.s.15"><b>4.5.5</b></a>, <a href="#rfc.xref.status.305.2">8.2</a>, <a href="#rfc.xref.status.305.3"> A</a></li>5182 <li>305 Use Proxy <a href="#rfc.xref.status.305.1">4.1</a>, <a href="#rfc.iref.s.15"><b>4.5.5</b></a>, <a href="#rfc.xref.status.305.2">8.2</a>, <a href="#rfc.xref.status.305.3">C</a></li> 5183 5183 <li>306 (Unused) <a href="#rfc.iref.s.16"><b>4.5.6</b></a>, <a href="#rfc.xref.status.306.1">8.2</a></li> 5184 <li>307 Temporary Redirect <a href="#rfc.xref.status.307.1">4.1</a>, <a href="#rfc.iref.s.17"><b>4.5.7</b></a>, <a href="#rfc.xref.status.307.2">8.2</a>, <a href="#rfc.xref.status.307.3"> A</a></li>5184 <li>307 Temporary Redirect <a href="#rfc.xref.status.307.1">4.1</a>, <a href="#rfc.iref.s.17"><b>4.5.7</b></a>, <a href="#rfc.xref.status.307.2">8.2</a>, <a href="#rfc.xref.status.307.3">C</a></li> 5185 5185 <li>400 Bad Request <a href="#rfc.xref.status.400.1">4.1</a>, <a href="#rfc.iref.s.18"><b>4.6.1</b></a>, <a href="#rfc.xref.status.400.2">8.2</a></li> 5186 5186 <li>402 Payment Required <a href="#rfc.xref.status.402.1">4.1</a>, <a href="#rfc.iref.s.19"><b>4.6.2</b></a>, <a href="#rfc.xref.status.402.2">8.2</a></li> … … 5197 5197 <li>415 Unsupported Media Type <a href="#rfc.xref.status.415.1">4.1</a>, <a href="#rfc.iref.s.30"><b>4.6.13</b></a>, <a href="#rfc.xref.status.415.2">8.2</a></li> 5198 5198 <li>417 Expectation Failed <a href="#rfc.xref.status.417.1">4.1</a>, <a href="#rfc.iref.s.31"><b>4.6.14</b></a>, <a href="#rfc.xref.status.417.2">8.2</a></li> 5199 <li>426 Upgrade Required <a href="#rfc.xref.status.426.1">4.1</a>, <a href="#rfc.iref.s.32"><b>4.6.15</b></a>, <a href="#rfc.xref.status.426.2">8.2</a>, <a href="#rfc.xref.status.426.3"> A</a></li>5199 <li>426 Upgrade Required <a href="#rfc.xref.status.426.1">4.1</a>, <a href="#rfc.iref.s.32"><b>4.6.15</b></a>, <a href="#rfc.xref.status.426.2">8.2</a>, <a href="#rfc.xref.status.426.3">C</a></li> 5200 5200 <li>500 Internal Server Error <a href="#rfc.xref.status.500.1">4.1</a>, <a href="#rfc.iref.s.33"><b>4.7.1</b></a>, <a href="#rfc.xref.status.500.2">8.2</a></li> 5201 5201 <li>501 Not Implemented <a href="#rfc.xref.status.501.1">4.1</a>, <a href="#rfc.iref.s.34"><b>4.7.2</b></a>, <a href="#rfc.xref.status.501.2">8.2</a></li> … … 5213 5213 </li> 5214 5214 <li><a id="rfc.index.U" href="#rfc.index.U"><b>U</b></a><ul> 5215 <li>User-Agent header field <a href="#rfc.xref.header.user-agent.1">3.2</a>, <a href="#rfc.iref.u.1"><b>7.18</b></a>, <a href="#rfc.xref.header.user-agent.2">8.3</a>, <a href="#rfc.xref.header.user-agent.3">9.1</a>, <a href="#rfc.xref.header.user-agent.4"> D.3.1</a></li>5215 <li>User-Agent header field <a href="#rfc.xref.header.user-agent.1">3.2</a>, <a href="#rfc.iref.u.1"><b>7.18</b></a>, <a href="#rfc.xref.header.user-agent.2">8.3</a>, <a href="#rfc.xref.header.user-agent.3">9.1</a>, <a href="#rfc.xref.header.user-agent.4">F.3.1</a></li> 5216 5216 </ul> 5217 5217 </li>
Note: See TracChangeset
for help on using the changeset viewer.
