Ignore:
Timestamp:
Mar 30, 2012, 8:57:47 AM (8 years ago)
Author:
julian.reschke@…
Message:

Step 9 of p2/p3-merge (see #351)

Location:
draft-ietf-httpbis/latest
Files:
4 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.html

    r1645 r1647  
    757757      <p id="rfc.section.1.p.1">The Hypertext Transfer Protocol (HTTP) is an application-level request/response protocol that uses extensible semantics and
    758758         MIME-like message payloads for flexible interaction with network-based hypertext information systems. HTTP relies upon the
    759          Uniform Resource Identifier (URI) standard <a href="#RFC3986" id="rfc.xref.RFC3986.1"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a> to indicate the target resource (<a href="#target-resource" title="Identifying a Target Resource">Section&nbsp;5.1</a>) and relationships between resources. Messages are passed in a format similar to that used by Internet mail <a href="#RFC5322" id="rfc.xref.RFC5322.1"><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> (see <a href="p2-semantics.html#differences.between.http.and.mime" title="Differences between HTTP and MIME">Appendix D.6</a> of <a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a> for the differences between HTTP and MIME messages).
     759         Uniform Resource Identifier (URI) standard <a href="#RFC3986" id="rfc.xref.RFC3986.1"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a> to indicate the target resource (<a href="#target-resource" title="Identifying a Target Resource">Section&nbsp;5.1</a>) and relationships between resources. Messages are passed in a format similar to that used by Internet mail <a href="#RFC5322" id="rfc.xref.RFC5322.1"><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> (see <a href="p2-semantics.html#differences.between.http.and.mime" title="Differences between HTTP and MIME">Appendix A</a> of <a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a> for the differences between HTTP and MIME messages).
    760760      </p>
    761761      <p id="rfc.section.1.p.2">HTTP is a generic interface protocol for information systems. It is designed to hide the details of how a service is implemented
     
    17251725      </p>
    17261726      <h3 id="rfc.section.4.3.1"><a href="#rfc.section.4.3.1">4.3.1</a>&nbsp;<a id="quality.values" href="#quality.values">Quality Values</a></h3>
    1727       <p id="rfc.section.4.3.1.p.1">Both transfer codings (TE request header field, <a href="#header.te" id="rfc.xref.header.te.3" title="TE">Section&nbsp;4.3</a>) and content negotiation (<a href="p2-semantics.html#content.negotiation" title="Content Negotiation">Appendix D.3</a> of <a href="#Part2" id="rfc.xref.Part2.10"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) use short "floating point" numbers to indicate the relative importance ("weight") of various negotiable parameters. A weight
     1727      <p id="rfc.section.4.3.1.p.1">Both transfer codings (TE request header field, <a href="#header.te" id="rfc.xref.header.te.3" title="TE">Section&nbsp;4.3</a>) and content negotiation (<a href="p2-semantics.html#content.negotiation" title="Content Negotiation">Appendix F.3</a> of <a href="#Part2" id="rfc.xref.Part2.10"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) use short "floating point" numbers to indicate the relative importance ("weight") of various negotiable parameters. A weight
    17281728         is normalized to a real number in the range 0 through 1, where 0 is the minimum and 1 the maximum value. If a parameter has
    17291729         a quality value of 0, then content with this parameter is "not acceptable" for the client. HTTP/1.1 applications <em class="bcp14">MUST NOT</em> generate more than three digits after the decimal point. User configuration of these values <em class="bcp14">SHOULD</em> also be limited in this fashion.
     
    37613761                        <li><em>Section 7.10</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.7">3.2</a></li>
    37623762                        <li><em>Section 7.11</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.19">6.4.3</a>, <a href="#rfc.xref.Part2.20">6.4.3</a></li>
    3763                         <li><em>Appendix D.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.10">4.3.1</a></li>
    3764                         <li><em>Appendix D.6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.1">1</a></li>
     3763                        <li><em>Appendix A</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.1">1</a></li>
     3764                        <li><em>Appendix F.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.10">4.3.1</a></li>
    37653765                     </ul>
    37663766                  </li>
  • draft-ietf-httpbis/latest/p2-semantics.html

    r1646 r1647  
    493493      <link rel="Chapter" title="10 Acknowledgments" href="#rfc.section.10">
    494494      <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">
    499501      <link href="p1-messaging.html" rel="prev">
    500502      <link href="p3-payload.html" rel="next">
     
    560562      <p>The current issues list is at &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/report/3">http://tools.ietf.org/wg/httpbis/trac/report/3</a>&gt; and related documents (including fancy diffs) can be found at &lt;<a href="http://tools.ietf.org/wg/httpbis/">http://tools.ietf.org/wg/httpbis/</a>&gt;.
    561563      </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&nbsp;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&nbsp;E.21</a>.
    563565      </p>
    564566      <h1><a id="rfc.status" href="#rfc.status">Status of This Memo</a></h1>
     
    750752         </li>
    751753         <li><a href="#rfc.authors">Authors' Addresses</a></li>
    752          <li>A.&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>
    753          <li>B.&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
    754          <li>C.&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul>
    755                <li>C.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C.1">Since RFC 2616</a></li>
    756                <li>C.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C.2">Since draft-ietf-httpbis-p2-semantics-00</a></li>
    757                <li>C.3&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C.3">Since draft-ietf-httpbis-p2-semantics-01</a></li>
    758                <li>C.4&nbsp;&nbsp;&nbsp;<a href="#changes.since.02">Since draft-ietf-httpbis-p2-semantics-02</a></li>
    759                <li>C.5&nbsp;&nbsp;&nbsp;<a href="#changes.since.03">Since draft-ietf-httpbis-p2-semantics-03</a></li>
    760                <li>C.6&nbsp;&nbsp;&nbsp;<a href="#changes.since.04">Since draft-ietf-httpbis-p2-semantics-04</a></li>
    761                <li>C.7&nbsp;&nbsp;&nbsp;<a href="#changes.since.05">Since draft-ietf-httpbis-p2-semantics-05</a></li>
    762                <li>C.8&nbsp;&nbsp;&nbsp;<a href="#changes.since.06">Since draft-ietf-httpbis-p2-semantics-06</a></li>
    763                <li>C.9&nbsp;&nbsp;&nbsp;<a href="#changes.since.07">Since draft-ietf-httpbis-p2-semantics-07</a></li>
    764                <li>C.10&nbsp;&nbsp;&nbsp;<a href="#changes.since.08">Since draft-ietf-httpbis-p2-semantics-08</a></li>
    765                <li>C.11&nbsp;&nbsp;&nbsp;<a href="#changes.since.09">Since draft-ietf-httpbis-p2-semantics-09</a></li>
    766                <li>C.12&nbsp;&nbsp;&nbsp;<a href="#changes.since.10">Since draft-ietf-httpbis-p2-semantics-10</a></li>
    767                <li>C.13&nbsp;&nbsp;&nbsp;<a href="#changes.since.11">Since draft-ietf-httpbis-p2-semantics-11</a></li>
    768                <li>C.14&nbsp;&nbsp;&nbsp;<a href="#changes.since.12">Since draft-ietf-httpbis-p2-semantics-12</a></li>
    769                <li>C.15&nbsp;&nbsp;&nbsp;<a href="#changes.since.13">Since draft-ietf-httpbis-p2-semantics-13</a></li>
    770                <li>C.16&nbsp;&nbsp;&nbsp;<a href="#changes.since.14">Since draft-ietf-httpbis-p2-semantics-14</a></li>
    771                <li>C.17&nbsp;&nbsp;&nbsp;<a href="#changes.since.15">Since draft-ietf-httpbis-p2-semantics-15</a></li>
    772                <li>C.18&nbsp;&nbsp;&nbsp;<a href="#changes.since.16">Since draft-ietf-httpbis-p2-semantics-16</a></li>
    773                <li>C.19&nbsp;&nbsp;&nbsp;<a href="#changes.since.17">Since draft-ietf-httpbis-p2-semantics-17</a></li>
    774                <li>C.20&nbsp;&nbsp;&nbsp;<a href="#changes.since.18">Since draft-ietf-httpbis-p2-semantics-18</a></li>
    775                <li>C.21&nbsp;&nbsp;&nbsp;<a href="#changes.since.19">Since draft-ietf-httpbis-p2-semantics-19</a></li>
     754         <li>A.&nbsp;&nbsp;&nbsp;<a href="#differences.between.http.and.mime">Differences between HTTP and MIME</a><ul>
     755               <li>A.1&nbsp;&nbsp;&nbsp;<a href="#mime-version">MIME-Version</a></li>
     756               <li>A.2&nbsp;&nbsp;&nbsp;<a href="#conversion.to.canonical.form">Conversion to Canonical Form</a></li>
     757               <li>A.3&nbsp;&nbsp;&nbsp;<a href="#conversion.of.date.formats">Conversion of Date Formats</a></li>
     758               <li>A.4&nbsp;&nbsp;&nbsp;<a href="#introduction.of.content-encoding">Introduction of Content-Encoding</a></li>
     759               <li>A.5&nbsp;&nbsp;&nbsp;<a href="#no.content-transfer-encoding">No Content-Transfer-Encoding</a></li>
     760               <li>A.6&nbsp;&nbsp;&nbsp;<a href="#introduction.of.transfer-encoding">Introduction of Transfer-Encoding</a></li>
     761               <li>A.7&nbsp;&nbsp;&nbsp;<a href="#mhtml.line.length">MHTML and Line Length Limitations</a></li>
    776762            </ul>
    777763         </li>
    778          <li>D.&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D">THE TEXT FORMERLY KNOWN AS PART3</a><ul>
    779                <li>D.1&nbsp;&nbsp;&nbsp;<a href="#payload">Payload</a><ul>
    780                      <li>D.1.1&nbsp;&nbsp;&nbsp;<a href="#payload.header.fields">Payload Header Fields</a></li>
    781                      <li>D.1.2&nbsp;&nbsp;&nbsp;<a href="#payload.body">Payload Body</a></li>
     764         <li>B.&nbsp;&nbsp;&nbsp;<a href="#additional.features">Additional Features</a></li>
     765         <li>C.&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>
     766         <li>D.&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
     767         <li>E.&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul>
     768               <li>E.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.E.1">Since RFC 2616</a></li>
     769               <li>E.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.E.2">Since draft-ietf-httpbis-p2-semantics-00</a></li>
     770               <li>E.3&nbsp;&nbsp;&nbsp;<a href="#rfc.section.E.3">Since draft-ietf-httpbis-p2-semantics-01</a></li>
     771               <li>E.4&nbsp;&nbsp;&nbsp;<a href="#changes.since.02">Since draft-ietf-httpbis-p2-semantics-02</a></li>
     772               <li>E.5&nbsp;&nbsp;&nbsp;<a href="#changes.since.03">Since draft-ietf-httpbis-p2-semantics-03</a></li>
     773               <li>E.6&nbsp;&nbsp;&nbsp;<a href="#changes.since.04">Since draft-ietf-httpbis-p2-semantics-04</a></li>
     774               <li>E.7&nbsp;&nbsp;&nbsp;<a href="#changes.since.05">Since draft-ietf-httpbis-p2-semantics-05</a></li>
     775               <li>E.8&nbsp;&nbsp;&nbsp;<a href="#changes.since.06">Since draft-ietf-httpbis-p2-semantics-06</a></li>
     776               <li>E.9&nbsp;&nbsp;&nbsp;<a href="#changes.since.07">Since draft-ietf-httpbis-p2-semantics-07</a></li>
     777               <li>E.10&nbsp;&nbsp;&nbsp;<a href="#changes.since.08">Since draft-ietf-httpbis-p2-semantics-08</a></li>
     778               <li>E.11&nbsp;&nbsp;&nbsp;<a href="#changes.since.09">Since draft-ietf-httpbis-p2-semantics-09</a></li>
     779               <li>E.12&nbsp;&nbsp;&nbsp;<a href="#changes.since.10">Since draft-ietf-httpbis-p2-semantics-10</a></li>
     780               <li>E.13&nbsp;&nbsp;&nbsp;<a href="#changes.since.11">Since draft-ietf-httpbis-p2-semantics-11</a></li>
     781               <li>E.14&nbsp;&nbsp;&nbsp;<a href="#changes.since.12">Since draft-ietf-httpbis-p2-semantics-12</a></li>
     782               <li>E.15&nbsp;&nbsp;&nbsp;<a href="#changes.since.13">Since draft-ietf-httpbis-p2-semantics-13</a></li>
     783               <li>E.16&nbsp;&nbsp;&nbsp;<a href="#changes.since.14">Since draft-ietf-httpbis-p2-semantics-14</a></li>
     784               <li>E.17&nbsp;&nbsp;&nbsp;<a href="#changes.since.15">Since draft-ietf-httpbis-p2-semantics-15</a></li>
     785               <li>E.18&nbsp;&nbsp;&nbsp;<a href="#changes.since.16">Since draft-ietf-httpbis-p2-semantics-16</a></li>
     786               <li>E.19&nbsp;&nbsp;&nbsp;<a href="#changes.since.17">Since draft-ietf-httpbis-p2-semantics-17</a></li>
     787               <li>E.20&nbsp;&nbsp;&nbsp;<a href="#changes.since.18">Since draft-ietf-httpbis-p2-semantics-18</a></li>
     788               <li>E.21&nbsp;&nbsp;&nbsp;<a href="#changes.since.19">Since draft-ietf-httpbis-p2-semantics-19</a></li>
     789            </ul>
     790         </li>
     791         <li>F.&nbsp;&nbsp;&nbsp;<a href="#rfc.section.F">THE TEXT FORMERLY KNOWN AS PART3</a><ul>
     792               <li>F.1&nbsp;&nbsp;&nbsp;<a href="#payload">Payload</a><ul>
     793                     <li>F.1.1&nbsp;&nbsp;&nbsp;<a href="#payload.header.fields">Payload Header Fields</a></li>
     794                     <li>F.1.2&nbsp;&nbsp;&nbsp;<a href="#payload.body">Payload Body</a></li>
    782795                  </ul>
    783796               </li>
    784                <li>D.2&nbsp;&nbsp;&nbsp;<a href="#representation3">Representation</a><ul>
    785                      <li>D.2.1&nbsp;&nbsp;&nbsp;<a href="#representation.header.fields">Representation Header Fields</a></li>
    786                      <li>D.2.2&nbsp;&nbsp;&nbsp;<a href="#representation.data">Representation Data</a></li>
     797               <li>F.2&nbsp;&nbsp;&nbsp;<a href="#representation3">Representation</a><ul>
     798                     <li>F.2.1&nbsp;&nbsp;&nbsp;<a href="#representation.header.fields">Representation Header Fields</a></li>
     799                     <li>F.2.2&nbsp;&nbsp;&nbsp;<a href="#representation.data">Representation Data</a></li>
    787800                  </ul>
    788801               </li>
    789                <li>D.3&nbsp;&nbsp;&nbsp;<a href="#content.negotiation">Content Negotiation</a><ul>
    790                      <li>D.3.1&nbsp;&nbsp;&nbsp;<a href="#server-driven.negotiation">Server-driven Negotiation</a></li>
    791                      <li>D.3.2&nbsp;&nbsp;&nbsp;<a href="#agent-driven.negotiation">Agent-driven Negotiation</a></li>
     802               <li>F.3&nbsp;&nbsp;&nbsp;<a href="#content.negotiation">Content Negotiation</a><ul>
     803                     <li>F.3.1&nbsp;&nbsp;&nbsp;<a href="#server-driven.negotiation">Server-driven Negotiation</a></li>
     804                     <li>F.3.2&nbsp;&nbsp;&nbsp;<a href="#agent-driven.negotiation">Agent-driven Negotiation</a></li>
    792805                  </ul>
    793806               </li>
    794                <li>D.4&nbsp;&nbsp;&nbsp;<a href="#differences.between.http.and.mime">Differences between HTTP and MIME</a><ul>
    795                      <li>D.4.1&nbsp;&nbsp;&nbsp;<a href="#mime-version">MIME-Version</a></li>
    796                      <li>D.4.2&nbsp;&nbsp;&nbsp;<a href="#conversion.to.canonical.form">Conversion to Canonical Form</a></li>
    797                      <li>D.4.3&nbsp;&nbsp;&nbsp;<a href="#conversion.of.date.formats">Conversion of Date Formats</a></li>
    798                      <li>D.4.4&nbsp;&nbsp;&nbsp;<a href="#introduction.of.content-encoding">Introduction of Content-Encoding</a></li>
    799                      <li>D.4.5&nbsp;&nbsp;&nbsp;<a href="#no.content-transfer-encoding">No Content-Transfer-Encoding</a></li>
    800                      <li>D.4.6&nbsp;&nbsp;&nbsp;<a href="#introduction.of.transfer-encoding">Introduction of Transfer-Encoding</a></li>
    801                      <li>D.4.7&nbsp;&nbsp;&nbsp;<a href="#mhtml.line.length">MHTML and Line Length Limitations</a></li>
    802                   </ul>
    803                </li>
    804                <li>D.5&nbsp;&nbsp;&nbsp;<a href="#additional.features">Additional Features</a></li>
    805                <li>D.6&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616-3">Changes from RFC 2616</a></li>
    806                <li>D.7&nbsp;&nbsp;&nbsp;<a href="#change.log3">Change Log (to be removed by RFC Editor before publication)</a><ul>
    807                      <li>D.7.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D.7.1">Since RFC 2616</a></li>
    808                      <li>D.7.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D.7.2">Since draft-ietf-httpbis-p3-payload-00</a></li>
    809                      <li>D.7.3&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D.7.3">Since draft-ietf-httpbis-p3-payload-01</a></li>
    810                      <li>D.7.4&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.02">Since draft-ietf-httpbis-p3-payload-02</a></li>
    811                      <li>D.7.5&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.03">Since draft-ietf-httpbis-p3-payload-03</a></li>
    812                      <li>D.7.6&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.04">Since draft-ietf-httpbis-p3-payload-04</a></li>
    813                      <li>D.7.7&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.05">Since draft-ietf-httpbis-p3-payload-05</a></li>
    814                      <li>D.7.8&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.06">Since draft-ietf-httpbis-p3-payload-06</a></li>
    815                      <li>D.7.9&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.07">Since draft-ietf-httpbis-p3-payload-07</a></li>
    816                      <li>D.7.10&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.08">Since draft-ietf-httpbis-p3-payload-08</a></li>
    817                      <li>D.7.11&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.09">Since draft-ietf-httpbis-p3-payload-09</a></li>
    818                      <li>D.7.12&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.10">Since draft-ietf-httpbis-p3-payload-10</a></li>
    819                      <li>D.7.13&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.11">Since draft-ietf-httpbis-p3-payload-11</a></li>
    820                      <li>D.7.14&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.12">Since draft-ietf-httpbis-p3-payload-12</a></li>
    821                      <li>D.7.15&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.13">Since draft-ietf-httpbis-p3-payload-13</a></li>
    822                      <li>D.7.16&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.14">Since draft-ietf-httpbis-p3-payload-14</a></li>
    823                      <li>D.7.17&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.15">Since draft-ietf-httpbis-p3-payload-15</a></li>
    824                      <li>D.7.18&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.16">Since draft-ietf-httpbis-p3-payload-16</a></li>
    825                      <li>D.7.19&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.17">Since draft-ietf-httpbis-p3-payload-17</a></li>
    826                      <li>D.7.20&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.18">Since draft-ietf-httpbis-p3-payload-18</a></li>
    827                      <li>D.7.21&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.19">Since draft-ietf-httpbis-p3-payload-19</a></li>
     807               <li>F.4&nbsp;&nbsp;&nbsp;<a href="#change.log3">Change Log (to be removed by RFC Editor before publication)</a><ul>
     808                     <li>F.4.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.F.4.1">Since RFC 2616</a></li>
     809                     <li>F.4.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.F.4.2">Since draft-ietf-httpbis-p3-payload-00</a></li>
     810                     <li>F.4.3&nbsp;&nbsp;&nbsp;<a href="#rfc.section.F.4.3">Since draft-ietf-httpbis-p3-payload-01</a></li>
     811                     <li>F.4.4&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.02">Since draft-ietf-httpbis-p3-payload-02</a></li>
     812                     <li>F.4.5&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.03">Since draft-ietf-httpbis-p3-payload-03</a></li>
     813                     <li>F.4.6&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.04">Since draft-ietf-httpbis-p3-payload-04</a></li>
     814                     <li>F.4.7&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.05">Since draft-ietf-httpbis-p3-payload-05</a></li>
     815                     <li>F.4.8&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.06">Since draft-ietf-httpbis-p3-payload-06</a></li>
     816                     <li>F.4.9&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.07">Since draft-ietf-httpbis-p3-payload-07</a></li>
     817                     <li>F.4.10&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.08">Since draft-ietf-httpbis-p3-payload-08</a></li>
     818                     <li>F.4.11&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.09">Since draft-ietf-httpbis-p3-payload-09</a></li>
     819                     <li>F.4.12&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.10">Since draft-ietf-httpbis-p3-payload-10</a></li>
     820                     <li>F.4.13&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.11">Since draft-ietf-httpbis-p3-payload-11</a></li>
     821                     <li>F.4.14&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.12">Since draft-ietf-httpbis-p3-payload-12</a></li>
     822                     <li>F.4.15&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.13">Since draft-ietf-httpbis-p3-payload-13</a></li>
     823                     <li>F.4.16&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.14">Since draft-ietf-httpbis-p3-payload-14</a></li>
     824                     <li>F.4.17&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.15">Since draft-ietf-httpbis-p3-payload-15</a></li>
     825                     <li>F.4.18&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.16">Since draft-ietf-httpbis-p3-payload-16</a></li>
     826                     <li>F.4.19&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.17">Since draft-ietf-httpbis-p3-payload-17</a></li>
     827                     <li>F.4.20&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.18">Since draft-ietf-httpbis-p3-payload-18</a></li>
     828                     <li>F.4.21&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.19">Since draft-ietf-httpbis-p3-payload-19</a></li>
    828829                  </ul>
    829830               </li>
     
    883884      </p>
    884885      <h2 id="rfc.section.1.3"><a href="#rfc.section.1.3">1.3</a>&nbsp;<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&nbsp;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&nbsp;D</a> shows the collected ABNF with the list rule expanded.
    886887      </p>
    887888      <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
     
    18041805         </li>
    18051806         <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&nbsp;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&nbsp;F.3.2</a>). This is status code 300 (Multiple Choices).
    18071808            </p>
    18081809         </li>
     
    18361837      <h3 id="rfc.section.4.5.1"><a href="#rfc.section.4.5.1">4.5.1</a>&nbsp;<a id="status.300" href="#status.300">300 Multiple Choices</a></h3>
    18371838      <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&nbsp;D.3</a>) is being provided so that the user (or user agent) can select a preferred representation by redirecting its request to that
     1839         (<a href="#content.negotiation" title="Content Negotiation">Appendix&nbsp;F.3</a>) is being provided so that the user (or user agent) can select a preferred representation by redirecting its request to that
    18391840         location.
    18401841      </p>
     
    19001901      <div id="rfc.iref.s.15"></div>
    19011902      <h3 id="rfc.section.4.5.5"><a href="#rfc.section.4.5.5">4.5.5</a>&nbsp;<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&nbsp;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&nbsp;C</a>), and is now deprecated.
    19031904      </p>
    19041905      <div id="rfc.iref.34"></div>
     
    26922693      </p>
    26932694      <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&nbsp;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&nbsp;F.2.2</a>.
    26952696      </p>
    26962697      <div id="rfc.iref.d.3"></div>
     
    33043305                  <td class="left">http</td>
    33053306                  <td class="left">standard</td>
    3306                   <td class="left"> <a href="#mime-version" id="rfc.xref.mime-version.1" title="MIME-Version">Appendix&nbsp;D.4.1</a>
     3307                  <td class="left"> <a href="#mime-version" id="rfc.xref.mime-version.1" title="MIME-Version">Appendix&nbsp;A.1</a>
    33073308                  </td>
    33083309               </tr>
     
    36773678               <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>&nbsp;<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>
    36783679      </div>
    3679       <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a>&nbsp;<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&nbsp;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&nbsp;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&nbsp;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&nbsp;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&nbsp;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&nbsp;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>&nbsp;<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>&nbsp;<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>&nbsp;<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&nbsp;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&nbsp;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>&nbsp;<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&nbsp;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>&nbsp;<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=&lt;content-coding&gt;"
     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>&nbsp;<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>&nbsp;<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>&nbsp;<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&nbsp;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>&nbsp;<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>&nbsp;<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&nbsp;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&nbsp;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&nbsp;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&nbsp;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&nbsp;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&nbsp;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
    36933762         user agent is able to make that determination based on the request method semantics. Furthermore, allow user agents to rewrite
    36943763         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>)
    36953764      </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 resource
     3765      <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
    36973766         needs to be accessed through the proxy given by the Location field. The Location field gave the URI of the proxy. The recipient
    36983767         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&nbsp;4.5.5</a>)
    36993768      </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&nbsp;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&nbsp;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 requirement
     3769      <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&nbsp;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&nbsp;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
    37053774         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&nbsp;7.5</a>)
    37063775      </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 simplified
     3776      <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
    37083777         (allowing trailing semicolons after "100-continue" when they were invalid before). (<a href="#header.expect" id="rfc.xref.header.expect.4" title="Expect">Section&nbsp;7.11</a>)
    37093778      </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 referred
     3779      <p id="rfc.section.C.p.13">Correct syntax of Location header field to allow URI references (including relative references and fragments), as referred
    37113780         symbol "absoluteURI" wasn't what was expected, and add some clarifications as to when use of fragments would not be appropriate.
    37123781         (<a href="#header.location" id="rfc.xref.header.location.5" title="Location">Section&nbsp;7.13</a>)
    37133782      </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&nbsp;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&nbsp;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&nbsp;7.17</a>)
    3720       </p>
    3721       <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<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&nbsp;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&nbsp;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&nbsp;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&nbsp;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&nbsp;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&nbsp;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&nbsp;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&nbsp;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&nbsp;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&nbsp;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&nbsp;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&nbsp;B</a>)
     3810      </p>
     3811      <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a>&nbsp;<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 "," [
    37233813 OWS media-range [ accept-params ] ] ) ]
    37243814<a href="#header.accept-charset" class="smpl">Accept-Charset</a> = *( "," OWS ) ( charset / "*" ) [ OWS ";" OWS "q="
     
    38673957
    38683958<a href="#preferred.date.format" class="smpl">year</a> = 4DIGIT
    3869 </pre> <div id="rfc.figure.u.63"></div>
     3959</pre> <div id="rfc.figure.u.64"></div>
    38703960      <p>ABNF diagnostics:</p><pre class="inline">; qvalue UNDEFINED
    38713961; Accept defined but not used
     
    38893979; User-Agent defined but not used
    38903980; obs-text defined but not used
    3891 </pre><h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<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>&nbsp;Since RFC 2616
     3981</pre><h1 id="rfc.section.E"><a href="#rfc.section.E">E.</a>&nbsp;<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>&nbsp;Since RFC 2616
    38933983      </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>&nbsp;Since draft-ietf-httpbis-p2-semantics-00
     3984      <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>&nbsp;Since draft-ietf-httpbis-p2-semantics-00
    38973987      </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>
    38993989      <ul>
    39003990         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/5">http://tools.ietf.org/wg/httpbis/trac/ticket/5</a>&gt;: "Via is a MUST" (&lt;<a href="http://purl.org/NET/http-errata#via-must">http://purl.org/NET/http-errata#via-must</a>&gt;)
     
    39154005         </li>
    39164006      </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>
    39184008      <ul>
    39194009         <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>
    39204010         </li>
    39214011      </ul>
    3922       <h2 id="rfc.section.C.3"><a href="#rfc.section.C.3">C.3</a>&nbsp;Since draft-ietf-httpbis-p2-semantics-01
     4012      <h2 id="rfc.section.E.3"><a href="#rfc.section.E.3">E.3</a>&nbsp;Since draft-ietf-httpbis-p2-semantics-01
    39234013      </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>
    39254015      <ul>
    39264016         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/21">http://tools.ietf.org/wg/httpbis/trac/ticket/21</a>&gt;: "PUT side effects"
     
    39294019         </li>
    39304020      </ul>
    3931       <p id="rfc.section.C.3.p.2">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
     4021      <p id="rfc.section.E.3.p.2">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
    39324022      </p>
    39334023      <ul>
     
    39364026         <li>Copy definition of delta-seconds from Part6 instead of referencing it.</li>
    39374027      </ul>
    3938       <h2 id="rfc.section.C.4"><a href="#rfc.section.C.4">C.4</a>&nbsp;<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>&nbsp;<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>
    39404030      <ul>
    39414031         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/24">http://tools.ietf.org/wg/httpbis/trac/ticket/24</a>&gt;: "Requiring Allow in 405 responses"
     
    39544044         </li>
    39554045      </ul>
    3956       <p id="rfc.section.C.4.p.2">Ongoing work on IANA Message Header Field Registration (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/40">http://tools.ietf.org/wg/httpbis/trac/ticket/40</a>&gt;):
     4046      <p id="rfc.section.E.4.p.2">Ongoing work on IANA Message Header Field Registration (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/40">http://tools.ietf.org/wg/httpbis/trac/ticket/40</a>&gt;):
    39574047      </p>
    39584048      <ul>
    39594049         <li>Reference RFC 3984, and update header field registrations for headers defined in this document.</li>
    39604050      </ul>
    3961       <p id="rfc.section.C.4.p.3">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
     4051      <p id="rfc.section.E.4.p.3">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
    39624052      </p>
    39634053      <ul>
    39644054         <li>Replace string literals when the string really is case-sensitive (method).</li>
    39654055      </ul>
    3966       <h2 id="rfc.section.C.5"><a href="#rfc.section.C.5">C.5</a>&nbsp;<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>&nbsp;<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>
    39684058      <ul>
    39694059         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/98">http://tools.ietf.org/wg/httpbis/trac/ticket/98</a>&gt;: "OPTIONS request bodies"
     
    39744064         </li>
    39754065      </ul>
    3976       <p id="rfc.section.C.5.p.2">Ongoing work on Method Registry (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/72">http://tools.ietf.org/wg/httpbis/trac/ticket/72</a>&gt;):
     4066      <p id="rfc.section.E.5.p.2">Ongoing work on Method Registry (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/72">http://tools.ietf.org/wg/httpbis/trac/ticket/72</a>&gt;):
    39774067      </p>
    39784068      <ul>
    39794069         <li>Added initial proposal for registration process, plus initial content (non-HTTP/1.1 methods to be added by a separate specification).</li>
    39804070      </ul>
    3981       <h2 id="rfc.section.C.6"><a href="#rfc.section.C.6">C.6</a>&nbsp;<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>&nbsp;<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>
    39834073      <ul>
    39844074         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/103">http://tools.ietf.org/wg/httpbis/trac/ticket/103</a>&gt;: "Content-*"
     
    39874077         </li>
    39884078      </ul>
    3989       <p id="rfc.section.C.6.p.2">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
     4079      <p id="rfc.section.E.6.p.2">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
    39904080      </p>
    39914081      <ul>
     
    39944084         <li>Rewrite ABNFs to spell out whitespace rules, factor out header field value format definitions.</li>
    39954085      </ul>
    3996       <h2 id="rfc.section.C.7"><a href="#rfc.section.C.7">C.7</a>&nbsp;<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>&nbsp;<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>
    39984088      <ul>
    39994089         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/94">http://tools.ietf.org/wg/httpbis/trac/ticket/94</a>&gt;: "reason-phrase BNF"
    40004090         </li>
    40014091      </ul>
    4002       <p id="rfc.section.C.7.p.2">Final work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
     4092      <p id="rfc.section.E.7.p.2">Final work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
    40034093      </p>
    40044094      <ul>
    40054095         <li>Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.</li>
    40064096      </ul>
    4007       <h2 id="rfc.section.C.8"><a href="#rfc.section.C.8">C.8</a>&nbsp;<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>&nbsp;<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>
    40094099      <ul>
    40104100         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/144">http://tools.ietf.org/wg/httpbis/trac/ticket/144</a>&gt;: "Clarify when Referer is sent"
     
    40154105         </li>
    40164106      </ul>
    4017       <h2 id="rfc.section.C.9"><a href="#rfc.section.C.9">C.9</a>&nbsp;<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>&nbsp;<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>
    40194109      <ul>
    40204110         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/27">http://tools.ietf.org/wg/httpbis/trac/ticket/27</a>&gt;: "Idempotency"
     
    40354125         </li>
    40364126      </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>
    40384128      <ul>
    40394129         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/171">http://tools.ietf.org/wg/httpbis/trac/ticket/171</a>&gt;: "Are OPTIONS and TRACE safe?"
    40404130         </li>
    40414131      </ul>
    4042       <h2 id="rfc.section.C.10"><a href="#rfc.section.C.10">C.10</a>&nbsp;<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>&nbsp;<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>
    40444134      <ul>
    40454135         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/10">http://tools.ietf.org/wg/httpbis/trac/ticket/10</a>&gt;: "Safe Methods vs Redirection" (we missed the introduction to the 3xx status codes when fixing this previously)
    40464136         </li>
    40474137      </ul>
    4048       <h2 id="rfc.section.C.11"><a href="#rfc.section.C.11">C.11</a>&nbsp;<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>&nbsp;<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>
    40504140      <ul>
    40514141         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/43">http://tools.ietf.org/wg/httpbis/trac/ticket/43</a>&gt;: "Fragment combination / precedence during redirects"
    40524142         </li>
    40534143      </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>
    40554145      <ul>
    40564146         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/185">http://tools.ietf.org/wg/httpbis/trac/ticket/185</a>&gt;: "Location header payload handling"
     
    40594149         </li>
    40604150      </ul>
    4061       <h2 id="rfc.section.C.12"><a href="#rfc.section.C.12">C.12</a>&nbsp;<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>&nbsp;<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>
    40634153      <ul>
    40644154         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/69">http://tools.ietf.org/wg/httpbis/trac/ticket/69</a>&gt;: "Clarify 'Requested Variant'"
     
    40754165         </li>
    40764166      </ul>
    4077       <h2 id="rfc.section.C.13"><a href="#rfc.section.C.13">C.13</a>&nbsp;<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>&nbsp;<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>
    40794169      <ul>
    40804170         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/229">http://tools.ietf.org/wg/httpbis/trac/ticket/229</a>&gt;: "Considerations for new status codes"
     
    40854175         </li>
    40864176      </ul>
    4087       <h2 id="rfc.section.C.14"><a href="#rfc.section.C.14">C.14</a>&nbsp;<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>&nbsp;<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>
    40894179      <ul>
    40904180         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/43">http://tools.ietf.org/wg/httpbis/trac/ticket/43</a>&gt;: "Fragment combination / precedence during redirects" (added warning about having a fragid on the redirect may cause inconvenience
     
    41284218         </li>
    41294219      </ul>
    4130       <h2 id="rfc.section.C.15"><a href="#rfc.section.C.15">C.15</a>&nbsp;<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>&nbsp;<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>
    41324222      <ul>
    41334223         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/276">http://tools.ietf.org/wg/httpbis/trac/ticket/276</a>&gt;: "untangle ABNFs for header fields"
     
    41364226         </li>
    41374227      </ul>
    4138       <h2 id="rfc.section.C.16"><a href="#rfc.section.C.16">C.16</a>&nbsp;<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>&nbsp;<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>
    41404230      <ul>
    41414231         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/255">http://tools.ietf.org/wg/httpbis/trac/ticket/255</a>&gt;: "Clarify status code for rate limiting"
     
    41484238         </li>
    41494239      </ul>
    4150       <h2 id="rfc.section.C.17"><a href="#rfc.section.C.17">C.17</a>&nbsp;<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>&nbsp;<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>
    41524242      <ul>
    41534243         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/285">http://tools.ietf.org/wg/httpbis/trac/ticket/285</a>&gt;: "Strength of requirements on Accept re: 406"
     
    41564246         </li>
    41574247      </ul>
    4158       <h2 id="rfc.section.C.18"><a href="#rfc.section.C.18">C.18</a>&nbsp;<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>&nbsp;<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>
    41604250      <ul>
    41614251         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/160">http://tools.ietf.org/wg/httpbis/trac/ticket/160</a>&gt;: "Redirects and non-GET methods"
     
    41684258         </li>
    41694259      </ul>
    4170       <h2 id="rfc.section.C.19"><a href="#rfc.section.C.19">C.19</a>&nbsp;<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>&nbsp;<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>
    41724262      <ul>
    41734263         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/185">http://tools.ietf.org/wg/httpbis/trac/ticket/185</a>&gt;: "Location header payload handling"
     
    41844274         </li>
    41854275      </ul>
    4186       <h2 id="rfc.section.C.20"><a href="#rfc.section.C.20">C.20</a>&nbsp;<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>&nbsp;<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>
    41884278      <ul>
    41894279         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/227">http://tools.ietf.org/wg/httpbis/trac/ticket/227</a>&gt;: "Combining HEAD responses"
     
    42064296         </li>
    42074297      </ul>
    4208       <h2 id="rfc.section.C.21"><a href="#rfc.section.C.21">C.21</a>&nbsp;<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>&nbsp;<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>
    42104300      <ul>
    42114301         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/312">http://tools.ietf.org/wg/httpbis/trac/ticket/312</a>&gt;: "should there be a permanent variant of 307"
    42124302         </li>
    42134303      </ul>
    4214       <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a>&nbsp;THE TEXT FORMERLY KNOWN AS PART3
     4304      <h1 id="rfc.section.F"><a href="#rfc.section.F">F.</a>&nbsp;THE TEXT FORMERLY KNOWN AS PART3
    42154305      </h1>
    4216       <h2 id="rfc.section.D.1"><a href="#rfc.section.D.1">D.1</a>&nbsp;<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>&nbsp;<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,
    42184308         in the form of header fields, and data, in the form of the sequence of octets in the message body after any transfer-coding
    42194309         has been decoded.
    42204310      </p>
    42214311      <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 representation
     4312      <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
    42234313         because some messages contain only the associated representation's header fields (e.g., responses to HEAD) or only some part(s)
    42244314         of the representation (e.g., the 206 status code).
    42254315      </p>
    4226       <h3 id="rfc.section.D.1.1"><a href="#rfc.section.D.1.1">D.1.1</a>&nbsp;<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 "payload
     4316      <h3 id="rfc.section.F.1.1"><a href="#rfc.section.F.1.1">F.1.1</a>&nbsp;<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
    42284318         header fields". The following payload header fields are defined by HTTP/1.1:
    42294319      </p>
     
    42394329               <tr>
    42404330                  <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.56"><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>
    42424332               </tr>
    42434333               <tr>
     
    42484338         </table>
    42494339      </div>
    4250       <h3 id="rfc.section.D.1.2"><a href="#rfc.section.D.1.2">D.1.2</a>&nbsp;<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 ensure
     4340      <h3 id="rfc.section.F.1.2"><a href="#rfc.section.F.1.2">F.1.2</a>&nbsp;<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
    42524342         safe and proper transfer of the message.
    42534343      </p>
    42544344      <div id="rfc.iref.r.3"></div>
    4255       <h2 id="rfc.section.D.2"><a href="#rfc.section.D.2">D.2</a>&nbsp;<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 information
     4345      <h2 id="rfc.section.F.2"><a href="#rfc.section.F.2">F.2</a>&nbsp;<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
    42574347         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
    42584348         at some point in the future (e.g., in a PUT request).
    42594349      </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 resource
     4350      <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
    42614351         identified by the effective request URI). The precise semantics of a representation are determined by the type of message
    42624352         (request or response), the request method, the response status code, and the representation metadata. For example, the above
     
    42674357         next steps are suggested for resolving it.
    42684358      </p>
    4269       <h3 id="rfc.section.D.2.1"><a href="#rfc.section.D.2.1">D.2.1</a>&nbsp;<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 message
     4359      <h3 id="rfc.section.F.2.1"><a href="#rfc.section.F.2.1">F.2.1</a>&nbsp;<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
    42714361         body is present, about the representation that would have been transferred in a 200 response to a simultaneous GET request
    42724362         with the same effective request URI.
    42734363      </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>
    42754365      <div id="rfc.table.u.6">
    42764366         <table class="tt full left" cellpadding="3" cellspacing="0">
     
    42924382               <tr>
    42934383                  <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&nbsp;7.8</a></td>
     4384                  <td class="left"><a href="#header.content-location" id="rfc.xref.header.content-location.5" title="Content-Location">Section&nbsp;7.8</a></td>
    42954385               </tr>
    42964386               <tr>
     
    43054395         </table>
    43064396      </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 included
     4397      <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
    43084398         in the message for responses to some state-changing methods. The following header fields are defined as selected representation
    43094399         metadata:
     
    43294419         </table>
    43304420      </div>
    4331       <h3 id="rfc.section.D.2.2"><a href="#rfc.section.D.2.2">D.2.2</a>&nbsp;<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 referred
     4421      <h3 id="rfc.section.F.2.2"><a href="#rfc.section.F.2.2">F.2.2</a>&nbsp;<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
    43334423         to by the message semantics and the effective request URI. The representation data is in a format and encoding defined by
    43344424         the representation metadata header fields.
    43354425      </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 define
     4426      <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
    43374427         a two-layer, ordered encoding model:
    43384428      </p>
    4339       <div id="rfc.figure.u.64"></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 payload
     4429      <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
    43414431         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
    43424432         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 for
     4433         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
    43464436         a given representation, with the result that some clients will examine a response body's content and override the specified
    43474437         type. Clients that do so risk drawing incorrect conclusions, which might expose additional security risks (e.g., "privilege
     
    43504440         such "content sniffing" when it is used.
    43514441      </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,
    43534443         that are a property of the representation. If Content-Encoding is not present, then there is no additional encoding beyond
    43544444         that defined by the Content-Type.
    43554445      </p>
    4356       <h2 id="rfc.section.D.3"><a href="#rfc.section.D.3">D.3</a>&nbsp;<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 further
     4446      <h2 id="rfc.section.F.3"><a href="#rfc.section.F.3">F.3</a>&nbsp;<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
    43584448         processing. Often, the server has different ways of representing the same information; for example, in different formats,
    43594449         languages, or using different character encodings.
    43604450      </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 influence
     4451      <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
    43624452         which representation, among those available from the server, would be best for the server to deliver. For this reason, HTTP
    43634453         provides mechanisms for "content negotiation" — a process of allowing selection of a representation of a given resource, when
    43644454         more than one is available.
    43654455      </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 representation
     4456      <p id="rfc.section.F.3.p.3">This specification defines two patterns of content negotiation; "server-driven", where the server selects the representation
    43674457         based upon the client's stated preferences, and "agent-driven" negotiation, where the server provides a list of representations
    43684458         for the client to choose from, based upon their metadata. In addition, there are other patterns: some applications use an
     
    43704460         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.
    43714461      </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 number
     4462      <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
    43734463         of preferences or capabilities to be expressed by a client are large (such as when many different formats are supported by
    43744464         a user-agent), server-driven negotiation becomes unwieldy, and might not be appropriate. Conversely, when the number of representations
    43754465         to choose from is very large, agent-driven negotiation might not be appropriate.
    43764466      </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 might
     4467      <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
    43784468         be considered to be the "same information".
    43794469      </p>
    4380       <h3 id="rfc.section.D.3.1"><a href="#rfc.section.D.3.1">D.3.1</a>&nbsp;<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-driven
     4470      <h3 id="rfc.section.F.3.1"><a href="#rfc.section.F.3.1">F.3.1</a>&nbsp;<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
    43824472         negotiation. Selection is based on the available representations of the response (the dimensions over which it can vary; e.g.,
    43834473         language, content-coding, etc.) and the contents of particular header fields in the request message or on other information
    43844474         pertaining to the request (such as the network address of the client).
    43854475      </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 difficult
     4476      <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
    43874477         to describe to the user agent, or when the server desires to send its "best guess" to the client along with the first response
    43884478         (hoping to avoid the round-trip delay of a subsequent request if the "best guess" is good enough for the user). In order to
    43894479         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.
    43904480      </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>
    43924482      <ol>
    43934483         <li>It is impossible for the server to accurately determine what might be "best" for any given user, since that would require
     
    44014491         <li>It might limit a public cache's ability to use the same response for multiple user's requests.</li>
    44024492      </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 honor
     4493      <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
    44044494         them. For example, the origin server might not implement server-driven negotiation, or it might decide that sending a response
    44054495         that doesn't conform to them is better than sending a 406 (Not Acceptable) response.
    44064496      </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 capabilities
    4410          and user preferences: Accept (<a href="#header.accept" id="rfc.xref.header.accept.4" title="Accept">Section&nbsp;7.1</a>), Accept-Charset (<a href="#header.accept-charset" id="rfc.xref.header.accept-charset.3" title="Accept-Charset">Section&nbsp;7.2</a>), Accept-Encoding (<a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.5" title="Accept-Encoding">Section&nbsp;7.3</a>), Accept-Language (<a href="#header.accept-language" id="rfc.xref.header.accept-language.3" title="Accept-Language">Section&nbsp;7.4</a>), and User-Agent (<a href="#header.user-agent" id="rfc.xref.header.user-agent.4" title="User-Agent">Section&nbsp;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
     4497      <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&nbsp;7.1</a>), Accept-Charset (<a href="#header.accept-charset" id="rfc.xref.header.accept-charset.4" title="Accept-Charset">Section&nbsp;7.2</a>), Accept-Encoding (<a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.5" title="Accept-Encoding">Section&nbsp;7.3</a>), Accept-Language (<a href="#header.accept-language" id="rfc.xref.header.accept-language.3" title="Accept-Language">Section&nbsp;7.4</a>), and User-Agent (<a href="#header.user-agent" id="rfc.xref.header.user-agent.4" title="User-Agent">Section&nbsp;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
    44114501         within extension header fields not defined by this specification.
    44124502      </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">
    44144504         <p> <b>Note:</b> In practice, User-Agent based negotiation is fragile, because new clients might not be recognized.
    44154505         </p>
    44164506      </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>&nbsp;<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 receiving
     4507      <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>&nbsp;<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
    44214511         an initial response from the origin server. Selection is based on a list of the available representations of the response
    44224512         included within the header fields or body of the initial response, with each representation identified by its own URI. Selection
     
    44244514         user selecting from a generated (possibly hypertext) menu.
    44254515      </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,
    44274517         or encoding), when the origin server is unable to determine a user agent's capabilities from examining the request, and generally
    44284518         when public caches are used to distribute server load and reduce network usage.
    44294519      </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.
    44314521         This second request is only efficient when caching is used. In addition, this specification does not define any mechanism
    44324522         for supporting automatic selection, though it also does not prevent any such mechanism from being developed as an extension
    44334523         and used within HTTP/1.1.
    44344524      </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 negotiation
     4525      <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
    44364526         when the server is unwilling or unable to provide a varying response using server-driven negotiation.
    44374527      </p>
    4438       <h2 id="rfc.section.D.4"><a href="#rfc.section.D.4">D.4</a>&nbsp;<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>&nbsp;<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>&nbsp;<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&nbsp;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&nbsp;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>&nbsp;<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&nbsp;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>&nbsp;<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=&lt;content-coding&gt;"
    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>&nbsp;<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>&nbsp;<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>&nbsp;<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&nbsp;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>&nbsp;<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>&nbsp;<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&nbsp;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&nbsp;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&nbsp;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&nbsp;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&nbsp;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&nbsp;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&nbsp;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&nbsp;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&nbsp;D.5</a>)
    4527       </p>
    4528       <h2 id="rfc.section.D.7"><a href="#rfc.section.D.7">D.7</a>&nbsp;<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>&nbsp;Since RFC 2616
     4528      <h2 id="rfc.section.F.4"><a href="#rfc.section.F.4">F.4</a>&nbsp;<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>&nbsp;Since RFC 2616
    45304530      </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>&nbsp;Since draft-ietf-httpbis-p3-payload-00
     4531      <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>&nbsp;Since draft-ietf-httpbis-p3-payload-00
    45344534      </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>
    45364536      <ul>
    45374537         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/8">http://tools.ietf.org/wg/httpbis/trac/ticket/8</a>&gt;: "Media Type Registrations" (&lt;<a href="http://purl.org/NET/http-errata#media-reg">http://purl.org/NET/http-errata#media-reg</a>&gt;)
     
    45584558         </li>
    45594559      </ul>
    4560       <h3 id="rfc.section.D.7.3"><a href="#rfc.section.D.7.3">D.7.3</a>&nbsp;Since draft-ietf-httpbis-p3-payload-01
     4560      <h3 id="rfc.section.F.4.3"><a href="#rfc.section.F.4.3">F.4.3</a>&nbsp;Since draft-ietf-httpbis-p3-payload-01
    45614561      </h3>
    4562       <p id="rfc.section.D.7.3.p.1">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
     4562      <p id="rfc.section.F.4.3.p.1">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
    45634563      </p>
    45644564      <ul>
    45654565         <li>Add explicit references to BNF syntax and rules imported from other parts of the specification.</li>
    45664566      </ul>
    4567       <h3 id="rfc.section.D.7.4"><a href="#rfc.section.D.7.4">D.7.4</a>&nbsp;<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>&nbsp;<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>
    45694569      <ul>
    45704570         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/67">http://tools.ietf.org/wg/httpbis/trac/ticket/67</a>&gt;: "Quoting Charsets"
     
    45754575         </li>
    45764576      </ul>
    4577       <p id="rfc.section.D.7.4.p.2">Ongoing work on IANA Message Header Field Registration (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/40">http://tools.ietf.org/wg/httpbis/trac/ticket/40</a>&gt;):
     4577      <p id="rfc.section.F.4.4.p.2">Ongoing work on IANA Message Header Field Registration (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/40">http://tools.ietf.org/wg/httpbis/trac/ticket/40</a>&gt;):
    45784578      </p>
    45794579      <ul>
    45804580         <li>Reference RFC 3984, and update header field registrations for headers defined in this document.</li>
    45814581      </ul>
    4582       <h3 id="rfc.section.D.7.5"><a href="#rfc.section.D.7.5">D.7.5</a>&nbsp;<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>&nbsp;<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>
    45844584      <ul>
    45854585         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/67">http://tools.ietf.org/wg/httpbis/trac/ticket/67</a>&gt;: "Quoting Charsets"
     
    45904590         </li>
    45914591      </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>
    45934593      <ul>
    45944594         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/68">http://tools.ietf.org/wg/httpbis/trac/ticket/68</a>&gt;: "Encoding References Normative" — rephrase the annotation and reference BCP97.
    45954595         </li>
    45964596      </ul>
    4597       <h3 id="rfc.section.D.7.6"><a href="#rfc.section.D.7.6">D.7.6</a>&nbsp;<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>&nbsp;<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>
    45994599      <ul>
    46004600         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/132">http://tools.ietf.org/wg/httpbis/trac/ticket/132</a>&gt;: "RFC 2822 is updated by RFC 5322"
    46014601         </li>
    46024602      </ul>
    4603       <p id="rfc.section.D.7.6.p.2">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
     4603      <p id="rfc.section.F.4.6.p.2">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
    46044604      </p>
    46054605      <ul>
     
    46084608         <li>Rewrite ABNFs to spell out whitespace rules, factor out header field value format definitions.</li>
    46094609      </ul>
    4610       <h3 id="rfc.section.D.7.7"><a href="#rfc.section.D.7.7">D.7.7</a>&nbsp;<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>&nbsp;<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>
    46124612      <ul>
    46134613         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/118">http://tools.ietf.org/wg/httpbis/trac/ticket/118</a>&gt;: "Join "Differences Between HTTP Entities and RFC 2045 Entities"?"
    46144614         </li>
    46154615      </ul>
    4616       <p id="rfc.section.D.7.7.p.2">Final work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
     4616      <p id="rfc.section.F.4.7.p.2">Final work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
    46174617      </p>
    46184618      <ul>
    46194619         <li>Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.</li>
    46204620      </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>
    46224622      <ul>
    46234623         <li>Move definition of quality values into Part 1.</li>
    46244624      </ul>
    4625       <h3 id="rfc.section.D.7.8"><a href="#rfc.section.D.7.8">D.7.8</a>&nbsp;<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>&nbsp;<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>
    46274627      <ul>
    46284628         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/80">http://tools.ietf.org/wg/httpbis/trac/ticket/80</a>&gt;: "Content-Location isn't special"
     
    46314631         </li>
    46324632      </ul>
    4633       <h3 id="rfc.section.D.7.9"><a href="#rfc.section.D.7.9">D.7.9</a>&nbsp;<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>&nbsp;<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>
    46354635      <ul>
    46364636         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/13">http://tools.ietf.org/wg/httpbis/trac/ticket/13</a>&gt;: "Updated reference for language tags"
     
    46474647         </li>
    46484648      </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>
    46504650      <ul>
    46514651         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/148">http://tools.ietf.org/wg/httpbis/trac/ticket/148</a>&gt;: "update IANA requirements wrt Transfer-Coding values" (add the IANA Considerations subsection)
     
    46544654         </li>
    46554655      </ul>
    4656       <h3 id="rfc.section.D.7.10"><a href="#rfc.section.D.7.10">D.7.10</a>&nbsp;<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>&nbsp;<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>
    46584658      <ul>
    46594659         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/81">http://tools.ietf.org/wg/httpbis/trac/ticket/81</a>&gt;: "Content Negotiation for media types"
     
    46624662         </li>
    46634663      </ul>
    4664       <h3 id="rfc.section.D.7.11"><a href="#rfc.section.D.7.11">D.7.11</a>&nbsp;<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>&nbsp;<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>
    46664666      <ul>
    46674667         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/122">http://tools.ietf.org/wg/httpbis/trac/ticket/122</a>&gt;: "MIME-Version not listed in P1, general header fields"
     
    46744674         </li>
    46754675      </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>
    46774677      <ul>
    46784678         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/196">http://tools.ietf.org/wg/httpbis/trac/ticket/196</a>&gt;: "Term for the requested resource's URI"
    46794679         </li>
    46804680      </ul>
    4681       <h3 id="rfc.section.D.7.12"><a href="#rfc.section.D.7.12">D.7.12</a>&nbsp;<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>&nbsp;<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>
    46834683      <ul>
    46844684         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/69">http://tools.ietf.org/wg/httpbis/trac/ticket/69</a>&gt;: "Clarify 'Requested Variant'"
     
    46994699         </li>
    47004700      </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>
    47024702      <ul>
    47034703         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/178">http://tools.ietf.org/wg/httpbis/trac/ticket/178</a>&gt;: "Content-MD5 and partial responses"
    47044704         </li>
    47054705      </ul>
    4706       <h3 id="rfc.section.D.7.13"><a href="#rfc.section.D.7.13">D.7.13</a>&nbsp;<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>&nbsp;<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>
    47084708      <ul>
    47094709         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/123">http://tools.ietf.org/wg/httpbis/trac/ticket/123</a>&gt;: "Factor out Content-Disposition"
    47104710         </li>
    47114711      </ul>
    4712       <h3 id="rfc.section.D.7.14"><a href="#rfc.section.D.7.14">D.7.14</a>&nbsp;<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>&nbsp;<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>
    47144714      <ul>
    47154715         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/224">http://tools.ietf.org/wg/httpbis/trac/ticket/224</a>&gt;: "Header Classification"
     
    47204720         </li>
    47214721      </ul>
    4722       <h3 id="rfc.section.D.7.15"><a href="#rfc.section.D.7.15">D.7.15</a>&nbsp;<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>&nbsp;<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>
    47244724      <ul>
    47254725         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/20">http://tools.ietf.org/wg/httpbis/trac/ticket/20</a>&gt;: "Default charsets for text media types"
     
    47324732         </li>
    47334733      </ul>
    4734       <h3 id="rfc.section.D.7.16"><a href="#rfc.section.D.7.16">D.7.16</a>&nbsp;<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>&nbsp;<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>&nbsp;<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>&nbsp;<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>
    47384738      <ul>
    47394739         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/285">http://tools.ietf.org/wg/httpbis/trac/ticket/285</a>&gt;: "Strength of requirements on Accept re: 406"
    47404740         </li>
    47414741      </ul>
    4742       <h3 id="rfc.section.D.7.18"><a href="#rfc.section.D.7.18">D.7.18</a>&nbsp;<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>&nbsp;<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>
    47444744      <ul>
    47454745         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/186">http://tools.ietf.org/wg/httpbis/trac/ticket/186</a>&gt;: "Document HTTP's error-handling philosophy"
    47464746         </li>
    47474747      </ul>
    4748       <h3 id="rfc.section.D.7.19"><a href="#rfc.section.D.7.19">D.7.19</a>&nbsp;<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>&nbsp;<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>
    47504750      <ul>
    47514751         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/323">http://tools.ietf.org/wg/httpbis/trac/ticket/323</a>&gt;: "intended maturity level vs normative references"
    47524752         </li>
    47534753      </ul>
    4754       <h3 id="rfc.section.D.7.20"><a href="#rfc.section.D.7.20">D.7.20</a>&nbsp;<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>&nbsp;<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>
    47564756      <ul>
    47574757         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/330">http://tools.ietf.org/wg/httpbis/trac/ticket/330</a>&gt;: "is ETag a representation header field?"
     
    47624762         </li>
    47634763      </ul>
    4764       <h3 id="rfc.section.D.7.21"><a href="#rfc.section.D.7.21">D.7.21</a>&nbsp;<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>&nbsp;<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>
    47664766      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
    47674767      <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>
     
    47794779                  <li>201 Created (status code)&nbsp;&nbsp;<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>
    47804780                  <li>202 Accepted (status code)&nbsp;&nbsp;<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)&nbsp;&nbsp;<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)&nbsp;&nbsp;<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>
    47824782                  <li>204 No Content (status code)&nbsp;&nbsp;<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>
    47834783                  <li>205 Reset Content (status code)&nbsp;&nbsp;<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>
     
    47864786            <li><a id="rfc.index.3" href="#rfc.index.3"><b>3</b></a><ul>
    47874787                  <li>300 Multiple Choices (status code)&nbsp;&nbsp;<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)&nbsp;&nbsp;<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)&nbsp;&nbsp;<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)&nbsp;&nbsp;<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)&nbsp;&nbsp;<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>
    47904790                  <li>303 See Other (status code)&nbsp;&nbsp;<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)&nbsp;&nbsp;<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)&nbsp;&nbsp;<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>
    47924792                  <li>306 (Unused) (status code)&nbsp;&nbsp;<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)&nbsp;&nbsp;<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)&nbsp;&nbsp;<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>
    47944794               </ul>
    47954795            </li>
     
    48094809                  <li>415 Unsupported Media Type (status code)&nbsp;&nbsp;<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>
    48104810                  <li>417 Expectation Failed (status code)&nbsp;&nbsp;<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)&nbsp;&nbsp;<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)&nbsp;&nbsp;<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>
    48124812               </ul>
    48134813            </li>
     
    48224822            </li>
    48234823            <li><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul>
    4824                   <li>Accept header field&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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>
    48294829               </ul>
    48304830            </li>
     
    48384838                  </li>
    48394839                  <li>compress (Coding Format)&nbsp;&nbsp;<a href="#rfc.iref.c.3">6.4</a></li>
    4840                   <li>CONNECT method&nbsp;&nbsp;<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&nbsp;&nbsp;<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>
    48414841                  <li>content negotiation&nbsp;&nbsp;<a href="#rfc.iref.c.1">1.1</a></li>
    4842                   <li>Content-Encoding header field&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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>
    48474847               </ul>
    48484848            </li>
     
    48554855            </li>
    48564856            <li><a id="rfc.index.E" href="#rfc.index.E"><b>E</b></a><ul>
    4857                   <li>Expect header field&nbsp;&nbsp;<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&nbsp;&nbsp;<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>
    48584858                  <li>Expect Values&nbsp;&nbsp;
    48594859                     <ul>
     
    49094909                        <li><tt>media-type</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.24"><b>6.5</b></a></li>
    49104910                        <li><tt>method</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.1"><b>2</b></a></li>
    4911                         <li><tt>MIME-Version</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.59"><b>D.4.1</b></a></li>
     4911                        <li><tt>MIME-Version</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.59"><b>A.1</b></a></li>
    49124912                        <li><tt>minute</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.8"><b>6.1</b></a></li>
    49134913                        <li><tt>month</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.13"><b>6.1</b></a></li>
     
    49374937                  <li>Header Fields&nbsp;&nbsp;
    49384938                     <ul>
    4939                         <li>Accept&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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>
    49494949                        <li>Date&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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>
    49514951                        <li>From&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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>
    49564956                        <li>Retry-After&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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>
    49594959                     </ul>
    49604960                  </li>
     
    49664966            </li>
    49674967            <li><a id="rfc.index.L" href="#rfc.index.L"><b>L</b></a><ul>
    4968                   <li>Location header field&nbsp;&nbsp;<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&nbsp;&nbsp;<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>
    49694969               </ul>
    49704970            </li>
    49714971            <li><a id="rfc.index.M" href="#rfc.index.M"><b>M</b></a><ul>
    4972                   <li>Max-Forwards header field&nbsp;&nbsp;<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&nbsp;&nbsp;<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>
    49734973                  <li>Methods&nbsp;&nbsp;
    49744974                     <ul>
    4975                         <li>CONNECT&nbsp;&nbsp;<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&nbsp;&nbsp;<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>
    49764976                        <li>DELETE&nbsp;&nbsp;<a href="#rfc.iref.m.6"><b>2.3.6</b></a>, <a href="#rfc.xref.DELETE.1">8.1</a></li>
    49774977                        <li>GET&nbsp;&nbsp;<a href="#rfc.iref.m.2"><b>2.3.2</b></a>, <a href="#rfc.xref.GET.1">8.1</a></li>
    49784978                        <li>HEAD&nbsp;&nbsp;<a href="#rfc.iref.m.3"><b>2.3.3</b></a>, <a href="#rfc.xref.HEAD.1">8.1</a></li>
    49794979                        <li>OPTIONS&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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>
    49824982                        <li>TRACE&nbsp;&nbsp;<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>
    49834983                     </ul>
    49844984                  </li>
    4985                   <li>MIME-Version header field&nbsp;&nbsp;<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&nbsp;&nbsp;<a href="#rfc.xref.mime-version.1">8.3</a>, <a href="#rfc.iref.m.10"><b>A.1</b></a></li>
    49864986               </ul>
    49874987            </li>
     
    49914991            </li>
    49924992            <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul>
    4993                   <li><em>Part1</em>&nbsp;&nbsp;<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>&nbsp;&nbsp;<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>
    49944994                        <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.3">1.3</a></li>
    49954995                        <li><em>Section 2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.2">1.2</a></li>
     
    50015001                        <li><em>Section 3.2.4</em>&nbsp;&nbsp;<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>
    50025002                        <li><em>Section 3.2.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.23">3.1</a></li>
    5003                         <li><em>Section 3.3</em>&nbsp;&nbsp;<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.57">D.1.2</a></li>
    5004                         <li><em>Section 3.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.59">D.4.6</a></li>
    5005                         <li><em>Section 3.3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.56">D.1.1</a></li>
     5003                        <li><em>Section 3.3</em>&nbsp;&nbsp;<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>&nbsp;&nbsp;<a href="#rfc.xref.Part1.55">A.6</a></li>
     5005                        <li><em>Section 3.3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.57">F.1.1</a></li>
    50065006                        <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.42">6.4.1</a></li>
    50075007                        <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.27">3.1</a></li>
     
    50115011                        <li><em>Section 4.2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.41">6.4</a>, <a href="#rfc.xref.Part1.53">8.4</a></li>
    50125012                        <li><em>Section 4.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.29">3.2</a></li>
    5013                         <li><em>Section 4.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.44">7.1</a>, <a href="#rfc.xref.Part1.45">7.3</a>, <a href="#rfc.xref.Part1.58">D.3.1</a></li>
     5013                        <li><em>Section 4.3.1</em>&nbsp;&nbsp;<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>
    50145014                        <li><em>Section 5.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.18">2.3.1</a>, <a href="#rfc.xref.Part1.21">2.3.8</a></li>
    50155015                        <li><em>Section 5.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.28">3.2</a></li>
    50165016                        <li><em>Section 5.5</em>&nbsp;&nbsp;<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>
    50175017                        <li><em>Section 6.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.26">3.1</a></li>
    5018                         <li><em>Section 6.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.19">2.3.7</a>, <a href="#rfc.xref.Part1.49">7.17</a>, <a href="#rfc.xref.Part1.55">A</a></li>
     5018                        <li><em>Section 6.2</em>&nbsp;&nbsp;<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>
    50195019                        <li><em>Section 6.4.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.31">4.3.1</a>, <a href="#rfc.xref.Part1.47">7.11</a></li>
    50205020                        <li><em>Section 6.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.32">4.3.2</a>, <a href="#rfc.xref.Part1.35">4.6.15</a></li>
     
    50235023                     </ul>
    50245024                  </li>
    5025                   <li><em>Part4</em>&nbsp;&nbsp;<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>&nbsp;&nbsp;<a href="#rfc.xref.Part4.13">D.2.1</a></li>
    5027                         <li><em>Section 2.3</em>&nbsp;&nbsp;<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>&nbsp;&nbsp;<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>&nbsp;&nbsp;<a href="#rfc.xref.Part4.13">F.2.1</a></li>
     5027                        <li><em>Section 2.3</em>&nbsp;&nbsp;<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>
    50285028                        <li><em>Section 3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">3.2</a></li>
    50295029                        <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.3">3.2</a></li>
     
    50355035                     </ul>
    50365036                  </li>
    5037                   <li><em>Part5</em>&nbsp;&nbsp;<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>&nbsp;&nbsp;<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>
    50385038                        <li><em>Section 3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.5">4.1</a></li>
    50395039                        <li><em>Section 3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.6">4.1</a></li>
    50405040                        <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.7">4.1</a></li>
    50415041                        <li><em>Section 5.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.4">3.3</a></li>
    5042                         <li><em>Section 5.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.8">D.1.1</a></li>
     5042                        <li><em>Section 5.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.8">F.1.1</a></li>
    50435043                        <li><em>Section 5.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.2">3.2</a></li>
    50445044                        <li><em>Section 5.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.1">2.3.2</a>, <a href="#rfc.xref.Part5.3">3.2</a></li>
    50455045                     </ul>
    50465046                  </li>
    5047                   <li><em>Part6</em>&nbsp;&nbsp;<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>&nbsp;&nbsp;<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>
    50485048                        <li><em>Section 2.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.4">2.3.4</a></li>
    50495049                        <li><em>Section 2.3.1.1</em>&nbsp;&nbsp;<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>
     
    50525052                        <li><em>Section 3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.8">3.3</a></li>
    50535053                        <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.12">4.4.4</a></li>
    5054                         <li><em>Section 3.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.18">D.2.1</a></li>
    5055                         <li><em>Section 3.5</em>&nbsp;&nbsp;<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>&nbsp;&nbsp;<a href="#rfc.xref.Part6.18">F.2.1</a></li>
     5055                        <li><em>Section 3.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.9">3.3</a>, <a href="#rfc.xref.Part6.19">F.3.1</a></li>
    50565056                        <li><em>Section 3.6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.13">4.4.4</a></li>
    50575057                     </ul>
     
    50675067                     </ul>
    50685068                  </li>
    5069                   <li>payload&nbsp;&nbsp;<a href="#rfc.iref.p.3">D.1</a></li>
    5070                   <li>POST method&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<a href="#rfc.iref.p.3">F.1</a></li>
     5070                  <li>POST method&nbsp;&nbsp;<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&nbsp;&nbsp;<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>
    50725072               </ul>
    50735073            </li>
    50745074            <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul>
    5075                   <li>Referer header field&nbsp;&nbsp;<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&nbsp;&nbsp;<a href="#rfc.iref.r.3">D.2</a></li>
     5075                  <li>Referer header field&nbsp;&nbsp;<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&nbsp;&nbsp;<a href="#rfc.iref.r.3">F.2</a></li>
    50775077                  <li>Retry-After header field&nbsp;&nbsp;<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>
    50785078                  <li><em>RFC1123</em>&nbsp;&nbsp;<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>
     
    50805080                     </ul>
    50815081                  </li>
    5082                   <li><em>RFC1945</em>&nbsp;&nbsp;<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>&nbsp;&nbsp;<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>
    50835083                        <li><em>Section 9.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1945.1">4.5</a></li>
    50845084                     </ul>
     
    50875087                  <li><em>RFC1951</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1951.1">8.4</a>, <a href="#RFC1951"><b>11.1</b></a></li>
    50885088                  <li><em>RFC1952</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1952.1">8.4</a>, <a href="#RFC1952"><b>11.1</b></a></li>
    5089                   <li><em>RFC2045</em>&nbsp;&nbsp;<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>&nbsp;&nbsp;<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>&nbsp;&nbsp;<a href="#rfc.xref.RFC2046.3">D.2.2</a></li>
     5089                  <li><em>RFC2045</em>&nbsp;&nbsp;<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>&nbsp;&nbsp;<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>&nbsp;&nbsp;<a href="#rfc.xref.RFC2046.4">F.2.2</a></li>
    50925092                        <li><em>Section 5.1.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2046.2">6.5.2</a></li>
    50935093                     </ul>
    50945094                  </li>
    5095                   <li><em>RFC2049</em>&nbsp;&nbsp;<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>&nbsp;&nbsp;<a href="#rfc.xref.RFC2049.1">D.4.2</a></li>
     5095                  <li><em>RFC2049</em>&nbsp;&nbsp;<a href="#RFC2049"><b>11.2</b></a>, <a href="#rfc.xref.RFC2049.1">A.2</a><ul>
     5096                        <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2049.1">A.2</a></li>
    50975097                     </ul>
    50985098                  </li>
    5099                   <li><em>RFC2068</em>&nbsp;&nbsp;<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>&nbsp;&nbsp;<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>
    51005100                        <li><em>Section 10.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2068.2">4.5</a></li>
    51015101                        <li><em>Section 10.3.4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2068.1">4.5</a></li>
    51025102                     </ul>
    51035103                  </li>
    5104                   <li><em>RFC2076</em>&nbsp;&nbsp;<a href="#RFC2076"><b>11.2</b></a>, <a href="#rfc.xref.RFC2076.1">D.5</a></li>
     5104                  <li><em>RFC2076</em>&nbsp;&nbsp;<a href="#RFC2076"><b>11.2</b></a>, <a href="#rfc.xref.RFC2076.1">B</a></li>
    51055105                  <li><em>RFC2119</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2119.1">1.2</a>, <a href="#RFC2119"><b>11.1</b></a></li>
    51065106                  <li><em>RFC2277</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2277.1">6.3</a>, <a href="#RFC2277"><b>11.2</b></a></li>
    5107                   <li><em>RFC2295</em>&nbsp;&nbsp;<a href="#RFC2295"><b>11.2</b></a>, <a href="#rfc.xref.RFC2295.1">D.3</a></li>
     5107                  <li><em>RFC2295</em>&nbsp;&nbsp;<a href="#RFC2295"><b>11.2</b></a>, <a href="#rfc.xref.RFC2295.1">F.3</a></li>
    51085108                  <li><em>RFC2388</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2388.1">6.5.2</a>, <a href="#RFC2388"><b>11.2</b></a></li>
    5109                   <li><em>RFC2557</em>&nbsp;&nbsp;<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>&nbsp;&nbsp;<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>
    51105110                        <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2557.1">7.8</a></li>
    51115111                     </ul>
    51125112                  </li>
    5113                   <li><em>RFC2616</em>&nbsp;&nbsp;<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>&nbsp;&nbsp;<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>
    51145114                        <li><em>Section 10.3.8</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.2">4.5</a></li>
    51155115                        <li><em>Section 14.4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.3">7.4</a></li>
    51165116                     </ul>
    51175117                  </li>
    5118                   <li><em>RFC2817</em>&nbsp;&nbsp;<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>&nbsp;&nbsp;<a href="#rfc.xref.RFC2817.1">8.2</a>, <a href="#rfc.xref.RFC2817.3">A</a></li>
     5118                  <li><em>RFC2817</em>&nbsp;&nbsp;<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>&nbsp;&nbsp;<a href="#rfc.xref.RFC2817.1">8.2</a>, <a href="#rfc.xref.RFC2817.3">C</a></li>
    51205120                     </ul>
    51215121                  </li>
     
    51465146                     </ul>
    51475147                  </li>
    5148                   <li><em>RFC5322</em>&nbsp;&nbsp;<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>&nbsp;&nbsp;<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>
    51495149                        <li><em>Section 3.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5322.1">6.1</a></li>
    51505150                        <li><em>Section 3.4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5322.3">7.12</a>, <a href="#rfc.xref.RFC5322.4">7.12</a></li>
     
    51585158                  <li><em>RFC5789</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5789.1">2.3.5</a>, <a href="#RFC5789"><b>11.2</b></a></li>
    51595159                  <li><em>RFC5987</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5987.1">3.1</a>, <a href="#RFC5987"><b>11.2</b></a></li>
    5160                   <li><em>RFC6151</em>&nbsp;&nbsp;<a href="#RFC6151"><b>11.2</b></a>, <a href="#rfc.xref.RFC6151.1">D.6</a></li>
    5161                   <li><em>RFC6266</em>&nbsp;&nbsp;<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>&nbsp;&nbsp;<a href="#RFC6151"><b>11.2</b></a>, <a href="#rfc.xref.RFC6151.1">C</a></li>
     5161                  <li><em>RFC6266</em>&nbsp;&nbsp;<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>
    51625162               </ul>
    51635163            </li>
     
    51655165                  <li>Safe Methods&nbsp;&nbsp;<a href="#rfc.iref.s.2"><b>2.1.1</b></a></li>
    51665166                  <li>selected representation&nbsp;&nbsp;<a href="#rfc.iref.s.1"><b>1.1</b></a></li>
    5167                   <li>Server header field&nbsp;&nbsp;<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&nbsp;&nbsp;<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>
    51685168                  <li>Status Codes&nbsp;&nbsp;
    51695169                     <ul>
     
    51735173                        <li>201 Created&nbsp;&nbsp;<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>
    51745174                        <li>202 Accepted&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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>
    51765176                        <li>204 No Content&nbsp;&nbsp;<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>
    51775177                        <li>205 Reset Content&nbsp;&nbsp;<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>
    51785178                        <li>300 Multiple Choices&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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>
    51815181                        <li>303 See Other&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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>
    51835183                        <li>306 (Unused)&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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>
    51855185                        <li>400 Bad Request&nbsp;&nbsp;<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>
    51865186                        <li>402 Payment Required&nbsp;&nbsp;<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>
     
    51975197                        <li>415 Unsupported Media Type&nbsp;&nbsp;<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>
    51985198                        <li>417 Expectation Failed&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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>
    52005200                        <li>500 Internal Server Error&nbsp;&nbsp;<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>
    52015201                        <li>501 Not Implemented&nbsp;&nbsp;<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>
     
    52135213            </li>
    52145214            <li><a id="rfc.index.U" href="#rfc.index.U"><b>U</b></a><ul>
    5215                   <li>User-Agent header field&nbsp;&nbsp;<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&nbsp;&nbsp;<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>
    52165216               </ul>
    52175217            </li>
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r1646 r1647  
    48904890</references>
    48914891
     4892<section title="Differences between HTTP and MIME" anchor="differences.between.http.and.mime">
     4893<t>
     4894   HTTP/1.1 uses many of the constructs defined for Internet Mail (<xref target="RFC5322"/>) and the Multipurpose Internet Mail Extensions (MIME <xref target="RFC2045"/>) to
     4895   allow a message body to be transmitted in an open variety of
     4896   representations and with extensible mechanisms. However, RFC 2045
     4897   discusses mail, and HTTP has a few features that are different from
     4898   those described in MIME. These differences were carefully chosen
     4899   to optimize performance over binary connections, to allow greater
     4900   freedom in the use of new media types, to make date comparisons
     4901   easier, and to acknowledge the practice of some early HTTP servers
     4902   and clients.
     4903</t>
     4904<t>
     4905   This appendix describes specific areas where HTTP differs from MIME.
     4906   Proxies and gateways to strict MIME environments &SHOULD; be
     4907   aware of these differences and provide the appropriate conversions
     4908   where necessary. Proxies and gateways from MIME environments to HTTP
     4909   also need to be aware of the differences because some conversions
     4910   might be required.
     4911</t>
     4912
     4913<section title="MIME-Version" anchor="mime-version">
     4914  <iref primary="true" item="MIME-Version header field" x:for-anchor=""/>
     4915  <iref primary="true" item="Header Fields" subitem="MIME-Version" x:for-anchor=""/>
     4916  <x:anchor-alias value="MIME-Version"/>
     4917<t>
     4918   HTTP is not a MIME-compliant protocol. However, HTTP/1.1 messages &MAY;
     4919   include a single MIME-Version header field to indicate what
     4920   version of the MIME protocol was used to construct the message. Use
     4921   of the MIME-Version header field indicates that the message is in
     4922   full conformance with the MIME protocol (as defined in <xref target="RFC2045"/>).
     4923   Proxies/gateways are responsible for ensuring full conformance (where
     4924   possible) when exporting HTTP messages to strict MIME environments.
     4925</t>
     4926<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="MIME-Version"/>
     4927  <x:ref>MIME-Version</x:ref> = 1*<x:ref>DIGIT</x:ref> "." 1*<x:ref>DIGIT</x:ref>
     4928</artwork></figure>
     4929<t>
     4930   MIME version "1.0" is the default for use in HTTP/1.1. However,
     4931   HTTP/1.1 message parsing and semantics are defined by this document
     4932   and not the MIME specification.
     4933</t>
     4934</section>
     4935
     4936<section title="Conversion to Canonical Form" anchor="conversion.to.canonical.form">
     4937<t>
     4938   MIME requires that an Internet mail body-part be converted to
     4939   canonical form prior to being transferred, as described in <xref target="RFC2049" x:fmt="of" x:sec="4"/>.
     4940   <xref target="canonicalization.and.text.defaults"/> of this document describes the forms
     4941   allowed for subtypes of the "text" media type when transmitted over
     4942   HTTP. <xref target="RFC2046"/> requires that content with a type of "text" represent
     4943   line breaks as CRLF and forbids the use of CR or LF outside of line
     4944   break sequences. HTTP allows CRLF, bare CR, and bare LF to indicate a
     4945   line break within text content when a message is transmitted over
     4946   HTTP.
     4947</t>
     4948<t>
     4949   Where it is possible, a proxy or gateway from HTTP to a strict MIME
     4950   environment &SHOULD; translate all line breaks within the text media
     4951   types described in <xref target="canonicalization.and.text.defaults"/>
     4952   of this document to the RFC 2049
     4953   canonical form of CRLF. Note, however, that this might be complicated
     4954   by the presence of a Content-Encoding and by the fact that HTTP
     4955   allows the use of some character encodings which do not use octets 13 and
     4956   10 to represent CR and LF, respectively, as is the case for some multi-byte
     4957   character encodings.
     4958</t>
     4959<t>
     4960   Conversion will break any cryptographic
     4961   checksums applied to the original content unless the original content
     4962   is already in canonical form. Therefore, the canonical form is
     4963   recommended for any content that uses such checksums in HTTP.
     4964</t>
     4965</section>
     4966
     4967
     4968<section title="Conversion of Date Formats" anchor="conversion.of.date.formats">
     4969<t>
     4970   HTTP/1.1 uses a restricted set of date formats (&http-date;) to
     4971   simplify the process of date comparison. Proxies and gateways from
     4972   other protocols &SHOULD; ensure that any Date header field present in a
     4973   message conforms to one of the HTTP/1.1 formats and rewrite the date
     4974   if necessary.
     4975</t>
     4976</section>
     4977
     4978<section title="Introduction of Content-Encoding" anchor="introduction.of.content-encoding">
     4979<t>
     4980   MIME does not include any concept equivalent to HTTP/1.1's
     4981   Content-Encoding header field. Since this acts as a modifier on the
     4982   media type, proxies and gateways from HTTP to MIME-compliant
     4983   protocols &MUST; either change the value of the Content-Type header
     4984   field or decode the representation before forwarding the message. (Some
     4985   experimental applications of Content-Type for Internet mail have used
     4986   a media-type parameter of ";conversions=&lt;content-coding&gt;" to perform
     4987   a function equivalent to Content-Encoding. However, this parameter is
     4988   not part of the MIME standards).
     4989</t>
     4990</section>
     4991
     4992<section title="No Content-Transfer-Encoding" anchor="no.content-transfer-encoding">
     4993  <iref item="Content-Transfer-Encoding header field" x:for-anchor=""/>
     4994  <iref item="Header Fields" subitem="Content-Transfer-Encoding" x:for-anchor=""/>
     4995<t>
     4996   HTTP does not use the Content-Transfer-Encoding field of MIME.
     4997   Proxies and gateways from MIME-compliant protocols to HTTP &MUST;
     4998   remove any Content-Transfer-Encoding
     4999   prior to delivering the response message to an HTTP client.
     5000</t>
     5001<t>
     5002   Proxies and gateways from HTTP to MIME-compliant protocols are
     5003   responsible for ensuring that the message is in the correct format
     5004   and encoding for safe transport on that protocol, where "safe
     5005   transport" is defined by the limitations of the protocol being used.
     5006   Such a proxy or gateway &SHOULD; label the data with an appropriate
     5007   Content-Transfer-Encoding if doing so will improve the likelihood of
     5008   safe transport over the destination protocol.
     5009</t>
     5010</section>
     5011
     5012<section title="Introduction of Transfer-Encoding" anchor="introduction.of.transfer-encoding">
     5013<t>
     5014   HTTP/1.1 introduces the Transfer-Encoding header field (&header-transfer-encoding;).
     5015   Proxies/gateways &MUST; remove any transfer-coding prior to
     5016   forwarding a message via a MIME-compliant protocol.
     5017</t>
     5018</section>
     5019
     5020<section title="MHTML and Line Length Limitations" anchor="mhtml.line.length">
     5021<t>
     5022   HTTP implementations which share code with MHTML <xref target="RFC2557"/> implementations
     5023   need to be aware of MIME line length limitations. Since HTTP does not
     5024   have this limitation, HTTP does not fold long lines. MHTML messages
     5025   being transported by HTTP follow all conventions of MHTML, including
     5026   line length limitations and folding, canonicalization, etc., since
     5027   HTTP transports all message-bodies as payload (see <xref target="multipart.types"/>) and
     5028   does not interpret the content or any MIME header lines that might be
     5029   contained therein.
     5030</t>
     5031</section>
     5032</section>
     5033
     5034<section title="Additional Features" anchor="additional.features">
     5035<t>
     5036   <xref target="RFC1945"/> and <xref target="RFC2068"/> document protocol elements used by some
     5037   existing HTTP implementations, but not consistently and correctly
     5038   across most HTTP/1.1 applications. Implementors are advised to be
     5039   aware of these features, but cannot rely upon their presence in, or
     5040   interoperability with, other HTTP/1.1 applications. Some of these
     5041   describe proposed experimental features, and some describe features
     5042   that experimental deployment found lacking that are now addressed in
     5043   the base HTTP/1.1 specification.
     5044</t>
     5045<t>
     5046   A number of other header fields, such as Content-Disposition and Title,
     5047   from SMTP and MIME are also often implemented (see <xref target="RFC6266"/>
     5048   and <xref target="RFC2076"/>).
     5049</t>
     5050</section>
     5051
    48925052<section title="Changes from RFC 2616" anchor="changes.from.rfc.2616">
    48935053<t>
     
    49795139  correctly in the description of the Via header field in &header-via;.
    49805140  (<xref target="header.server"/>)
     5141</t>
     5142<t>
     5143  Clarify contexts that charset is used in.
     5144  (<xref target="character.sets"/>)
     5145</t>
     5146<t>
     5147  Registration of Content Codings now requires IETF Review
     5148  (<xref target="content.coding.registry"/>)
     5149</t>
     5150<t>
     5151  Remove the default character encoding for text media types; the default
     5152  now is whatever the media type definition says.
     5153  (<xref target="canonicalization.and.text.defaults"/>)
     5154</t>
     5155<t>
     5156  Change ABNF productions for header fields to only define the field value.
     5157  (<xref target="header.field.definitions"/>)
     5158</t>
     5159<t>
     5160  Remove definition of Content-MD5 header field because it was inconsistently
     5161  implemented with respect to partial responses, and also because of known
     5162  deficiencies in the hash algorithm itself (see <xref target="RFC6151"/> for details).
     5163  (<xref target="header.field.definitions"/>)
     5164</t>
     5165<t>
     5166  Remove ISO-8859-1 special-casing in Accept-Charset.
     5167  (<xref target="header.accept-charset"/>)
     5168</t>
     5169<t>
     5170  Remove base URI setting semantics for Content-Location due to poor
     5171  implementation support, which was caused by too many broken servers emitting
     5172  bogus Content-Location header fields, and also the potentially undesirable effect
     5173  of potentially breaking relative links in content-negotiated resources.
     5174  (<xref target="header.content-location"/>)
     5175</t>
     5176<t>
     5177  Remove reference to non-existant identity transfer-coding value tokens.
     5178  (<xref target="no.content-transfer-encoding"/>)
     5179</t>
     5180<t>
     5181  Remove discussion of Content-Disposition header field, it is now defined
     5182  by <xref target="RFC6266"/>.
     5183  (<xref target="additional.features"/>)
    49815184</t>
    49825185</section>
     
    61246327</section>
    61256328
    6126 <section title="Differences between HTTP and MIME" anchor="differences.between.http.and.mime">
    6127 <t>
    6128    HTTP/1.1 uses many of the constructs defined for Internet Mail (<xref target="RFC5322"/>) and the Multipurpose Internet Mail Extensions (MIME <xref target="RFC2045"/>) to
    6129    allow a message body to be transmitted in an open variety of
    6130    representations and with extensible mechanisms. However, RFC 2045
    6131    discusses mail, and HTTP has a few features that are different from
    6132    those described in MIME. These differences were carefully chosen
    6133    to optimize performance over binary connections, to allow greater
    6134    freedom in the use of new media types, to make date comparisons
    6135    easier, and to acknowledge the practice of some early HTTP servers
    6136    and clients.
    6137 </t>
    6138 <t>
    6139    This appendix describes specific areas where HTTP differs from MIME.
    6140    Proxies and gateways to strict MIME environments &SHOULD; be
    6141    aware of these differences and provide the appropriate conversions
    6142    where necessary. Proxies and gateways from MIME environments to HTTP
    6143    also need to be aware of the differences because some conversions
    6144    might be required.
    6145 </t>
    6146 
    6147 <section title="MIME-Version" anchor="mime-version">
    6148   <iref primary="true" item="MIME-Version header field" x:for-anchor=""/>
    6149   <iref primary="true" item="Header Fields" subitem="MIME-Version" x:for-anchor=""/>
    6150   <x:anchor-alias value="MIME-Version"/>
    6151 <t>
    6152    HTTP is not a MIME-compliant protocol. However, HTTP/1.1 messages &MAY;
    6153    include a single MIME-Version header field to indicate what
    6154    version of the MIME protocol was used to construct the message. Use
    6155    of the MIME-Version header field indicates that the message is in
    6156    full conformance with the MIME protocol (as defined in <xref target="RFC2045"/>).
    6157    Proxies/gateways are responsible for ensuring full conformance (where
    6158    possible) when exporting HTTP messages to strict MIME environments.
    6159 </t>
    6160 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="MIME-Version"/>
    6161   <x:ref>MIME-Version</x:ref> = 1*<x:ref>DIGIT</x:ref> "." 1*<x:ref>DIGIT</x:ref>
    6162 </artwork></figure>
    6163 <t>
    6164    MIME version "1.0" is the default for use in HTTP/1.1. However,
    6165    HTTP/1.1 message parsing and semantics are defined by this document
    6166    and not the MIME specification.
    6167 </t>
    6168 </section>
    6169 
    6170 <section title="Conversion to Canonical Form" anchor="conversion.to.canonical.form">
    6171 <t>
    6172    MIME requires that an Internet mail body-part be converted to
    6173    canonical form prior to being transferred, as described in <xref target="RFC2049" x:fmt="of" x:sec="4"/>.
    6174    <xref target="canonicalization.and.text.defaults"/> of this document describes the forms
    6175    allowed for subtypes of the "text" media type when transmitted over
    6176    HTTP. <xref target="RFC2046"/> requires that content with a type of "text" represent
    6177    line breaks as CRLF and forbids the use of CR or LF outside of line
    6178    break sequences. HTTP allows CRLF, bare CR, and bare LF to indicate a
    6179    line break within text content when a message is transmitted over
    6180    HTTP.
    6181 </t>
    6182 <t>
    6183    Where it is possible, a proxy or gateway from HTTP to a strict MIME
    6184    environment &SHOULD; translate all line breaks within the text media
    6185    types described in <xref target="canonicalization.and.text.defaults"/>
    6186    of this document to the RFC 2049
    6187    canonical form of CRLF. Note, however, that this might be complicated
    6188    by the presence of a Content-Encoding and by the fact that HTTP
    6189    allows the use of some character encodings which do not use octets 13 and
    6190    10 to represent CR and LF, respectively, as is the case for some multi-byte
    6191    character encodings.
    6192 </t>
    6193 <t>
    6194    Conversion will break any cryptographic
    6195    checksums applied to the original content unless the original content
    6196    is already in canonical form. Therefore, the canonical form is
    6197    recommended for any content that uses such checksums in HTTP.
    6198 </t>
    6199 </section>
    6200 
    6201 
    6202 <section title="Conversion of Date Formats" anchor="conversion.of.date.formats">
    6203 <t>
    6204    HTTP/1.1 uses a restricted set of date formats (&http-date;) to
    6205    simplify the process of date comparison. Proxies and gateways from
    6206    other protocols &SHOULD; ensure that any Date header field present in a
    6207    message conforms to one of the HTTP/1.1 formats and rewrite the date
    6208    if necessary.
    6209 </t>
    6210 </section>
    6211 
    6212 <section title="Introduction of Content-Encoding" anchor="introduction.of.content-encoding">
    6213 <t>
    6214    MIME does not include any concept equivalent to HTTP/1.1's
    6215    Content-Encoding header field. Since this acts as a modifier on the
    6216    media type, proxies and gateways from HTTP to MIME-compliant
    6217    protocols &MUST; either change the value of the Content-Type header
    6218    field or decode the representation before forwarding the message. (Some
    6219    experimental applications of Content-Type for Internet mail have used
    6220    a media-type parameter of ";conversions=&lt;content-coding&gt;" to perform
    6221    a function equivalent to Content-Encoding. However, this parameter is
    6222    not part of the MIME standards).
    6223 </t>
    6224 </section>
    6225 
    6226 <section title="No Content-Transfer-Encoding" anchor="no.content-transfer-encoding">
    6227   <iref item="Content-Transfer-Encoding header field" x:for-anchor=""/>
    6228   <iref item="Header Fields" subitem="Content-Transfer-Encoding" x:for-anchor=""/>
    6229 <t>
    6230    HTTP does not use the Content-Transfer-Encoding field of MIME.
    6231    Proxies and gateways from MIME-compliant protocols to HTTP &MUST;
    6232    remove any Content-Transfer-Encoding
    6233    prior to delivering the response message to an HTTP client.
    6234 </t>
    6235 <t>
    6236    Proxies and gateways from HTTP to MIME-compliant protocols are
    6237    responsible for ensuring that the message is in the correct format
    6238    and encoding for safe transport on that protocol, where "safe
    6239    transport" is defined by the limitations of the protocol being used.
    6240    Such a proxy or gateway &SHOULD; label the data with an appropriate
    6241    Content-Transfer-Encoding if doing so will improve the likelihood of
    6242    safe transport over the destination protocol.
    6243 </t>
    6244 </section>
    6245 
    6246 <section title="Introduction of Transfer-Encoding" anchor="introduction.of.transfer-encoding">
    6247 <t>
    6248    HTTP/1.1 introduces the Transfer-Encoding header field (&header-transfer-encoding;).
    6249    Proxies/gateways &MUST; remove any transfer-coding prior to
    6250    forwarding a message via a MIME-compliant protocol.
    6251 </t>
    6252 </section>
    6253 
    6254 <section title="MHTML and Line Length Limitations" anchor="mhtml.line.length">
    6255 <t>
    6256    HTTP implementations which share code with MHTML <xref target="RFC2557"/> implementations
    6257    need to be aware of MIME line length limitations. Since HTTP does not
    6258    have this limitation, HTTP does not fold long lines. MHTML messages
    6259    being transported by HTTP follow all conventions of MHTML, including
    6260    line length limitations and folding, canonicalization, etc., since
    6261    HTTP transports all message-bodies as payload (see <xref target="multipart.types"/>) and
    6262    does not interpret the content or any MIME header lines that might be
    6263    contained therein.
    6264 </t>
    6265 </section>
    6266 </section>
    6267 
    6268 <section title="Additional Features" anchor="additional.features">
    6269 <t>
    6270    <xref target="RFC1945"/> and <xref target="RFC2068"/> document protocol elements used by some
    6271    existing HTTP implementations, but not consistently and correctly
    6272    across most HTTP/1.1 applications. Implementors are advised to be
    6273    aware of these features, but cannot rely upon their presence in, or
    6274    interoperability with, other HTTP/1.1 applications. Some of these
    6275    describe proposed experimental features, and some describe features
    6276    that experimental deployment found lacking that are now addressed in
    6277    the base HTTP/1.1 specification.
    6278 </t>
    6279 <t>
    6280    A number of other header fields, such as Content-Disposition and Title,
    6281    from SMTP and MIME are also often implemented (see <xref target="RFC6266"/>
    6282    and <xref target="RFC2076"/>).
    6283 </t>
    6284 </section>
    6285 
    6286 <section title="Changes from RFC 2616" anchor="changes.from.rfc.2616-3">
    6287 <t>
    6288   Clarify contexts that charset is used in.
    6289   (<xref target="character.sets"/>)
    6290 </t>
    6291 <t>
    6292   Registration of Content Codings now requires IETF Review
    6293   (<xref target="content.coding.registry"/>)
    6294 </t>
    6295 <t>
    6296   Remove the default character encoding for text media types; the default
    6297   now is whatever the media type definition says.
    6298   (<xref target="canonicalization.and.text.defaults"/>)
    6299 </t>
    6300 <t>
    6301   Change ABNF productions for header fields to only define the field value.
    6302   (<xref target="header.field.definitions"/>)
    6303 </t>
    6304 <t>
    6305   Remove definition of Content-MD5 header field because it was inconsistently
    6306   implemented with respect to partial responses, and also because of known
    6307   deficiencies in the hash algorithm itself (see <xref target="RFC6151"/> for details).
    6308   (<xref target="header.field.definitions"/>)
    6309 </t>
    6310 <t>
    6311   Remove ISO-8859-1 special-casing in Accept-Charset.
    6312   (<xref target="header.accept-charset"/>)
    6313 </t>
    6314 <t>
    6315   Remove base URI setting semantics for Content-Location due to poor
    6316   implementation support, which was caused by too many broken servers emitting
    6317   bogus Content-Location header fields, and also the potentially undesirable effect
    6318   of potentially breaking relative links in content-negotiated resources.
    6319   (<xref target="header.content-location"/>)
    6320 </t>
    6321 <t>
    6322   Remove reference to non-existant identity transfer-coding value tokens.
    6323   (<xref target="no.content-transfer-encoding"/>)
    6324 </t>
    6325 <t>
    6326   Remove discussion of Content-Disposition header field, it is now defined
    6327   by <xref target="RFC6266"/>.
    6328   (<xref target="additional.features"/>)
    6329 </t>
    6330 </section>
    63316329
    63326330<section title="Change Log (to be removed by RFC Editor before publication)" anchor="change.log3">
  • draft-ietf-httpbis/latest/p4-conditional.html

    r1645 r1647  
    896896      </div>
    897897      <h3 id="rfc.section.2.3.3"><a href="#rfc.section.2.3.3">2.3.3</a>&nbsp;<a id="example.entity.tag.vs.conneg" href="#example.entity.tag.vs.conneg">Example: Entity-tags varying on Content-Negotiated Resources</a></h3>
    898       <p id="rfc.section.2.3.3.p.1">Consider a resource that is subject to content negotiation (<a href="p2-semantics.html#content.negotiation" title="Content Negotiation">Appendix D.3</a> of <a href="#Part2" id="rfc.xref.Part2.3"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>), and where the representations returned upon a GET request vary based on the Accept-Encoding request header field (<a href="p2-semantics.html#header.accept-encoding" title="Accept-Encoding">Section 7.3</a> of <a href="#Part2" id="rfc.xref.Part2.4"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>):
     898      <p id="rfc.section.2.3.3.p.1">Consider a resource that is subject to content negotiation (<a href="p2-semantics.html#content.negotiation" title="Content Negotiation">Appendix F.3</a> of <a href="#Part2" id="rfc.xref.Part2.3"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>), and where the representations returned upon a GET request vary based on the Accept-Encoding request header field (<a href="p2-semantics.html#header.accept-encoding" title="Accept-Encoding">Section 7.3</a> of <a href="#Part2" id="rfc.xref.Part2.4"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>):
    899899      </p>
    900900      <div id="rfc.figure.u.6"></div>
     
    14271427                        <li><em>Section 7.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.4">2.3.3</a></li>
    14281428                        <li><em>Section 7.10</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.5">4.1</a></li>
    1429                         <li><em>Appendix D.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.3">2.3.3</a></li>
     1429                        <li><em>Appendix F.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.3">2.3.3</a></li>
    14301430                     </ul>
    14311431                  </li>
Note: See TracChangeset for help on using the changeset viewer.