Changeset 1631


Ignore:
Timestamp:
Mar 28, 2012, 9:29:49 AM (8 years ago)
Author:
julian.reschke@…
Message:

reorg experiment

Location:
draft-ietf-httpbis/experiment
Files:
3 edited

Legend:

Unmodified
Added
Removed

  • draft-ietf-httpbis/experiment/p2-semantics.html

    r1630 r1631  
    486486      <link rel="Chapter" title="3 Header Fields" href="#rfc.section.3">
    487487      <link rel="Chapter" title="4 Status Code and Reason Phrase" href="#rfc.section.4">
    488       <link rel="Chapter" title="5 Representation" href="#rfc.section.5">
    489       <link rel="Chapter" title="6 Common Protocol Parameters" href="#rfc.section.6">
    490       <link rel="Chapter" title="7 Payload" href="#rfc.section.7">
    491       <link rel="Chapter" title="8 Representation" href="#rfc.section.8">
    492       <link rel="Chapter" title="9 Content Negotiation" href="#rfc.section.9">
    493       <link rel="Chapter" title="10 Header Field Definitions" href="#rfc.section.10">
    494       <link rel="Chapter" title="11 IANA Considerations" href="#rfc.section.11">
    495       <link rel="Chapter" title="12 Security Considerations" href="#rfc.section.12">
    496       <link rel="Chapter" title="13 Acknowledgments" href="#rfc.section.13">
    497       <link rel="Chapter" href="#rfc.section.14" title="14 References">
     488      <link rel="Chapter" title="5 Common Protocol Parameters" href="#rfc.section.5">
     489      <link rel="Chapter" title="6 Payload" href="#rfc.section.6">
     490      <link rel="Chapter" title="7 Representation" href="#rfc.section.7">
     491      <link rel="Chapter" title="8 Content Negotiation" href="#rfc.section.8">
     492      <link rel="Chapter" title="9 Header Field Definitions" href="#rfc.section.9">
     493      <link rel="Chapter" title="10 IANA Considerations" href="#rfc.section.10">
     494      <link rel="Chapter" title="11 Security Considerations" href="#rfc.section.11">
     495      <link rel="Chapter" title="12 Acknowledgments" href="#rfc.section.12">
     496      <link rel="Chapter" href="#rfc.section.13" title="13 References">
    498497      <link rel="Appendix" title="A Differences between HTTP and MIME" href="#rfc.section.A">
    499498      <link rel="Appendix" title="B Additional Features" href="#rfc.section.B">
    … …  
    691690            </ul>
    692691         </li>
    693          <li>5.&nbsp;&nbsp;&nbsp;<a href="#representation">Representation</a><ul>
    694                <li>5.1&nbsp;&nbsp;&nbsp;<a href="#identifying.response.associated.with.representation">Identifying the Resource Associated with a Representation</a></li>
    695             </ul>
    696          </li>
    697          <li>6.&nbsp;&nbsp;&nbsp;<a href="#common.protocol.parameters">Common Protocol Parameters</a><ul>
    698                <li>6.1&nbsp;&nbsp;&nbsp;<a href="#http.date">Date/Time Formats</a></li>
    699                <li>6.2&nbsp;&nbsp;&nbsp;<a href="#product.tokens">Product Tokens</a></li>
    700                <li>6.3&nbsp;&nbsp;&nbsp;<a href="#character.sets">Character Encodings (charset)</a></li>
    701                <li>6.4&nbsp;&nbsp;&nbsp;<a href="#content.codings">Content Codings</a><ul>
    702                      <li>6.4.1&nbsp;&nbsp;&nbsp;<a href="#content.coding.registry">Content Coding Registry</a></li>
     692         <li>5.&nbsp;&nbsp;&nbsp;<a href="#common.protocol.parameters">Common Protocol Parameters</a><ul>
     693               <li>5.1&nbsp;&nbsp;&nbsp;<a href="#http.date">Date/Time Formats</a></li>
     694               <li>5.2&nbsp;&nbsp;&nbsp;<a href="#product.tokens">Product Tokens</a></li>
     695               <li>5.3&nbsp;&nbsp;&nbsp;<a href="#character.sets">Character Encodings (charset)</a></li>
     696               <li>5.4&nbsp;&nbsp;&nbsp;<a href="#content.codings">Content Codings</a><ul>
     697                     <li>5.4.1&nbsp;&nbsp;&nbsp;<a href="#content.coding.registry">Content Coding Registry</a></li>
    703698                  </ul>
    704699               </li>
    705                <li>6.5&nbsp;&nbsp;&nbsp;<a href="#media.types">Media Types</a><ul>
    706                      <li>6.5.1&nbsp;&nbsp;&nbsp;<a href="#canonicalization.and.text.defaults">Canonicalization and Text Defaults</a></li>
    707                      <li>6.5.2&nbsp;&nbsp;&nbsp;<a href="#multipart.types">Multipart Types</a></li>
     700               <li>5.5&nbsp;&nbsp;&nbsp;<a href="#media.types">Media Types</a><ul>
     701                     <li>5.5.1&nbsp;&nbsp;&nbsp;<a href="#canonicalization.and.text.defaults">Canonicalization and Text Defaults</a></li>
     702                     <li>5.5.2&nbsp;&nbsp;&nbsp;<a href="#multipart.types">Multipart Types</a></li>
    708703                  </ul>
    709704               </li>
    710                <li>6.6&nbsp;&nbsp;&nbsp;<a href="#language.tags">Language Tags</a></li>
     705               <li>5.6&nbsp;&nbsp;&nbsp;<a href="#language.tags">Language Tags</a></li>
    711706            </ul>
    712707         </li>
    713          <li>7.&nbsp;&nbsp;&nbsp;<a href="#payload">Payload</a><ul>
    714                <li>7.1&nbsp;&nbsp;&nbsp;<a href="#payload.header.fields">Payload Header Fields</a></li>
    715                <li>7.2&nbsp;&nbsp;&nbsp;<a href="#payload.body">Payload Body</a></li>
     708         <li>6.&nbsp;&nbsp;&nbsp;<a href="#payload">Payload</a><ul>
     709               <li>6.1&nbsp;&nbsp;&nbsp;<a href="#payload.header.fields">Payload Header Fields</a></li>
     710               <li>6.2&nbsp;&nbsp;&nbsp;<a href="#payload.body">Payload Body</a></li>
    716711            </ul>
    717712         </li>
    718          <li>8.&nbsp;&nbsp;&nbsp;<a href="#representation-TODO">Representation</a><ul>
    719                <li>8.1&nbsp;&nbsp;&nbsp;<a href="#representation.header.fields">Representation Header Fields</a></li>
    720                <li>8.2&nbsp;&nbsp;&nbsp;<a href="#representation.data">Representation Data</a></li>
     713         <li>7.&nbsp;&nbsp;&nbsp;<a href="#rfc.section.7">Representation</a><ul>
     714               <li>7.1&nbsp;&nbsp;&nbsp;<a href="#identifying.response.associated.with.representation">Identifying the Resource Associated with a Representation</a></li>
     715               <li>7.2&nbsp;&nbsp;&nbsp;<a href="#representation.header.fields">Representation Header Fields</a></li>
     716               <li>7.3&nbsp;&nbsp;&nbsp;<a href="#representation.data">Representation Data</a></li>
    721717            </ul>
    722718         </li>
    723          <li>9.&nbsp;&nbsp;&nbsp;<a href="#content.negotiation">Content Negotiation</a><ul>
    724                <li>9.1&nbsp;&nbsp;&nbsp;<a href="#server-driven.negotiation">Server-driven Negotiation</a></li>
    725                <li>9.2&nbsp;&nbsp;&nbsp;<a href="#agent-driven.negotiation">Agent-driven Negotiation</a></li>
     719         <li>8.&nbsp;&nbsp;&nbsp;<a href="#content.negotiation">Content Negotiation</a><ul>
     720               <li>8.1&nbsp;&nbsp;&nbsp;<a href="#server-driven.negotiation">Server-driven Negotiation</a></li>
     721               <li>8.2&nbsp;&nbsp;&nbsp;<a href="#agent-driven.negotiation">Agent-driven Negotiation</a></li>
    726722            </ul>
    727723         </li>
    728          <li>10.&nbsp;&nbsp;&nbsp;<a href="#header.field.definitions">Header Field Definitions</a><ul>
    729                <li>10.1&nbsp;&nbsp;&nbsp;<a href="#header.allow">Allow</a></li>
    730                <li>10.2&nbsp;&nbsp;&nbsp;<a href="#header.date">Date</a></li>
    731                <li>10.3&nbsp;&nbsp;&nbsp;<a href="#header.expect">Expect</a></li>
    732                <li>10.4&nbsp;&nbsp;&nbsp;<a href="#header.from">From</a></li>
    733                <li>10.5&nbsp;&nbsp;&nbsp;<a href="#header.location">Location</a></li>
    734                <li>10.6&nbsp;&nbsp;&nbsp;<a href="#header.max-forwards">Max-Forwards</a></li>
    735                <li>10.7&nbsp;&nbsp;&nbsp;<a href="#header.referer">Referer</a></li>
    736                <li>10.8&nbsp;&nbsp;&nbsp;<a href="#header.retry-after">Retry-After</a></li>
    737                <li>10.9&nbsp;&nbsp;&nbsp;<a href="#header.server">Server</a></li>
    738                <li>10.10&nbsp;&nbsp;&nbsp;<a href="#header.user-agent">User-Agent</a></li>
    739                <li>10.11&nbsp;&nbsp;&nbsp;<a href="#header.accept">Accept</a></li>
    740                <li>10.12&nbsp;&nbsp;&nbsp;<a href="#header.accept-charset">Accept-Charset</a></li>
    741                <li>10.13&nbsp;&nbsp;&nbsp;<a href="#header.accept-encoding">Accept-Encoding</a></li>
    742                <li>10.14&nbsp;&nbsp;&nbsp;<a href="#header.accept-language">Accept-Language</a></li>
    743                <li>10.15&nbsp;&nbsp;&nbsp;<a href="#header.content-encoding">Content-Encoding</a></li>
    744                <li>10.16&nbsp;&nbsp;&nbsp;<a href="#header.content-language">Content-Language</a></li>
    745                <li>10.17&nbsp;&nbsp;&nbsp;<a href="#header.content-location">Content-Location</a></li>
    746                <li>10.18&nbsp;&nbsp;&nbsp;<a href="#header.content-type">Content-Type</a></li>
     724         <li>9.&nbsp;&nbsp;&nbsp;<a href="#header.field.definitions">Header Field Definitions</a><ul>
     725               <li>9.1&nbsp;&nbsp;&nbsp;<a href="#header.allow">Allow</a></li>
     726               <li>9.2&nbsp;&nbsp;&nbsp;<a href="#header.date">Date</a></li>
     727               <li>9.3&nbsp;&nbsp;&nbsp;<a href="#header.expect">Expect</a></li>
     728               <li>9.4&nbsp;&nbsp;&nbsp;<a href="#header.from">From</a></li>
     729               <li>9.5&nbsp;&nbsp;&nbsp;<a href="#header.location">Location</a></li>
     730               <li>9.6&nbsp;&nbsp;&nbsp;<a href="#header.max-forwards">Max-Forwards</a></li>
     731               <li>9.7&nbsp;&nbsp;&nbsp;<a href="#header.referer">Referer</a></li>
     732               <li>9.8&nbsp;&nbsp;&nbsp;<a href="#header.retry-after">Retry-After</a></li>
     733               <li>9.9&nbsp;&nbsp;&nbsp;<a href="#header.server">Server</a></li>
     734               <li>9.10&nbsp;&nbsp;&nbsp;<a href="#header.user-agent">User-Agent</a></li>
     735               <li>9.11&nbsp;&nbsp;&nbsp;<a href="#header.accept">Accept</a></li>
     736               <li>9.12&nbsp;&nbsp;&nbsp;<a href="#header.accept-charset">Accept-Charset</a></li>
     737               <li>9.13&nbsp;&nbsp;&nbsp;<a href="#header.accept-encoding">Accept-Encoding</a></li>
     738               <li>9.14&nbsp;&nbsp;&nbsp;<a href="#header.accept-language">Accept-Language</a></li>
     739               <li>9.15&nbsp;&nbsp;&nbsp;<a href="#header.content-encoding">Content-Encoding</a></li>
     740               <li>9.16&nbsp;&nbsp;&nbsp;<a href="#header.content-language">Content-Language</a></li>
     741               <li>9.17&nbsp;&nbsp;&nbsp;<a href="#header.content-location">Content-Location</a></li>
     742               <li>9.18&nbsp;&nbsp;&nbsp;<a href="#header.content-type">Content-Type</a></li>
    747743            </ul>
    748744         </li>
    749          <li>11.&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a><ul>
    750                <li>11.1&nbsp;&nbsp;&nbsp;<a href="#method.registration">Method Registry</a></li>
    751                <li>11.2&nbsp;&nbsp;&nbsp;<a href="#status.code.registration">Status Code Registry</a></li>
    752                <li>11.3&nbsp;&nbsp;&nbsp;<a href="#header.field.registration">Header Field Registration</a></li>
    753                <li>11.4&nbsp;&nbsp;&nbsp;<a href="#content.coding.registration">Content Coding Registry</a></li>
     745         <li>10.&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a><ul>
     746               <li>10.1&nbsp;&nbsp;&nbsp;<a href="#method.registration">Method Registry</a></li>
     747               <li>10.2&nbsp;&nbsp;&nbsp;<a href="#status.code.registration">Status Code Registry</a></li>
     748               <li>10.3&nbsp;&nbsp;&nbsp;<a href="#header.field.registration">Header Field Registration</a></li>
     749               <li>10.4&nbsp;&nbsp;&nbsp;<a href="#content.coding.registration">Content Coding Registry</a></li>
    754750            </ul>
    755751         </li>
    756          <li>12.&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a><ul>
    757                <li>12.1&nbsp;&nbsp;&nbsp;<a href="#security.sensitive">Transfer of Sensitive Information</a></li>
    758                <li>12.2&nbsp;&nbsp;&nbsp;<a href="#encoding.sensitive.information.in.uris">Encoding Sensitive Information in URIs</a></li>
    759                <li>12.3&nbsp;&nbsp;&nbsp;<a href="#location.spoofing-leakage">Location Header Fields: Spoofing and Information Leakage</a></li>
    760                <li>12.4&nbsp;&nbsp;&nbsp;<a href="#rfc.section.12.4">Security Considerations for CONNECT</a></li>
    761                <li>12.5&nbsp;&nbsp;&nbsp;<a href="#privacy.issues.connected.to.accept.header.fields">Privacy Issues Connected to Accept Header Fields</a></li>
     752         <li>11.&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a><ul>
     753               <li>11.1&nbsp;&nbsp;&nbsp;<a href="#security.sensitive">Transfer of Sensitive Information</a></li>
     754               <li>11.2&nbsp;&nbsp;&nbsp;<a href="#encoding.sensitive.information.in.uris">Encoding Sensitive Information in URIs</a></li>
     755               <li>11.3&nbsp;&nbsp;&nbsp;<a href="#location.spoofing-leakage">Location Header Fields: Spoofing and Information Leakage</a></li>
     756               <li>11.4&nbsp;&nbsp;&nbsp;<a href="#rfc.section.11.4">Security Considerations for CONNECT</a></li>
     757               <li>11.5&nbsp;&nbsp;&nbsp;<a href="#privacy.issues.connected.to.accept.header.fields">Privacy Issues Connected to Accept Header Fields</a></li>
    762758            </ul>
    763759         </li>
    764          <li>13.&nbsp;&nbsp;&nbsp;<a href="#acks">Acknowledgments</a></li>
    765          <li>14.&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
    766                <li>14.1&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
    767                <li>14.2&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
     760         <li>12.&nbsp;&nbsp;&nbsp;<a href="#acks">Acknowledgments</a></li>
     761         <li>13.&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
     762               <li>13.1&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
     763               <li>13.2&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
    768764            </ul>
    769765         </li>
    … …  
    907903      </p>
    908904      <div id="rfc.figure.u.3"></div><pre class="inline"><span id="rfc.iref.g.1"></span>  <a href="#methods" class="smpl">method</a>         = <a href="#core.rules" class="smpl">token</a>
    909 </pre><p id="rfc.section.2.p.3">The list of methods allowed by a resource can be specified in an Allow header field (<a href="#header.allow" id="rfc.xref.header.allow.1" title="Allow">Section&nbsp;10.1</a>). The status code of the response always notifies the client whether a method is currently allowed on a resource, since the
     905</pre><p id="rfc.section.2.p.3">The list of methods allowed by a resource can be specified in an Allow header field (<a href="#header.allow" id="rfc.xref.header.allow.1" title="Allow">Section&nbsp;9.1</a>). The status code of the response always notifies the client whether a method is currently allowed on a resource, since the
    910906         set of allowed methods can change dynamically. An origin server <em class="bcp14">SHOULD</em> respond with the status code 405 (Method Not Allowed) if the method is known by the origin server but not allowed for the
    911907         resource, and 501 (Not Implemented) if the method is unrecognized or not implemented by the origin server. The methods GET
    … …  
    987983         but might be defined by future extensions to HTTP. Content negotiation <em class="bcp14">MAY</em> be used to select the appropriate response format. If no response body is included, the response <em class="bcp14">MUST</em> include a Content-Length field with a field-value of "0".
    988984      </p>
    989       <p id="rfc.section.2.3.1.p.7">The Max-Forwards header field <em class="bcp14">MAY</em> be used to target a specific proxy in the request chain (see <a href="#header.max-forwards" id="rfc.xref.header.max-forwards.1" title="Max-Forwards">Section&nbsp;10.6</a>). If no Max-Forwards field is present in the request, then the forwarded request <em class="bcp14">MUST NOT</em> include a Max-Forwards field.
     985      <p id="rfc.section.2.3.1.p.7">The Max-Forwards header field <em class="bcp14">MAY</em> be used to target a specific proxy in the request chain (see <a href="#header.max-forwards" id="rfc.xref.header.max-forwards.1" title="Max-Forwards">Section&nbsp;9.6</a>). If no Max-Forwards field is present in the request, then the forwarded request <em class="bcp14">MUST NOT</em> include a Max-Forwards field.
    990986      </p>
    991987      <h3 id="rfc.section.2.3.2"><a href="#rfc.section.2.3.2">2.3.2</a>&nbsp;<a id="GET" href="#GET">GET</a></h3>
    … …  
    10111007      <p id="rfc.section.2.3.2.p.6">The response to a GET request is cacheable and <em class="bcp14">MAY</em> be used to satisfy subsequent GET and HEAD requests (see <a href="#Part6" id="rfc.xref.Part6.2"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).
    10121008      </p>
    1013       <p id="rfc.section.2.3.2.p.7">See <a href="#encoding.sensitive.information.in.uris" title="Encoding Sensitive Information in URIs">Section&nbsp;12.2</a> for security considerations when used for forms.
     1009      <p id="rfc.section.2.3.2.p.7">See <a href="#encoding.sensitive.information.in.uris" title="Encoding Sensitive Information in URIs">Section&nbsp;11.2</a> for security considerations when used for forms.
    10141010      </p>
    10151011      <h3 id="rfc.section.2.3.3"><a href="#rfc.section.2.3.3">2.3.3</a>&nbsp;<a id="HEAD" href="#HEAD">HEAD</a></h3>
    … …  
    10451041      </p>
    10461042      <p id="rfc.section.2.3.4.p.4">If a resource has been created on the origin server, the response <em class="bcp14">SHOULD</em> be 201 (Created) and contain a representation which describes the status of the request and refers to the new resource, and
    1047          a Location header field (see <a href="#header.location" id="rfc.xref.header.location.1" title="Location">Section&nbsp;10.5</a>).
    1048       </p>
    1049       <p id="rfc.section.2.3.4.p.5">Responses to POST requests are only cacheable when they include explicit freshness information (see <a href="p6-cache.html#calculating.freshness.lifetime" title="Calculating Freshness Lifetime">Section 2.3.1</a> of <a href="#Part6" id="rfc.xref.Part6.4"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>). A cached POST response with a Content-Location header field (see <a href="#header.content-location" id="rfc.xref.header.content-location.1" title="Content-Location">Section&nbsp;10.17</a>) whose value is the effective Request URI <em class="bcp14">MAY</em> be used to satisfy subsequent GET and HEAD requests.
     1043         a Location header field (see <a href="#header.location" id="rfc.xref.header.location.1" title="Location">Section&nbsp;9.5</a>).
     1044      </p>
     1045      <p id="rfc.section.2.3.4.p.5">Responses to POST requests are only cacheable when they include explicit freshness information (see <a href="p6-cache.html#calculating.freshness.lifetime" title="Calculating Freshness Lifetime">Section 2.3.1</a> of <a href="#Part6" id="rfc.xref.Part6.4"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>). A cached POST response with a Content-Location header field (see <a href="#header.content-location" id="rfc.xref.header.content-location.1" title="Content-Location">Section&nbsp;9.17</a>) whose value is the effective Request URI <em class="bcp14">MAY</em> be used to satisfy subsequent GET and HEAD requests.
    10501046      </p>
    10511047      <p id="rfc.section.2.3.4.p.6">Note that POST caching is not widely implemented. However, the 303 (See Other) response can be used to direct the user agent
    … …  
    11351131      <div id="rfc.iref.m.7"></div>
    11361132      <p id="rfc.section.2.3.7.p.1">The TRACE method requests a remote, application-layer loop-back of the request message. The final recipient of the request <em class="bcp14">SHOULD</em> reflect the message received back to the client as the message body of a 200 (OK) response. The final recipient is either
    1137          the origin server or the first proxy to receive a Max-Forwards value of zero (0) in the request (see <a href="#header.max-forwards" id="rfc.xref.header.max-forwards.2" title="Max-Forwards">Section&nbsp;10.6</a>). A TRACE request <em class="bcp14">MUST NOT</em> include a message body.
     1133         the origin server or the first proxy to receive a Max-Forwards value of zero (0) in the request (see <a href="#header.max-forwards" id="rfc.xref.header.max-forwards.2" title="Max-Forwards">Section&nbsp;9.6</a>). A TRACE request <em class="bcp14">MUST NOT</em> include a message body.
    11381134      </p>
    11391135      <p id="rfc.section.2.3.7.p.2">TRACE allows the client to see what is being received at the other end of the request chain and use that data for testing
    … …  
    12101206         double quotes will likely cause unnecessary confusion.
    12111207      </p>
    1212       <p id="rfc.section.3.1.p.8">Many header fields use a format including (case-insensitively) named parameters (for instance, Content-Type, defined in <a href="#header.content-type" id="rfc.xref.header.content-type.1" title="Content-Type">Section&nbsp;10.18</a>). Allowing both unquoted (token) and quoted (quoted-string) syntax for the parameter value enables recipients to use existing
     1208      <p id="rfc.section.3.1.p.8">Many header fields use a format including (case-insensitively) named parameters (for instance, Content-Type, defined in <a href="#header.content-type" id="rfc.xref.header.content-type.1" title="Content-Type">Section&nbsp;9.18</a>). Allowing both unquoted (token) and quoted (quoted-string) syntax for the parameter value enables recipients to use existing
    12131209         parser components. When allowing both forms, the meaning of a parameter value ought to be independent of the syntax used for
    1214          it (for an example, see the notes on parameter handling for media types in <a href="#media.types" title="Media Types">Section&nbsp;6.5</a>).
     1210         it (for an example, see the notes on parameter handling for media types in <a href="#media.types" title="Media Types">Section&nbsp;5.5</a>).
    12151211      </p>
    12161212      <p id="rfc.section.3.1.p.9">Authors of specifications defining new header fields are advised to consider documenting: </p>
    … …  
    12671263               <tr>
    12681264                  <td class="left">Accept</td>
    1269                   <td class="left"><a href="#header.accept" id="rfc.xref.header.accept.1" title="Accept">Section&nbsp;10.11</a></td>
     1265                  <td class="left"><a href="#header.accept" id="rfc.xref.header.accept.1" title="Accept">Section&nbsp;9.11</a></td>
    12701266               </tr>
    12711267               <tr>
    12721268                  <td class="left">Accept-Charset</td>
    1273                   <td class="left"><a href="#header.accept-charset" id="rfc.xref.header.accept-charset.1" title="Accept-Charset">Section&nbsp;10.12</a></td>
     1269                  <td class="left"><a href="#header.accept-charset" id="rfc.xref.header.accept-charset.1" title="Accept-Charset">Section&nbsp;9.12</a></td>
    12741270               </tr>
    12751271               <tr>
    12761272                  <td class="left">Accept-Encoding</td>
    1277                   <td class="left"><a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.1" title="Accept-Encoding">Section&nbsp;10.13</a></td>
     1273                  <td class="left"><a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.1" title="Accept-Encoding">Section&nbsp;9.13</a></td>
    12781274               </tr>
    12791275               <tr>
    12801276                  <td class="left">Accept-Language</td>
    1281                   <td class="left"><a href="#header.accept-language" id="rfc.xref.header.accept-language.1" title="Accept-Language">Section&nbsp;10.14</a></td>
     1277                  <td class="left"><a href="#header.accept-language" id="rfc.xref.header.accept-language.1" title="Accept-Language">Section&nbsp;9.14</a></td>
    12821278               </tr>
    12831279               <tr>
    … …  
    12871283               <tr>
    12881284                  <td class="left">Expect</td>
    1289                   <td class="left"><a href="#header.expect" id="rfc.xref.header.expect.1" title="Expect">Section&nbsp;10.3</a></td>
     1285                  <td class="left"><a href="#header.expect" id="rfc.xref.header.expect.1" title="Expect">Section&nbsp;9.3</a></td>
    12901286               </tr>
    12911287               <tr>
    12921288                  <td class="left">From</td>
    1293                   <td class="left"><a href="#header.from" id="rfc.xref.header.from.1" title="From">Section&nbsp;10.4</a></td>
     1289                  <td class="left"><a href="#header.from" id="rfc.xref.header.from.1" title="From">Section&nbsp;9.4</a></td>
    12941290               </tr>
    12951291               <tr>
    … …  
    13191315               <tr>
    13201316                  <td class="left">Max-Forwards</td>
    1321                   <td class="left"><a href="#header.max-forwards" id="rfc.xref.header.max-forwards.3" title="Max-Forwards">Section&nbsp;10.6</a></td>
     1317                  <td class="left"><a href="#header.max-forwards" id="rfc.xref.header.max-forwards.3" title="Max-Forwards">Section&nbsp;9.6</a></td>
    13221318               </tr>
    13231319               <tr>
    … …  
    13311327               <tr>
    13321328                  <td class="left">Referer</td>
    1333                   <td class="left"><a href="#header.referer" id="rfc.xref.header.referer.1" title="Referer">Section&nbsp;10.7</a></td>
     1329                  <td class="left"><a href="#header.referer" id="rfc.xref.header.referer.1" title="Referer">Section&nbsp;9.7</a></td>
    13341330               </tr>
    13351331               <tr>
    … …  
    13391335               <tr>
    13401336                  <td class="left">User-Agent</td>
    1341                   <td class="left"><a href="#header.user-agent" id="rfc.xref.header.user-agent.1" title="User-Agent">Section&nbsp;10.10</a></td>
     1337                  <td class="left"><a href="#header.user-agent" id="rfc.xref.header.user-agent.1" title="User-Agent">Section&nbsp;9.10</a></td>
    13421338               </tr>
    13431339            </tbody>
    … …  
    13671363               <tr>
    13681364                  <td class="left">Allow</td>
    1369                   <td class="left"><a href="#header.allow" id="rfc.xref.header.allow.2" title="Allow">Section&nbsp;10.1</a></td>
     1365                  <td class="left"><a href="#header.allow" id="rfc.xref.header.allow.2" title="Allow">Section&nbsp;9.1</a></td>
    13701366               </tr>
    13711367               <tr>
    13721368                  <td class="left">Date</td>
    1373                   <td class="left"><a href="#header.date" id="rfc.xref.header.date.1" title="Date">Section&nbsp;10.2</a></td>
     1369                  <td class="left"><a href="#header.date" id="rfc.xref.header.date.1" title="Date">Section&nbsp;9.2</a></td>
    13741370               </tr>
    13751371               <tr>
    … …  
    13791375               <tr>
    13801376                  <td class="left">Location</td>
    1381                   <td class="left"><a href="#header.location" id="rfc.xref.header.location.2" title="Location">Section&nbsp;10.5</a></td>
     1377                  <td class="left"><a href="#header.location" id="rfc.xref.header.location.2" title="Location">Section&nbsp;9.5</a></td>
    13821378               </tr>
    13831379               <tr>
    … …  
    13871383               <tr>
    13881384                  <td class="left">Retry-After</td>
    1389                   <td class="left"><a href="#header.retry-after" id="rfc.xref.header.retry-after.1" title="Retry-After">Section&nbsp;10.8</a></td>
     1385                  <td class="left"><a href="#header.retry-after" id="rfc.xref.header.retry-after.1" title="Retry-After">Section&nbsp;9.8</a></td>
    13901386               </tr>
    13911387               <tr>
    13921388                  <td class="left">Server</td>
    1393                   <td class="left"><a href="#header.server" id="rfc.xref.header.server.1" title="Server">Section&nbsp;10.9</a></td>
     1389                  <td class="left"><a href="#header.server" id="rfc.xref.header.server.1" title="Server">Section&nbsp;9.9</a></td>
    13941390               </tr>
    13951391               <tr>
    … …  
    14281424      </ul>
    14291425      <p id="rfc.section.4.p.6">For most status codes the response can carry a payload, in which case a Content-Type header field indicates the payload's
    1430          media type (<a href="#header.content-type" id="rfc.xref.header.content-type.2" title="Content-Type">Section&nbsp;10.18</a>).
     1426         media type (<a href="#header.content-type" id="rfc.xref.header.content-type.2" title="Content-Type">Section&nbsp;9.18</a>).
    14311427      </p>
    14321428      <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a>&nbsp;<a id="overview.of.status.codes" href="#overview.of.status.codes">Overview of Status Codes</a></h2>
    … …  
    16741670         a zero-length response body. They can require the presence of one or more particular HTTP response header(s).
    16751671      </p>
    1676       <p id="rfc.section.4.2.1.p.5">Likewise, their definitions can specify that caches are allowed to use heuristics to determine their freshness (see <a href="#Part6" id="rfc.xref.Part6.10"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>; by default, it is not allowed), and can define how to determine the resource which they carry a representation for (see <a href="#identifying.response.associated.with.representation" title="Identifying the Resource Associated with a Representation">Section&nbsp;5.1</a>; by default, it is anonymous).
     1672      <p id="rfc.section.4.2.1.p.5">Likewise, their definitions can specify that caches are allowed to use heuristics to determine their freshness (see <a href="#Part6" id="rfc.xref.Part6.10"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>; by default, it is not allowed), and can define how to determine the resource which they carry a representation for (see <a href="#identifying.response.associated.with.representation" title="Identifying the Resource Associated with a Representation">Section&nbsp;7.1</a>; by default, it is anonymous).
    16771673      </p>
    16781674      <h2 id="rfc.section.4.3"><a href="#rfc.section.4.3">4.3</a>&nbsp;<a id="status.1xx" href="#status.1xx">Informational 1xx</a></h2>
    … …  
    18071803         </li>
    18081804         <li>
    1809             <p>Redirection offering a choice of matching resources for use by agent-driven content negotiation (<a href="#agent-driven.negotiation" title="Agent-driven Negotiation">Section&nbsp;9.2</a>). This is status code 300 (Multiple Choices).
     1805            <p>Redirection offering a choice of matching resources for use by agent-driven content negotiation (<a href="#agent-driven.negotiation" title="Agent-driven Negotiation">Section&nbsp;8.2</a>). This is status code 300 (Multiple Choices).
    18101806            </p>
    18111807         </li>
    … …  
    18241820         </p>
    18251821      </div>
    1826       <p id="rfc.section.4.5.p.4">A Location header field on a 3xx response indicates that a client <em class="bcp14">MAY</em> automatically redirect to the URI provided; see <a href="#header.location" id="rfc.xref.header.location.3" title="Location">Section&nbsp;10.5</a>.
     1822      <p id="rfc.section.4.5.p.4">A Location header field on a 3xx response indicates that a client <em class="bcp14">MAY</em> automatically redirect to the URI provided; see <a href="#header.location" id="rfc.xref.header.location.3" title="Location">Section&nbsp;9.5</a>.
    18271823      </p>
    18281824      <p id="rfc.section.4.5.p.5">Note that for methods not known to be "safe", as defined in <a href="#safe.methods" title="Safe Methods">Section&nbsp;2.1.1</a>, automatic redirection needs to done with care, since the redirect might change the conditions under which the request was
    … …  
    18391835      <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>
    18401836      <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
    1841          (<a href="#content.negotiation" title="Content Negotiation">Section&nbsp;9</a>) is being provided so that the user (or user agent) can select a preferred representation by redirecting its request to that
     1837         (<a href="#content.negotiation" title="Content Negotiation">Section&nbsp;8</a>) is being provided so that the user (or user agent) can select a preferred representation by redirecting its request to that
    18421838         location.
    18431839      </p>
    … …  
    20402036      <div id="rfc.iref.s.31"></div>
    20412037      <h3 id="rfc.section.4.6.14"><a href="#rfc.section.4.6.14">4.6.14</a>&nbsp;<a id="status.417" href="#status.417">417 Expectation Failed</a></h3>
    2042       <p id="rfc.section.4.6.14.p.1">The expectation given in an Expect header field (see <a href="#header.expect" id="rfc.xref.header.expect.2" title="Expect">Section&nbsp;10.3</a>) could not be met by this server, or, if the server is a proxy, the server has unambiguous evidence that the request could
     2038      <p id="rfc.section.4.6.14.p.1">The expectation given in an Expect header field (see <a href="#header.expect" id="rfc.xref.header.expect.2" title="Expect">Section&nbsp;9.3</a>) could not be met by this server, or, if the server is a proxy, the server has unambiguous evidence that the request could
    20432039         not be met by the next-hop server.
    20442040      </p>
    … …  
    20852081      <p id="rfc.section.4.7.4.p.1">The server is currently unable to handle the request due to a temporary overloading or maintenance of the server.</p>
    20862082      <p id="rfc.section.4.7.4.p.2">The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the
    2087          delay <em class="bcp14">MAY</em> be indicated in a Retry-After header field (<a href="#header.retry-after" id="rfc.xref.header.retry-after.2" title="Retry-After">Section&nbsp;10.8</a>). If no Retry-After is given, the client <em class="bcp14">SHOULD</em> handle the response as it would for a 500 response.
     2083         delay <em class="bcp14">MAY</em> be indicated in a Retry-After header field (<a href="#header.retry-after" id="rfc.xref.header.retry-after.2" title="Retry-After">Section&nbsp;9.8</a>). If no Retry-After is given, the client <em class="bcp14">SHOULD</em> handle the response as it would for a 500 response.
    20882084      </p>
    20892085      <div class="note" id="rfc.section.4.7.4.p.3">
    … …  
    21092105         in <a href="p1-messaging.html#http.version" title="Protocol Versioning">Section 2.6</a> of <a href="#Part1" id="rfc.xref.Part1.37"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, other than with this error message. The response <em class="bcp14">SHOULD</em> contain a representation describing why that version is not supported and what other protocols are supported by that server.
    21102106      </p>
    2111       <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a id="representation" href="#representation">Representation</a></h1>
    2112       <p id="rfc.section.5.p.1">Request and Response messages <em class="bcp14">MAY</em> transfer a representation if not otherwise restricted by the request method or response status code. A representation consists
    2113          of metadata (representation header fields) and data (representation body). When a complete or partial representation is enclosed
    2114          in an HTTP message, it is referred to as the payload of the message. HTTP representations are defined in <a href="#payload" title="Payload">Section&nbsp;7</a>.
    2115       </p>
    2116       <p id="rfc.section.5.p.2">A representation 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.38"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. The representation body is obtained from the message body by decoding any Transfer-Encoding that might have been applied
    2117          to ensure safe and proper transfer of the message.
    2118       </p>
    2119       <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;<a id="identifying.response.associated.with.representation" href="#identifying.response.associated.with.representation">Identifying the Resource Associated with a Representation</a></h2>
    2120       <p id="rfc.section.5.1.p.1">It is sometimes necessary to determine an identifier for the resource associated with a representation.</p>
    2121       <p id="rfc.section.5.1.p.2">An HTTP request representation, when present, is always associated with an anonymous (i.e., unidentified) resource.</p>
    2122       <p id="rfc.section.5.1.p.3">In the common case, an HTTP response is a representation of the target resource (see <a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.39"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). However, this is not always the case. To determine the URI of the resource a response is associated with, the following
    2123          rules are used (with the first applicable one being selected):
    2124       </p>
    2125       <ol>
    2126          <li>If the response status code is 200 or 203 and the request method was GET, the response payload is a representation of the
    2127             target resource.
    2128          </li>
    2129          <li>If the response status code is 204, 206, or 304 and the request method was GET or HEAD, the response payload is a partial
    2130             representation of the target resource.
    2131          </li>
    2132          <li>If the response has a Content-Location header field, and that URI is the same as the effective request URI, the response payload
    2133             is a representation of the target resource.
    2134          </li>
    2135          <li>If the response has a Content-Location header field, and that URI is not the same as the effective request URI, then the response
    2136             asserts that its payload is a representation of the resource identified by the Content-Location URI. However, such an assertion
    2137             cannot be trusted unless it can be verified by other means (not defined by HTTP).
    2138          </li>
    2139          <li>Otherwise, the response is a representation of an anonymous (i.e., unidentified) resource.</li>
    2140       </ol>
    2141       <p id="rfc.section.5.1.p.5"> <span class="comment" id="TODO-req-uri">[<a href="#TODO-req-uri" class="smpl">TODO-req-uri</a>: The comparison function is going to have to be defined somewhere, because we already need to compare URIs for things like
    2142             cache invalidation.]</span>
    2143       </p>
    2144       <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="common.protocol.parameters" href="#common.protocol.parameters">Common Protocol Parameters</a></h1>
    2145       <h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a>&nbsp;<a id="http.date" href="#http.date">Date/Time Formats</a></h2>
    2146       <p id="rfc.section.6.1.p.1">HTTP applications have historically allowed three different formats for date/time stamps. However, the preferred format is
     2107      <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a id="common.protocol.parameters" href="#common.protocol.parameters">Common Protocol Parameters</a></h1>
     2108      <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;<a id="http.date" href="#http.date">Date/Time Formats</a></h2>
     2109      <p id="rfc.section.5.1.p.1">HTTP applications have historically allowed three different formats for date/time stamps. However, the preferred format is
    21472110         a fixed-length subset of that defined by <a href="#RFC1123" id="rfc.xref.RFC1123.1"><cite title="Requirements for Internet Hosts - Application and Support">[RFC1123]</cite></a>:
    21482111      </p>
    21492112      <div id="rfc.figure.u.9"></div><pre class="text">Sun, 06 Nov 1994 08:49:37 GMT  ; RFC 1123
    2150 </pre><p id="rfc.section.6.1.p.3">The other formats are described here only for compatibility with obsolete implementations.</p>
     2113</pre><p id="rfc.section.5.1.p.3">The other formats are described here only for compatibility with obsolete implementations.</p>
    21512114      <div id="rfc.figure.u.10"></div><pre class="text">Sunday, 06-Nov-94 08:49:37 GMT ; obsolete RFC 850 format
    21522115Sun Nov  6 08:49:37 1994       ; ANSI C's asctime() format
    2153 </pre><p id="rfc.section.6.1.p.5">HTTP/1.1 clients and servers that parse a date value <em class="bcp14">MUST</em> accept all three formats (for compatibility with HTTP/1.0), though they <em class="bcp14">MUST</em> only generate the RFC 1123 format for representing HTTP-date values in header fields.
    2154       </p>
    2155       <p id="rfc.section.6.1.p.6">All HTTP date/time stamps <em class="bcp14">MUST</em> be represented in Greenwich Mean Time (GMT), without exception. For the purposes of HTTP, GMT is exactly equal to UTC (Coordinated
     2116</pre><p id="rfc.section.5.1.p.5">HTTP/1.1 clients and servers that parse a date value <em class="bcp14">MUST</em> accept all three formats (for compatibility with HTTP/1.0), though they <em class="bcp14">MUST</em> only generate the RFC 1123 format for representing HTTP-date values in header fields.
     2117      </p>
     2118      <p id="rfc.section.5.1.p.6">All HTTP date/time stamps <em class="bcp14">MUST</em> be represented in Greenwich Mean Time (GMT), without exception. For the purposes of HTTP, GMT is exactly equal to UTC (Coordinated
    21562119         Universal Time). This is indicated in the first two formats by the inclusion of "GMT" as the three-letter abbreviation for
    21572120         time zone, and <em class="bcp14">MUST</em> be assumed when reading the asctime format. HTTP-date is case sensitive and <em class="bcp14">MUST NOT</em> include additional whitespace beyond that specifically included as SP in the grammar.
    … …  
    21592122      <div id="rfc.figure.u.11"></div><pre class="inline"><span id="rfc.iref.g.6"></span>  <a href="#http.date" class="smpl">HTTP-date</a>    = <a href="#preferred.date.format" class="smpl">rfc1123-date</a> / <a href="#obsolete.date.formats" class="smpl">obs-date</a>
    21602123</pre><div id="preferred.date.format">
    2161          <p id="rfc.section.6.1.p.8">                    Preferred format:</p>
     2124         <p id="rfc.section.5.1.p.8">                    Preferred format:</p>
    21622125      </div>
    21632126      <div id="rfc.figure.u.12"></div><pre class="inline"><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span><span id="rfc.iref.g.9"></span><span id="rfc.iref.g.10"></span><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></span><span id="rfc.iref.g.16"></span><span id="rfc.iref.g.17"></span><span id="rfc.iref.g.18"></span>  <a href="#preferred.date.format" class="smpl">rfc1123-date</a> = <a href="#preferred.date.format" class="smpl">day-name</a> "," <a href="#notation" class="smpl">SP</a> date1 <a href="#notation" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">time-of-day</a> <a href="#notation" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">GMT</a>
    … …  
    21992162  <a href="#preferred.date.format" class="smpl">minute</a>       = 2<a href="#notation" class="smpl">DIGIT</a>               
    22002163  <a href="#preferred.date.format" class="smpl">second</a>       = 2<a href="#notation" class="smpl">DIGIT</a>               
    2201 </pre><p id="rfc.section.6.1.p.10">The semantics of <a href="#preferred.date.format" class="smpl">day-name</a>, <a href="#preferred.date.format" class="smpl">day</a>, <a href="#preferred.date.format" class="smpl">month</a>, <a href="#preferred.date.format" class="smpl">year</a>, and <a href="#preferred.date.format" class="smpl">time-of-day</a> are the same as those defined for the RFC 5322 constructs with the corresponding name (<a href="#RFC5322" id="rfc.xref.RFC5322.1"><cite title="Internet Message Format">[RFC5322]</cite></a>, <a href="http://tools.ietf.org/html/rfc5322#section-3.3">Section 3.3</a>).
     2164</pre><p id="rfc.section.5.1.p.10">The semantics of <a href="#preferred.date.format" class="smpl">day-name</a>, <a href="#preferred.date.format" class="smpl">day</a>, <a href="#preferred.date.format" class="smpl">month</a>, <a href="#preferred.date.format" class="smpl">year</a>, and <a href="#preferred.date.format" class="smpl">time-of-day</a> are the same as those defined for the RFC 5322 constructs with the corresponding name (<a href="#RFC5322" id="rfc.xref.RFC5322.1"><cite title="Internet Message Format">[RFC5322]</cite></a>, <a href="http://tools.ietf.org/html/rfc5322#section-3.3">Section 3.3</a>).
    22022165      </p>
    22032166      <div id="obsolete.date.formats">
    2204          <p id="rfc.section.6.1.p.11">                Obsolete formats:</p>
     2167         <p id="rfc.section.5.1.p.11">                Obsolete formats:</p>
    22052168      </div>
    22062169      <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.19"></span>  <a href="#obsolete.date.formats" class="smpl">obs-date</a>     = <a href="#obsolete.date.formats" class="smpl">rfc850-date</a> / <a href="#obsolete.date.formats" class="smpl">asctime-date</a>
    … …  
    22192182  <a href="#obsolete.date.formats" class="smpl">date3</a>        = <a href="#preferred.date.format" class="smpl">month</a> <a href="#notation" class="smpl">SP</a> ( 2<a href="#notation" class="smpl">DIGIT</a> / ( <a href="#notation" class="smpl">SP</a> 1<a href="#notation" class="smpl">DIGIT</a> ))
    22202183                 ; month day (e.g., Jun  2)
    2221 </pre><div class="note" id="rfc.section.6.1.p.15">
     2184</pre><div class="note" id="rfc.section.5.1.p.15">
    22222185         <p> <b>Note:</b> Recipients of date values are encouraged to be robust in accepting date values that might have been sent by non-HTTP applications,
    22232186            as is sometimes the case when retrieving or posting messages via proxies/gateways to SMTP or NNTP.
    22242187         </p>
    22252188      </div>
    2226       <div class="note" id="rfc.section.6.1.p.16">
     2189      <div class="note" id="rfc.section.5.1.p.16">
    22272190         <p> <b>Note:</b> HTTP requirements for the date/time stamp format apply only to their usage within the protocol stream. Clients and servers
    22282191            are not required to use these formats for user presentation, request logging, etc.
    22292192         </p>
    22302193      </div>
    2231       <h2 id="rfc.section.6.2"><a href="#rfc.section.6.2">6.2</a>&nbsp;<a id="product.tokens" href="#product.tokens">Product Tokens</a></h2>
    2232       <p id="rfc.section.6.2.p.1">Product tokens are used to allow communicating applications to identify themselves by software name and version. Most fields
     2194      <h2 id="rfc.section.5.2"><a href="#rfc.section.5.2">5.2</a>&nbsp;<a id="product.tokens" href="#product.tokens">Product Tokens</a></h2>
     2195      <p id="rfc.section.5.2.p.1">Product tokens are used to allow communicating applications to identify themselves by software name and version. Most fields
    22332196         using product tokens also allow sub-products which form a significant part of the application to be listed, separated by whitespace.
    22342197         By convention, the products are listed in order of their significance for identifying the application.
    … …  
    22362199      <div id="rfc.figure.u.16"></div><pre class="inline"><span id="rfc.iref.g.22"></span><span id="rfc.iref.g.23"></span>  <a href="#product.tokens" class="smpl">product</a>         = <a href="#core.rules" class="smpl">token</a> ["/" <a href="#product.tokens" class="smpl">product-version</a>]
    22372200  <a href="#product.tokens" class="smpl">product-version</a> = <a href="#core.rules" class="smpl">token</a>
    2238 </pre><p id="rfc.section.6.2.p.3">Examples:</p>
     2201</pre><p id="rfc.section.5.2.p.3">Examples:</p>
    22392202      <div id="rfc.figure.u.17"></div><pre class="text">  User-Agent: CERN-LineMode/2.15 libwww/2.17b3
    22402203  Server: Apache/0.8.4
    2241 </pre><p id="rfc.section.6.2.p.5">Product tokens <em class="bcp14">SHOULD</em> be short and to the point. They <em class="bcp14">MUST NOT</em> be used for advertising or other non-essential information. Although any token octet <em class="bcp14">MAY</em> appear in a product-version, this token <em class="bcp14">SHOULD</em> only be used for a version identifier (i.e., successive versions of the same product <em class="bcp14">SHOULD</em> only differ in the product-version portion of the product value).
    2242       </p>
    2243       <h2 id="rfc.section.6.3"><a href="#rfc.section.6.3">6.3</a>&nbsp;<a id="character.sets" href="#character.sets">Character Encodings (charset)</a></h2>
    2244       <p id="rfc.section.6.3.p.1">HTTP uses charset names to indicate the character encoding of a textual representation.</p>
     2204</pre><p id="rfc.section.5.2.p.5">Product tokens <em class="bcp14">SHOULD</em> be short and to the point. They <em class="bcp14">MUST NOT</em> be used for advertising or other non-essential information. Although any token octet <em class="bcp14">MAY</em> appear in a product-version, this token <em class="bcp14">SHOULD</em> only be used for a version identifier (i.e., successive versions of the same product <em class="bcp14">SHOULD</em> only differ in the product-version portion of the product value).
     2205      </p>
     2206      <h2 id="rfc.section.5.3"><a href="#rfc.section.5.3">5.3</a>&nbsp;<a id="character.sets" href="#character.sets">Character Encodings (charset)</a></h2>
     2207      <p id="rfc.section.5.3.p.1">HTTP uses charset names to indicate the character encoding of a textual representation.</p>
    22452208      <div id="rule.charset">
    2246          <p id="rfc.section.6.3.p.2">  A character encoding is identified by a case-insensitive token. The complete set of tokens is defined by the IANA Character
     2209         <p id="rfc.section.5.3.p.2">  A character encoding is identified by a case-insensitive token. The complete set of tokens is defined by the IANA Character
    22472210            Set registry (&lt;<a href="http://www.iana.org/assignments/character-sets">http://www.iana.org/assignments/character-sets</a>&gt;).
    22482211         </p>
    22492212      </div>
    22502213      <div id="rfc.figure.u.18"></div><pre class="inline"><span id="rfc.iref.g.24"></span>  <a href="#rule.charset" class="smpl">charset</a> = <a href="#core.rules" class="smpl">token</a>
    2251 </pre><p id="rfc.section.6.3.p.4">Although HTTP allows an arbitrary token to be used as a charset value, any token that has a predefined value within the IANA
     2214</pre><p id="rfc.section.5.3.p.4">Although HTTP allows an arbitrary token to be used as a charset value, any token that has a predefined value within the IANA
    22522215         Character Set registry <em class="bcp14">MUST</em> represent the character encoding defined by that registry. Applications <em class="bcp14">SHOULD</em> limit their use of character encodings to those defined within the IANA registry.
    22532216      </p>
    2254       <p id="rfc.section.6.3.p.5">HTTP uses charset in two contexts: within an Accept-Charset request header field (in which the charset value is an unquoted
     2217      <p id="rfc.section.5.3.p.5">HTTP uses charset in two contexts: within an Accept-Charset request header field (in which the charset value is an unquoted
    22552218         token) and as the value of a parameter in a Content-Type header field (within a request or response), in which case the parameter
    22562219         value of the charset parameter can be quoted.
    22572220      </p>
    2258       <p id="rfc.section.6.3.p.6">Implementors need to be aware of IETF character set requirements <a href="#RFC3629" id="rfc.xref.RFC3629.1"><cite title="UTF-8, a transformation format of ISO 10646">[RFC3629]</cite></a>  <a href="#RFC2277" id="rfc.xref.RFC2277.1"><cite title="IETF Policy on Character Sets and Languages">[RFC2277]</cite></a>.
    2259       </p>
    2260       <h2 id="rfc.section.6.4"><a href="#rfc.section.6.4">6.4</a>&nbsp;<a id="content.codings" href="#content.codings">Content Codings</a></h2>
    2261       <p id="rfc.section.6.4.p.1">Content coding values indicate an encoding transformation that has been or can be applied to a representation. Content codings
     2221      <p id="rfc.section.5.3.p.6">Implementors need to be aware of IETF character set requirements <a href="#RFC3629" id="rfc.xref.RFC3629.1"><cite title="UTF-8, a transformation format of ISO 10646">[RFC3629]</cite></a>  <a href="#RFC2277" id="rfc.xref.RFC2277.1"><cite title="IETF Policy on Character Sets and Languages">[RFC2277]</cite></a>.
     2222      </p>
     2223      <h2 id="rfc.section.5.4"><a href="#rfc.section.5.4">5.4</a>&nbsp;<a id="content.codings" href="#content.codings">Content Codings</a></h2>
     2224      <p id="rfc.section.5.4.p.1">Content coding values indicate an encoding transformation that has been or can be applied to a representation. Content codings
    22622225         are primarily used to allow a representation to be compressed or otherwise usefully transformed without losing the identity
    22632226         of its underlying media type and without loss of information. Frequently, the representation is stored in coded form, transmitted
    … …  
    22652228      </p>
    22662229      <div id="rfc.figure.u.19"></div><pre class="inline"><span id="rfc.iref.g.25"></span>  <a href="#content.codings" class="smpl">content-coding</a>   = <a href="#core.rules" class="smpl">token</a>
    2267 </pre><p id="rfc.section.6.4.p.3">All content-coding values are case-insensitive. HTTP/1.1 uses content-coding values in the Accept-Encoding (<a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.2" title="Accept-Encoding">Section&nbsp;10.13</a>) and Content-Encoding (<a href="#header.content-encoding" id="rfc.xref.header.content-encoding.1" title="Content-Encoding">Section&nbsp;10.15</a>) header fields. Although the value describes the content-coding, what is more important is that it indicates what decoding
     2230</pre><p id="rfc.section.5.4.p.3">All content-coding values are case-insensitive. HTTP/1.1 uses content-coding values in the Accept-Encoding (<a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.2" title="Accept-Encoding">Section&nbsp;9.13</a>) and Content-Encoding (<a href="#header.content-encoding" id="rfc.xref.header.content-encoding.1" title="Content-Encoding">Section&nbsp;9.15</a>) header fields. Although the value describes the content-coding, what is more important is that it indicates what decoding
    22682231         mechanism will be required to remove the encoding.
    22692232      </p>
    2270       <p id="rfc.section.6.4.p.4">compress<span id="rfc.iref.c.3"></span><span id="rfc.iref.c.4"></span> 
     2233      <p id="rfc.section.5.4.p.4">compress<span id="rfc.iref.c.3"></span><span id="rfc.iref.c.4"></span> 
    22712234      </p>
    22722235      <ul class="empty">
    2273          <li>See <a href="p1-messaging.html#compress.coding" title="Compress Coding">Section 4.2.1</a> of <a href="#Part1" id="rfc.xref.Part1.40"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
    2274          </li>
    2275       </ul>
    2276       <p id="rfc.section.6.4.p.5">deflate<span id="rfc.iref.d.2"></span><span id="rfc.iref.c.5"></span> 
     2236         <li>See <a href="p1-messaging.html#compress.coding" title="Compress Coding">Section 4.2.1</a> of <a href="#Part1" id="rfc.xref.Part1.38"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
     2237         </li>
     2238      </ul>
     2239      <p id="rfc.section.5.4.p.5">deflate<span id="rfc.iref.d.2"></span><span id="rfc.iref.c.5"></span> 
    22772240      </p>
    22782241      <ul class="empty">
    2279          <li>See <a href="p1-messaging.html#deflate.coding" title="Deflate Coding">Section 4.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.41"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
    2280          </li>
    2281       </ul>
    2282       <p id="rfc.section.6.4.p.6">gzip<span id="rfc.iref.g.26"></span><span id="rfc.iref.c.6"></span> 
     2242         <li>See <a href="p1-messaging.html#deflate.coding" title="Deflate Coding">Section 4.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.39"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
     2243         </li>
     2244      </ul>
     2245      <p id="rfc.section.5.4.p.6">gzip<span id="rfc.iref.g.26"></span><span id="rfc.iref.c.6"></span> 
    22832246      </p>
    22842247      <ul class="empty">
    2285          <li>See <a href="p1-messaging.html#gzip.coding" title="Gzip Coding">Section 4.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.42"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
    2286          </li>
    2287       </ul>
    2288       <h3 id="rfc.section.6.4.1"><a href="#rfc.section.6.4.1">6.4.1</a>&nbsp;<a id="content.coding.registry" href="#content.coding.registry">Content Coding Registry</a></h3>
    2289       <p id="rfc.section.6.4.1.p.1">The HTTP Content Coding Registry defines the name space for the content coding names.</p>
    2290       <p id="rfc.section.6.4.1.p.2">Registrations <em class="bcp14">MUST</em> include the following fields:
     2248         <li>See <a href="p1-messaging.html#gzip.coding" title="Gzip Coding">Section 4.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.40"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
     2249         </li>
     2250      </ul>
     2251      <h3 id="rfc.section.5.4.1"><a href="#rfc.section.5.4.1">5.4.1</a>&nbsp;<a id="content.coding.registry" href="#content.coding.registry">Content Coding Registry</a></h3>
     2252      <p id="rfc.section.5.4.1.p.1">The HTTP Content Coding Registry defines the name space for the content coding names.</p>
     2253      <p id="rfc.section.5.4.1.p.2">Registrations <em class="bcp14">MUST</em> include the following fields:
    22912254      </p>
    22922255      <ul>
    … …  
    22952258         <li>Pointer to specification text</li>
    22962259      </ul>
    2297       <p id="rfc.section.6.4.1.p.3">Names of content codings <em class="bcp14">MUST NOT</em> overlap with names of transfer codings (<a href="p1-messaging.html#transfer.codings" title="Transfer Codings">Section 4</a> of <a href="#Part1" id="rfc.xref.Part1.43"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>), unless the encoding transformation is identical (as is the case for the compression codings defined in <a href="p1-messaging.html#compression.codings" title="Compression Codings">Section 4.2</a> of <a href="#Part1" id="rfc.xref.Part1.44"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).
    2298       </p>
    2299       <p id="rfc.section.6.4.1.p.4">Values to be added to this name space require IETF Review (see <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a> of <a href="#RFC5226" id="rfc.xref.RFC5226.3"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>), and <em class="bcp14">MUST</em> conform to the purpose of content coding defined in this section.
    2300       </p>
    2301       <p id="rfc.section.6.4.1.p.5">The registry itself is maintained at &lt;<a href="http://www.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http-parameters</a>&gt;.
    2302       </p>
    2303       <h2 id="rfc.section.6.5"><a href="#rfc.section.6.5">6.5</a>&nbsp;<a id="media.types" href="#media.types">Media Types</a></h2>
    2304       <p id="rfc.section.6.5.p.1">HTTP uses Internet Media Types <a href="#RFC2046" id="rfc.xref.RFC2046.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a> in the Content-Type (<a href="#header.content-type" id="rfc.xref.header.content-type.3" title="Content-Type">Section&nbsp;10.18</a>) and Accept (<a href="#header.accept" id="rfc.xref.header.accept.2" title="Accept">Section&nbsp;10.11</a>) header fields in order to provide open and extensible data typing and type negotiation.
     2260      <p id="rfc.section.5.4.1.p.3">Names of content codings <em class="bcp14">MUST NOT</em> overlap with names of transfer codings (<a href="p1-messaging.html#transfer.codings" title="Transfer Codings">Section 4</a> of <a href="#Part1" id="rfc.xref.Part1.41"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>), unless the encoding transformation is identical (as is the case for the compression codings defined in <a href="p1-messaging.html#compression.codings" title="Compression Codings">Section 4.2</a> of <a href="#Part1" id="rfc.xref.Part1.42"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).
     2261      </p>
     2262      <p id="rfc.section.5.4.1.p.4">Values to be added to this name space require IETF Review (see <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a> of <a href="#RFC5226" id="rfc.xref.RFC5226.3"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>), and <em class="bcp14">MUST</em> conform to the purpose of content coding defined in this section.
     2263      </p>
     2264      <p id="rfc.section.5.4.1.p.5">The registry itself is maintained at &lt;<a href="http://www.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http-parameters</a>&gt;.
     2265      </p>
     2266      <h2 id="rfc.section.5.5"><a href="#rfc.section.5.5">5.5</a>&nbsp;<a id="media.types" href="#media.types">Media Types</a></h2>
     2267      <p id="rfc.section.5.5.p.1">HTTP uses Internet Media Types <a href="#RFC2046" id="rfc.xref.RFC2046.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a> in the Content-Type (<a href="#header.content-type" id="rfc.xref.header.content-type.3" title="Content-Type">Section&nbsp;9.18</a>) and Accept (<a href="#header.accept" id="rfc.xref.header.accept.2" title="Accept">Section&nbsp;9.11</a>) header fields in order to provide open and extensible data typing and type negotiation.
    23052268      </p>
    23062269      <div id="rfc.figure.u.20"></div><pre class="inline"><span id="rfc.iref.g.27"></span><span id="rfc.iref.g.28"></span><span id="rfc.iref.g.29"></span>  <a href="#media.types" class="smpl">media-type</a> = <a href="#media.types" class="smpl">type</a> "/" <a href="#media.types" class="smpl">subtype</a> *( <a href="#core.rules" class="smpl">OWS</a> ";" <a href="#core.rules" class="smpl">OWS</a> <a href="#rule.parameter" class="smpl">parameter</a> )
    … …  
    23082271  <a href="#media.types" class="smpl">subtype</a>    = <a href="#core.rules" class="smpl">token</a>
    23092272</pre><div id="rule.parameter">
    2310          <p id="rfc.section.6.5.p.3">      The type/subtype <em class="bcp14">MAY</em> be followed by parameters in the form of attribute/value pairs.
     2273         <p id="rfc.section.5.5.p.3">      The type/subtype <em class="bcp14">MAY</em> be followed by parameters in the form of attribute/value pairs.
    23112274         </p>
    23122275      </div>
    … …  
    23142277  <a href="#rule.parameter" class="smpl">attribute</a>      = <a href="#core.rules" class="smpl">token</a>
    23152278  <a href="#rule.parameter" class="smpl">value</a>          = <a href="#core.rules" class="smpl">word</a>
    2316 </pre><p id="rfc.section.6.5.p.5">The type, subtype, and parameter attribute names are case-insensitive. Parameter values might or might not be case-sensitive,
     2279</pre><p id="rfc.section.5.5.p.5">The type, subtype, and parameter attribute names are case-insensitive. Parameter values might or might not be case-sensitive,
    23172280         depending on the semantics of the parameter name. The presence or absence of a parameter might be significant to the processing
    23182281         of a media-type, depending on its definition within the media type registry.
    23192282      </p>
    2320       <p id="rfc.section.6.5.p.6">A parameter value that matches the <a href="#core.rules" class="smpl">token</a> production can be transmitted as either a token or within a quoted-string. The quoted and unquoted values are equivalent.
    2321       </p>
    2322       <p id="rfc.section.6.5.p.7">Note that some older HTTP applications do not recognize media type parameters. When sending data to older HTTP applications,
     2283      <p id="rfc.section.5.5.p.6">A parameter value that matches the <a href="#core.rules" class="smpl">token</a> production can be transmitted as either a token or within a quoted-string. The quoted and unquoted values are equivalent.
     2284      </p>
     2285      <p id="rfc.section.5.5.p.7">Note that some older HTTP applications do not recognize media type parameters. When sending data to older HTTP applications,
    23232286         implementations <em class="bcp14">SHOULD</em> only use media type parameters when they are required by that type/subtype definition.
    23242287      </p>
    2325       <p id="rfc.section.6.5.p.8">Media-type values are registered with the Internet Assigned Number Authority (IANA). The media type registration process is
     2288      <p id="rfc.section.5.5.p.8">Media-type values are registered with the Internet Assigned Number Authority (IANA). The media type registration process is
    23262289         outlined in <a href="#RFC4288" id="rfc.xref.RFC4288.1"><cite title="Media Type Specifications and Registration Procedures">[RFC4288]</cite></a>. Use of non-registered media types is discouraged.
    23272290      </p>
    2328       <h3 id="rfc.section.6.5.1"><a href="#rfc.section.6.5.1">6.5.1</a>&nbsp;<a id="canonicalization.and.text.defaults" href="#canonicalization.and.text.defaults">Canonicalization and Text Defaults</a></h3>
    2329       <p id="rfc.section.6.5.1.p.1">Internet media types are registered with a canonical form. A representation transferred via HTTP messages <em class="bcp14">MUST</em> be in the appropriate canonical form prior to its transmission except for "text" types, as defined in the next paragraph.
    2330       </p>
    2331       <p id="rfc.section.6.5.1.p.2">When in canonical form, media subtypes of the "text" type use CRLF as the text line break. HTTP relaxes this requirement and
     2291      <h3 id="rfc.section.5.5.1"><a href="#rfc.section.5.5.1">5.5.1</a>&nbsp;<a id="canonicalization.and.text.defaults" href="#canonicalization.and.text.defaults">Canonicalization and Text Defaults</a></h3>
     2292      <p id="rfc.section.5.5.1.p.1">Internet media types are registered with a canonical form. A representation transferred via HTTP messages <em class="bcp14">MUST</em> be in the appropriate canonical form prior to its transmission except for "text" types, as defined in the next paragraph.
     2293      </p>
     2294      <p id="rfc.section.5.5.1.p.2">When in canonical form, media subtypes of the "text" type use CRLF as the text line break. HTTP relaxes this requirement and
    23322295         allows the transport of text media with plain CR or LF alone representing a line break when it is done consistently for an
    23332296         entire representation. HTTP applications <em class="bcp14">MUST</em> accept CRLF, bare CR, and bare LF as indicating a line break in text media received via HTTP. In addition, if the text is
    … …  
    23372300         body; a bare CR or LF <em class="bcp14">MUST NOT</em> be substituted for CRLF within any of the HTTP control structures (such as header fields and multipart boundaries).
    23382301      </p>
    2339       <p id="rfc.section.6.5.1.p.3">If a representation is encoded with a content-coding, the underlying data <em class="bcp14">MUST</em> be in a form defined above prior to being encoded.
    2340       </p>
    2341       <h3 id="rfc.section.6.5.2"><a href="#rfc.section.6.5.2">6.5.2</a>&nbsp;<a id="multipart.types" href="#multipart.types">Multipart Types</a></h3>
    2342       <p id="rfc.section.6.5.2.p.1">MIME provides for a number of "multipart" types — encapsulations of one or more representations within a single message body.
     2302      <p id="rfc.section.5.5.1.p.3">If a representation is encoded with a content-coding, the underlying data <em class="bcp14">MUST</em> be in a form defined above prior to being encoded.
     2303      </p>
     2304      <h3 id="rfc.section.5.5.2"><a href="#rfc.section.5.5.2">5.5.2</a>&nbsp;<a id="multipart.types" href="#multipart.types">Multipart Types</a></h3>
     2305      <p id="rfc.section.5.5.2.p.1">MIME provides for a number of "multipart" types — encapsulations of one or more representations within a single message body.
    23432306         All multipart types share a common syntax, as defined in <a href="http://tools.ietf.org/html/rfc2046#section-5.1.1">Section 5.1.1</a> of <a href="#RFC2046" id="rfc.xref.RFC2046.2"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a>, and <em class="bcp14">MUST</em> include a boundary parameter as part of the media type value. The message body is itself a protocol element and <em class="bcp14">MUST</em> therefore use only CRLF to represent line breaks between body-parts.
    23442307      </p>
    2345       <p id="rfc.section.6.5.2.p.2">In general, HTTP treats a multipart message body no differently than any other media type: strictly as payload. HTTP does
     2308      <p id="rfc.section.5.5.2.p.2">In general, HTTP treats a multipart message body no differently than any other media type: strictly as payload. HTTP does
    23462309         not use the multipart boundary as an indicator of message body length.  In all other respects, an HTTP user agent <em class="bcp14">SHOULD</em> follow the same or similar behavior as a MIME user agent would upon receipt of a multipart type. The MIME header fields within
    23472310         each body-part of a multipart message body do not have any significance to HTTP beyond that defined by their MIME semantics.
    23482311      </p>
    2349       <p id="rfc.section.6.5.2.p.3">If an application receives an unrecognized multipart subtype, the application <em class="bcp14">MUST</em> treat it as being equivalent to "multipart/mixed".
    2350       </p>
    2351       <div class="note" id="rfc.section.6.5.2.p.4">
     2312      <p id="rfc.section.5.5.2.p.3">If an application receives an unrecognized multipart subtype, the application <em class="bcp14">MUST</em> treat it as being equivalent to "multipart/mixed".
     2313      </p>
     2314      <div class="note" id="rfc.section.5.5.2.p.4">
    23522315         <p> <b>Note:</b> The "multipart/form-data" type has been specifically defined for carrying form data suitable for processing via the POST request
    23532316            method, as described in <a href="#RFC2388" id="rfc.xref.RFC2388.1"><cite title="Returning Values from Forms: multipart/form-data">[RFC2388]</cite></a>.
    23542317         </p>
    23552318      </div>
    2356       <h2 id="rfc.section.6.6"><a href="#rfc.section.6.6">6.6</a>&nbsp;<a id="language.tags" href="#language.tags">Language Tags</a></h2>
    2357       <p id="rfc.section.6.6.p.1">A language tag, as defined in <a href="#RFC5646" id="rfc.xref.RFC5646.1"><cite title="Tags for Identifying Languages">[RFC5646]</cite></a>, identifies a natural language spoken, written, or otherwise conveyed by human beings for communication of information to
     2319      <h2 id="rfc.section.5.6"><a href="#rfc.section.5.6">5.6</a>&nbsp;<a id="language.tags" href="#language.tags">Language Tags</a></h2>
     2320      <p id="rfc.section.5.6.p.1">A language tag, as defined in <a href="#RFC5646" id="rfc.xref.RFC5646.1"><cite title="Tags for Identifying Languages">[RFC5646]</cite></a>, identifies a natural language spoken, written, or otherwise conveyed by human beings for communication of information to
    23582321         other human beings. Computer languages are explicitly excluded. HTTP uses language tags within the Accept-Language and Content-Language
    23592322         fields.
    23602323      </p>
    2361       <p id="rfc.section.6.6.p.2">In summary, a language tag is composed of one or more parts: A primary language subtag followed by a possibly empty series
     2324      <p id="rfc.section.5.6.p.2">In summary, a language tag is composed of one or more parts: A primary language subtag followed by a possibly empty series
    23622325         of subtags:
    23632326      </p>
    23642327      <div id="rfc.figure.u.22"></div><pre class="inline"><span id="rfc.iref.g.33"></span>  <a href="#language.tags" class="smpl">language-tag</a> = &lt;Language-Tag, defined in <a href="#RFC5646" id="rfc.xref.RFC5646.2"><cite title="Tags for Identifying Languages">[RFC5646]</cite></a>, <a href="http://tools.ietf.org/html/rfc5646#section-2.1">Section 2.1</a>&gt;
    2365 </pre><p id="rfc.section.6.6.p.4">White space is not allowed within the tag and all tags are case-insensitive. The name space of language subtags is administered
     2328</pre><p id="rfc.section.5.6.p.4">White space is not allowed within the tag and all tags are case-insensitive. The name space of language subtags is administered
    23662329         by the IANA (see &lt;<a href="http://www.iana.org/assignments/language-subtag-registry">http://www.iana.org/assignments/language-subtag-registry</a>&gt;).
    23672330      </p>
    23682331      <div id="rfc.figure.u.23"></div>
    23692332      <p>Example tags include:</p>  <pre class="text">  en, en-US, es-419, az-Arab, x-pig-latin, man-Nkoo-GN
    2370 </pre> <p id="rfc.section.6.6.p.6">See <a href="#RFC5646" id="rfc.xref.RFC5646.3"><cite title="Tags for Identifying Languages">[RFC5646]</cite></a> for further information.
    2371       </p>
    2372       <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a id="payload" href="#payload">Payload</a></h1>
    2373       <p id="rfc.section.7.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,
     2333</pre> <p id="rfc.section.5.6.p.6">See <a href="#RFC5646" id="rfc.xref.RFC5646.3"><cite title="Tags for Identifying Languages">[RFC5646]</cite></a> for further information.
     2334      </p>
     2335      <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="payload" href="#payload">Payload</a></h1>
     2336      <p id="rfc.section.6.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,
    23742337         in the form of header fields, and data, in the form of the sequence of octets in the message body after any transfer-coding
    23752338         has been decoded.
    23762339      </p>
    23772340      <div id="rfc.iref.p.3"></div>
    2378       <p id="rfc.section.7.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
     2341      <p id="rfc.section.6.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
    23792342         because some messages contain only the associated representation's header fields (e.g., responses to HEAD) or only some part(s)
    23802343         of the representation (e.g., the 206 status code).
    23812344      </p>
    2382       <h2 id="rfc.section.7.1"><a href="#rfc.section.7.1">7.1</a>&nbsp;<a id="payload.header.fields" href="#payload.header.fields">Payload Header Fields</a></h2>
    2383       <p id="rfc.section.7.1.p.1">HTTP header fields that specifically define the payload, rather than the associated representation, are referred to as "payload
     2345      <h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a>&nbsp;<a id="payload.header.fields" href="#payload.header.fields">Payload Header Fields</a></h2>
     2346      <p id="rfc.section.6.1.p.1">HTTP header fields that specifically define the payload, rather than the associated representation, are referred to as "payload
    23842347         header fields". The following payload header fields are defined by HTTP/1.1:
    23852348      </p>
    … …  
    23952358               <tr>
    23962359                  <td class="left">Content-Length</td>
    2397                   <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.45"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a></td>
     2360                  <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.43"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a></td>
    23982361               </tr>
    23992362               <tr>
    … …  
    24042367         </table>
    24052368      </div>
    2406       <h2 id="rfc.section.7.2"><a href="#rfc.section.7.2">7.2</a>&nbsp;<a id="payload.body" href="#payload.body">Payload Body</a></h2>
    2407       <p id="rfc.section.7.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.46"><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
     2369      <h2 id="rfc.section.6.2"><a href="#rfc.section.6.2">6.2</a>&nbsp;<a id="payload.body" href="#payload.body">Payload Body</a></h2>
     2370      <p id="rfc.section.6.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.44"><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
    24082371         safe and proper transfer of the message.
    24092372      </p>
    24102373      <div id="rfc.iref.r.1"></div>
    2411       <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a id="representation-TODO" href="#representation-TODO">Representation</a></h1>
    2412       <p id="rfc.section.8.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
     2374      <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;Representation
     2375      </h1>
     2376      <p id="rfc.section.7.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
    24132377         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
    24142378         at some point in the future (e.g., in a PUT request).
    24152379      </p>
    2416       <p id="rfc.section.8.p.2">Most, but not all, representations transferred via HTTP are intended to be a representation of the target resource (the resource
     2380      <p id="rfc.section.7.p.2">Most, but not all, representations transferred via HTTP are intended to be a representation of the target resource (the resource
    24172381         identified by the effective request URI). The precise semantics of a representation are determined by the type of message
    24182382         (request or response), the request method, the response status code, and the representation metadata. For example, the above
    … …  
    24232387         next steps are suggested for resolving it.
    24242388      </p>
    2425       <h2 id="rfc.section.8.1"><a href="#rfc.section.8.1">8.1</a>&nbsp;<a id="representation.header.fields" href="#representation.header.fields">Representation Header Fields</a></h2>
    2426       <p id="rfc.section.8.1.p.1">Representation header fields define metadata about the representation data enclosed in the message body or, if no message
     2389      <p id="rfc.section.7.p.3">Request and Response messages <em class="bcp14">MAY</em> transfer a representation if not otherwise restricted by the request method or response status code. A representation consists
     2390         of metadata (representation header fields) and data (representation body). When a complete or partial representation is enclosed
     2391         in an HTTP message, it is referred to as the payload of the message.<span class="comment" id="rfc.comment.2">[<a href="#rfc.comment.2" class="smpl">rfc.comment.2</a>: MOVEDFIXME]</span>
     2392      </p>
     2393      <p id="rfc.section.7.p.4">A representation 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.45"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. The representation body is obtained from the message body by decoding any Transfer-Encoding that might have been applied
     2394         to ensure safe and proper transfer of the message.<span class="comment" id="rfc.comment.3">[<a href="#rfc.comment.3" class="smpl">rfc.comment.3</a>: MOVEDFIXME]</span>
     2395      </p>
     2396      <h2 id="rfc.section.7.1"><a href="#rfc.section.7.1">7.1</a>&nbsp;<a id="identifying.response.associated.with.representation" href="#identifying.response.associated.with.representation">Identifying the Resource Associated with a Representation</a></h2>
     2397      <p id="rfc.section.7.1.p.1">It is sometimes necessary to determine an identifier for the resource associated with a representation.</p>
     2398      <p id="rfc.section.7.1.p.2">An HTTP request representation, when present, is always associated with an anonymous (i.e., unidentified) resource.</p>
     2399      <p id="rfc.section.7.1.p.3">In the common case, an HTTP response is a representation of the target resource (see <a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.46"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). However, this is not always the case. To determine the URI of the resource a response is associated with, the following
     2400         rules are used (with the first applicable one being selected):
     2401      </p>
     2402      <ol>
     2403         <li>If the response status code is 200 or 203 and the request method was GET, the response payload is a representation of the
     2404            target resource.
     2405         </li>
     2406         <li>If the response status code is 204, 206, or 304 and the request method was GET or HEAD, the response payload is a partial
     2407            representation of the target resource.
     2408         </li>
     2409         <li>If the response has a Content-Location header field, and that URI is the same as the effective request URI, the response payload
     2410            is a representation of the target resource.
     2411         </li>
     2412         <li>If the response has a Content-Location header field, and that URI is not the same as the effective request URI, then the response
     2413            asserts that its payload is a representation of the resource identified by the Content-Location URI. However, such an assertion
     2414            cannot be trusted unless it can be verified by other means (not defined by HTTP).
     2415         </li>
     2416         <li>Otherwise, the response is a representation of an anonymous (i.e., unidentified) resource.</li>
     2417      </ol>
     2418      <p id="rfc.section.7.1.p.5"> <span class="comment" id="TODO-req-uri">[<a href="#TODO-req-uri" class="smpl">TODO-req-uri</a>: The comparison function is going to have to be defined somewhere, because we already need to compare URIs for things like
     2419            cache invalidation.]</span>
     2420      </p>
     2421      <h2 id="rfc.section.7.2"><a href="#rfc.section.7.2">7.2</a>&nbsp;<a id="representation.header.fields" href="#representation.header.fields">Representation Header Fields</a></h2>
     2422      <p id="rfc.section.7.2.p.1">Representation header fields define metadata about the representation data enclosed in the message body or, if no message
    24272423         body is present, about the representation that would have been transferred in a 200 response to a simultaneous GET request
    24282424         with the same effective request URI.
    24292425      </p>
    2430       <p id="rfc.section.8.1.p.2">The following header fields are defined as representation metadata:</p>
     2426      <p id="rfc.section.7.2.p.2">The following header fields are defined as representation metadata:</p>
    24312427      <div id="rfc.table.u.5">
    24322428         <table class="tt full left" cellpadding="3" cellspacing="0">
    … …  
    24402436               <tr>
    24412437                  <td class="left">Content-Encoding</td>
    2442                   <td class="left"><a href="#header.content-encoding" id="rfc.xref.header.content-encoding.2" title="Content-Encoding">Section&nbsp;10.15</a></td>
     2438                  <td class="left"><a href="#header.content-encoding" id="rfc.xref.header.content-encoding.2" title="Content-Encoding">Section&nbsp;9.15</a></td>
    24432439               </tr>
    24442440               <tr>
    24452441                  <td class="left">Content-Language</td>
    2446                   <td class="left"><a href="#header.content-language" id="rfc.xref.header.content-language.1" title="Content-Language">Section&nbsp;10.16</a></td>
     2442                  <td class="left"><a href="#header.content-language" id="rfc.xref.header.content-language.1" title="Content-Language">Section&nbsp;9.16</a></td>
    24472443               </tr>
    24482444               <tr>
    24492445                  <td class="left">Content-Location</td>
    2450                   <td class="left"><a href="#header.content-location" id="rfc.xref.header.content-location.2" title="Content-Location">Section&nbsp;10.17</a></td>
     2446                  <td class="left"><a href="#header.content-location" id="rfc.xref.header.content-location.2" title="Content-Location">Section&nbsp;9.17</a></td>
    24512447               </tr>
    24522448               <tr>
    24532449                  <td class="left">Content-Type</td>
    2454                   <td class="left"><a href="#header.content-type" id="rfc.xref.header.content-type.4" title="Content-Type">Section&nbsp;10.18</a></td>
     2450                  <td class="left"><a href="#header.content-type" id="rfc.xref.header.content-type.4" title="Content-Type">Section&nbsp;9.18</a></td>
    24552451               </tr>
    24562452               <tr>
    … …  
    24612457         </table>
    24622458      </div>
    2463       <p id="rfc.section.8.1.p.3">Additional header fields define metadata about the selected representation, which might differ from the representation included
     2459      <p id="rfc.section.7.2.p.3">Additional header fields define metadata about the selected representation, which might differ from the representation included
    24642460         in the message for responses to some state-changing methods. The following header fields are defined as selected representation
    24652461         metadata:
    … …  
    24852481         </table>
    24862482      </div>
    2487       <h2 id="rfc.section.8.2"><a href="#rfc.section.8.2">8.2</a>&nbsp;<a id="representation.data" href="#representation.data">Representation Data</a></h2>
    2488       <p id="rfc.section.8.2.p.1">The representation body associated with an HTTP message is either provided as the payload body of the message or referred
     2483      <h2 id="rfc.section.7.3"><a href="#rfc.section.7.3">7.3</a>&nbsp;<a id="representation.data" href="#representation.data">Representation Data</a></h2>
     2484      <p id="rfc.section.7.3.p.1">The representation body associated with an HTTP message is either provided as the payload body of the message or referred
    24892485         to by the message semantics and the effective request URI. The representation data is in a format and encoding defined by
    24902486         the representation metadata header fields.
    24912487      </p>
    2492       <p id="rfc.section.8.2.p.2">The data type of the representation data is determined via the header fields Content-Type and Content-Encoding. These define
     2488      <p id="rfc.section.7.3.p.2">The data type of the representation data is determined via the header fields Content-Type and Content-Encoding. These define
    24932489         a two-layer, ordered encoding model:
    24942490      </p>
    24952491      <div id="rfc.figure.u.24"></div><pre class="text">  representation-data := Content-Encoding( Content-Type( bits ) )
    2496 </pre><p id="rfc.section.8.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
     2492</pre><p id="rfc.section.7.3.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
    24972493         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
    24982494         to the sender. If the Content-Type header field is not present, it indicates that the sender does not know the media type
    24992495         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.
    25002496      </p>
    2501       <p id="rfc.section.8.2.p.5">In practice, resource owners do not always properly configure their origin server to provide the correct Content-Type for
     2497      <p id="rfc.section.7.3.p.5">In practice, resource owners do not always properly configure their origin server to provide the correct Content-Type for
    25022498         a given representation, with the result that some clients will examine a response body's content and override the specified
    25032499         type. Clients that do so risk drawing incorrect conclusions, which might expose additional security risks (e.g., "privilege
    … …  
    25062502         such "content sniffing" when it is used.
    25072503      </p>
    2508       <p id="rfc.section.8.2.p.6">Content-Encoding is used to indicate any additional content codings applied to the data, usually for the purpose of data compression,
     2504      <p id="rfc.section.7.3.p.6">Content-Encoding is used to indicate any additional content codings applied to the data, usually for the purpose of data compression,
    25092505         that are a property of the representation. If Content-Encoding is not present, then there is no additional encoding beyond
    25102506         that defined by the Content-Type.
    25112507      </p>
    2512       <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a>&nbsp;<a id="content.negotiation" href="#content.negotiation">Content Negotiation</a></h1>
    2513       <p id="rfc.section.9.p.1">HTTP responses include a representation which contains information for interpretation, whether by a human user or for further
     2508      <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a id="content.negotiation" href="#content.negotiation">Content Negotiation</a></h1>
     2509      <p id="rfc.section.8.p.1">HTTP responses include a representation which contains information for interpretation, whether by a human user or for further
    25142510         processing. Often, the server has different ways of representing the same information; for example, in different formats,
    25152511         languages, or using different character encodings.
    25162512      </p>
    2517       <p id="rfc.section.9.p.2">HTTP clients and their users might have different or variable capabilities, characteristics or preferences which would influence
     2513      <p id="rfc.section.8.p.2">HTTP clients and their users might have different or variable capabilities, characteristics or preferences which would influence
    25182514         which representation, among those available from the server, would be best for the server to deliver. For this reason, HTTP
    25192515         provides mechanisms for "content negotiation" — a process of allowing selection of a representation of a given resource, when
    25202516         more than one is available.
    25212517      </p>
    2522       <p id="rfc.section.9.p.3">This specification defines two patterns of content negotiation; "server-driven", where the server selects the representation
     2518      <p id="rfc.section.8.p.3">This specification defines two patterns of content negotiation; "server-driven", where the server selects the representation
    25232519         based upon the client's stated preferences, and "agent-driven" negotiation, where the server provides a list of representations
    25242520         for the client to choose from, based upon their metadata. In addition, there are other patterns: some applications use an
    … …  
    25262522         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.
    25272523      </p>
    2528       <p id="rfc.section.9.p.4">These patterns are all widely used, and have trade-offs in applicability and practicality. In particular, when the number
     2524      <p id="rfc.section.8.p.4">These patterns are all widely used, and have trade-offs in applicability and practicality. In particular, when the number
    25292525         of preferences or capabilities to be expressed by a client are large (such as when many different formats are supported by
    25302526         a user-agent), server-driven negotiation becomes unwieldy, and might not be appropriate. Conversely, when the number of representations
    25312527         to choose from is very large, agent-driven negotiation might not be appropriate.
    25322528      </p>
    2533       <p id="rfc.section.9.p.5">Note that in all cases, the supplier of representations has the responsibility for determining which representations might
     2529      <p id="rfc.section.8.p.5">Note that in all cases, the supplier of representations has the responsibility for determining which representations might
    25342530         be considered to be the "same information".
    25352531      </p>
    2536       <h2 id="rfc.section.9.1"><a href="#rfc.section.9.1">9.1</a>&nbsp;<a id="server-driven.negotiation" href="#server-driven.negotiation">Server-driven Negotiation</a></h2>
    2537       <p id="rfc.section.9.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
     2532      <h2 id="rfc.section.8.1"><a href="#rfc.section.8.1">8.1</a>&nbsp;<a id="server-driven.negotiation" href="#server-driven.negotiation">Server-driven Negotiation</a></h2>
     2533      <p id="rfc.section.8.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
    25382534         negotiation. Selection is based on the available representations of the response (the dimensions over which it can vary; e.g.,
    25392535         language, content-coding, etc.) and the contents of particular header fields in the request message or on other information
    25402536         pertaining to the request (such as the network address of the client).
    25412537      </p>
    2542       <p id="rfc.section.9.1.p.2">Server-driven negotiation is advantageous when the algorithm for selecting from among the available representations is difficult
     2538      <p id="rfc.section.8.1.p.2">Server-driven negotiation is advantageous when the algorithm for selecting from among the available representations is difficult
    25432539         to describe to the user agent, or when the server desires to send its "best guess" to the client along with the first response
    25442540         (hoping to avoid the round-trip delay of a subsequent request if the "best guess" is good enough for the user). In order to
    25452541         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.
    25462542      </p>
    2547       <p id="rfc.section.9.1.p.3">Server-driven negotiation has disadvantages: </p>
     2543      <p id="rfc.section.8.1.p.3">Server-driven negotiation has disadvantages: </p>
    25482544      <ol>
    25492545         <li>It is impossible for the server to accurately determine what might be "best" for any given user, since that would require
    … …  
    25572553         <li>It might limit a public cache's ability to use the same response for multiple user's requests.</li>
    25582554      </ol>
    2559       <p id="rfc.section.9.1.p.4">Server-driven negotiation allows the user agent to specify its preferences, but it cannot expect responses to always honor
     2555      <p id="rfc.section.8.1.p.4">Server-driven negotiation allows the user agent to specify its preferences, but it cannot expect responses to always honor
    25602556         them. For example, the origin server might not implement server-driven negotiation, or it might decide that sending a response
    25612557         that doesn't conform to them is better than sending a 406 (Not Acceptable) response.
    25622558      </p>
    2563       <p id="rfc.section.9.1.p.5">Many of the mechanisms for expressing preferences use quality values to declare relative preference. See qvalue; for more
     2559      <p id="rfc.section.8.1.p.5">Many of the mechanisms for expressing preferences use quality values to declare relative preference. See qvalue; for more
    25642560         information.
    25652561      </p>
    2566       <p id="rfc.section.9.1.p.6">HTTP/1.1 includes the following header fields for enabling server-driven negotiation through description of user agent capabilities
    2567          and user preferences: Accept (<a href="#header.accept" id="rfc.xref.header.accept.3" title="Accept">Section&nbsp;10.11</a>), Accept-Charset (<a href="#header.accept-charset" id="rfc.xref.header.accept-charset.2" title="Accept-Charset">Section&nbsp;10.12</a>), Accept-Encoding (<a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.3" title="Accept-Encoding">Section&nbsp;10.13</a>), Accept-Language (<a href="#header.accept-language" id="rfc.xref.header.accept-language.2" title="Accept-Language">Section&nbsp;10.14</a>), and User-Agent (<a href="#header.user-agent" id="rfc.xref.header.user-agent.2" title="User-Agent">Section&nbsp;10.10</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
     2562      <p id="rfc.section.8.1.p.6">HTTP/1.1 includes the following header fields for enabling server-driven negotiation through description of user agent capabilities
     2563         and user preferences: Accept (<a href="#header.accept" id="rfc.xref.header.accept.3" title="Accept">Section&nbsp;9.11</a>), Accept-Charset (<a href="#header.accept-charset" id="rfc.xref.header.accept-charset.2" title="Accept-Charset">Section&nbsp;9.12</a>), Accept-Encoding (<a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.3" title="Accept-Encoding">Section&nbsp;9.13</a>), Accept-Language (<a href="#header.accept-language" id="rfc.xref.header.accept-language.2" title="Accept-Language">Section&nbsp;9.14</a>), and User-Agent (<a href="#header.user-agent" id="rfc.xref.header.user-agent.2" title="User-Agent">Section&nbsp;9.10</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
    25682564         within extension header fields not defined by this specification.
    25692565      </p>
    2570       <div class="note" id="rfc.section.9.1.p.7">
     2566      <div class="note" id="rfc.section.8.1.p.7">
    25712567         <p> <b>Note:</b> In practice, User-Agent based negotiation is fragile, because new clients might not be recognized.
    25722568         </p>
    25732569      </div>
    2574       <p id="rfc.section.9.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.
    2575       </p>
    2576       <h2 id="rfc.section.9.2"><a href="#rfc.section.9.2">9.2</a>&nbsp;<a id="agent-driven.negotiation" href="#agent-driven.negotiation">Agent-driven Negotiation</a></h2>
    2577       <p id="rfc.section.9.2.p.1">With agent-driven negotiation, selection of the best representation for a response is performed by the user agent after receiving
     2570      <p id="rfc.section.8.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.
     2571      </p>
     2572      <h2 id="rfc.section.8.2"><a href="#rfc.section.8.2">8.2</a>&nbsp;<a id="agent-driven.negotiation" href="#agent-driven.negotiation">Agent-driven Negotiation</a></h2>
     2573      <p id="rfc.section.8.2.p.1">With agent-driven negotiation, selection of the best representation for a response is performed by the user agent after receiving
    25782574         an initial response from the origin server. Selection is based on a list of the available representations of the response
    25792575         included within the header fields or body of the initial response, with each representation identified by its own URI. Selection
    … …  
    25812577         user selecting from a generated (possibly hypertext) menu.
    25822578      </p>
    2583       <p id="rfc.section.9.2.p.2">Agent-driven negotiation is advantageous when the response would vary over commonly-used dimensions (such as type, language,
     2579      <p id="rfc.section.8.2.p.2">Agent-driven negotiation is advantageous when the response would vary over commonly-used dimensions (such as type, language,
    25842580         or encoding), when the origin server is unable to determine a user agent's capabilities from examining the request, and generally
    25852581         when public caches are used to distribute server load and reduce network usage.
    25862582      </p>
    2587       <p id="rfc.section.9.2.p.3">Agent-driven negotiation suffers from the disadvantage of needing a second request to obtain the best alternate representation.
     2583      <p id="rfc.section.8.2.p.3">Agent-driven negotiation suffers from the disadvantage of needing a second request to obtain the best alternate representation.
    25882584         This second request is only efficient when caching is used. In addition, this specification does not define any mechanism
    25892585         for supporting automatic selection, though it also does not prevent any such mechanism from being developed as an extension
    25902586         and used within HTTP/1.1.
    25912587      </p>
    2592       <p id="rfc.section.9.2.p.4">This specification defines the 300 (Multiple Choices) and 406 (Not Acceptable) status codes for enabling agent-driven negotiation
     2588      <p id="rfc.section.8.2.p.4">This specification defines the 300 (Multiple Choices) and 406 (Not Acceptable) status codes for enabling agent-driven negotiation
    25932589         when the server is unwilling or unable to provide a varying response using server-driven negotiation.
    25942590      </p>
    2595       <h1 id="rfc.section.10"><a href="#rfc.section.10">10.</a>&nbsp;<a id="header.field.definitions" href="#header.field.definitions">Header Field Definitions</a></h1>
    2596       <p id="rfc.section.10.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields related to request and response semantics, and to
     2591      <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a>&nbsp;<a id="header.field.definitions" href="#header.field.definitions">Header Field Definitions</a></h1>
     2592      <p id="rfc.section.9.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields related to request and response semantics, and to
    25972593         the payload of messages.
    25982594      </p>
    25992595      <div id="rfc.iref.a.1"></div>
    26002596      <div id="rfc.iref.h.2"></div>
    2601       <h2 id="rfc.section.10.1"><a href="#rfc.section.10.1">10.1</a>&nbsp;<a id="header.allow" href="#header.allow">Allow</a></h2>
    2602       <p id="rfc.section.10.1.p.1">The "Allow" header field lists the set of methods advertised as supported by the target resource. The purpose of this field
     2597      <h2 id="rfc.section.9.1"><a href="#rfc.section.9.1">9.1</a>&nbsp;<a id="header.allow" href="#header.allow">Allow</a></h2>
     2598      <p id="rfc.section.9.1.p.1">The "Allow" header field lists the set of methods advertised as supported by the target resource. The purpose of this field
    26032599         is strictly to inform the recipient of valid request methods associated with the resource.
    26042600      </p>
    26052601      <div id="rfc.figure.u.25"></div><pre class="inline"><span id="rfc.iref.g.34"></span>  <a href="#header.allow" class="smpl">Allow</a> = #<a href="#methods" class="smpl">method</a>
    2606 </pre><p id="rfc.section.10.1.p.3">Example of use:</p>
     2602</pre><p id="rfc.section.9.1.p.3">Example of use:</p>
    26072603      <div id="rfc.figure.u.26"></div><pre class="text">  Allow: GET, HEAD, PUT
    2608 </pre><p id="rfc.section.10.1.p.5">The actual set of allowed methods is defined by the origin server at the time of each request.</p>
    2609       <p id="rfc.section.10.1.p.6">A proxy <em class="bcp14">MUST NOT</em> modify the Allow header field — it does not need to understand all the methods specified in order to handle them according
     2604</pre><p id="rfc.section.9.1.p.5">The actual set of allowed methods is defined by the origin server at the time of each request.</p>
     2605      <p id="rfc.section.9.1.p.6">A proxy <em class="bcp14">MUST NOT</em> modify the Allow header field — it does not need to understand all the methods specified in order to handle them according
    26102606         to the generic message handling rules.
    26112607      </p>
    26122608      <div id="rfc.iref.d.3"></div>
    26132609      <div id="rfc.iref.h.3"></div>
    2614       <h2 id="rfc.section.10.2"><a href="#rfc.section.10.2">10.2</a>&nbsp;<a id="header.date" href="#header.date">Date</a></h2>
    2615       <p id="rfc.section.10.2.p.1">The "Date" header field represents the date and time at which the message was originated, having the same semantics as the
    2616          Origination Date Field (orig-date) defined in <a href="http://tools.ietf.org/html/rfc5322#section-3.6.1">Section 3.6.1</a> of <a href="#RFC5322" id="rfc.xref.RFC5322.2"><cite title="Internet Message Format">[RFC5322]</cite></a>. The field value is an HTTP-date, as defined in <a href="#http.date" title="Date/Time Formats">Section&nbsp;6.1</a>; it <em class="bcp14">MUST</em> be sent in rfc1123-date format.
     2610      <h2 id="rfc.section.9.2"><a href="#rfc.section.9.2">9.2</a>&nbsp;<a id="header.date" href="#header.date">Date</a></h2>
     2611      <p id="rfc.section.9.2.p.1">The "Date" header field represents the date and time at which the message was originated, having the same semantics as the
     2612         Origination Date Field (orig-date) defined in <a href="http://tools.ietf.org/html/rfc5322#section-3.6.1">Section 3.6.1</a> of <a href="#RFC5322" id="rfc.xref.RFC5322.2"><cite title="Internet Message Format">[RFC5322]</cite></a>. The field value is an HTTP-date, as defined in <a href="#http.date" title="Date/Time Formats">Section&nbsp;5.1</a>; it <em class="bcp14">MUST</em> be sent in rfc1123-date format.
    26172613      </p>
    26182614      <div id="rfc.figure.u.27"></div><pre class="inline"><span id="rfc.iref.g.35"></span>  <a href="#header.date" class="smpl">Date</a> = <a href="#http.date" class="smpl">HTTP-date</a>
    2619 </pre><p id="rfc.section.10.2.p.3">An example is</p>
     2615</pre><p id="rfc.section.9.2.p.3">An example is</p>
    26202616      <div id="rfc.figure.u.28"></div><pre class="text">  Date: Tue, 15 Nov 1994 08:12:31 GMT
    2621 </pre><p id="rfc.section.10.2.p.5">Origin servers <em class="bcp14">MUST</em> include a Date header field in all responses, except in these cases:
     2617</pre><p id="rfc.section.9.2.p.5">Origin servers <em class="bcp14">MUST</em> include a Date header field in all responses, except in these cases:
    26222618      </p>
    26232619      <ol>
    … …  
    26302626         </li>
    26312627      </ol>
    2632       <p id="rfc.section.10.2.p.6">A received message that does not have a Date header field <em class="bcp14">MUST</em> be assigned one by the recipient if the message will be cached by that recipient.
    2633       </p>
    2634       <p id="rfc.section.10.2.p.7">Clients can use the Date header field as well; in order to keep request messages small, they are advised not to include it
     2628      <p id="rfc.section.9.2.p.6">A received message that does not have a Date header field <em class="bcp14">MUST</em> be assigned one by the recipient if the message will be cached by that recipient.
     2629      </p>
     2630      <p id="rfc.section.9.2.p.7">Clients can use the Date header field as well; in order to keep request messages small, they are advised not to include it
    26352631         when it doesn't convey any useful information (as is usually the case for requests that do not contain a payload).
    26362632      </p>
    2637       <p id="rfc.section.10.2.p.8">The HTTP-date sent in a Date header field <em class="bcp14">SHOULD NOT</em> represent a date and time subsequent to the generation of the message. It <em class="bcp14">SHOULD</em> represent the best available approximation of the date and time of message generation, unless the implementation has no means
     2633      <p id="rfc.section.9.2.p.8">The HTTP-date sent in a Date header field <em class="bcp14">SHOULD NOT</em> represent a date and time subsequent to the generation of the message. It <em class="bcp14">SHOULD</em> represent the best available approximation of the date and time of message generation, unless the implementation has no means
    26382634         of generating a reasonably accurate date and time. In theory, the date ought to represent the moment just before the payload
    26392635         is generated. In practice, the date can be generated at any time during the message origination without affecting its semantic
    … …  
    26422638      <div id="rfc.iref.e.1"></div>
    26432639      <div id="rfc.iref.h.4"></div>
    2644       <h2 id="rfc.section.10.3"><a href="#rfc.section.10.3">10.3</a>&nbsp;<a id="header.expect" href="#header.expect">Expect</a></h2>
    2645       <p id="rfc.section.10.3.p.1">The "Expect" header field is used to indicate that particular server behaviors are required by the client.</p>
     2640      <h2 id="rfc.section.9.3"><a href="#rfc.section.9.3">9.3</a>&nbsp;<a id="header.expect" href="#header.expect">Expect</a></h2>
     2641      <p id="rfc.section.9.3.p.1">The "Expect" header field is used to indicate that particular server behaviors are required by the client.</p>
    26462642      <div id="rfc.figure.u.29"></div><pre class="inline"><span id="rfc.iref.g.36"></span><span id="rfc.iref.g.37"></span><span id="rfc.iref.g.38"></span><span id="rfc.iref.g.39"></span><span id="rfc.iref.g.40"></span>  <a href="#header.expect" class="smpl">Expect</a>       = 1#<a href="#header.expect" class="smpl">expectation</a>
    26472643 
    … …  
    26522648  <a href="#header.expect" class="smpl">expect-name</a>  = <a href="#core.rules" class="smpl">token</a>
    26532649  <a href="#header.expect" class="smpl">expect-value</a> = <a href="#core.rules" class="smpl">token</a> / <a href="#core.rules" class="smpl">quoted-string</a>
    2654 </pre><p id="rfc.section.10.3.p.3">If all received Expect header field(s) are syntactically valid but contain an expectation that the recipient does not understand
     2650</pre><p id="rfc.section.9.3.p.3">If all received Expect header field(s) are syntactically valid but contain an expectation that the recipient does not understand
    26552651         or cannot comply with, the recipient <em class="bcp14">MUST</em> respond with a 417 (Expectation Failed) status code. A recipient of a syntactically invalid Expectation header field <em class="bcp14">MUST</em> respond with a 4xx status code other than 417.
    26562652      </p>
    2657       <p id="rfc.section.10.3.p.4">The only expectation defined by this specification is:</p>
    2658       <p id="rfc.section.10.3.p.5"><span id="rfc.iref.108"></span><span id="rfc.iref.e.2"></span> 100-continue
     2653      <p id="rfc.section.9.3.p.4">The only expectation defined by this specification is:</p>
     2654      <p id="rfc.section.9.3.p.5"><span id="rfc.iref.108"></span><span id="rfc.iref.e.2"></span> 100-continue
    26592655      </p>
    26602656      <ul class="empty">
    … …  
    26622658         </li>
    26632659      </ul>
    2664       <p id="rfc.section.10.3.p.6">Comparison is case-insensitive for names (expect-name), and case-sensitive for values (expect-value).</p>
    2665       <p id="rfc.section.10.3.p.7">The Expect mechanism is hop-by-hop: the above requirements apply to any server, including proxies. However, the Expect header
     2660      <p id="rfc.section.9.3.p.6">Comparison is case-insensitive for names (expect-name), and case-sensitive for values (expect-value).</p>
     2661      <p id="rfc.section.9.3.p.7">The Expect mechanism is hop-by-hop: the above requirements apply to any server, including proxies. However, the Expect header
    26662662         field itself is end-to-end; it <em class="bcp14">MUST</em> be forwarded if the request is forwarded.
    26672663      </p>
    2668       <p id="rfc.section.10.3.p.8">Many older HTTP/1.0 and HTTP/1.1 applications do not understand the Expect header field.</p>
     2664      <p id="rfc.section.9.3.p.8">Many older HTTP/1.0 and HTTP/1.1 applications do not understand the Expect header field.</p>
    26692665      <div id="rfc.iref.f.1"></div>
    26702666      <div id="rfc.iref.h.5"></div>
    2671       <h2 id="rfc.section.10.4"><a href="#rfc.section.10.4">10.4</a>&nbsp;<a id="header.from" href="#header.from">From</a></h2>
    2672       <p id="rfc.section.10.4.p.1">The "From" header field, if given, <em class="bcp14">SHOULD</em> contain an Internet e-mail address for the human user who controls the requesting user agent. The address <em class="bcp14">SHOULD</em> be machine-usable, as defined by "mailbox" in <a href="http://tools.ietf.org/html/rfc5322#section-3.4">Section 3.4</a> of <a href="#RFC5322" id="rfc.xref.RFC5322.3"><cite title="Internet Message Format">[RFC5322]</cite></a>:
     2667      <h2 id="rfc.section.9.4"><a href="#rfc.section.9.4">9.4</a>&nbsp;<a id="header.from" href="#header.from">From</a></h2>
     2668      <p id="rfc.section.9.4.p.1">The "From" header field, if given, <em class="bcp14">SHOULD</em> contain an Internet e-mail address for the human user who controls the requesting user agent. The address <em class="bcp14">SHOULD</em> be machine-usable, as defined by "mailbox" in <a href="http://tools.ietf.org/html/rfc5322#section-3.4">Section 3.4</a> of <a href="#RFC5322" id="rfc.xref.RFC5322.3"><cite title="Internet Message Format">[RFC5322]</cite></a>:
    26732669      </p>
    26742670      <div id="rfc.figure.u.30"></div><pre class="inline"><span id="rfc.iref.g.41"></span>  <a href="#header.from" class="smpl">From</a>    = <a href="#header.from" class="smpl">mailbox</a>
    26752671 
    26762672  <a href="#header.from" class="smpl">mailbox</a> = &lt;mailbox, defined in <a href="#RFC5322" id="rfc.xref.RFC5322.4"><cite title="Internet Message Format">[RFC5322]</cite></a>, <a href="http://tools.ietf.org/html/rfc5322#section-3.4">Section 3.4</a>&gt;
    2677 </pre><p id="rfc.section.10.4.p.3">An example is:</p>
     2673</pre><p id="rfc.section.9.4.p.3">An example is:</p>
    26782674      <div id="rfc.figure.u.31"></div><pre class="text">  From: webmaster@example.org
    2679 </pre><p id="rfc.section.10.4.p.5">This header field <em class="bcp14">MAY</em> be used for logging purposes and as a means for identifying the source of invalid or unwanted requests. It <em class="bcp14">SHOULD NOT</em> be used as an insecure form of access protection. The interpretation of this field is that the request is being performed
     2675</pre><p id="rfc.section.9.4.p.5">This header field <em class="bcp14">MAY</em> be used for logging purposes and as a means for identifying the source of invalid or unwanted requests. It <em class="bcp14">SHOULD NOT</em> be used as an insecure form of access protection. The interpretation of this field is that the request is being performed
    26802676         on behalf of the person given, who accepts responsibility for the method performed. In particular, robot agents <em class="bcp14">SHOULD</em> include this header field so that the person responsible for running the robot can be contacted if problems occur on the receiving
    26812677         end.
    26822678      </p>
    2683       <p id="rfc.section.10.4.p.6">The Internet e-mail address in this field <em class="bcp14">MAY</em> be separate from the Internet host which issued the request. For example, when a request is passed through a proxy the original
     2679      <p id="rfc.section.9.4.p.6">The Internet e-mail address in this field <em class="bcp14">MAY</em> be separate from the Internet host which issued the request. For example, when a request is passed through a proxy the original
    26842680         issuer's address <em class="bcp14">SHOULD</em> be used.
    26852681      </p>
    2686       <p id="rfc.section.10.4.p.7">The client <em class="bcp14">SHOULD NOT</em> send the From header field without the user's approval, as it might conflict with the user's privacy interests or their site's
     2682      <p id="rfc.section.9.4.p.7">The client <em class="bcp14">SHOULD NOT</em> send the From header field without the user's approval, as it might conflict with the user's privacy interests or their site's
    26872683         security policy. It is strongly recommended that the user be able to disable, enable, and modify the value of this field at
    26882684         any time prior to a request.
    … …  
    26902686      <div id="rfc.iref.l.1"></div>
    26912687      <div id="rfc.iref.h.6"></div>
    2692       <h2 id="rfc.section.10.5"><a href="#rfc.section.10.5">10.5</a>&nbsp;<a id="header.location" href="#header.location">Location</a></h2>
    2693       <p id="rfc.section.10.5.p.1">The "Location" header field <em class="bcp14">MAY</em> be sent in responses to refer to a specific resource in accordance with the semantics of the status code.
     2688      <h2 id="rfc.section.9.5"><a href="#rfc.section.9.5">9.5</a>&nbsp;<a id="header.location" href="#header.location">Location</a></h2>
     2689      <p id="rfc.section.9.5.p.1">The "Location" header field <em class="bcp14">MAY</em> be sent in responses to refer to a specific resource in accordance with the semantics of the status code.
    26942690      </p>
    26952691      <div id="rfc.figure.u.32"></div><pre class="inline"><span id="rfc.iref.g.42"></span>  <a href="#header.location" class="smpl">Location</a> = <a href="#abnf.dependencies" class="smpl">URI-reference</a>
    2696 </pre><p id="rfc.section.10.5.p.3">For 201 (Created) responses, the Location is the URI of the new resource which was created by the request. For 3xx responses,
     2692</pre><p id="rfc.section.9.5.p.3">For 201 (Created) responses, the Location is the URI of the new resource which was created by the request. For 3xx responses,
    26972693         the location <em class="bcp14">SHOULD</em> indicate the server's preferred URI for automatic redirection to the resource.
    26982694      </p>
    2699       <p id="rfc.section.10.5.p.4">The field value consists of a single URI-reference. When it has the form of a relative reference (<a href="#RFC3986" id="rfc.xref.RFC3986.1"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-4.2">Section 4.2</a>), the final value is computed by resolving it against the effective request URI (<a href="#RFC3986" id="rfc.xref.RFC3986.2"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-5">Section 5</a>). If the original URI, as navigated to by the user agent, did contain a fragment identifier, and the final value does not,
     2695      <p id="rfc.section.9.5.p.4">The field value consists of a single URI-reference. When it has the form of a relative reference (<a href="#RFC3986" id="rfc.xref.RFC3986.1"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-4.2">Section 4.2</a>), the final value is computed by resolving it against the effective request URI (<a href="#RFC3986" id="rfc.xref.RFC3986.2"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-5">Section 5</a>). If the original URI, as navigated to by the user agent, did contain a fragment identifier, and the final value does not,
    27002696         then the original URI's fragment identifier is added to the final value.
    27012697      </p>
    … …  
    27062702      <p>An original URI "http://www.example.org/index.html#larry", combined with a field value given as:</p>  <pre class="text">  Location: http://www.example.net/index.html
    27072703</pre>  <p>would result in a final value of "http://www.example.net/index.html#larry", preserving the original fragment identifier.</p>
    2708       <div class="note" id="rfc.section.10.5.p.7">
     2704      <div class="note" id="rfc.section.9.5.p.7">
    27092705         <p> <b>Note:</b> Some recipients attempt to recover from Location fields that are not valid URI references. This specification does not mandate
    27102706            or define such processing, but does allow it (see <a href="#intro.conformance.and.error.handling" title="Conformance and Error Handling">Section&nbsp;1.2</a>).
    27112707         </p>
    27122708      </div>
    2713       <p id="rfc.section.10.5.p.8">There are circumstances in which a fragment identifier in a Location URI would not be appropriate. For instance, when it appears
     2709      <p id="rfc.section.9.5.p.8">There are circumstances in which a fragment identifier in a Location URI would not be appropriate. For instance, when it appears
    27142710         in a 201 Created response, where the Location header field specifies the URI for the entire created resource.
    27152711      </p>
    2716       <div class="note" id="rfc.section.10.5.p.9">
    2717          <p> <b>Note:</b> The Content-Location header field (<a href="#header.content-location" id="rfc.xref.header.content-location.3" title="Content-Location">Section&nbsp;10.17</a>) differs from Location in that the Content-Location identifies the most specific resource corresponding to the enclosed representation.
     2712      <div class="note" id="rfc.section.9.5.p.9">
     2713         <p> <b>Note:</b> The Content-Location header field (<a href="#header.content-location" id="rfc.xref.header.content-location.3" title="Content-Location">Section&nbsp;9.17</a>) differs from Location in that the Content-Location identifies the most specific resource corresponding to the enclosed representation.
    27182714            It is therefore possible for a response to contain header fields for both Location and Content-Location.
    27192715         </p>
    … …  
    27212717      <div id="rfc.iref.m.9"></div>
    27222718      <div id="rfc.iref.h.7"></div>
    2723       <h2 id="rfc.section.10.6"><a href="#rfc.section.10.6">10.6</a>&nbsp;<a id="header.max-forwards" href="#header.max-forwards">Max-Forwards</a></h2>
    2724       <p id="rfc.section.10.6.p.1">The "Max-Forwards" header field provides a mechanism with the TRACE (<a href="#TRACE" id="rfc.xref.TRACE.1" title="TRACE">Section&nbsp;2.3.7</a>) and OPTIONS (<a href="#OPTIONS" id="rfc.xref.OPTIONS.1" title="OPTIONS">Section&nbsp;2.3.1</a>) methods to limit the number of times that the request is forwarded by proxies. This can be useful when the client is attempting
     2719      <h2 id="rfc.section.9.6"><a href="#rfc.section.9.6">9.6</a>&nbsp;<a id="header.max-forwards" href="#header.max-forwards">Max-Forwards</a></h2>
     2720      <p id="rfc.section.9.6.p.1">The "Max-Forwards" header field provides a mechanism with the TRACE (<a href="#TRACE" id="rfc.xref.TRACE.1" title="TRACE">Section&nbsp;2.3.7</a>) and OPTIONS (<a href="#OPTIONS" id="rfc.xref.OPTIONS.1" title="OPTIONS">Section&nbsp;2.3.1</a>) methods to limit the number of times that the request is forwarded by proxies. This can be useful when the client is attempting
    27252721         to trace a request which appears to be failing or looping mid-chain.
    27262722      </p>
    27272723      <div id="rfc.figure.u.35"></div><pre class="inline"><span id="rfc.iref.g.43"></span>  <a href="#header.max-forwards" class="smpl">Max-Forwards</a> = 1*<a href="#notation" class="smpl">DIGIT</a>
    2728 </pre><p id="rfc.section.10.6.p.3">The Max-Forwards value is a decimal integer indicating the remaining number of times this request message can be forwarded.</p>
    2729       <p id="rfc.section.10.6.p.4">Each recipient of a TRACE or OPTIONS request containing a Max-Forwards header field <em class="bcp14">MUST</em> check and update its value prior to forwarding the request. If the received value is zero (0), the recipient <em class="bcp14">MUST NOT</em> forward the request; instead, it <em class="bcp14">MUST</em> respond as the final recipient. If the received Max-Forwards value is greater than zero, then the forwarded message <em class="bcp14">MUST</em> contain an updated Max-Forwards field with a value decremented by one (1).
    2730       </p>
    2731       <p id="rfc.section.10.6.p.5">The Max-Forwards header field <em class="bcp14">MAY</em> be ignored for all other request methods.
     2724</pre><p id="rfc.section.9.6.p.3">The Max-Forwards value is a decimal integer indicating the remaining number of times this request message can be forwarded.</p>
     2725      <p id="rfc.section.9.6.p.4">Each recipient of a TRACE or OPTIONS request containing a Max-Forwards header field <em class="bcp14">MUST</em> check and update its value prior to forwarding the request. If the received value is zero (0), the recipient <em class="bcp14">MUST NOT</em> forward the request; instead, it <em class="bcp14">MUST</em> respond as the final recipient. If the received Max-Forwards value is greater than zero, then the forwarded message <em class="bcp14">MUST</em> contain an updated Max-Forwards field with a value decremented by one (1).
     2726      </p>
     2727      <p id="rfc.section.9.6.p.5">The Max-Forwards header field <em class="bcp14">MAY</em> be ignored for all other request methods.
    27322728      </p>
    27332729      <div id="rfc.iref.r.2"></div>
    27342730      <div id="rfc.iref.h.8"></div>
    2735       <h2 id="rfc.section.10.7"><a href="#rfc.section.10.7">10.7</a>&nbsp;<a id="header.referer" href="#header.referer">Referer</a></h2>
    2736       <p id="rfc.section.10.7.p.1">The "Referer" [sic] header field allows the client to specify the URI of the resource from which the target URI was obtained
     2731      <h2 id="rfc.section.9.7"><a href="#rfc.section.9.7">9.7</a>&nbsp;<a id="header.referer" href="#header.referer">Referer</a></h2>
     2732      <p id="rfc.section.9.7.p.1">The "Referer" [sic] header field allows the client to specify the URI of the resource from which the target URI was obtained
    27372733         (the "referrer", although the header field is misspelled.).
    27382734      </p>
    2739       <p id="rfc.section.10.7.p.2">The Referer header field allows servers to generate lists of back-links to resources for interest, logging, optimized caching,
     2735      <p id="rfc.section.9.7.p.2">The Referer header field allows servers to generate lists of back-links to resources for interest, logging, optimized caching,
    27402736         etc. It also allows obsolete or mistyped links to be traced for maintenance. Some servers use Referer as a means of controlling
    27412737         where they allow links from (so-called "deep linking"), but legitimate requests do not always contain a Referer header field.
    27422738      </p>
    2743       <p id="rfc.section.10.7.p.3">If the target URI was obtained from a source that does not have its own URI (e.g., input from the user keyboard), the Referer
     2739      <p id="rfc.section.9.7.p.3">If the target URI was obtained from a source that does not have its own URI (e.g., input from the user keyboard), the Referer
    27442740         field <em class="bcp14">MUST</em> either be sent with the value "about:blank", or not be sent at all. Note that this requirement does not apply to sources with
    27452741         non-HTTP URIs (e.g., FTP).
    27462742      </p>
    27472743      <div id="rfc.figure.u.36"></div><pre class="inline"><span id="rfc.iref.g.44"></span>  <a href="#header.referer" class="smpl">Referer</a> = <a href="#abnf.dependencies" class="smpl">absolute-URI</a> / <a href="#abnf.dependencies" class="smpl">partial-URI</a>
    2748 </pre><p id="rfc.section.10.7.p.5">Example:</p>
     2744</pre><p id="rfc.section.9.7.p.5">Example:</p>
    27492745      <div id="rfc.figure.u.37"></div><pre class="text">  Referer: http://www.example.org/hypertext/Overview.html
    2750 </pre><p id="rfc.section.10.7.p.7">If the field value is a relative URI, it <em class="bcp14">SHOULD</em> be interpreted relative to the effective request URI. The URI <em class="bcp14">MUST NOT</em> include a fragment. See <a href="#encoding.sensitive.information.in.uris" title="Encoding Sensitive Information in URIs">Section&nbsp;12.2</a> for security considerations.
     2746</pre><p id="rfc.section.9.7.p.7">If the field value is a relative URI, it <em class="bcp14">SHOULD</em> be interpreted relative to the effective request URI. The URI <em class="bcp14">MUST NOT</em> include a fragment. See <a href="#encoding.sensitive.information.in.uris" title="Encoding Sensitive Information in URIs">Section&nbsp;11.2</a> for security considerations.
    27512747      </p>
    27522748      <div id="rfc.iref.r.3"></div>
    27532749      <div id="rfc.iref.h.9"></div>
    2754       <h2 id="rfc.section.10.8"><a href="#rfc.section.10.8">10.8</a>&nbsp;<a id="header.retry-after" href="#header.retry-after">Retry-After</a></h2>
    2755       <p id="rfc.section.10.8.p.1">The header "Retry-After" field can be used with a 503 (Service Unavailable) response to indicate how long the service is expected
     2750      <h2 id="rfc.section.9.8"><a href="#rfc.section.9.8">9.8</a>&nbsp;<a id="header.retry-after" href="#header.retry-after">Retry-After</a></h2>
     2751      <p id="rfc.section.9.8.p.1">The header "Retry-After" field can be used with a 503 (Service Unavailable) response to indicate how long the service is expected
    27562752         to be unavailable to the requesting client. This field <em class="bcp14">MAY</em> also be used with any 3xx (Redirection) response to indicate the minimum time the user-agent is asked to wait before issuing
    27572753         the redirected request.
    27582754      </p>
    2759       <p id="rfc.section.10.8.p.2">The value of this field can be either an HTTP-date or an integer number of seconds (in decimal) after the time of the response.</p>
     2755      <p id="rfc.section.9.8.p.2">The value of this field can be either an HTTP-date or an integer number of seconds (in decimal) after the time of the response.</p>
    27602756      <div id="rfc.figure.u.38"></div><pre class="inline"><span id="rfc.iref.g.45"></span>  <a href="#header.retry-after" class="smpl">Retry-After</a> = <a href="#http.date" class="smpl">HTTP-date</a> / <a href="#rule.delta-seconds" class="smpl">delta-seconds</a>
    27612757</pre><div id="rule.delta-seconds">
    2762          <p id="rfc.section.10.8.p.4">  Time spans are non-negative decimal integers, representing time in seconds.</p>
     2758         <p id="rfc.section.9.8.p.4">  Time spans are non-negative decimal integers, representing time in seconds.</p>
    27632759      </div>
    27642760      <div id="rfc.figure.u.39"></div><pre class="inline"><span id="rfc.iref.g.46"></span>  <a href="#rule.delta-seconds" class="smpl">delta-seconds</a>  = 1*<a href="#notation" class="smpl">DIGIT</a>
    2765 </pre><p id="rfc.section.10.8.p.6">Two examples of its use are</p>
     2761</pre><p id="rfc.section.9.8.p.6">Two examples of its use are</p>
    27662762      <div id="rfc.figure.u.40"></div><pre class="text">  Retry-After: Fri, 31 Dec 1999 23:59:59 GMT
    27672763  Retry-After: 120
    2768 </pre><p id="rfc.section.10.8.p.8">In the latter example, the delay is 2 minutes.</p>
     2764</pre><p id="rfc.section.9.8.p.8">In the latter example, the delay is 2 minutes.</p>
    27692765      <div id="rfc.iref.s.39"></div>
    27702766      <div id="rfc.iref.h.10"></div>
    2771       <h2 id="rfc.section.10.9"><a href="#rfc.section.10.9">10.9</a>&nbsp;<a id="header.server" href="#header.server">Server</a></h2>
    2772       <p id="rfc.section.10.9.p.1">The "Server" header field contains information about the software used by the origin server to handle the request.</p>
    2773       <p id="rfc.section.10.9.p.2">The field can contain multiple product tokens (<a href="#product.tokens" title="Product Tokens">Section&nbsp;6.2</a>) and comments (<a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.48"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) identifying the server and any significant subproducts. The product tokens are listed in order of their significance for
     2767      <h2 id="rfc.section.9.9"><a href="#rfc.section.9.9">9.9</a>&nbsp;<a id="header.server" href="#header.server">Server</a></h2>
     2768      <p id="rfc.section.9.9.p.1">The "Server" header field contains information about the software used by the origin server to handle the request.</p>
     2769      <p id="rfc.section.9.9.p.2">The field can contain multiple product tokens (<a href="#product.tokens" title="Product Tokens">Section&nbsp;5.2</a>) and comments (<a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.48"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) identifying the server and any significant subproducts. The product tokens are listed in order of their significance for
    27742770         identifying the application.
    27752771      </p>
    27762772      <div id="rfc.figure.u.41"></div><pre class="inline"><span id="rfc.iref.g.47"></span>  <a href="#header.server" class="smpl">Server</a> = <a href="#product.tokens" class="smpl">product</a> *( <a href="#core.rules" class="smpl">RWS</a> ( <a href="#product.tokens" class="smpl">product</a> / <a href="#abnf.dependencies" class="smpl">comment</a> ) )
    2777 </pre><p id="rfc.section.10.9.p.4">Example:</p>
     2773</pre><p id="rfc.section.9.9.p.4">Example:</p>
    27782774      <div id="rfc.figure.u.42"></div><pre class="text">  Server: CERN/3.0 libwww/2.17
    2779 </pre><p id="rfc.section.10.9.p.6">If the response is being forwarded through a proxy, the proxy application <em class="bcp14">MUST NOT</em> modify the Server header field. Instead, it <em class="bcp14">MUST</em> include a Via field (as described in <a href="p1-messaging.html#header.via" title="Via">Section 6.2</a> of <a href="#Part1" id="rfc.xref.Part1.49"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).
    2780       </p>
    2781       <div class="note" id="rfc.section.10.9.p.7">
     2775</pre><p id="rfc.section.9.9.p.6">If the response is being forwarded through a proxy, the proxy application <em class="bcp14">MUST NOT</em> modify the Server header field. Instead, it <em class="bcp14">MUST</em> include a Via field (as described in <a href="p1-messaging.html#header.via" title="Via">Section 6.2</a> of <a href="#Part1" id="rfc.xref.Part1.49"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).
     2776      </p>
     2777      <div class="note" id="rfc.section.9.9.p.7">
    27822778         <p> <b>Note:</b> Revealing the specific software version of the server might allow the server machine to become more vulnerable to attacks
    27832779            against software that is known to contain security holes. Server implementors are encouraged to make this field a configurable
    … …  
    27872783      <div id="rfc.iref.u.1"></div>
    27882784      <div id="rfc.iref.h.11"></div>
    2789       <h2 id="rfc.section.10.10"><a href="#rfc.section.10.10">10.10</a>&nbsp;<a id="header.user-agent" href="#header.user-agent">User-Agent</a></h2>
    2790       <p id="rfc.section.10.10.p.1">The "User-Agent" header field contains information about the user agent originating the request. User agents <em class="bcp14">SHOULD</em> include this field with requests.
    2791       </p>
    2792       <p id="rfc.section.10.10.p.2">Typically, it is used for statistical purposes, the tracing of protocol violations, and tailoring responses to avoid particular
     2785      <h2 id="rfc.section.9.10"><a href="#rfc.section.9.10">9.10</a>&nbsp;<a id="header.user-agent" href="#header.user-agent">User-Agent</a></h2>
     2786      <p id="rfc.section.9.10.p.1">The "User-Agent" header field contains information about the user agent originating the request. User agents <em class="bcp14">SHOULD</em> include this field with requests.
     2787      </p>
     2788      <p id="rfc.section.9.10.p.2">Typically, it is used for statistical purposes, the tracing of protocol violations, and tailoring responses to avoid particular
    27932789         user agent limitations.
    27942790      </p>
    2795       <p id="rfc.section.10.10.p.3">The field can contain multiple product tokens (<a href="#product.tokens" title="Product Tokens">Section&nbsp;6.2</a>) and comments (<a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.50"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) identifying the agent and its significant subproducts. By convention, the product tokens are listed in order of their significance
     2791      <p id="rfc.section.9.10.p.3">The field can contain multiple product tokens (<a href="#product.tokens" title="Product Tokens">Section&nbsp;5.2</a>) and comments (<a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.50"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) identifying the agent and its significant subproducts. By convention, the product tokens are listed in order of their significance
    27962792         for identifying the application.
    27972793      </p>
    2798       <p id="rfc.section.10.10.p.4">Because this field is usually sent on every request a user agent makes, implementations are encouraged not to include needlessly
     2794      <p id="rfc.section.9.10.p.4">Because this field is usually sent on every request a user agent makes, implementations are encouraged not to include needlessly
    27992795         fine-grained detail, and to limit (or even prohibit) the addition of subproducts by third parties. Overly long and detailed
    28002796         User-Agent field values make requests larger and can also be used to identify ("fingerprint") the user against their wishes.
    28012797      </p>
    2802       <p id="rfc.section.10.10.p.5">Likewise, implementations are encouraged not to use the product tokens of other implementations in order to declare compatibility
     2798      <p id="rfc.section.9.10.p.5">Likewise, implementations are encouraged not to use the product tokens of other implementations in order to declare compatibility
    28032799         with them, as this circumvents the purpose of the field. Finally, they are encouraged not to use comments to identify products;
    28042800         doing so makes the field value more difficult to parse.
    28052801      </p>
    28062802      <div id="rfc.figure.u.43"></div><pre class="inline"><span id="rfc.iref.g.48"></span>  <a href="#header.user-agent" class="smpl">User-Agent</a> = <a href="#product.tokens" class="smpl">product</a> *( <a href="#core.rules" class="smpl">RWS</a> ( <a href="#product.tokens" class="smpl">product</a> / <a href="#abnf.dependencies" class="smpl">comment</a> ) )
    2807 </pre><p id="rfc.section.10.10.p.7">Example:</p>
     2803</pre><p id="rfc.section.9.10.p.7">Example:</p>
    28082804      <div id="rfc.figure.u.44"></div><pre class="text">  User-Agent: CERN-LineMode/2.15 libwww/2.17b3
    28092805</pre><div id="rfc.iref.a.2"></div>
    28102806      <div id="rfc.iref.h.12"></div>
    2811       <h2 id="rfc.section.10.11"><a href="#rfc.section.10.11">10.11</a>&nbsp;<a id="header.accept" href="#header.accept">Accept</a></h2>
    2812       <p id="rfc.section.10.11.p.1">The "Accept" header field can be used by user agents to specify response media types that are acceptable. Accept header fields
     2807      <h2 id="rfc.section.9.11"><a href="#rfc.section.9.11">9.11</a>&nbsp;<a id="header.accept" href="#header.accept">Accept</a></h2>
     2808      <p id="rfc.section.9.11.p.1">The "Accept" header field can be used by user agents to specify response media types that are acceptable. Accept header fields
    28132809         can be used to indicate that the request is specifically limited to a small set of desired types, as in the case of a request
    28142810         for an in-line image.
    … …  
    28222818  <a href="#header.accept" class="smpl">accept-params</a>  = <a href="#core.rules" class="smpl">OWS</a> ";" <a href="#core.rules" class="smpl">OWS</a> "q=" <a href="#abnf.dependencies" class="smpl">qvalue</a> *( <a href="#header.accept" class="smpl">accept-ext</a> )
    28232819  <a href="#header.accept" class="smpl">accept-ext</a>     = <a href="#core.rules" class="smpl">OWS</a> ";" <a href="#core.rules" class="smpl">OWS</a> <a href="#core.rules" class="smpl">token</a> [ "=" <a href="#core.rules" class="smpl">word</a> ]
    2824 </pre><p id="rfc.section.10.11.p.3">The asterisk "*" character is used to group media types into ranges, with "*/*" indicating all media types and "type/*" indicating
     2820</pre><p id="rfc.section.9.11.p.3">The asterisk "*" character is used to group media types into ranges, with "*/*" indicating all media types and "type/*" indicating
    28252821         all subtypes of that type. The media-range <em class="bcp14">MAY</em> include media type parameters that are applicable to that range.
    28262822      </p>
    2827       <p id="rfc.section.10.11.p.4">Each media-range <em class="bcp14">MAY</em> be followed by one or more accept-params, beginning with the "q" parameter for indicating a relative quality factor. The first
     2823      <p id="rfc.section.9.11.p.4">Each media-range <em class="bcp14">MAY</em> be followed by one or more accept-params, beginning with the "q" parameter for indicating a relative quality factor. The first
    28282824         "q" parameter (if any) separates the media-range parameter(s) from the accept-params. Quality factors allow the user or user
    28292825         agent to indicate the relative degree of preference for that media-range, using the qvalue scale from 0 to 1 (qvalue;). The
    28302826         default value is q=1.
    28312827      </p>
    2832       <div class="note" id="rfc.section.10.11.p.5">
     2828      <div class="note" id="rfc.section.9.11.p.5">
    28332829         <p> <b>Note:</b> Use of the "q" parameter name to separate media type parameters from Accept extension parameters is due to historical practice.
    28342830            Although this prevents any media type parameter named "q" from being used with a media range, such an event is believed to
    … …  
    28372833         </p>
    28382834      </div>
    2839       <p id="rfc.section.10.11.p.6">The example</p>
     2835      <p id="rfc.section.9.11.p.6">The example</p>
    28402836      <div id="rfc.figure.u.46"></div><pre class="text">  Accept: audio/*; q=0.2, audio/basic
    2841 </pre><p id="rfc.section.10.11.p.8"> <em class="bcp14">SHOULD</em> be interpreted as "I prefer audio/basic, but send me any audio type if it is the best available after an 80% mark-down in
     2837</pre><p id="rfc.section.9.11.p.8"> <em class="bcp14">SHOULD</em> be interpreted as "I prefer audio/basic, but send me any audio type if it is the best available after an 80% mark-down in
    28422838         quality".
    28432839      </p>
    2844       <p id="rfc.section.10.11.p.9">A request without any Accept header field implies that the user agent will accept any media type in response. If an Accept
     2840      <p id="rfc.section.9.11.p.9">A request without any Accept header field implies that the user agent will accept any media type in response. If an Accept
    28452841         header field is present in a request and none of the available representations for the response have a media type that is
    28462842         listed as acceptable, the origin server <em class="bcp14">MAY</em> either honor the Accept header field by sending a 406 (Not Acceptable) response or disregard the Accept header field by treating
    28472843         the response as if it is not subject to content negotiation.
    28482844      </p>
    2849       <p id="rfc.section.10.11.p.10">A more elaborate example is</p>
     2845      <p id="rfc.section.9.11.p.10">A more elaborate example is</p>
    28502846      <div id="rfc.figure.u.47"></div><pre class="text">  Accept: text/plain; q=0.5, text/html,
    28512847          text/x-dvi; q=0.8, text/x-c
    2852 </pre><p id="rfc.section.10.11.p.12">Verbally, this would be interpreted as "text/html and text/x-c are the preferred media types, but if they do not exist, then
     2848</pre><p id="rfc.section.9.11.p.12">Verbally, this would be interpreted as "text/html and text/x-c are the preferred media types, but if they do not exist, then
    28532849         send the text/x-dvi representation, and if that does not exist, send the text/plain representation".
    28542850      </p>
    2855       <p id="rfc.section.10.11.p.13">Media ranges can be overridden by more specific media ranges or specific media types. If more than one media range applies
     2851      <p id="rfc.section.9.11.p.13">Media ranges can be overridden by more specific media ranges or specific media types. If more than one media range applies
    28562852         to a given type, the most specific reference has precedence. For example,
    28572853      </p>
    28582854      <div id="rfc.figure.u.48"></div><pre class="text">  Accept: text/*, text/plain, text/plain;format=flowed, */*
    2859 </pre><p id="rfc.section.10.11.p.15">have the following precedence: </p>
     2855</pre><p id="rfc.section.9.11.p.15">have the following precedence: </p>
    28602856      <ol>
    28612857         <li>text/plain;format=flowed</li>
    … …  
    28642860         <li>*/*</li>
    28652861      </ol>
    2866       <p id="rfc.section.10.11.p.16">The media type quality factor associated with a given type is determined by finding the media range with the highest precedence
     2862      <p id="rfc.section.9.11.p.16">The media type quality factor associated with a given type is determined by finding the media range with the highest precedence
    28672863         which matches that type. For example,
    28682864      </p>
    28692865      <div id="rfc.figure.u.49"></div><pre class="text">  Accept: text/*;q=0.3, text/html;q=0.7, text/html;level=1,
    28702866          text/html;level=2;q=0.4, */*;q=0.5
    2871 </pre><p id="rfc.section.10.11.p.18">would cause the following values to be associated:</p>
     2867</pre><p id="rfc.section.9.11.p.18">would cause the following values to be associated:</p>
    28722868      <div id="rfc.table.u.7">
    28732869         <table class="tt full left" cellpadding="3" cellspacing="0">
    … …  
    29062902         </table>
    29072903      </div>
    2908       <p id="rfc.section.10.11.p.19"> <b>Note:</b> A user agent might be provided with a default set of quality values for certain media ranges. However, unless the user agent
     2904      <p id="rfc.section.9.11.p.19"> <b>Note:</b> A user agent might be provided with a default set of quality values for certain media ranges. However, unless the user agent
    29092905         is a closed system which cannot interact with other rendering agents, this default set ought to be configurable by the user.
    29102906      </p>
    29112907      <div id="rfc.iref.a.3"></div>
    29122908      <div id="rfc.iref.h.13"></div>
    2913       <h2 id="rfc.section.10.12"><a href="#rfc.section.10.12">10.12</a>&nbsp;<a id="header.accept-charset" href="#header.accept-charset">Accept-Charset</a></h2>
    2914       <p id="rfc.section.10.12.p.1">The "Accept-Charset" header field can be used by user agents to indicate what character encodings are acceptable in a response
     2909      <h2 id="rfc.section.9.12"><a href="#rfc.section.9.12">9.12</a>&nbsp;<a id="header.accept-charset" href="#header.accept-charset">Accept-Charset</a></h2>
     2910      <p id="rfc.section.9.12.p.1">The "Accept-Charset" header field can be used by user agents to indicate what character encodings are acceptable in a response
    29152911         payload. This field allows clients capable of understanding more comprehensive or special-purpose character encodings to signal
    29162912         that capability to a server which is capable of representing documents in those character encodings.
    … …  
    29182914      <div id="rfc.figure.u.50"></div><pre class="inline"><span id="rfc.iref.g.53"></span>  <a href="#header.accept-charset" class="smpl">Accept-Charset</a> = 1#( ( <a href="#rule.charset" class="smpl">charset</a> / "*" )
    29192915                         [ <a href="#core.rules" class="smpl">OWS</a> ";" <a href="#core.rules" class="smpl">OWS</a> "q=" <a href="#abnf.dependencies" class="smpl">qvalue</a> ] )
    2920 </pre><p id="rfc.section.10.12.p.3">Character encoding values (a.k.a., charsets) are described in <a href="#character.sets" title="Character Encodings (charset)">Section&nbsp;6.3</a>. Each charset <em class="bcp14">MAY</em> be given an associated quality value which represents the user's preference for that charset. The default value is q=1. An
     2916</pre><p id="rfc.section.9.12.p.3">Character encoding values (a.k.a., charsets) are described in <a href="#character.sets" title="Character Encodings (charset)">Section&nbsp;5.3</a>. Each charset <em class="bcp14">MAY</em> be given an associated quality value which represents the user's preference for that charset. The default value is q=1. An
    29212917         example is
    29222918      </p>
    29232919      <div id="rfc.figure.u.51"></div><pre class="text">  Accept-Charset: iso-8859-5, unicode-1-1;q=0.8
    2924 </pre><p id="rfc.section.10.12.p.5">The special value "*", if present in the Accept-Charset field, matches every character encoding which is not mentioned elsewhere
     2920</pre><p id="rfc.section.9.12.p.5">The special value "*", if present in the Accept-Charset field, matches every character encoding which is not mentioned elsewhere
    29252921         in the Accept-Charset field. If no "*" is present in an Accept-Charset field, then all character encodings not explicitly
    29262922         mentioned get a quality value of 0.
    29272923      </p>
    2928       <p id="rfc.section.10.12.p.6">A request without any Accept-Charset header field implies that the user agent will accept any character encoding in response.
     2924      <p id="rfc.section.9.12.p.6">A request without any Accept-Charset header field implies that the user agent will accept any character encoding in response.
    29292925         If an Accept-Charset header field is present in a request and none of the available representations for the response have
    29302926         a character encoding that is listed as acceptable, the origin server <em class="bcp14">MAY</em> either honor the Accept-Charset header field by sending a 406 (Not Acceptable) response or disregard the Accept-Charset header
    … …  
    29332929      <div id="rfc.iref.a.4"></div>
    29342930      <div id="rfc.iref.h.14"></div>
    2935       <h2 id="rfc.section.10.13"><a href="#rfc.section.10.13">10.13</a>&nbsp;<a id="header.accept-encoding" href="#header.accept-encoding">Accept-Encoding</a></h2>
    2936       <p id="rfc.section.10.13.p.1">The "Accept-Encoding" header field can be used by user agents to indicate what response content-codings (<a href="#content.codings" title="Content Codings">Section&nbsp;6.4</a>) are acceptable in the response. An "identity" token is used as a synonym for "no encoding" in order to communicate when
     2931      <h2 id="rfc.section.9.13"><a href="#rfc.section.9.13">9.13</a>&nbsp;<a id="header.accept-encoding" href="#header.accept-encoding">Accept-Encoding</a></h2>
     2932      <p id="rfc.section.9.13.p.1">The "Accept-Encoding" header field can be used by user agents to indicate what response content-codings (<a href="#content.codings" title="Content Codings">Section&nbsp;5.4</a>) are acceptable in the response. An "identity" token is used as a synonym for "no encoding" in order to communicate when
    29372933         no encoding is preferred.
    29382934      </p>
    29392935      <div id="rfc.figure.u.52"></div><pre class="inline"><span id="rfc.iref.g.54"></span><span id="rfc.iref.g.55"></span>  <a href="#header.accept-encoding" class="smpl">Accept-Encoding</a>  = #( <a href="#header.accept-encoding" class="smpl">codings</a> [ <a href="#core.rules" class="smpl">OWS</a> ";" <a href="#core.rules" class="smpl">OWS</a> "q=" <a href="#abnf.dependencies" class="smpl">qvalue</a> ] )
    29402936  <a href="#header.accept-encoding" class="smpl">codings</a>          = <a href="#content.codings" class="smpl">content-coding</a> / "identity" / "*"
    2941 </pre><p id="rfc.section.10.13.p.3">Each codings value <em class="bcp14">MAY</em> be given an associated quality value which represents the preference for that encoding. The default value is q=1.
    2942       </p>
    2943       <p id="rfc.section.10.13.p.4">For example,</p>
     2937</pre><p id="rfc.section.9.13.p.3">Each codings value <em class="bcp14">MAY</em> be given an associated quality value which represents the preference for that encoding. The default value is q=1.
     2938      </p>
     2939      <p id="rfc.section.9.13.p.4">For example,</p>
    29442940      <div id="rfc.figure.u.53"></div><pre class="text">  Accept-Encoding: compress, gzip
    29452941  Accept-Encoding:
    … …  
    29472943  Accept-Encoding: compress;q=0.5, gzip;q=1.0
    29482944  Accept-Encoding: gzip;q=1.0, identity; q=0.5, *;q=0
    2949 </pre><p id="rfc.section.10.13.p.6">A server tests whether a content-coding for a given representation is acceptable, according to an Accept-Encoding field, using
     2945</pre><p id="rfc.section.9.13.p.6">A server tests whether a content-coding for a given representation is acceptable, according to an Accept-Encoding field, using
    29502946         these rules:
    29512947      </p>
    … …  
    29622958         <li>If multiple content-codings are acceptable, then the acceptable content-coding with the highest non-zero qvalue is preferred.</li>
    29632959      </ol>
    2964       <p id="rfc.section.10.13.p.7">An Accept-Encoding header field with a combined field-value that is empty implies that the user agent does not want any content-coding
     2960      <p id="rfc.section.9.13.p.7">An Accept-Encoding header field with a combined field-value that is empty implies that the user agent does not want any content-coding
    29652961         in response. If an Accept-Encoding header field is present in a request and none of the available representations for the
    29662962         response have a content-coding that is listed as acceptable, the origin server <em class="bcp14">SHOULD</em> send a response without any content-coding.
    29672963      </p>
    2968       <p id="rfc.section.10.13.p.8">A request without an Accept-Encoding header field implies that the user agent will accept any content-coding in response,
     2964      <p id="rfc.section.9.13.p.8">A request without an Accept-Encoding header field implies that the user agent will accept any content-coding in response,
    29692965         but a representation without content-coding is preferred for compatibility with the widest variety of user agents.
    29702966      </p>
    2971       <div class="note" id="rfc.section.10.13.p.9">
     2967      <div class="note" id="rfc.section.9.13.p.9">
    29722968         <p> <b>Note:</b> Most HTTP/1.0 applications do not recognize or obey qvalues associated with content-codings. This means that qvalues will
    29732969            not work and are not permitted with x-gzip or x-compress.
    … …  
    29762972      <div id="rfc.iref.a.5"></div>
    29772973      <div id="rfc.iref.h.15"></div>
    2978       <h2 id="rfc.section.10.14"><a href="#rfc.section.10.14">10.14</a>&nbsp;<a id="header.accept-language" href="#header.accept-language">Accept-Language</a></h2>
    2979       <p id="rfc.section.10.14.p.1">The "Accept-Language" header field can be used by user agents to indicate the set of natural languages that are preferred
    2980          in the response. Language tags are defined in <a href="#language.tags" title="Language Tags">Section&nbsp;6.6</a>.
     2974      <h2 id="rfc.section.9.14"><a href="#rfc.section.9.14">9.14</a>&nbsp;<a id="header.accept-language" href="#header.accept-language">Accept-Language</a></h2>
     2975      <p id="rfc.section.9.14.p.1">The "Accept-Language" header field can be used by user agents to indicate the set of natural languages that are preferred
     2976         in the response. Language tags are defined in <a href="#language.tags" title="Language Tags">Section&nbsp;5.6</a>.
    29812977      </p>
    29822978      <div id="rfc.figure.u.54"></div><pre class="inline"><span id="rfc.iref.g.56"></span><span id="rfc.iref.g.57"></span>  <a href="#header.accept-language" class="smpl">Accept-Language</a> =
    … …  
    29842980  <a href="#header.accept-language" class="smpl">language-range</a>  =
    29852981            &lt;language-range, defined in <a href="#RFC4647" id="rfc.xref.RFC4647.1"><cite title="Matching of Language Tags">[RFC4647]</cite></a>, <a href="http://tools.ietf.org/html/rfc4647#section-2.1">Section 2.1</a>&gt;
    2986 </pre><p id="rfc.section.10.14.p.3">Each language-range can be given an associated quality value which represents an estimate of the user's preference for the
     2982</pre><p id="rfc.section.9.14.p.3">Each language-range can be given an associated quality value which represents an estimate of the user's preference for the
    29872983         languages specified by that range. The quality value defaults to "q=1". For example,
    29882984      </p>
    29892985      <div id="rfc.figure.u.55"></div><pre class="text">  Accept-Language: da, en-gb;q=0.8, en;q=0.7
    2990 </pre><p id="rfc.section.10.14.p.5">would mean: "I prefer Danish, but will accept British English and other types of English". (see also <a href="http://tools.ietf.org/html/rfc4647#section-2.3">Section 2.3</a> of <a href="#RFC4647" id="rfc.xref.RFC4647.2"><cite title="Matching of Language Tags">[RFC4647]</cite></a>)
    2991       </p>
    2992       <p id="rfc.section.10.14.p.6">For matching, <a href="http://tools.ietf.org/html/rfc4647#section-3">Section 3</a> of <a href="#RFC4647" id="rfc.xref.RFC4647.3"><cite title="Matching of Language Tags">[RFC4647]</cite></a> defines several matching schemes. Implementations can offer the most appropriate matching scheme for their requirements.
    2993       </p>
    2994       <div class="note" id="rfc.section.10.14.p.7">
     2986</pre><p id="rfc.section.9.14.p.5">would mean: "I prefer Danish, but will accept British English and other types of English". (see also <a href="http://tools.ietf.org/html/rfc4647#section-2.3">Section 2.3</a> of <a href="#RFC4647" id="rfc.xref.RFC4647.2"><cite title="Matching of Language Tags">[RFC4647]</cite></a>)
     2987      </p>
     2988      <p id="rfc.section.9.14.p.6">For matching, <a href="http://tools.ietf.org/html/rfc4647#section-3">Section 3</a> of <a href="#RFC4647" id="rfc.xref.RFC4647.3"><cite title="Matching of Language Tags">[RFC4647]</cite></a> defines several matching schemes. Implementations can offer the most appropriate matching scheme for their requirements.
     2989      </p>
     2990      <div class="note" id="rfc.section.9.14.p.7">
    29952991         <p> <b>Note:</b> The "Basic Filtering" scheme (<a href="#RFC4647" id="rfc.xref.RFC4647.4"><cite title="Matching of Language Tags">[RFC4647]</cite></a>, <a href="http://tools.ietf.org/html/rfc4647#section-3.3.1">Section 3.3.1</a>) is identical to the matching scheme that was previously defined in <a href="http://tools.ietf.org/html/rfc2616#section-14.4">Section 14.4</a> of <a href="#RFC2616" id="rfc.xref.RFC2616.3"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
    29962992         </p>
    29972993      </div>
    2998       <p id="rfc.section.10.14.p.8">It might be contrary to the privacy expectations of the user to send an Accept-Language header field with the complete linguistic
    2999          preferences of the user in every request. For a discussion of this issue, see <a href="#privacy.issues.connected.to.accept.header.fields" title="Privacy Issues Connected to Accept Header Fields">Section&nbsp;12.5</a>.
    3000       </p>
    3001       <p id="rfc.section.10.14.p.9">As intelligibility is highly dependent on the individual user, it is recommended that client applications make the choice
     2994      <p id="rfc.section.9.14.p.8">It might be contrary to the privacy expectations of the user to send an Accept-Language header field with the complete linguistic
     2995         preferences of the user in every request. For a discussion of this issue, see <a href="#privacy.issues.connected.to.accept.header.fields" title="Privacy Issues Connected to Accept Header Fields">Section&nbsp;11.5</a>.
     2996      </p>
     2997      <p id="rfc.section.9.14.p.9">As intelligibility is highly dependent on the individual user, it is recommended that client applications make the choice
    30022998         of linguistic preference available to the user. If the choice is not made available, then the Accept-Language header field <em class="bcp14">MUST NOT</em> be given in the request.
    30032999      </p>
    3004       <div class="note" id="rfc.section.10.14.p.10">
     3000      <div class="note" id="rfc.section.9.14.p.10">
    30053001         <p> <b>Note:</b> When making the choice of linguistic preference available to the user, we remind implementors of the fact that users are not
    30063002            familiar with the details of language matching as described above, and ought to be provided appropriate guidance. As an example,
    … …  
    30113007      <div id="rfc.iref.c.7"></div>
    30123008      <div id="rfc.iref.h.16"></div>
    3013       <h2 id="rfc.section.10.15"><a href="#rfc.section.10.15">10.15</a>&nbsp;<a id="header.content-encoding" href="#header.content-encoding">Content-Encoding</a></h2>
    3014       <p id="rfc.section.10.15.p.1">The "Content-Encoding" header field indicates what content-codings have been applied to the representation beyond those inherent
     3009      <h2 id="rfc.section.9.15"><a href="#rfc.section.9.15">9.15</a>&nbsp;<a id="header.content-encoding" href="#header.content-encoding">Content-Encoding</a></h2>
     3010      <p id="rfc.section.9.15.p.1">The "Content-Encoding" header field indicates what content-codings have been applied to the representation beyond those inherent
    30153011         in the media type, and thus what decoding mechanisms have to be applied in order to obtain the media-type referenced by the
    30163012         Content-Type header field. Content-Encoding is primarily used to allow a representation to be compressed without losing the
    … …  
    30183014      </p>
    30193015      <div id="rfc.figure.u.56"></div><pre class="inline"><span id="rfc.iref.g.58"></span>  <a href="#header.content-encoding" class="smpl">Content-Encoding</a> = 1#<a href="#content.codings" class="smpl">content-coding</a>
    3020 </pre><p id="rfc.section.10.15.p.3">Content codings are defined in <a href="#content.codings" title="Content Codings">Section&nbsp;6.4</a>. An example of its use is
     3016</pre><p id="rfc.section.9.15.p.3">Content codings are defined in <a href="#content.codings" title="Content Codings">Section&nbsp;5.4</a>. An example of its use is
    30213017      </p>
    30223018      <div id="rfc.figure.u.57"></div><pre class="text">  Content-Encoding: gzip
    3023 </pre><p id="rfc.section.10.15.p.5">The content-coding is a characteristic of the representation. Typically, the representation body is stored with this encoding
     3019</pre><p id="rfc.section.9.15.p.5">The content-coding is a characteristic of the representation. Typically, the representation body is stored with this encoding
    30243020         and is only decoded before rendering or analogous usage. However, a transforming proxy <em class="bcp14">MAY</em> modify the content-coding if the new coding is known to be acceptable to the recipient, unless the "no-transform" cache-control
    30253021         directive is present in the message.
    30263022      </p>
    3027       <p id="rfc.section.10.15.p.6">If the media type includes an inherent encoding, such as a data format that is always compressed, then that encoding would
     3023      <p id="rfc.section.9.15.p.6">If the media type includes an inherent encoding, such as a data format that is always compressed, then that encoding would
    30283024         not be restated as a Content-Encoding even if it happens to be the same algorithm as one of the content-codings. Such a content-coding
    30293025         would only be listed if, for some bizarre reason, it is applied a second time to form the representation. Likewise, an origin
    … …  
    30323028         response (e.g., open a "Save as ..." dialog instead of automatic decompression and rendering of content).
    30333029      </p>
    3034       <p id="rfc.section.10.15.p.7">A representation that has a content-coding applied to it <em class="bcp14">MUST</em> include a Content-Encoding header field (<a href="#header.content-encoding" id="rfc.xref.header.content-encoding.3" title="Content-Encoding">Section&nbsp;10.15</a>) that lists the content-coding(s) applied.
    3035       </p>
    3036       <p id="rfc.section.10.15.p.8">If multiple encodings have been applied to a representation, the content codings <em class="bcp14">MUST</em> be listed in the order in which they were applied. Additional information about the encoding parameters <em class="bcp14">MAY</em> be provided by other header fields not defined by this specification.
    3037       </p>
    3038       <p id="rfc.section.10.15.p.9">If the content-coding of a representation in a request message is not acceptable to the origin server, the server <em class="bcp14">SHOULD</em> respond with a status code of 415 (Unsupported Media Type).
     3030      <p id="rfc.section.9.15.p.7">A representation that has a content-coding applied to it <em class="bcp14">MUST</em> include a Content-Encoding header field (<a href="#header.content-encoding" id="rfc.xref.header.content-encoding.3" title="Content-Encoding">Section&nbsp;9.15</a>) that lists the content-coding(s) applied.
     3031      </p>
     3032      <p id="rfc.section.9.15.p.8">If multiple encodings have been applied to a representation, the content codings <em class="bcp14">MUST</em> be listed in the order in which they were applied. Additional information about the encoding parameters <em class="bcp14">MAY</em> be provided by other header fields not defined by this specification.
     3033      </p>
     3034      <p id="rfc.section.9.15.p.9">If the content-coding of a representation in a request message is not acceptable to the origin server, the server <em class="bcp14">SHOULD</em> respond with a status code of 415 (Unsupported Media Type).
    30393035      </p>
    30403036      <div id="rfc.iref.c.8"></div>
    30413037      <div id="rfc.iref.h.17"></div>
    3042       <h2 id="rfc.section.10.16"><a href="#rfc.section.10.16">10.16</a>&nbsp;<a id="header.content-language" href="#header.content-language">Content-Language</a></h2>
    3043       <p id="rfc.section.10.16.p.1">The "Content-Language" header field describes the natural language(s) of the intended audience for the representation. Note
     3038      <h2 id="rfc.section.9.16"><a href="#rfc.section.9.16">9.16</a>&nbsp;<a id="header.content-language" href="#header.content-language">Content-Language</a></h2>
     3039      <p id="rfc.section.9.16.p.1">The "Content-Language" header field describes the natural language(s) of the intended audience for the representation. Note
    30443040         that this might not be equivalent to all the languages used within the representation.
    30453041      </p>
    30463042      <div id="rfc.figure.u.58"></div><pre class="inline"><span id="rfc.iref.g.59"></span>  <a href="#header.content-language" class="smpl">Content-Language</a> = 1#<a href="#language.tags" class="smpl">language-tag</a>
    3047 </pre><p id="rfc.section.10.16.p.3">Language tags are defined in <a href="#language.tags" title="Language Tags">Section&nbsp;6.6</a>. The primary purpose of Content-Language is to allow a user to identify and differentiate representations according to the
     3043</pre><p id="rfc.section.9.16.p.3">Language tags are defined in <a href="#language.tags" title="Language Tags">Section&nbsp;5.6</a>. The primary purpose of Content-Language is to allow a user to identify and differentiate representations according to the
    30483044         user's own preferred language. Thus, if the body content is intended only for a Danish-literate audience, the appropriate
    30493045         field is
    30503046      </p>
    30513047      <div id="rfc.figure.u.59"></div><pre class="text">  Content-Language: da
    3052 </pre><p id="rfc.section.10.16.p.5">If no Content-Language is specified, the default is that the content is intended for all language audiences. This might mean
     3048</pre><p id="rfc.section.9.16.p.5">If no Content-Language is specified, the default is that the content is intended for all language audiences. This might mean
    30533049         that the sender does not consider it to be specific to any natural language, or that the sender does not know for which language
    30543050         it is intended.
    30553051      </p>
    3056       <p id="rfc.section.10.16.p.6">Multiple languages <em class="bcp14">MAY</em> be listed for content that is intended for multiple audiences. For example, a rendition of the "Treaty of Waitangi", presented
     3052      <p id="rfc.section.9.16.p.6">Multiple languages <em class="bcp14">MAY</em> be listed for content that is intended for multiple audiences. For example, a rendition of the "Treaty of Waitangi", presented
    30573053         simultaneously in the original Maori and English versions, would call for
    30583054      </p>
    30593055      <div id="rfc.figure.u.60"></div><pre class="text">  Content-Language: mi, en
    3060 </pre><p id="rfc.section.10.16.p.8">However, just because multiple languages are present within a representation does not mean that it is intended for multiple
     3056</pre><p id="rfc.section.9.16.p.8">However, just because multiple languages are present within a representation does not mean that it is intended for multiple
    30613057         linguistic audiences. An example would be a beginner's language primer, such as "A First Lesson in Latin", which is clearly
    30623058         intended to be used by an English-literate audience. In this case, the Content-Language would properly only include "en".
    30633059      </p>
    3064       <p id="rfc.section.10.16.p.9">Content-Language <em class="bcp14">MAY</em> be applied to any media type — it is not limited to textual documents.
     3060      <p id="rfc.section.9.16.p.9">Content-Language <em class="bcp14">MAY</em> be applied to any media type — it is not limited to textual documents.
    30653061      </p>
    30663062      <div id="rfc.iref.c.9"></div>
    30673063      <div id="rfc.iref.h.18"></div>
    3068       <h2 id="rfc.section.10.17"><a href="#rfc.section.10.17">10.17</a>&nbsp;<a id="header.content-location" href="#header.content-location">Content-Location</a></h2>
    3069       <p id="rfc.section.10.17.p.1">The "Content-Location" header field supplies a URI that can be used as a specific identifier for the representation in this
     3064      <h2 id="rfc.section.9.17"><a href="#rfc.section.9.17">9.17</a>&nbsp;<a id="header.content-location" href="#header.content-location">Content-Location</a></h2>
     3065      <p id="rfc.section.9.17.p.1">The "Content-Location" header field supplies a URI that can be used as a specific identifier for the representation in this
    30703066         message. In other words, if one were to perform a GET on this URI at the time of this message's generation, then a 200 response
    30713067         would contain the same representation that is enclosed as payload in this message.
    30723068      </p>
    30733069      <div id="rfc.figure.u.61"></div><pre class="inline"><span id="rfc.iref.g.60"></span>  <a href="#header.content-location" class="smpl">Content-Location</a> = <a href="#abnf.dependencies" class="smpl">absolute-URI</a> / <a href="#abnf.dependencies" class="smpl">partial-URI</a>
    3074 </pre><p id="rfc.section.10.17.p.3">The Content-Location value is not a replacement for the effective Request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.51"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). It is representation metadata. It has the same syntax and semantics as the header field of the same name defined for MIME
     3070</pre><p id="rfc.section.9.17.p.3">The Content-Location value is not a replacement for the effective Request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.51"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). It is representation metadata. It has the same syntax and semantics as the header field of the same name defined for MIME
    30753071         body parts in <a href="http://tools.ietf.org/html/rfc2557#section-4">Section 4</a> of <a href="#RFC2557" id="rfc.xref.RFC2557.1"><cite title="MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)">[RFC2557]</cite></a>. However, its appearance in an HTTP message has some special implications for HTTP recipients.
    30763072      </p>
    3077       <p id="rfc.section.10.17.p.4">If Content-Location is included in a response message and its value is the same as the effective request URI, then the response
     3073      <p id="rfc.section.9.17.p.4">If Content-Location is included in a response message and its value is the same as the effective request URI, then the response
    30783074         payload <em class="bcp14">SHOULD</em> be considered a current representation of that resource. For a GET or HEAD request, this is the same as the default semantics
    30793075         when no Content-Location is provided by the server. For a state-changing request like PUT or POST, it implies that the server's
    … …  
    30823078         need for a subsequent GET request.
    30833079      </p>
    3084       <p id="rfc.section.10.17.p.5">If Content-Location is included in a response message and its value differs from the effective request URI, then the origin
     3080      <p id="rfc.section.9.17.p.5">If Content-Location is included in a response message and its value differs from the effective request URI, then the origin
    30853081         server is informing recipients that this representation has its own, presumably more specific, identifier. For a GET or HEAD
    30863082         request, this is an indication that the effective request URI identifies a resource that is subject to content negotiation
    … …  
    30913087         in the future.
    30923088      </p>
    3093       <p id="rfc.section.10.17.p.6">If Content-Location is included in a request message, then it <em class="bcp14">MAY</em> be interpreted by the origin server as an indication of where the user agent originally obtained the content of the enclosed
     3089      <p id="rfc.section.9.17.p.6">If Content-Location is included in a request message, then it <em class="bcp14">MAY</em> be interpreted by the origin server as an indication of where the user agent originally obtained the content of the enclosed
    30943090         representation (prior to any subsequent modification of the content by that user agent). In other words, the user agent is
    30953091         providing the same representation metadata that it received with the original representation. However, such interpretation <em class="bcp14">MUST NOT</em> be used to alter the semantics of the method requested by the client. For example, if a client makes a PUT request on a negotiated
    … …  
    30993095         latter semantics, it would have applied the PUT directly to the Content-Location URI.
    31003096      </p>
    3101       <p id="rfc.section.10.17.p.7">A Content-Location field received in a request message is transitory information that <em class="bcp14">SHOULD NOT</em> be saved with other representation metadata for use in later responses. The Content-Location's value might be saved for use
     3097      <p id="rfc.section.9.17.p.7">A Content-Location field received in a request message is transitory information that <em class="bcp14">SHOULD NOT</em> be saved with other representation metadata for use in later responses. The Content-Location's value might be saved for use
    31023098         in other contexts, such as within source links or other metadata.
    31033099      </p>
    3104       <p id="rfc.section.10.17.p.8">A cache cannot assume that a representation with a Content-Location different from the URI used to retrieve it can be used
     3100      <p id="rfc.section.9.17.p.8">A cache cannot assume that a representation with a Content-Location different from the URI used to retrieve it can be used
    31053101         to respond to later requests on that Content-Location URI.
    31063102      </p>
    3107       <p id="rfc.section.10.17.p.9">If the Content-Location value is a partial URI, the partial URI is interpreted relative to the effective request URI.</p>
     3103      <p id="rfc.section.9.17.p.9">If the Content-Location value is a partial URI, the partial URI is interpreted relative to the effective request URI.</p>
    31083104      <div id="rfc.iref.c.10"></div>
    31093105      <div id="rfc.iref.h.19"></div>
    3110       <h2 id="rfc.section.10.18"><a href="#rfc.section.10.18">10.18</a>&nbsp;<a id="header.content-type" href="#header.content-type">Content-Type</a></h2>
    3111       <p id="rfc.section.10.18.p.1">The "Content-Type" header field indicates the media type of the representation. In the case of responses to the HEAD method,
     3106      <h2 id="rfc.section.9.18"><a href="#rfc.section.9.18">9.18</a>&nbsp;<a id="header.content-type" href="#header.content-type">Content-Type</a></h2>
     3107      <p id="rfc.section.9.18.p.1">The "Content-Type" header field indicates the media type of the representation. In the case of responses to the HEAD method,
    31123108         the media type is that which would have been sent had the request been a GET.
    31133109      </p>
    31143110      <div id="rfc.figure.u.62"></div><pre class="inline"><span id="rfc.iref.g.61"></span>  <a href="#header.content-type" class="smpl">Content-Type</a> = <a href="#media.types" class="smpl">media-type</a>
    3115 </pre><p id="rfc.section.10.18.p.3">Media types are defined in <a href="#media.types" title="Media Types">Section&nbsp;6.5</a>. An example of the field is
     3111</pre><p id="rfc.section.9.18.p.3">Media types are defined in <a href="#media.types" title="Media Types">Section&nbsp;5.5</a>. An example of the field is
    31163112      </p>
    31173113      <div id="rfc.figure.u.63"></div><pre class="text">  Content-Type: text/html; charset=ISO-8859-4
    3118 </pre><p id="rfc.section.10.18.p.5">Further discussion of Content-Type is provided in <a href="#representation.data" title="Representation Data">Section&nbsp;8.2</a>.
    3119       </p>
    3120       <h1 id="rfc.section.11"><a href="#rfc.section.11">11.</a>&nbsp;<a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1>
    3121       <h2 id="rfc.section.11.1"><a href="#rfc.section.11.1">11.1</a>&nbsp;<a id="method.registration" href="#method.registration">Method Registry</a></h2>
    3122       <p id="rfc.section.11.1.p.1">The registration procedure for HTTP request methods is defined by <a href="#method.registry" title="Method Registry">Section&nbsp;2.2</a> of this document.
    3123       </p>
    3124       <p id="rfc.section.11.1.p.2">The HTTP Method Registry shall be created at &lt;<a href="http://www.iana.org/assignments/http-methods">http://www.iana.org/assignments/http-methods</a>&gt; and be populated with the registrations below:
     3114</pre><p id="rfc.section.9.18.p.5">Further discussion of Content-Type is provided in <a href="#representation.data" title="Representation Data">Section&nbsp;7.3</a>.
     3115      </p>
     3116      <h1 id="rfc.section.10"><a href="#rfc.section.10">10.</a>&nbsp;<a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1>
     3117      <h2 id="rfc.section.10.1"><a href="#rfc.section.10.1">10.1</a>&nbsp;<a id="method.registration" href="#method.registration">Method Registry</a></h2>
     3118      <p id="rfc.section.10.1.p.1">The registration procedure for HTTP request methods is defined by <a href="#method.registry" title="Method Registry">Section&nbsp;2.2</a> of this document.
     3119      </p>
     3120      <p id="rfc.section.10.1.p.2">The HTTP Method Registry shall be created at &lt;<a href="http://www.iana.org/assignments/http-methods">http://www.iana.org/assignments/http-methods</a>&gt; and be populated with the registrations below:
    31253121      </p>
    31263122      <div id="rfc.table.1">
    … …  
    31863182         </table>
    31873183      </div>
    3188       <h2 id="rfc.section.11.2"><a href="#rfc.section.11.2">11.2</a>&nbsp;<a id="status.code.registration" href="#status.code.registration">Status Code Registry</a></h2>
    3189       <p id="rfc.section.11.2.p.1">The registration procedure for HTTP Status Codes — 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.1"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a> — is now defined by <a href="#status.code.registry" title="Status Code Registry">Section&nbsp;4.2</a> of this document.
    3190       </p>
    3191       <p id="rfc.section.11.2.p.2">The HTTP Status Code Registry located at &lt;<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>&gt; shall be updated with the registrations below:
     3184      <h2 id="rfc.section.10.2"><a href="#rfc.section.10.2">10.2</a>&nbsp;<a id="status.code.registration" href="#status.code.registration">Status Code Registry</a></h2>
     3185      <p id="rfc.section.10.2.p.1">The registration procedure for HTTP Status Codes — 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.1"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a> — is now defined by <a href="#status.code.registry" title="Status Code Registry">Section&nbsp;4.2</a> of this document.
     3186      </p>
     3187      <p id="rfc.section.10.2.p.2">The HTTP Status Code Registry located at &lt;<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>&gt; shall be updated with the registrations below:
    31923188      </p>
    31933189      <div id="rfc.table.2">
    … …  
    34213417         </table>
    34223418      </div>
    3423       <h2 id="rfc.section.11.3"><a href="#rfc.section.11.3">11.3</a>&nbsp;<a id="header.field.registration" href="#header.field.registration">Header Field Registration</a></h2>
    3424       <p id="rfc.section.11.3.p.1">The Message Header Field Registry located at &lt;<a href="http://www.iana.org/assignments/message-headers/message-header-index.html">http://www.iana.org/assignments/message-headers/message-header-index.html</a>&gt; shall be updated with the permanent registrations below (see <a href="#RFC3864" id="rfc.xref.RFC3864.3"><cite title="Registration Procedures for Message Header Fields">[RFC3864]</cite></a>):
     3419      <h2 id="rfc.section.10.3"><a href="#rfc.section.10.3">10.3</a>&nbsp;<a id="header.field.registration" href="#header.field.registration">Header Field Registration</a></h2>
     3420      <p id="rfc.section.10.3.p.1">The Message Header Field Registry located at &lt;<a href="http://www.iana.org/assignments/message-headers/message-header-index.html">http://www.iana.org/assignments/message-headers/message-header-index.html</a>&gt; shall be updated with the permanent registrations below (see <a href="#RFC3864" id="rfc.xref.RFC3864.3"><cite title="Registration Procedures for Message Header Fields">[RFC3864]</cite></a>):
    34253421      </p>
    34263422      <div id="rfc.table.3">
    … …  
    34403436                  <td class="left">http</td>
    34413437                  <td class="left">standard</td>
    3442                   <td class="left"> <a href="#header.accept" id="rfc.xref.header.accept.4" title="Accept">Section&nbsp;10.11</a>
     3438                  <td class="left"> <a href="#header.accept" id="rfc.xref.header.accept.4" title="Accept">Section&nbsp;9.11</a>
    34433439                  </td>
    34443440               </tr>
    … …  
    34473443                  <td class="left">http</td>
    34483444                  <td class="left">standard</td>
    3449                   <td class="left"> <a href="#header.accept-charset" id="rfc.xref.header.accept-charset.3" title="Accept-Charset">Section&nbsp;10.12</a>
     3445                  <td class="left"> <a href="#header.accept-charset" id="rfc.xref.header.accept-charset.3" title="Accept-Charset">Section&nbsp;9.12</a>
    34503446                  </td>
    34513447               </tr>
    … …  
    34543450                  <td class="left">http</td>
    34553451                  <td class="left">standard</td>
    3456                   <td class="left"> <a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.4" title="Accept-Encoding">Section&nbsp;10.13</a>
     3452                  <td class="left"> <a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.4" title="Accept-Encoding">Section&nbsp;9.13</a>
    34573453                  </td>
    34583454               </tr>
    … …  
    34613457                  <td class="left">http</td>
    34623458                  <td class="left">standard</td>
    3463                   <td class="left"> <a href="#header.accept-language" id="rfc.xref.header.accept-language.3" title="Accept-Language">Section&nbsp;10.14</a>
     3459                  <td class="left"> <a href="#header.accept-language" id="rfc.xref.header.accept-language.3" title="Accept-Language">Section&nbsp;9.14</a>
    34643460                  </td>
    34653461               </tr>
    … …  
    34683464                  <td class="left">http</td>
    34693465                  <td class="left">standard</td>
    3470                   <td class="left"> <a href="#header.allow" id="rfc.xref.header.allow.3" title="Allow">Section&nbsp;10.1</a>
     3466                  <td class="left"> <a href="#header.allow" id="rfc.xref.header.allow.3" title="Allow">Section&nbsp;9.1</a>
    34713467                  </td>
    34723468               </tr>
    … …  
    34753471                  <td class="left">http</td>
    34763472                  <td class="left">standard</td>
    3477                   <td class="left"> <a href="#header.content-encoding" id="rfc.xref.header.content-encoding.4" title="Content-Encoding">Section&nbsp;10.15</a>
     3473                  <td class="left"> <a href="#header.content-encoding" id="rfc.xref.header.content-encoding.4" title="Content-Encoding">Section&nbsp;9.15</a>
    34783474                  </td>
    34793475               </tr>
    … …  
    34823478                  <td class="left">http</td>
    34833479                  <td class="left">standard</td>
    3484                   <td class="left"> <a href="#header.content-language" id="rfc.xref.header.content-language.2" title="Content-Language">Section&nbsp;10.16</a>
     3480                  <td class="left"> <a href="#header.content-language" id="rfc.xref.header.content-language.2" title="Content-Language">Section&nbsp;9.16</a>
    34853481                  </td>
    34863482               </tr>
    … …  
    34893485                  <td class="left">http</td>
    34903486                  <td class="left">standard</td>
    3491                   <td class="left"> <a href="#header.content-location" id="rfc.xref.header.content-location.4" title="Content-Location">Section&nbsp;10.17</a>
     3487                  <td class="left"> <a href="#header.content-location" id="rfc.xref.header.content-location.4" title="Content-Location">Section&nbsp;9.17</a>
    34923488                  </td>
    34933489               </tr>
    … …  
    34963492                  <td class="left">http</td>
    34973493                  <td class="left">standard</td>
    3498                   <td class="left"> <a href="#header.content-type" id="rfc.xref.header.content-type.5" title="Content-Type">Section&nbsp;10.18</a>
     3494                  <td class="left"> <a href="#header.content-type" id="rfc.xref.header.content-type.5" title="Content-Type">Section&nbsp;9.18</a>
    34993495                  </td>
    35003496               </tr>
    … …  
    35033499                  <td class="left">http</td>
    35043500                  <td class="left">standard</td>
    3505                   <td class="left"> <a href="#header.date" id="rfc.xref.header.date.2" title="Date">Section&nbsp;10.2</a>
     3501                  <td class="left"> <a href="#header.date" id="rfc.xref.header.date.2" title="Date">Section&nbsp;9.2</a>
    35063502                  </td>
    35073503               </tr>
    … …  
    35103506                  <td class="left">http</td>
    35113507                  <td class="left">standard</td>
    3512                   <td class="left"> <a href="#header.expect" id="rfc.xref.header.expect.3" title="Expect">Section&nbsp;10.3</a>
     3508                  <td class="left"> <a href="#header.expect" id="rfc.xref.header.expect.3" title="Expect">Section&nbsp;9.3</a>
    35133509                  </td>
    35143510               </tr>
    … …  
    35173513                  <td class="left">http</td>
    35183514                  <td class="left">standard</td>
    3519                   <td class="left"> <a href="#header.from" id="rfc.xref.header.from.2" title="From">Section&nbsp;10.4</a>
     3515                  <td class="left"> <a href="#header.from" id="rfc.xref.header.from.2" title="From">Section&nbsp;9.4</a>
    35203516                  </td>
    35213517               </tr>
    … …  
    35243520                  <td class="left">http</td>
    35253521                  <td class="left">standard</td>
    3526                   <td class="left"> <a href="#header.location" id="rfc.xref.header.location.4" title="Location">Section&nbsp;10.5</a>
     3522                  <td class="left"> <a href="#header.location" id="rfc.xref.header.location.4" title="Location">Section&nbsp;9.5</a>
    35273523                  </td>
    35283524               </tr>
    … …  
    35383534                  <td class="left">http</td>
    35393535                  <td class="left">standard</td>
    3540                   <td class="left"> <a href="#header.max-forwards" id="rfc.xref.header.max-forwards.4" title="Max-Forwards">Section&nbsp;10.6</a>
     3536                  <td class="left"> <a href="#header.max-forwards" id="rfc.xref.header.max-forwards.4" title="Max-Forwards">Section&nbsp;9.6</a>
    35413537                  </td>
    35423538               </tr>
    … …  
    35453541                  <td class="left">http</td>
    35463542                  <td class="left">standard</td>
    3547                   <td class="left"> <a href="#header.referer" id="rfc.xref.header.referer.2" title="Referer">Section&nbsp;10.7</a>
     3543                  <td class="left"> <a href="#header.referer" id="rfc.xref.header.referer.2" title="Referer">Section&nbsp;9.7</a>
    35483544                  </td>
    35493545               </tr>
    … …  
    35523548                  <td class="left">http</td>
    35533549                  <td class="left">standard</td>
    3554                   <td class="left"> <a href="#header.retry-after" id="rfc.xref.header.retry-after.3" title="Retry-After">Section&nbsp;10.8</a>
     3550                  <td class="left"> <a href="#header.retry-after" id="rfc.xref.header.retry-after.3" title="Retry-After">Section&nbsp;9.8</a>
    35553551                  </td>
    35563552               </tr>
    … …  
    35593555                  <td class="left">http</td>
    35603556                  <td class="left">standard</td>
    3561                   <td class="left"> <a href="#header.server" id="rfc.xref.header.server.2" title="Server">Section&nbsp;10.9</a>
     3557                  <td class="left"> <a href="#header.server" id="rfc.xref.header.server.2" title="Server">Section&nbsp;9.9</a>
    35623558                  </td>
    35633559               </tr>
    … …  
    35663562                  <td class="left">http</td>
    35673563                  <td class="left">standard</td>
    3568                   <td class="left"> <a href="#header.user-agent" id="rfc.xref.header.user-agent.3" title="User-Agent">Section&nbsp;10.10</a>
     3564                  <td class="left"> <a href="#header.user-agent" id="rfc.xref.header.user-agent.3" title="User-Agent">Section&nbsp;9.10</a>
    35693565                  </td>
    35703566               </tr>
    … …  
    35723568         </table>
    35733569      </div>
    3574       <p id="rfc.section.11.3.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
    3575       <h2 id="rfc.section.11.4"><a href="#rfc.section.11.4">11.4</a>&nbsp;<a id="content.coding.registration" href="#content.coding.registration">Content Coding Registry</a></h2>
    3576       <p id="rfc.section.11.4.p.1">The registration procedure for HTTP Content Codings is now defined by <a href="#content.coding.registry" title="Content Coding Registry">Section&nbsp;6.4.1</a> of this document.
    3577       </p>
    3578       <p id="rfc.section.11.4.p.2">The HTTP Content Codings Registry located at &lt;<a href="http://www.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http-parameters</a>&gt; shall be updated with the registration below:
     3570      <p id="rfc.section.10.3.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
     3571      <h2 id="rfc.section.10.4"><a href="#rfc.section.10.4">10.4</a>&nbsp;<a id="content.coding.registration" href="#content.coding.registration">Content Coding Registry</a></h2>
     3572      <p id="rfc.section.10.4.p.1">The registration procedure for HTTP Content Codings is now defined by <a href="#content.coding.registry" title="Content Coding Registry">Section&nbsp;5.4.1</a> of this document.
     3573      </p>
     3574      <p id="rfc.section.10.4.p.2">The HTTP Content Codings Registry located at &lt;<a href="http://www.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http-parameters</a>&gt; shall be updated with the registration below:
    35793575      </p>
    35803576      <div id="rfc.table.4">
    … …  
    36113607                  <td class="left">identity</td>
    36123608                  <td class="left">reserved (synonym for "no encoding" in Accept-Encoding header field)</td>
    3613                   <td class="left"> <a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.5" title="Accept-Encoding">Section&nbsp;10.13</a>
     3609                  <td class="left"> <a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.5" title="Accept-Encoding">Section&nbsp;9.13</a>
    36143610                  </td>
    36153611               </tr>
    … …  
    36173613         </table>
    36183614      </div>
    3619       <h1 id="rfc.section.12"><a href="#rfc.section.12">12.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>
    3620       <p id="rfc.section.12.p.1">This section is meant to inform application developers, information providers, and users of the security limitations in HTTP/1.1
     3615      <h1 id="rfc.section.11"><a href="#rfc.section.11">11.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>
     3616      <p id="rfc.section.11.p.1">This section is meant to inform application developers, information providers, and users of the security limitations in HTTP/1.1
    36213617         as described by this document. The discussion does not include definitive solutions to the problems revealed, though it does
    36223618         make some suggestions for reducing security risks.
    36233619      </p>
    3624       <h2 id="rfc.section.12.1"><a href="#rfc.section.12.1">12.1</a>&nbsp;<a id="security.sensitive" href="#security.sensitive">Transfer of Sensitive Information</a></h2>
    3625       <p id="rfc.section.12.1.p.1">Like any generic data transfer protocol, HTTP cannot regulate the content of the data that is transferred, nor is there any
     3620      <h2 id="rfc.section.11.1"><a href="#rfc.section.11.1">11.1</a>&nbsp;<a id="security.sensitive" href="#security.sensitive">Transfer of Sensitive Information</a></h2>
     3621      <p id="rfc.section.11.1.p.1">Like any generic data transfer protocol, HTTP cannot regulate the content of the data that is transferred, nor is there any
    36263622         a priori method of determining the sensitivity of any particular piece of information within the context of any given request.
    36273623         Therefore, applications <em class="bcp14">SHOULD</em> supply as much control over this information as possible to the provider of that information. Four header fields are worth
    36283624         special mention in this context: Server, Via, Referer and From.
    36293625      </p>
    3630       <p id="rfc.section.12.1.p.2">Revealing the specific software version of the server might allow the server machine to become more vulnerable to attacks
     3626      <p id="rfc.section.11.1.p.2">Revealing the specific software version of the server might allow the server machine to become more vulnerable to attacks
    36313627         against software that is known to contain security holes. Implementors <em class="bcp14">SHOULD</em> make the Server header field a configurable option.
    36323628      </p>
    3633       <p id="rfc.section.12.1.p.3">Proxies which serve as a portal through a network firewall <em class="bcp14">SHOULD</em> take special precautions regarding the transfer of header information that identifies the hosts behind the firewall. In particular,
     3629      <p id="rfc.section.11.1.p.3">Proxies which serve as a portal through a network firewall <em class="bcp14">SHOULD</em> take special precautions regarding the transfer of header information that identifies the hosts behind the firewall. In particular,
    36343630         they <em class="bcp14">SHOULD</em> remove, or replace with sanitized versions, any Via fields generated behind the firewall.
    36353631      </p>
    3636       <p id="rfc.section.12.1.p.4">The Referer header field allows reading patterns to be studied and reverse links drawn. Although it can be very useful, its
     3632      <p id="rfc.section.11.1.p.4">The Referer header field allows reading patterns to be studied and reverse links drawn. Although it can be very useful, its
    36373633         power can be abused if user details are not separated from the information contained in the Referer. Even when the personal
    36383634         information has been removed, the Referer header field might indicate a private document's URI whose publication would be
    36393635         inappropriate.
    36403636      </p>
    3641       <p id="rfc.section.12.1.p.5">The information sent in the From field might conflict with the user's privacy interests or their site's security policy, and
     3637      <p id="rfc.section.11.1.p.5">The information sent in the From field might conflict with the user's privacy interests or their site's security policy, and
    36423638         hence it <em class="bcp14">SHOULD NOT</em> be transmitted without the user being able to disable, enable, and modify the contents of the field. The user <em class="bcp14">MUST</em> be able to set the contents of this field within a user preference or application defaults configuration.
    36433639      </p>
    3644       <p id="rfc.section.12.1.p.6">We suggest, though do not require, that a convenient toggle interface be provided for the user to enable or disable the sending
     3640      <p id="rfc.section.11.1.p.6">We suggest, though do not require, that a convenient toggle interface be provided for the user to enable or disable the sending
    36453641         of From and Referer information.
    36463642      </p>
    3647       <p id="rfc.section.12.1.p.7">The User-Agent (<a href="#header.user-agent" id="rfc.xref.header.user-agent.4" title="User-Agent">Section&nbsp;10.10</a>) or Server (<a href="#header.server" id="rfc.xref.header.server.3" title="Server">Section&nbsp;10.9</a>) header fields can sometimes be used to determine that a specific client or server has a particular security hole which might
     3643      <p id="rfc.section.11.1.p.7">The User-Agent (<a href="#header.user-agent" id="rfc.xref.header.user-agent.4" title="User-Agent">Section&nbsp;9.10</a>) or Server (<a href="#header.server" id="rfc.xref.header.server.3" title="Server">Section&nbsp;9.9</a>) header fields can sometimes be used to determine that a specific client or server has a particular security hole which might
    36483644         be exploited. Unfortunately, this same information is often used for other valuable purposes for which HTTP currently has
    36493645         no better mechanism.
    36503646      </p>
    3651       <p id="rfc.section.12.1.p.8">Furthermore, the User-Agent header field may contain enough entropy to be used, possibly in conjunction with other material,
     3647      <p id="rfc.section.11.1.p.8">Furthermore, the User-Agent header field may contain enough entropy to be used, possibly in conjunction with other material,
    36523648         to uniquely identify the user.
    36533649      </p>
    3654       <p id="rfc.section.12.1.p.9">Some request methods, like TRACE (<a href="#TRACE" id="rfc.xref.TRACE.3" title="TRACE">Section&nbsp;2.3.7</a>), expose information that was sent in request header fields within the body of their response. Clients <em class="bcp14">SHOULD</em> be careful with sensitive information, like Cookies, Authorization credentials, and other header fields that might be used
     3650      <p id="rfc.section.11.1.p.9">Some request methods, like TRACE (<a href="#TRACE" id="rfc.xref.TRACE.3" title="TRACE">Section&nbsp;2.3.7</a>), expose information that was sent in request header fields within the body of their response. Clients <em class="bcp14">SHOULD</em> be careful with sensitive information, like Cookies, Authorization credentials, and other header fields that might be used
    36553651         to collect data from the client.
    36563652      </p>
    3657       <h2 id="rfc.section.12.2"><a href="#rfc.section.12.2">12.2</a>&nbsp;<a id="encoding.sensitive.information.in.uris" href="#encoding.sensitive.information.in.uris">Encoding Sensitive Information in URIs</a></h2>
    3658       <p id="rfc.section.12.2.p.1">Because the source of a link might be private information or might reveal an otherwise private information source, it is strongly
     3653      <h2 id="rfc.section.11.2"><a href="#rfc.section.11.2">11.2</a>&nbsp;<a id="encoding.sensitive.information.in.uris" href="#encoding.sensitive.information.in.uris">Encoding Sensitive Information in URIs</a></h2>
     3654      <p id="rfc.section.11.2.p.1">Because the source of a link might be private information or might reveal an otherwise private information source, it is strongly
    36593655         recommended that the user be able to select whether or not the Referer field is sent. For example, a browser client could
    36603656         have a toggle switch for browsing openly/anonymously, which would respectively enable/disable the sending of Referer and From
    36613657         information.
    36623658      </p>
    3663       <p id="rfc.section.12.2.p.2">Clients <em class="bcp14">SHOULD NOT</em> include a Referer header field in a (non-secure) HTTP request if the referring page was transferred with a secure protocol.
    3664       </p>
    3665       <p id="rfc.section.12.2.p.3">Authors of services <em class="bcp14">SHOULD NOT</em> use GET-based forms for the submission of sensitive data because that data will be placed in the request-target. Many existing
     3659      <p id="rfc.section.11.2.p.2">Clients <em class="bcp14">SHOULD NOT</em> include a Referer header field in a (non-secure) HTTP request if the referring page was transferred with a secure protocol.
     3660      </p>
     3661      <p id="rfc.section.11.2.p.3">Authors of services <em class="bcp14">SHOULD NOT</em> use GET-based forms for the submission of sensitive data because that data will be placed in the request-target. Many existing
    36663662         servers, proxies, and user agents log or display the request-target in places where it might be visible to third parties.
    36673663         Such services can use POST-based form submission instead.
    36683664      </p>
    3669       <h2 id="rfc.section.12.3"><a href="#rfc.section.12.3">12.3</a>&nbsp;<a id="location.spoofing-leakage" href="#location.spoofing-leakage">Location Header Fields: Spoofing and Information Leakage</a></h2>
    3670       <p id="rfc.section.12.3.p.1">If a single server supports multiple organizations that do not trust one another, then it <em class="bcp14">MUST</em> check the values of Location and Content-Location header fields in responses that are generated under control of said organizations
     3665      <h2 id="rfc.section.11.3"><a href="#rfc.section.11.3">11.3</a>&nbsp;<a id="location.spoofing-leakage" href="#location.spoofing-leakage">Location Header Fields: Spoofing and Information Leakage</a></h2>
     3666      <p id="rfc.section.11.3.p.1">If a single server supports multiple organizations that do not trust one another, then it <em class="bcp14">MUST</em> check the values of Location and Content-Location header fields in responses that are generated under control of said organizations
    36713667         to make sure that they do not attempt to invalidate resources over which they have no authority.
    36723668      </p>
    3673       <p id="rfc.section.12.3.p.2">Furthermore, appending the fragment identifier from one URI to another one obtained from a Location header field might leak
     3669      <p id="rfc.section.11.3.p.2">Furthermore, appending the fragment identifier from one URI to another one obtained from a Location header field might leak
    36743670         confidential information to the target server — although the fragment identifier is not transmitted in the final request,
    36753671         it might be visible to the user agent through other means, such as scripting.
    36763672      </p>
    3677       <h2 id="rfc.section.12.4"><a href="#rfc.section.12.4">12.4</a>&nbsp;Security Considerations for CONNECT
     3673      <h2 id="rfc.section.11.4"><a href="#rfc.section.11.4">11.4</a>&nbsp;Security Considerations for CONNECT
    36783674      </h2>
    3679       <p id="rfc.section.12.4.p.1">Since tunneled data is opaque to the proxy, there are additional risks to tunneling to other well-known or reserved ports.
     3675      <p id="rfc.section.11.4.p.1">Since tunneled data is opaque to the proxy, there are additional risks to tunneling to other well-known or reserved ports.
    36803676         A HTTP client CONNECTing to port 25 could relay spam via SMTP, for example. As such, proxies <em class="bcp14">SHOULD</em> restrict CONNECT access to a small number of known ports.
    36813677      </p>
    3682       <h2 id="rfc.section.12.5"><a href="#rfc.section.12.5">12.5</a>&nbsp;<a id="privacy.issues.connected.to.accept.header.fields" href="#privacy.issues.connected.to.accept.header.fields">Privacy Issues Connected to Accept Header Fields</a></h2>
    3683       <p id="rfc.section.12.5.p.1">Accept header fields can reveal information about the user to all servers which are accessed. The Accept-Language header field
     3678      <h2 id="rfc.section.11.5"><a href="#rfc.section.11.5">11.5</a>&nbsp;<a id="privacy.issues.connected.to.accept.header.fields" href="#privacy.issues.connected.to.accept.header.fields">Privacy Issues Connected to Accept Header Fields</a></h2>
     3679      <p id="rfc.section.11.5.p.1">Accept header fields can reveal information about the user to all servers which are accessed. The Accept-Language header field
    36843680         in particular can reveal information the user would consider to be of a private nature, because the understanding of particular
    36853681         languages is often strongly correlated to the membership of a particular ethnic group. User agents which offer the option
    … …  
    36873683         configuration process include a message which makes the user aware of the loss of privacy involved.
    36883684      </p>
    3689       <p id="rfc.section.12.5.p.2">An approach that limits the loss of privacy would be for a user agent to omit the sending of Accept-Language header fields
     3685      <p id="rfc.section.11.5.p.2">An approach that limits the loss of privacy would be for a user agent to omit the sending of Accept-Language header fields
    36903686         by default, and to ask the user whether or not to start sending Accept-Language header fields to a server if it detects, by
    36913687         looking for any Vary header fields generated by the server, that such sending could improve the quality of service.
    36923688      </p>
    3693       <p id="rfc.section.12.5.p.3">Elaborate user-customized accept header fields sent in every request, in particular if these include quality values, can be
     3689      <p id="rfc.section.11.5.p.3">Elaborate user-customized accept header fields sent in every request, in particular if these include quality values, can be
    36943690         used by servers as relatively reliable and long-lived user identifiers. Such user identifiers would allow content providers
    36953691         to do click-trail tracking, and would allow collaborating content providers to match cross-server click-trails or form submissions
    … …  
    36993695         filter the accept header fields in relayed requests. General purpose user agents which provide a high degree of header configurability <em class="bcp14">SHOULD</em> warn users about the loss of privacy which can be involved.
    37003696      </p>
    3701       <h1 id="rfc.section.13"><a href="#rfc.section.13">13.</a>&nbsp;<a id="acks" href="#acks">Acknowledgments</a></h1>
    3702       <p id="rfc.section.13.p.1">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 9</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>.
    3703       </p>
    3704       <h1 id="rfc.references"><a id="rfc.section.14" href="#rfc.section.14">14.</a> References
     3697      <h1 id="rfc.section.12"><a href="#rfc.section.12">12.</a>&nbsp;<a id="acks" href="#acks">Acknowledgments</a></h1>
     3698      <p id="rfc.section.12.p.1">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 9</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>.
     3699      </p>
     3700      <h1 id="rfc.references"><a id="rfc.section.13" href="#rfc.section.13">13.</a> References
    37053701      </h1>
    3706       <h2 id="rfc.references.1"><a href="#rfc.section.14.1" id="rfc.section.14.1">14.1</a> Normative References
     3702      <h2 id="rfc.references.1"><a href="#rfc.section.13.1" id="rfc.section.13.1">13.1</a> Normative References
    37073703      </h2>
    37083704      <table>                                 
    … …  
    37933789         </tr>
    37943790      </table>
    3795       <h2 id="rfc.references.2"><a href="#rfc.section.14.2" id="rfc.section.14.2">14.2</a> Informative References
     3791      <h2 id="rfc.references.2"><a href="#rfc.section.13.2" id="rfc.section.13.2">13.2</a> Informative References
    37963792      </h2>
    37973793      <table>                                     
    … …  
    39263922      </p>
    39273923      <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>
    3928       <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.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
     3924      <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;5.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
    39293925         break sequences. HTTP allows CRLF, bare CR, and bare LF to indicate a line break within text content when a message is transmitted
    39303926         over HTTP.
    39313927      </p>
    3932       <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
     3928      <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;5.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
    39333929         a Content-Encoding and by the fact that HTTP allows the use of some character encodings which do not use octets 13 and 10
    39343930         to represent CR and LF, respectively, as is the case for some multi-byte character encodings.
    … …  
    39383934      </p>
    39393935      <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>
    3940       <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.
     3936      <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;5.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.
    39413937      </p>
    39423938      <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>
    … …  
    39623958      <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
    39633959         fold long lines. MHTML messages being transported by HTTP follow all conventions of MHTML, including line length limitations
    3964          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.
     3960         and folding, canonicalization, etc., since HTTP transports all message-bodies as payload (see <a href="#multipart.types" title="Multipart Types">Section&nbsp;5.5.2</a>) and does not interpret the content or any MIME header lines that might be contained therein.
    39653961      </p>
    39663962      <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="additional.features" href="#additional.features">Additional Features</a></h1>
    … …  
    39953991      <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>)
    39963992      </p>
    3997       <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;10</a>)
     3993      <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;9</a>)
    39983994      </p>
    39993995      <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
    4000          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;10.1</a>)
     3996         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;9.1</a>)
    40013997      </p>
    40023998      <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
    4003          (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;10.3</a>)
     3999         (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;9.3</a>)
    40044000      </p>
    40054001      <p id="rfc.section.C.p.13">Correct syntax of Location header field to allow URI references (including relative references and fragments), as referred
    40064002         symbol "absoluteURI" wasn't what was expected, and add some clarifications as to when use of fragments would not be appropriate.
    4007          (<a href="#header.location" id="rfc.xref.header.location.5" title="Location">Section&nbsp;10.5</a>)
    4008       </p>
    4009       <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;10.6</a>)
    4010       </p>
    4011       <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;10.7</a>)
     4003         (<a href="#header.location" id="rfc.xref.header.location.5" title="Location">Section&nbsp;9.5</a>)
     4004      </p>
     4005      <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;9.6</a>)
     4006      </p>
     4007      <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;9.7</a>)
    40124008      </p>
    40134009      <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
    4014          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.57"><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;10.9</a>)
    4015       </p>
    4016       <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>)
    4017       </p>
    4018       <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>)
    4019       </p>
    4020       <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>)
    4021       </p>
    4022       <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;10</a>)
     4010         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.57"><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;9.9</a>)
     4011      </p>
     4012      <p id="rfc.section.C.p.17">Clarify contexts that charset is used in. (<a href="#character.sets" title="Character Encodings (charset)">Section&nbsp;5.3</a>)
     4013      </p>
     4014      <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;5.4.1</a>)
     4015      </p>
     4016      <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;5.5.1</a>)
     4017      </p>
     4018      <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;9</a>)
    40234019      </p>
    40244020      <p id="rfc.section.C.p.21">Remove definition of Content-MD5 header field because it was inconsistently implemented with respect to partial responses,
    4025          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;10</a>)
    4026       </p>
    4027       <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.4" title="Accept-Charset">Section&nbsp;10.12</a>)
     4021         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;9</a>)
     4022      </p>
     4023      <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.4" title="Accept-Charset">Section&nbsp;9.12</a>)
    40284024      </p>
    40294025      <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
    40304026         servers emitting bogus Content-Location header fields, and also the potentially undesirable effect of potentially breaking
    4031          relative links in content-negotiated resources. (<a href="#header.content-location" id="rfc.xref.header.content-location.5" title="Content-Location">Section&nbsp;10.17</a>)
     4027         relative links in content-negotiated resources. (<a href="#header.content-location" id="rfc.xref.header.content-location.5" title="Content-Location">Section&nbsp;9.17</a>)
    40324028      </p>
    40334029      <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>)
    … …  
    47544750         <ul class="ind">
    47554751            <li><a id="rfc.index.1" href="#rfc.index.1"><b>1</b></a><ul>
    4756                   <li>100 Continue (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.100.1">4.1</a>, <a href="#rfc.iref.24"><b>4.3.1</b></a>, <a href="#rfc.xref.status.100.2">11.2</a></li>
    4757                   <li>100-continue (expect value)&nbsp;&nbsp;<a href="#rfc.iref.108"><b>10.3</b></a></li>
    4758                   <li>101 Switching Protocols (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.101.1">4.1</a>, <a href="#rfc.iref.25"><b>4.3.2</b></a>, <a href="#rfc.xref.status.101.2">11.2</a></li>
     4752                  <li>100 Continue (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.100.1">4.1</a>, <a href="#rfc.iref.24"><b>4.3.1</b></a>, <a href="#rfc.xref.status.100.2">10.2</a></li>
     4753                  <li>100-continue (expect value)&nbsp;&nbsp;<a href="#rfc.iref.108"><b>9.3</b></a></li>
     4754                  <li>101 Switching Protocols (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.101.1">4.1</a>, <a href="#rfc.iref.25"><b>4.3.2</b></a>, <a href="#rfc.xref.status.101.2">10.2</a></li>
    47594755               </ul>
    47604756            </li>
    47614757            <li><a id="rfc.index.2" href="#rfc.index.2"><b>2</b></a><ul>
    4762                   <li>200 OK (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.200.1">4.1</a>, <a href="#rfc.iref.26"><b>4.4.1</b></a>, <a href="#rfc.xref.status.200.2">11.2</a></li>
    4763                   <li>201 Created (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.201.1">4.1</a>, <a href="#rfc.iref.27"><b>4.4.2</b></a>, <a href="#rfc.xref.status.201.2">11.2</a></li>
    4764                   <li>202 Accepted (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.202.1">4.1</a>, <a href="#rfc.iref.28"><b>4.4.3</b></a>, <a href="#rfc.xref.status.202.2">11.2</a></li>
    4765                   <li>203 Non-Authoritative Information (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.203.1">4.1</a>, <a href="#rfc.iref.29"><b>4.4.4</b></a>, <a href="#rfc.xref.status.203.2">11.2</a>, <a href="#rfc.xref.status.203.3">C</a></li>
    4766                   <li>204 No Content (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.204.1">4.1</a>, <a href="#rfc.iref.30"><b>4.4.5</b></a>, <a href="#rfc.xref.status.204.2">11.2</a></li>
    4767                   <li>205 Reset Content (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.205.1">4.1</a>, <a href="#rfc.iref.31"><b>4.4.6</b></a>, <a href="#rfc.xref.status.205.2">11.2</a></li>
     4758                  <li>200 OK (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.200.1">4.1</a>, <a href="#rfc.iref.26"><b>4.4.1</b></a>, <a href="#rfc.xref.status.200.2">10.2</a></li>
     4759                  <li>201 Created (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.201.1">4.1</a>, <a href="#rfc.iref.27"><b>4.4.2</b></a>, <a href="#rfc.xref.status.201.2">10.2</a></li>
     4760                  <li>202 Accepted (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.202.1">4.1</a>, <a href="#rfc.iref.28"><b>4.4.3</b></a>, <a href="#rfc.xref.status.202.2">10.2</a></li>
     4761                  <li>203 Non-Authoritative Information (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.203.1">4.1</a>, <a href="#rfc.iref.29"><b>4.4.4</b></a>, <a href="#rfc.xref.status.203.2">10.2</a>, <a href="#rfc.xref.status.203.3">C</a></li>
     4762                  <li>204 No Content (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.204.1">4.1</a>, <a href="#rfc.iref.30"><b>4.4.5</b></a>, <a href="#rfc.xref.status.204.2">10.2</a></li>
     4763                  <li>205 Reset Content (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.205.1">4.1</a>, <a href="#rfc.iref.31"><b>4.4.6</b></a>, <a href="#rfc.xref.status.205.2">10.2</a></li>
    47684764               </ul>
    47694765            </li>
    47704766            <li><a id="rfc.index.3" href="#rfc.index.3"><b>3</b></a><ul>
    4771                   <li>300 Multiple Choices (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.300.1">4.1</a>, <a href="#rfc.iref.32"><b>4.5.1</b></a>, <a href="#rfc.xref.status.300.2">11.2</a></li>
    4772                   <li>301 Moved Permanently (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.301.1">4.1</a>, <a href="#rfc.iref.33"><b>4.5.2</b></a>, <a href="#rfc.xref.status.301.2">11.2</a>, <a href="#rfc.xref.status.301.3">C</a></li>
    4773                   <li>302 Found (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.302.1">4.1</a>, <a href="#rfc.iref.34"><b>4.5.3</b></a>, <a href="#rfc.xref.status.302.2">11.2</a>, <a href="#rfc.xref.status.302.3">C</a></li>
    4774                   <li>303 See Other (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.303.1">4.1</a>, <a href="#rfc.iref.35"><b>4.5.4</b></a>, <a href="#rfc.xref.status.303.2">11.2</a></li>
    4775                   <li>305 Use Proxy (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.305.1">4.1</a>, <a href="#rfc.iref.36"><b>4.5.5</b></a>, <a href="#rfc.xref.status.305.2">11.2</a>, <a href="#rfc.xref.status.305.3">C</a></li>
    4776                   <li>306 (Unused) (status code)&nbsp;&nbsp;<a href="#rfc.iref.37"><b>4.5.6</b></a>, <a href="#rfc.xref.status.306.1">11.2</a></li>
    4777                   <li>307 Temporary Redirect (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.307.1">4.1</a>, <a href="#rfc.iref.38"><b>4.5.7</b></a>, <a href="#rfc.xref.status.307.2">11.2</a>, <a href="#rfc.xref.status.307.3">C</a></li>
     4767                  <li>300 Multiple Choices (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.300.1">4.1</a>, <a href="#rfc.iref.32"><b>4.5.1</b></a>, <a href="#rfc.xref.status.300.2">10.2</a></li>
     4768                  <li>301 Moved Permanently (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.301.1">4.1</a>, <a href="#rfc.iref.33"><b>4.5.2</b></a>, <a href="#rfc.xref.status.301.2">10.2</a>, <a href="#rfc.xref.status.301.3">C</a></li>
     4769                  <li>302 Found (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.302.1">4.1</a>, <a href="#rfc.iref.34"><b>4.5.3</b></a>, <a href="#rfc.xref.status.302.2">10.2</a>, <a href="#rfc.xref.status.302.3">C</a></li>
     4770                  <li>303 See Other (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.303.1">4.1</a>, <a href="#rfc.iref.35"><b>4.5.4</b></a>, <a href="#rfc.xref.status.303.2">10.2</a></li>
     4771                  <li>305 Use Proxy (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.305.1">4.1</a>, <a href="#rfc.iref.36"><b>4.5.5</b></a>, <a href="#rfc.xref.status.305.2">10.2</a>, <a href="#rfc.xref.status.305.3">C</a></li>
     4772                  <li>306 (Unused) (status code)&nbsp;&nbsp;<a href="#rfc.iref.37"><b>4.5.6</b></a>, <a href="#rfc.xref.status.306.1">10.2</a></li>
     4773                  <li>307 Temporary Redirect (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.307.1">4.1</a>, <a href="#rfc.iref.38"><b>4.5.7</b></a>, <a href="#rfc.xref.status.307.2">10.2</a>, <a href="#rfc.xref.status.307.3">C</a></li>
    47784774               </ul>
    47794775            </li>
    47804776            <li><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul>
    4781                   <li>400 Bad Request (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.400.1">4.1</a>, <a href="#rfc.iref.39"><b>4.6.1</b></a>, <a href="#rfc.xref.status.400.2">11.2</a></li>
    4782                   <li>402 Payment Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.402.1">4.1</a>, <a href="#rfc.iref.40"><b>4.6.2</b></a>, <a href="#rfc.xref.status.402.2">11.2</a></li>
    4783                   <li>403 Forbidden (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.403.1">4.1</a>, <a href="#rfc.iref.41"><b>4.6.3</b></a>, <a href="#rfc.xref.status.403.2">11.2</a></li>
    4784                   <li>404 Not Found (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.404.1">4.1</a>, <a href="#rfc.iref.42"><b>4.6.4</b></a>, <a href="#rfc.xref.status.404.2">11.2</a></li>
    4785                   <li>405 Method Not Allowed (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.405.1">4.1</a>, <a href="#rfc.iref.43"><b>4.6.5</b></a>, <a href="#rfc.xref.status.405.2">11.2</a></li>
    4786                   <li>406 Not Acceptable (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.406.1">4.1</a>, <a href="#rfc.iref.44"><b>4.6.6</b></a>, <a href="#rfc.xref.status.406.2">11.2</a></li>
    4787                   <li>408 Request Timeout (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.408.1">4.1</a>, <a href="#rfc.iref.45"><b>4.6.7</b></a>, <a href="#rfc.xref.status.408.2">11.2</a></li>
    4788                   <li>409 Conflict (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.409.1">4.1</a>, <a href="#rfc.iref.46"><b>4.6.8</b></a>, <a href="#rfc.xref.status.409.2">11.2</a></li>
    4789                   <li>410 Gone (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.410.1">4.1</a>, <a href="#rfc.iref.47"><b>4.6.9</b></a>, <a href="#rfc.xref.status.410.2">11.2</a></li>
    4790                   <li>411 Length Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.411.1">4.1</a>, <a href="#rfc.iref.48"><b>4.6.10</b></a>, <a href="#rfc.xref.status.411.2">11.2</a></li>
    4791                   <li>413 Request Representation Too Large (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.413.1">4.1</a>, <a href="#rfc.iref.49"><b>4.6.11</b></a>, <a href="#rfc.xref.status.413.2">11.2</a></li>
    4792                   <li>414 URI Too Long (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.414.1">4.1</a>, <a href="#rfc.iref.50"><b>4.6.12</b></a>, <a href="#rfc.xref.status.414.2">11.2</a></li>
    4793                   <li>415 Unsupported Media Type (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.415.1">4.1</a>, <a href="#rfc.iref.51"><b>4.6.13</b></a>, <a href="#rfc.xref.status.415.2">11.2</a></li>
    4794                   <li>417 Expectation Failed (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.417.1">4.1</a>, <a href="#rfc.iref.52"><b>4.6.14</b></a>, <a href="#rfc.xref.status.417.2">11.2</a></li>
    4795                   <li>426 Upgrade Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.426.1">4.1</a>, <a href="#rfc.iref.53"><b>4.6.15</b></a>, <a href="#rfc.xref.status.426.2">11.2</a>, <a href="#rfc.xref.status.426.3">C</a></li>
     4777                  <li>400 Bad Request (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.400.1">4.1</a>, <a href="#rfc.iref.39"><b>4.6.1</b></a>, <a href="#rfc.xref.status.400.2">10.2</a></li>
     4778                  <li>402 Payment Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.402.1">4.1</a>, <a href="#rfc.iref.40"><b>4.6.2</b></a>, <a href="#rfc.xref.status.402.2">10.2</a></li>
     4779                  <li>403 Forbidden (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.403.1">4.1</a>, <a href="#rfc.iref.41"><b>4.6.3</b></a>, <a href="#rfc.xref.status.403.2">10.2</a></li>
     4780                  <li>404 Not Found (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.404.1">4.1</a>, <a href="#rfc.iref.42"><b>4.6.4</b></a>, <a href="#rfc.xref.status.404.2">10.2</a></li>
     4781                  <li>405 Method Not Allowed (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.405.1">4.1</a>, <a href="#rfc.iref.43"><b>4.6.5</b></a>, <a href="#rfc.xref.status.405.2">10.2</a></li>
     4782                  <li>406 Not Acceptable (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.406.1">4.1</a>, <a href="#rfc.iref.44"><b>4.6.6</b></a>, <a href="#rfc.xref.status.406.2">10.2</a></li>
     4783                  <li>408 Request Timeout (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.408.1">4.1</a>, <a href="#rfc.iref.45"><b>4.6.7</b></a>, <a href="#rfc.xref.status.408.2">10.2</a></li>
     4784                  <li>409 Conflict (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.409.1">4.1</a>, <a href="#rfc.iref.46"><b>4.6.8</b></a>, <a href="#rfc.xref.status.409.2">10.2</a></li>
     4785                  <li>410 Gone (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.410.1">4.1</a>, <a href="#rfc.iref.47"><b>4.6.9</b></a>, <a href="#rfc.xref.status.410.2">10.2</a></li>
     4786                  <li>411 Length Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.411.1">4.1</a>, <a href="#rfc.iref.48"><b>4.6.10</b></a>, <a href="#rfc.xref.status.411.2">10.2</a></li>
     4787                  <li>413 Request Representation Too Large (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.413.1">4.1</a>, <a href="#rfc.iref.49"><b>4.6.11</b></a>, <a href="#rfc.xref.status.413.2">10.2</a></li>
     4788                  <li>414 URI Too Long (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.414.1">4.1</a>, <a href="#rfc.iref.50"><b>4.6.12</b></a>, <a href="#rfc.xref.status.414.2">10.2</a></li>
     4789                  <li>415 Unsupported Media Type (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.415.1">4.1</a>, <a href="#rfc.iref.51"><b>4.6.13</b></a>, <a href="#rfc.xref.status.415.2">10.2</a></li>
     4790                  <li>417 Expectation Failed (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.417.1">4.1</a>, <a href="#rfc.iref.52"><b>4.6.14</b></a>, <a href="#rfc.xref.status.417.2">10.2</a></li>
     4791                  <li>426 Upgrade Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.426.1">4.1</a>, <a href="#rfc.iref.53"><b>4.6.15</b></a>, <a href="#rfc.xref.status.426.2">10.2</a>, <a href="#rfc.xref.status.426.3">C</a></li>
    47964792               </ul>
    47974793            </li>
    47984794            <li><a id="rfc.index.5" href="#rfc.index.5"><b>5</b></a><ul>
    4799                   <li>500 Internal Server Error (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.500.1">4.1</a>, <a href="#rfc.iref.54"><b>4.7.1</b></a>, <a href="#rfc.xref.status.500.2">11.2</a></li>
    4800                   <li>501 Not Implemented (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.501.1">4.1</a>, <a href="#rfc.iref.55"><b>4.7.2</b></a>, <a href="#rfc.xref.status.501.2">11.2</a></li>
    4801                   <li>502 Bad Gateway (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.502.1">4.1</a>, <a href="#rfc.iref.56"><b>4.7.3</b></a>, <a href="#rfc.xref.status.502.2">11.2</a></li>
    4802                   <li>503 Service Unavailable (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.503.1">4.1</a>, <a href="#rfc.iref.57"><b>4.7.4</b></a>, <a href="#rfc.xref.status.503.2">11.2</a></li>
    4803                   <li>504 Gateway Timeout (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.504.1">4.1</a>, <a href="#rfc.iref.58"><b>4.7.5</b></a>, <a href="#rfc.xref.status.504.2">11.2</a></li>
    4804                   <li>505 HTTP Version Not Supported (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.505.1">4.1</a>, <a href="#rfc.iref.59"><b>4.7.6</b></a>, <a href="#rfc.xref.status.505.2">11.2</a></li>
     4795                  <li>500 Internal Server Error (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.500.1">4.1</a>, <a href="#rfc.iref.54"><b>4.7.1</b></a>, <a href="#rfc.xref.status.500.2">10.2</a></li>
     4796                  <li>501 Not Implemented (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.501.1">4.1</a>, <a href="#rfc.iref.55"><b>4.7.2</b></a>, <a href="#rfc.xref.status.501.2">10.2</a></li>
     4797                  <li>502 Bad Gateway (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.502.1">4.1</a>, <a href="#rfc.iref.56"><b>4.7.3</b></a>, <a href="#rfc.xref.status.502.2">10.2</a></li>
     4798                  <li>503 Service Unavailable (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.503.1">4.1</a>, <a href="#rfc.iref.57"><b>4.7.4</b></a>, <a href="#rfc.xref.status.503.2">10.2</a></li>
     4799                  <li>504 Gateway Timeout (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.504.1">4.1</a>, <a href="#rfc.iref.58"><b>4.7.5</b></a>, <a href="#rfc.xref.status.504.2">10.2</a></li>
     4800                  <li>505 HTTP Version Not Supported (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.505.1">4.1</a>, <a href="#rfc.iref.59"><b>4.7.6</b></a>, <a href="#rfc.xref.status.505.2">10.2</a></li>
    48054801               </ul>
    48064802            </li>
    48074803            <li><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul>
    4808                   <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.xref.header.accept.3">9.1</a>, <a href="#rfc.iref.a.2"><b>10.11</b></a>, <a href="#rfc.xref.header.accept.4">11.3</a></li>
    4809                   <li>Accept-Charset header field&nbsp;&nbsp;<a href="#rfc.xref.header.accept-charset.1">3.2</a>, <a href="#rfc.xref.header.accept-charset.2">9.1</a>, <a href="#rfc.iref.a.3"><b>10.12</b></a>, <a href="#rfc.xref.header.accept-charset.3">11.3</a>, <a href="#rfc.xref.header.accept-charset.4">C</a></li>
    4810                   <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.xref.header.accept-encoding.3">9.1</a>, <a href="#rfc.iref.a.4"><b>10.13</b></a>, <a href="#rfc.xref.header.accept-encoding.4">11.3</a>, <a href="#rfc.xref.header.accept-encoding.5">11.4</a></li>
    4811                   <li>Accept-Language header field&nbsp;&nbsp;<a href="#rfc.xref.header.accept-language.1">3.2</a>, <a href="#rfc.xref.header.accept-language.2">9.1</a>, <a href="#rfc.iref.a.5"><b>10.14</b></a>, <a href="#rfc.xref.header.accept-language.3">11.3</a></li>
    4812                   <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.1"><b>10.1</b></a>, <a href="#rfc.xref.header.allow.3">11.3</a>, <a href="#rfc.xref.header.allow.4">C</a></li>
     4804                  <li>Accept header field&nbsp;&nbsp;<a href="#rfc.xref.header.accept.1">3.2</a>, <a href="#rfc.xref.header.accept.2">5.5</a>, <a href="#rfc.xref.header.accept.3">8.1</a>, <a href="#rfc.iref.a.2"><b>9.11</b></a>, <a href="#rfc.xref.header.accept.4">10.3</a></li>
     4805                  <li>Accept-Charset header field&nbsp;&nbsp;<a href="#rfc.xref.header.accept-charset.1">3.2</a>, <a href="#rfc.xref.header.accept-charset.2">8.1</a>, <a href="#rfc.iref.a.3"><b>9.12</b></a>, <a href="#rfc.xref.header.accept-charset.3">10.3</a>, <a href="#rfc.xref.header.accept-charset.4">C</a></li>
     4806                  <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">5.4</a>, <a href="#rfc.xref.header.accept-encoding.3">8.1</a>, <a href="#rfc.iref.a.4"><b>9.13</b></a>, <a href="#rfc.xref.header.accept-encoding.4">10.3</a>, <a href="#rfc.xref.header.accept-encoding.5">10.4</a></li>
     4807                  <li>Accept-Language header field&nbsp;&nbsp;<a href="#rfc.xref.header.accept-language.1">3.2</a>, <a href="#rfc.xref.header.accept-language.2">8.1</a>, <a href="#rfc.iref.a.5"><b>9.14</b></a>, <a href="#rfc.xref.header.accept-language.3">10.3</a></li>
     4808                  <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.1"><b>9.1</b></a>, <a href="#rfc.xref.header.allow.3">10.3</a>, <a href="#rfc.xref.header.allow.4">C</a></li>
    48134809               </ul>
    48144810            </li>
    … …  
    48164812                  <li>Coding Format&nbsp;&nbsp;
    48174813                     <ul>
    4818                         <li>compress&nbsp;&nbsp;<a href="#rfc.iref.c.4">6.4</a></li>
    4819                         <li>deflate&nbsp;&nbsp;<a href="#rfc.iref.c.5">6.4</a></li>
    4820                         <li>gzip&nbsp;&nbsp;<a href="#rfc.iref.c.6">6.4</a></li>
     4814                        <li>compress&nbsp;&nbsp;<a href="#rfc.iref.c.4">5.4</a></li>
     4815                        <li>deflate&nbsp;&nbsp;<a href="#rfc.iref.c.5">5.4</a></li>
     4816                        <li>gzip&nbsp;&nbsp;<a href="#rfc.iref.c.6">5.4</a></li>
    48214817                     </ul>
    48224818                  </li>
    4823                   <li>compress (Coding Format)&nbsp;&nbsp;<a href="#rfc.iref.c.3">6.4</a></li>
    4824                   <li>CONNECT method&nbsp;&nbsp;<a href="#rfc.iref.c.2"><b>2.3.8</b></a>, <a href="#rfc.xref.CONNECT.1">11.1</a>, <a href="#rfc.xref.CONNECT.2">C</a></li>
     4819                  <li>compress (Coding Format)&nbsp;&nbsp;<a href="#rfc.iref.c.3">5.4</a></li>
     4820                  <li>CONNECT method&nbsp;&nbsp;<a href="#rfc.iref.c.2"><b>2.3.8</b></a>, <a href="#rfc.xref.CONNECT.1">10.1</a>, <a href="#rfc.xref.CONNECT.2">C</a></li>
    48254821                  <li>content negotiation&nbsp;&nbsp;<a href="#rfc.iref.c.1">1.1</a></li>
    4826                   <li>Content-Encoding header field&nbsp;&nbsp;<a href="#rfc.xref.header.content-encoding.1">6.4</a>, <a href="#rfc.xref.header.content-encoding.2">8.1</a>, <a href="#rfc.iref.c.7"><b>10.15</b></a>, <a href="#rfc.xref.header.content-encoding.3">10.15</a>, <a href="#rfc.xref.header.content-encoding.4">11.3</a></li>
    4827                   <li>Content-Language header field&nbsp;&nbsp;<a href="#rfc.xref.header.content-language.1">8.1</a>, <a href="#rfc.iref.c.8"><b>10.16</b></a>, <a href="#rfc.xref.header.content-language.2">11.3</a></li>
    4828                   <li>Content-Location header field&nbsp;&nbsp;<a href="#rfc.xref.header.content-location.1">2.3.4</a>, <a href="#rfc.xref.header.content-location.2">8.1</a>, <a href="#rfc.xref.header.content-location.3">10.5</a>, <a href="#rfc.iref.c.9"><b>10.17</b></a>, <a href="#rfc.xref.header.content-location.4">11.3</a>, <a href="#rfc.xref.header.content-location.5">C</a></li>
     4822                  <li>Content-Encoding header field&nbsp;&nbsp;<a href="#rfc.xref.header.content-encoding.1">5.4</a>, <a href="#rfc.xref.header.content-encoding.2">7.2</a>, <a href="#rfc.iref.c.7"><b>9.15</b></a>, <a href="#rfc.xref.header.content-encoding.3">9.15</a>, <a href="#rfc.xref.header.content-encoding.4">10.3</a></li>
     4823                  <li>Content-Language header field&nbsp;&nbsp;<a href="#rfc.xref.header.content-language.1">7.2</a>, <a href="#rfc.iref.c.8"><b>9.16</b></a>, <a href="#rfc.xref.header.content-language.2">10.3</a></li>
     4824                  <li>Content-Location header field&nbsp;&nbsp;<a href="#rfc.xref.header.content-location.1">2.3.4</a>, <a href="#rfc.xref.header.content-location.2">7.2</a>, <a href="#rfc.xref.header.content-location.3">9.5</a>, <a href="#rfc.iref.c.9"><b>9.17</b></a>, <a href="#rfc.xref.header.content-location.4">10.3</a>, <a href="#rfc.xref.header.content-location.5">C</a></li>
    48294825                  <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>
    4830                   <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.xref.header.content-type.4">8.1</a>, <a href="#rfc.iref.c.10"><b>10.18</b></a>, <a href="#rfc.xref.header.content-type.5">11.3</a></li>
     4826                  <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">5.5</a>, <a href="#rfc.xref.header.content-type.4">7.2</a>, <a href="#rfc.iref.c.10"><b>9.18</b></a>, <a href="#rfc.xref.header.content-type.5">10.3</a></li>
    48314827               </ul>
    48324828            </li>
    48334829            <li><a id="rfc.index.D" href="#rfc.index.D"><b>D</b></a><ul>
    4834                   <li>Date header field&nbsp;&nbsp;<a href="#rfc.xref.header.date.1">3.3</a>, <a href="#rfc.iref.d.3"><b>10.2</b></a>, <a href="#rfc.xref.header.date.2">11.3</a></li>
    4835                   <li>deflate (Coding Format)&nbsp;&nbsp;<a href="#rfc.iref.d.2">6.4</a></li>
    4836                   <li>DELETE method&nbsp;&nbsp;<a href="#rfc.iref.d.1"><b>2.3.6</b></a>, <a href="#rfc.xref.DELETE.1">11.1</a></li>
    4837                   <li><em>draft-reschke-http-status-308</em>&nbsp;&nbsp;<a href="#rfc.xref.draft-reschke-http-status-308.1">4.5.7</a>, <a href="#draft-reschke-http-status-308"><b>14.2</b></a></li>
     4830                  <li>Date header field&nbsp;&nbsp;<a href="#rfc.xref.header.date.1">3.3</a>, <a href="#rfc.iref.d.3"><b>9.2</b></a>, <a href="#rfc.xref.header.date.2">10.3</a></li>
     4831                  <li>deflate (Coding Format)&nbsp;&nbsp;<a href="#rfc.iref.d.2">5.4</a></li>
     4832                  <li>DELETE method&nbsp;&nbsp;<a href="#rfc.iref.d.1"><b>2.3.6</b></a>, <a href="#rfc.xref.DELETE.1">10.1</a></li>
     4833                  <li><em>draft-reschke-http-status-308</em>&nbsp;&nbsp;<a href="#rfc.xref.draft-reschke-http-status-308.1">4.5.7</a>, <a href="#draft-reschke-http-status-308"><b>13.2</b></a></li>
    48384834               </ul>
    48394835            </li>
    48404836            <li><a id="rfc.index.E" href="#rfc.index.E"><b>E</b></a><ul>
    4841                   <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>10.3</b></a>, <a href="#rfc.xref.header.expect.3">11.3</a>, <a href="#rfc.xref.header.expect.4">C</a></li>
     4837                  <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>9.3</b></a>, <a href="#rfc.xref.header.expect.3">10.3</a>, <a href="#rfc.xref.header.expect.4">C</a></li>
    48424838                  <li>Expect Values&nbsp;&nbsp;
    48434839                     <ul>
    4844                         <li>100-continue&nbsp;&nbsp;<a href="#rfc.iref.e.2"><b>10.3</b></a></li>
     4840                        <li>100-continue&nbsp;&nbsp;<a href="#rfc.iref.e.2"><b>9.3</b></a></li>
    48454841                     </ul>
    48464842                  </li>
    … …  
    48484844            </li>
    48494845            <li><a id="rfc.index.F" href="#rfc.index.F"><b>F</b></a><ul>
    4850                   <li>From header field&nbsp;&nbsp;<a href="#rfc.xref.header.from.1">3.2</a>, <a href="#rfc.iref.f.1"><b>10.4</b></a>, <a href="#rfc.xref.header.from.2">11.3</a></li>
     4846                  <li>From header field&nbsp;&nbsp;<a href="#rfc.xref.header.from.1">3.2</a>, <a href="#rfc.iref.f.1"><b>9.4</b></a>, <a href="#rfc.xref.header.from.2">10.3</a></li>
    48514847               </ul>
    48524848            </li>
    48534849            <li><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul>
    4854                   <li>GET method&nbsp;&nbsp;<a href="#rfc.iref.g.2"><b>2.3.2</b></a>, <a href="#rfc.xref.GET.1">11.1</a></li>
     4850                  <li>GET method&nbsp;&nbsp;<a href="#rfc.iref.g.2"><b>2.3.2</b></a>, <a href="#rfc.xref.GET.1">10.1</a></li>
    48554851                  <li><tt>Grammar</tt>&nbsp;&nbsp;
    48564852                     <ul>
    4857                         <li><tt>Accept</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.49"><b>10.11</b></a></li>
    4858                         <li><tt>Accept-Charset</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.53"><b>10.12</b></a></li>
    4859                         <li><tt>Accept-Encoding</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.54"><b>10.13</b></a></li>
    4860                         <li><tt>accept-ext</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.52"><b>10.11</b></a></li>
    4861                         <li><tt>Accept-Language</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.56"><b>10.14</b></a></li>
    4862                         <li><tt>accept-params</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.51"><b>10.11</b></a></li>
    4863                         <li><tt>Allow</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.34"><b>10.1</b></a></li>
    4864                         <li><tt>asctime-date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.21"><b>6.1</b></a></li>
    4865                         <li><tt>attribute</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.31"><b>6.5</b></a></li>
    4866                         <li><tt>charset</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.24"><b>6.3</b></a></li>
    4867                         <li><tt>codings</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.55"><b>10.13</b></a></li>
    4868                         <li><tt>content-coding</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.25"><b>6.4</b></a></li>
    4869                         <li><tt>Content-Encoding</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.58"><b>10.15</b></a></li>
    4870                         <li><tt>Content-Language</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.59"><b>10.16</b></a></li>
    4871                         <li><tt>Content-Location</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.60"><b>10.17</b></a></li>
    4872                         <li><tt>Content-Type</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.61"><b>10.18</b></a></li>
    4873                         <li><tt>Date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.35"><b>10.2</b></a></li>
    4874                         <li><tt>date1</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.8"><b>6.1</b></a></li>
    4875                         <li><tt>day</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.15"><b>6.1</b></a></li>
    4876                         <li><tt>day-name</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.13"><b>6.1</b></a></li>
    4877                         <li><tt>day-name-l</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.14"><b>6.1</b></a></li>
    4878                         <li><tt>delta-seconds</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.46"><b>10.8</b></a></li>
    4879                         <li><tt>Expect</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.36"><b>10.3</b></a></li>
    4880                         <li><tt>expect-name</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.40"><b>10.3</b></a></li>
    4881                         <li><tt>expect-param</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.38"><b>10.3</b></a></li>
    4882                         <li><tt>expect-value</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.39"><b>10.3</b></a></li>
    4883                         <li><tt>expectation</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.37"><b>10.3</b></a></li>
     4853                        <li><tt>Accept</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.49"><b>9.11</b></a></li>
     4854                        <li><tt>Accept-Charset</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.53"><b>9.12</b></a></li>
     4855                        <li><tt>Accept-Encoding</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.54"><b>9.13</b></a></li>
     4856                        <li><tt>accept-ext</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.52"><b>9.11</b></a></li>
     4857                        <li><tt>Accept-Language</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.56"><b>9.14</b></a></li>
     4858                        <li><tt>accept-params</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.51"><b>9.11</b></a></li>
     4859                        <li><tt>Allow</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.34"><b>9.1</b></a></li>
     4860                        <li><tt>asctime-date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.21"><b>5.1</b></a></li>
     4861                        <li><tt>attribute</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.31"><b>5.5</b></a></li>
     4862                        <li><tt>charset</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.24"><b>5.3</b></a></li>
     4863                        <li><tt>codings</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.55"><b>9.13</b></a></li>
     4864                        <li><tt>content-coding</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.25"><b>5.4</b></a></li>
     4865                        <li><tt>Content-Encoding</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.58"><b>9.15</b></a></li>
     4866                        <li><tt>Content-Language</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.59"><b>9.16</b></a></li>
     4867                        <li><tt>Content-Location</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.60"><b>9.17</b></a></li>
     4868                        <li><tt>Content-Type</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.61"><b>9.18</b></a></li>
     4869                        <li><tt>Date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.35"><b>9.2</b></a></li>
     4870                        <li><tt>date1</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.8"><b>5.1</b></a></li>
     4871                        <li><tt>day</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.15"><b>5.1</b></a></li>
     4872                        <li><tt>day-name</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.13"><b>5.1</b></a></li>
     4873                        <li><tt>day-name-l</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.14"><b>5.1</b></a></li>
     4874                        <li><tt>delta-seconds</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.46"><b>9.8</b></a></li>
     4875                        <li><tt>Expect</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.36"><b>9.3</b></a></li>
     4876                        <li><tt>expect-name</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.40"><b>9.3</b></a></li>
     4877                        <li><tt>expect-param</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.38"><b>9.3</b></a></li>
     4878                        <li><tt>expect-value</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.39"><b>9.3</b></a></li>
     4879                        <li><tt>expectation</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.37"><b>9.3</b></a></li>
    48844880                        <li><tt>extension-code</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.4"><b>4</b></a></li>
    4885                         <li><tt>From</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.41"><b>10.4</b></a></li>
    4886                         <li><tt>GMT</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.18"><b>6.1</b></a></li>
    4887                         <li><tt>hour</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.10"><b>6.1</b></a></li>
    4888                         <li><tt>HTTP-date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.6"><b>6.1</b></a></li>
    4889                         <li><tt>language-range</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.57"><b>10.14</b></a></li>
    4890                         <li><tt>language-tag</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.33"><b>6.6</b></a></li>
    4891                         <li><tt>Location</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.42"><b>10.5</b></a></li>
    4892                         <li><tt>Max-Forwards</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.43"><b>10.6</b></a></li>
    4893                         <li><tt>media-range</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.50"><b>10.11</b></a></li>
    4894                         <li><tt>media-type</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.27"><b>6.5</b></a></li>
     4881                        <li><tt>From</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.41"><b>9.4</b></a></li>
     4882                        <li><tt>GMT</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.18"><b>5.1</b></a></li>
     4883                        <li><tt>hour</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.10"><b>5.1</b></a></li>
     4884                        <li><tt>HTTP-date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.6"><b>5.1</b></a></li>
     4885                        <li><tt>language-range</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.57"><b>9.14</b></a></li>
     4886                        <li><tt>language-tag</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.33"><b>5.6</b></a></li>
     4887                        <li><tt>Location</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.42"><b>9.5</b></a></li>
     4888                        <li><tt>Max-Forwards</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.43"><b>9.6</b></a></li>
     4889                        <li><tt>media-range</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.50"><b>9.11</b></a></li>
     4890                        <li><tt>media-type</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.27"><b>5.5</b></a></li>
    48954891                        <li><tt>method</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.1"><b>2</b></a></li>
    48964892                        <li><tt>MIME-Version</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.62"><b>A.1</b></a></li>
    4897                         <li><tt>minute</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.11"><b>6.1</b></a></li>
    4898                         <li><tt>month</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.16"><b>6.1</b></a></li>
    4899                         <li><tt>obs-date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.19"><b>6.1</b></a></li>
    4900                         <li><tt>parameter</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.30"><b>6.5</b></a></li>
    4901                         <li><tt>product</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.22"><b>6.2</b></a></li>
    4902                         <li><tt>product-version</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.23"><b>6.2</b></a></li>
     4893                        <li><tt>minute</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.11"><b>5.1</b></a></li>
     4894                        <li><tt>month</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.16"><b>5.1</b></a></li>
     4895                        <li><tt>obs-date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.19"><b>5.1</b></a></li>
     4896                        <li><tt>parameter</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.30"><b>5.5</b></a></li>
     4897                        <li><tt>product</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.22"><b>5.2</b></a></li>
     4898                        <li><tt>product-version</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.23"><b>5.2</b></a></li>
    49034899                        <li><tt>reason-phrase</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.5"><b>4</b></a></li>
    4904                         <li><tt>Referer</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.44"><b>10.7</b></a></li>
    4905                         <li><tt>Retry-After</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.45"><b>10.8</b></a></li>
    4906                         <li><tt>rfc1123-date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.7"><b>6.1</b></a></li>
    4907                         <li><tt>rfc850-date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.20"><b>6.1</b></a></li>
    4908                         <li><tt>second</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.12"><b>6.1</b></a></li>
    4909                         <li><tt>Server</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.47"><b>10.9</b></a></li>
     4900                        <li><tt>Referer</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.44"><b>9.7</b></a></li>
     4901                        <li><tt>Retry-After</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.45"><b>9.8</b></a></li>
     4902                        <li><tt>rfc1123-date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.7"><b>5.1</b></a></li>
     4903                        <li><tt>rfc850-date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.20"><b>5.1</b></a></li>
     4904                        <li><tt>second</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.12"><b>5.1</b></a></li>
     4905                        <li><tt>Server</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.47"><b>9.9</b></a></li>
    49104906                        <li><tt>status-code</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.3"><b>4</b></a></li>
    4911                         <li><tt>subtype</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.29"><b>6.5</b></a></li>
    4912                         <li><tt>time-of-day</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.9"><b>6.1</b></a></li>
    4913                         <li><tt>type</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.28"><b>6.5</b></a></li>
    4914                         <li><tt>User-Agent</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.48"><b>10.10</b></a></li>
    4915                         <li><tt>value</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.32"><b>6.5</b></a></li>
    4916                         <li><tt>year</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.17"><b>6.1</b></a></li>
     4907                        <li><tt>subtype</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.29"><b>5.5</b></a></li>
     4908                        <li><tt>time-of-day</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.9"><b>5.1</b></a></li>
     4909                        <li><tt>type</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.28"><b>5.5</b></a></li>
     4910                        <li><tt>User-Agent</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.48"><b>9.10</b></a></li>
     4911                        <li><tt>value</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.32"><b>5.5</b></a></li>
     4912                        <li><tt>year</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.17"><b>5.1</b></a></li>
    49174913                     </ul>
    49184914                  </li>
    4919                   <li>gzip (Coding Format)&nbsp;&nbsp;<a href="#rfc.iref.g.26">6.4</a></li>
     4915                  <li>gzip (Coding Format)&nbsp;&nbsp;<a href="#rfc.iref.g.26">5.4</a></li>
    49204916               </ul>
    49214917            </li>
    49224918            <li><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul>
    4923                   <li>HEAD method&nbsp;&nbsp;<a href="#rfc.iref.h.1"><b>2.3.3</b></a>, <a href="#rfc.xref.HEAD.1">11.1</a></li>
     4919                  <li>HEAD method&nbsp;&nbsp;<a href="#rfc.iref.h.1"><b>2.3.3</b></a>, <a href="#rfc.xref.HEAD.1">10.1</a></li>
    49244920                  <li>Header Fields&nbsp;&nbsp;
    49254921                     <ul>
    4926                         <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.xref.header.accept.3">9.1</a>, <a href="#rfc.iref.h.12"><b>10.11</b></a>, <a href="#rfc.xref.header.accept.4">11.3</a></li>
    4927                         <li>Accept-Charset&nbsp;&nbsp;<a href="#rfc.xref.header.accept-charset.1">3.2</a>, <a href="#rfc.xref.header.accept-charset.2">9.1</a>, <a href="#rfc.iref.h.13"><b>10.12</b></a>, <a href="#rfc.xref.header.accept-charset.3">11.3</a>, <a href="#rfc.xref.header.accept-charset.4">C</a></li>
    4928                         <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.xref.header.accept-encoding.3">9.1</a>, <a href="#rfc.iref.h.14"><b>10.13</b></a>, <a href="#rfc.xref.header.accept-encoding.4">11.3</a>, <a href="#rfc.xref.header.accept-encoding.5">11.4</a></li>
    4929                         <li>Accept-Language&nbsp;&nbsp;<a href="#rfc.xref.header.accept-language.1">3.2</a>, <a href="#rfc.xref.header.accept-language.2">9.1</a>, <a href="#rfc.iref.h.15"><b>10.14</b></a>, <a href="#rfc.xref.header.accept-language.3">11.3</a></li>
    4930                         <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.2"><b>10.1</b></a>, <a href="#rfc.xref.header.allow.3">11.3</a>, <a href="#rfc.xref.header.allow.4">C</a></li>
    4931                         <li>Content-Encoding&nbsp;&nbsp;<a href="#rfc.xref.header.content-encoding.1">6.4</a>, <a href="#rfc.xref.header.content-encoding.2">8.1</a>, <a href="#rfc.iref.h.16"><b>10.15</b></a>, <a href="#rfc.xref.header.content-encoding.3">10.15</a>, <a href="#rfc.xref.header.content-encoding.4">11.3</a></li>
    4932                         <li>Content-Language&nbsp;&nbsp;<a href="#rfc.xref.header.content-language.1">8.1</a>, <a href="#rfc.iref.h.17"><b>10.16</b></a>, <a href="#rfc.xref.header.content-language.2">11.3</a></li>
    4933                         <li>Content-Location&nbsp;&nbsp;<a href="#rfc.xref.header.content-location.1">2.3.4</a>, <a href="#rfc.xref.header.content-location.2">8.1</a>, <a href="#rfc.xref.header.content-location.3">10.5</a>, <a href="#rfc.iref.h.18"><b>10.17</b></a>, <a href="#rfc.xref.header.content-location.4">11.3</a>, <a href="#rfc.xref.header.content-location.5">C</a></li>
     4922                        <li>Accept&nbsp;&nbsp;<a href="#rfc.xref.header.accept.1">3.2</a>, <a href="#rfc.xref.header.accept.2">5.5</a>, <a href="#rfc.xref.header.accept.3">8.1</a>, <a href="#rfc.iref.h.12"><b>9.11</b></a>, <a href="#rfc.xref.header.accept.4">10.3</a></li>
     4923                        <li>Accept-Charset&nbsp;&nbsp;<a href="#rfc.xref.header.accept-charset.1">3.2</a>, <a href="#rfc.xref.header.accept-charset.2">8.1</a>, <a href="#rfc.iref.h.13"><b>9.12</b></a>, <a href="#rfc.xref.header.accept-charset.3">10.3</a>, <a href="#rfc.xref.header.accept-charset.4">C</a></li>
     4924                        <li>Accept-Encoding&nbsp;&nbsp;<a href="#rfc.xref.header.accept-encoding.1">3.2</a>, <a href="#rfc.xref.header.accept-encoding.2">5.4</a>, <a href="#rfc.xref.header.accept-encoding.3">8.1</a>, <a href="#rfc.iref.h.14"><b>9.13</b></a>, <a href="#rfc.xref.header.accept-encoding.4">10.3</a>, <a href="#rfc.xref.header.accept-encoding.5">10.4</a></li>
     4925                        <li>Accept-Language&nbsp;&nbsp;<a href="#rfc.xref.header.accept-language.1">3.2</a>, <a href="#rfc.xref.header.accept-language.2">8.1</a>, <a href="#rfc.iref.h.15"><b>9.14</b></a>, <a href="#rfc.xref.header.accept-language.3">10.3</a></li>
     4926                        <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.2"><b>9.1</b></a>, <a href="#rfc.xref.header.allow.3">10.3</a>, <a href="#rfc.xref.header.allow.4">C</a></li>
     4927                        <li>Content-Encoding&nbsp;&nbsp;<a href="#rfc.xref.header.content-encoding.1">5.4</a>, <a href="#rfc.xref.header.content-encoding.2">7.2</a>, <a href="#rfc.iref.h.16"><b>9.15</b></a>, <a href="#rfc.xref.header.content-encoding.3">9.15</a>, <a href="#rfc.xref.header.content-encoding.4">10.3</a></li>
     4928                        <li>Content-Language&nbsp;&nbsp;<a href="#rfc.xref.header.content-language.1">7.2</a>, <a href="#rfc.iref.h.17"><b>9.16</b></a>, <a href="#rfc.xref.header.content-language.2">10.3</a></li>
     4929                        <li>Content-Location&nbsp;&nbsp;<a href="#rfc.xref.header.content-location.1">2.3.4</a>, <a href="#rfc.xref.header.content-location.2">7.2</a>, <a href="#rfc.xref.header.content-location.3">9.5</a>, <a href="#rfc.iref.h.18"><b>9.17</b></a>, <a href="#rfc.xref.header.content-location.4">10.3</a>, <a href="#rfc.xref.header.content-location.5">C</a></li>
    49344930                        <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>
    4935                         <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.xref.header.content-type.4">8.1</a>, <a href="#rfc.iref.h.19"><b>10.18</b></a>, <a href="#rfc.xref.header.content-type.5">11.3</a></li>
    4936                         <li>Date&nbsp;&nbsp;<a href="#rfc.xref.header.date.1">3.3</a>, <a href="#rfc.iref.h.3"><b>10.2</b></a>, <a href="#rfc.xref.header.date.2">11.3</a></li>
    4937                         <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.4"><b>10.3</b></a>, <a href="#rfc.xref.header.expect.3">11.3</a>, <a href="#rfc.xref.header.expect.4">C</a></li>
    4938                         <li>From&nbsp;&nbsp;<a href="#rfc.xref.header.from.1">3.2</a>, <a href="#rfc.iref.h.5"><b>10.4</b></a>, <a href="#rfc.xref.header.from.2">11.3</a></li>
    4939                         <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.6"><b>10.5</b></a>, <a href="#rfc.xref.header.location.4">11.3</a>, <a href="#rfc.xref.header.location.5">C</a></li>
    4940                         <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.7"><b>10.6</b></a>, <a href="#rfc.xref.header.max-forwards.4">11.3</a>, <a href="#rfc.xref.header.max-forwards.5">C</a></li>
    4941                         <li>MIME-Version&nbsp;&nbsp;<a href="#rfc.xref.mime-version.1">11.3</a>, <a href="#rfc.iref.h.20"><b>A.1</b></a></li>
    4942                         <li>Referer&nbsp;&nbsp;<a href="#rfc.xref.header.referer.1">3.2</a>, <a href="#rfc.iref.h.8"><b>10.7</b></a>, <a href="#rfc.xref.header.referer.2">11.3</a>, <a href="#rfc.xref.header.referer.3">C</a></li>
    4943                         <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.9"><b>10.8</b></a>, <a href="#rfc.xref.header.retry-after.3">11.3</a></li>
    4944                         <li>Server&nbsp;&nbsp;<a href="#rfc.xref.header.server.1">3.3</a>, <a href="#rfc.iref.h.10"><b>10.9</b></a>, <a href="#rfc.xref.header.server.2">11.3</a>, <a href="#rfc.xref.header.server.3">12.1</a>, <a href="#rfc.xref.header.server.4">C</a></li>
    4945                         <li>User-Agent&nbsp;&nbsp;<a href="#rfc.xref.header.user-agent.1">3.2</a>, <a href="#rfc.xref.header.user-agent.2">9.1</a>, <a href="#rfc.iref.h.11"><b>10.10</b></a>, <a href="#rfc.xref.header.user-agent.3">11.3</a>, <a href="#rfc.xref.header.user-agent.4">12.1</a></li>
     4931                        <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">5.5</a>, <a href="#rfc.xref.header.content-type.4">7.2</a>, <a href="#rfc.iref.h.19"><b>9.18</b></a>, <a href="#rfc.xref.header.content-type.5">10.3</a></li>
     4932                        <li>Date&nbsp;&nbsp;<a href="#rfc.xref.header.date.1">3.3</a>, <a href="#rfc.iref.h.3"><b>9.2</b></a>, <a href="#rfc.xref.header.date.2">10.3</a></li>
     4933                        <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.4"><b>9.3</b></a>, <a href="#rfc.xref.header.expect.3">10.3</a>, <a href="#rfc.xref.header.expect.4">C</a></li>
     4934                        <li>From&nbsp;&nbsp;<a href="#rfc.xref.header.from.1">3.2</a>, <a href="#rfc.iref.h.5"><b>9.4</b></a>, <a href="#rfc.xref.header.from.2">10.3</a></li>
     4935                        <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.6"><b>9.5</b></a>, <a href="#rfc.xref.header.location.4">10.3</a>, <a href="#rfc.xref.header.location.5">C</a></li>
     4936                        <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.7"><b>9.6</b></a>, <a href="#rfc.xref.header.max-forwards.4">10.3</a>, <a href="#rfc.xref.header.max-forwards.5">C</a></li>
     4937                        <li>MIME-Version&nbsp;&nbsp;<a href="#rfc.xref.mime-version.1">10.3</a>, <a href="#rfc.iref.h.20"><b>A.1</b></a></li>
     4938                        <li>Referer&nbsp;&nbsp;<a href="#rfc.xref.header.referer.1">3.2</a>, <a href="#rfc.iref.h.8"><b>9.7</b></a>, <a href="#rfc.xref.header.referer.2">10.3</a>, <a href="#rfc.xref.header.referer.3">C</a></li>
     4939                        <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.9"><b>9.8</b></a>, <a href="#rfc.xref.header.retry-after.3">10.3</a></li>
     4940                        <li>Server&nbsp;&nbsp;<a href="#rfc.xref.header.server.1">3.3</a>, <a href="#rfc.iref.h.10"><b>9.9</b></a>, <a href="#rfc.xref.header.server.2">10.3</a>, <a href="#rfc.xref.header.server.3">11.1</a>, <a href="#rfc.xref.header.server.4">C</a></li>
     4941                        <li>User-Agent&nbsp;&nbsp;<a href="#rfc.xref.header.user-agent.1">3.2</a>, <a href="#rfc.xref.header.user-agent.2">8.1</a>, <a href="#rfc.iref.h.11"><b>9.10</b></a>, <a href="#rfc.xref.header.user-agent.3">10.3</a>, <a href="#rfc.xref.header.user-agent.4">11.1</a></li>
    49464942                     </ul>
    49474943                  </li>
    … …  
    49534949            </li>
    49544950            <li><a id="rfc.index.L" href="#rfc.index.L"><b>L</b></a><ul>
    4955                   <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>10.5</b></a>, <a href="#rfc.xref.header.location.4">11.3</a>, <a href="#rfc.xref.header.location.5">C</a></li>
     4951                  <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>9.5</b></a>, <a href="#rfc.xref.header.location.4">10.3</a>, <a href="#rfc.xref.header.location.5">C</a></li>
    49564952               </ul>
    49574953            </li>
    49584954            <li><a id="rfc.index.M" href="#rfc.index.M"><b>M</b></a><ul>
    4959                   <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>10.6</b></a>, <a href="#rfc.xref.header.max-forwards.4">11.3</a>, <a href="#rfc.xref.header.max-forwards.5">C</a></li>
     4955                  <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>9.6</b></a>, <a href="#rfc.xref.header.max-forwards.4">10.3</a>, <a href="#rfc.xref.header.max-forwards.5">C</a></li>
    49604956                  <li>Methods&nbsp;&nbsp;
    49614957                     <ul>
    4962                         <li>CONNECT&nbsp;&nbsp;<a href="#rfc.iref.m.8"><b>2.3.8</b></a>, <a href="#rfc.xref.CONNECT.1">11.1</a>, <a href="#rfc.xref.CONNECT.2">C</a></li>
    4963                         <li>DELETE&nbsp;&nbsp;<a href="#rfc.iref.m.6"><b>2.3.6</b></a>, <a href="#rfc.xref.DELETE.1">11.1</a></li>
    4964                         <li>GET&nbsp;&nbsp;<a href="#rfc.iref.m.2"><b>2.3.2</b></a>, <a href="#rfc.xref.GET.1">11.1</a></li>
    4965                         <li>HEAD&nbsp;&nbsp;<a href="#rfc.iref.m.3"><b>2.3.3</b></a>, <a href="#rfc.xref.HEAD.1">11.1</a></li>
    4966                         <li>OPTIONS&nbsp;&nbsp;<a href="#rfc.iref.m.1"><b>2.3.1</b></a>, <a href="#rfc.xref.OPTIONS.1">10.6</a>, <a href="#rfc.xref.OPTIONS.2">11.1</a></li>
    4967                         <li>POST&nbsp;&nbsp;<a href="#rfc.iref.m.4"><b>2.3.4</b></a>, <a href="#rfc.xref.POST.1">11.1</a>, <a href="#rfc.xref.POST.2">C</a></li>
    4968                         <li>PUT&nbsp;&nbsp;<a href="#rfc.iref.m.5"><b>2.3.5</b></a>, <a href="#rfc.xref.PUT.1">11.1</a>, <a href="#rfc.xref.PUT.2">C</a></li>
    4969                         <li>TRACE&nbsp;&nbsp;<a href="#rfc.iref.m.7"><b>2.3.7</b></a>, <a href="#rfc.xref.TRACE.1">10.6</a>, <a href="#rfc.xref.TRACE.2">11.1</a>, <a href="#rfc.xref.TRACE.3">12.1</a></li>
     4958                        <li>CONNECT&nbsp;&nbsp;<a href="#rfc.iref.m.8"><b>2.3.8</b></a>, <a href="#rfc.xref.CONNECT.1">10.1</a>, <a href="#rfc.xref.CONNECT.2">C</a></li>
     4959                        <li>DELETE&nbsp;&nbsp;<a href="#rfc.iref.m.6"><b>2.3.6</b></a>, <a href="#rfc.xref.DELETE.1">10.1</a></li>
     4960                        <li>GET&nbsp;&nbsp;<a href="#rfc.iref.m.2"><b>2.3.2</b></a>, <a href="#rfc.xref.GET.1">10.1</a></li>
     4961                        <li>HEAD&nbsp;&nbsp;<a href="#rfc.iref.m.3"><b>2.3.3</b></a>, <a href="#rfc.xref.HEAD.1">10.1</a></li>
     4962                        <li>OPTIONS&nbsp;&nbsp;<a href="#rfc.iref.m.1"><b>2.3.1</b></a>, <a href="#rfc.xref.OPTIONS.1">9.6</a>, <a href="#rfc.xref.OPTIONS.2">10.1</a></li>
     4963                        <li>POST&nbsp;&nbsp;<a href="#rfc.iref.m.4"><b>2.3.4</b></a>, <a href="#rfc.xref.POST.1">10.1</a>, <a href="#rfc.xref.POST.2">C</a></li>
     4964                        <li>PUT&nbsp;&nbsp;<a href="#rfc.iref.m.5"><b>2.3.5</b></a>, <a href="#rfc.xref.PUT.1">10.1</a>, <a href="#rfc.xref.PUT.2">C</a></li>
     4965                        <li>TRACE&nbsp;&nbsp;<a href="#rfc.iref.m.7"><b>2.3.7</b></a>, <a href="#rfc.xref.TRACE.1">9.6</a>, <a href="#rfc.xref.TRACE.2">10.1</a>, <a href="#rfc.xref.TRACE.3">11.1</a></li>
    49704966                     </ul>
    49714967                  </li>
    4972                   <li>MIME-Version header field&nbsp;&nbsp;<a href="#rfc.xref.mime-version.1">11.3</a>, <a href="#rfc.iref.m.10"><b>A.1</b></a></li>
     4968                  <li>MIME-Version header field&nbsp;&nbsp;<a href="#rfc.xref.mime-version.1">10.3</a>, <a href="#rfc.iref.m.10"><b>A.1</b></a></li>
    49734969               </ul>
    49744970            </li>
    49754971            <li><a id="rfc.index.O" href="#rfc.index.O"><b>O</b></a><ul>
    4976                   <li>OPTIONS method&nbsp;&nbsp;<a href="#rfc.iref.o.1"><b>2.3.1</b></a>, <a href="#rfc.xref.OPTIONS.1">10.6</a>, <a href="#rfc.xref.OPTIONS.2">11.1</a></li>
     4972                  <li>OPTIONS method&nbsp;&nbsp;<a href="#rfc.iref.o.1"><b>2.3.1</b></a>, <a href="#rfc.xref.OPTIONS.1">9.6</a>, <a href="#rfc.xref.OPTIONS.2">10.1</a></li>
    49774973               </ul>
    49784974            </li>
    49794975            <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul>
    4980                   <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">1.3.2</a>, <a href="#rfc.xref.Part1.17">2</a>, <a href="#rfc.xref.Part1.18">2.2.1</a>, <a href="#rfc.xref.Part1.19">2.3.1</a>, <a href="#rfc.xref.Part1.20">2.3.7</a>, <a href="#rfc.xref.Part1.21">2.3.7</a>, <a href="#rfc.xref.Part1.22">2.3.8</a>, <a href="#rfc.xref.Part1.23">3</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.1</a>, <a href="#rfc.xref.Part1.29">3.2</a>, <a href="#rfc.xref.Part1.30">3.2</a>, <a href="#rfc.xref.Part1.31">3.3</a>, <a href="#rfc.xref.Part1.32">4.3.1</a>, <a href="#rfc.xref.Part1.33">4.3.2</a>, <a href="#rfc.xref.Part1.34">4.4.4</a>, <a href="#rfc.xref.Part1.35">4.4.6</a>, <a href="#rfc.xref.Part1.36">4.6.15</a>, <a href="#rfc.xref.Part1.37">4.7.6</a>, <a href="#rfc.xref.Part1.38">5</a>, <a href="#rfc.xref.Part1.39">5.1</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</a>, <a href="#rfc.xref.Part1.43">6.4.1</a>, <a href="#rfc.xref.Part1.44">6.4.1</a>, <a href="#rfc.xref.Part1.45">7.1</a>, <a href="#rfc.xref.Part1.46">7.2</a>, <a href="#rfc.xref.Part1.47">10.3</a>, <a href="#rfc.xref.Part1.48">10.9</a>, <a href="#rfc.xref.Part1.49">10.9</a>, <a href="#rfc.xref.Part1.50">10.10</a>, <a href="#rfc.xref.Part1.51">10.17</a>, <a href="#rfc.xref.Part1.52">11.4</a>, <a href="#rfc.xref.Part1.53">11.4</a>, <a href="#rfc.xref.Part1.54">11.4</a>, <a href="#rfc.xref.Part1.55">13</a>, <a href="#Part1"><b>14.1</b></a>, <a href="#rfc.xref.Part1.56">A.6</a>, <a href="#rfc.xref.Part1.57">C</a><ul>
     4976                  <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">1.3.2</a>, <a href="#rfc.xref.Part1.17">2</a>, <a href="#rfc.xref.Part1.18">2.2.1</a>, <a href="#rfc.xref.Part1.19">2.3.1</a>, <a href="#rfc.xref.Part1.20">2.3.7</a>, <a href="#rfc.xref.Part1.21">2.3.7</a>, <a href="#rfc.xref.Part1.22">2.3.8</a>, <a href="#rfc.xref.Part1.23">3</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.1</a>, <a href="#rfc.xref.Part1.29">3.2</a>, <a href="#rfc.xref.Part1.30">3.2</a>, <a href="#rfc.xref.Part1.31">3.3</a>, <a href="#rfc.xref.Part1.32">4.3.1</a>, <a href="#rfc.xref.Part1.33">4.3.2</a>, <a href="#rfc.xref.Part1.34">4.4.4</a>, <a href="#rfc.xref.Part1.35">4.4.6</a>, <a href="#rfc.xref.Part1.36">4.6.15</a>, <a href="#rfc.xref.Part1.37">4.7.6</a>, <a href="#rfc.xref.Part1.38">5.4</a>, <a href="#rfc.xref.Part1.39">5.4</a>, <a href="#rfc.xref.Part1.40">5.4</a>, <a href="#rfc.xref.Part1.41">5.4.1</a>, <a href="#rfc.xref.Part1.42">5.4.1</a>, <a href="#rfc.xref.Part1.43">6.1</a>, <a href="#rfc.xref.Part1.44">6.2</a>, <a href="#rfc.xref.Part1.45">7</a>, <a href="#rfc.xref.Part1.46">7.1</a>, <a href="#rfc.xref.Part1.47">9.3</a>, <a href="#rfc.xref.Part1.48">9.9</a>, <a href="#rfc.xref.Part1.49">9.9</a>, <a href="#rfc.xref.Part1.50">9.10</a>, <a href="#rfc.xref.Part1.51">9.17</a>, <a href="#rfc.xref.Part1.52">10.4</a>, <a href="#rfc.xref.Part1.53">10.4</a>, <a href="#rfc.xref.Part1.54">10.4</a>, <a href="#rfc.xref.Part1.55">12</a>, <a href="#Part1"><b>13.1</b></a>, <a href="#rfc.xref.Part1.56">A.6</a>, <a href="#rfc.xref.Part1.57">C</a><ul>
    49814977                        <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.3">1.3</a></li>
    49824978                        <li><em>Section 2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.2">1.2</a></li>
    … …  
    49854981                        <li><em>Section 2.7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.12">1.3.2</a>, <a href="#rfc.xref.Part1.14">1.3.2</a>, <a href="#rfc.xref.Part1.16">1.3.2</a></li>
    49864982                        <li><em>Section 3.2.1</em>&nbsp;&nbsp;<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></li>
    4987                         <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.23">3</a>, <a href="#rfc.xref.Part1.26">3.1</a>, <a href="#rfc.xref.Part1.48">10.9</a>, <a href="#rfc.xref.Part1.50">10.10</a></li>
     4983                        <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.23">3</a>, <a href="#rfc.xref.Part1.26">3.1</a>, <a href="#rfc.xref.Part1.48">9.9</a>, <a href="#rfc.xref.Part1.50">9.10</a></li>
    49884984                        <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.25">3.1</a></li>
    49894985                        <li><em>Section 3.2.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.24">3.1</a></li>
    4990                         <li><em>Section 3.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.18">2.2.1</a>, <a href="#rfc.xref.Part1.35">4.4.6</a>, <a href="#rfc.xref.Part1.38">5</a>, <a href="#rfc.xref.Part1.46">7.2</a></li>
     4986                        <li><em>Section 3.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.18">2.2.1</a>, <a href="#rfc.xref.Part1.35">4.4.6</a>, <a href="#rfc.xref.Part1.44">6.2</a>, <a href="#rfc.xref.Part1.45">7</a></li>
    49914987                        <li><em>Section 3.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.56">A.6</a></li>
    4992                         <li><em>Section 3.3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.45">7.1</a></li>
    4993                         <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.43">6.4.1</a></li>
     4988                        <li><em>Section 3.3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.43">6.1</a></li>
     4989                        <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.41">5.4.1</a></li>
    49944990                        <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.28">3.1</a></li>
    4995                         <li><em>Section 4.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.40">6.4</a>, <a href="#rfc.xref.Part1.52">11.4</a></li>
    4996                         <li><em>Section 4.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.44">6.4.1</a></li>
    4997                         <li><em>Section 4.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.41">6.4</a>, <a href="#rfc.xref.Part1.53">11.4</a></li>
    4998                         <li><em>Section 4.2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.42">6.4</a>, <a href="#rfc.xref.Part1.54">11.4</a></li>
     4991                        <li><em>Section 4.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.38">5.4</a>, <a href="#rfc.xref.Part1.52">10.4</a></li>
     4992                        <li><em>Section 4.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.42">5.4.1</a></li>
     4993                        <li><em>Section 4.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.39">5.4</a>, <a href="#rfc.xref.Part1.53">10.4</a></li>
     4994                        <li><em>Section 4.2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.40">5.4</a>, <a href="#rfc.xref.Part1.54">10.4</a></li>
    49994995                        <li><em>Section 4.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.15">1.3.2</a></li>
    50004996                        <li><em>Section 4.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.30">3.2</a></li>
    50014997                        <li><em>Section 5.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.19">2.3.1</a>, <a href="#rfc.xref.Part1.22">2.3.8</a></li>
    50024998                        <li><em>Section 5.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.29">3.2</a></li>
    5003                         <li><em>Section 5.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.17">2</a>, <a href="#rfc.xref.Part1.31">3.3</a>, <a href="#rfc.xref.Part1.39">5.1</a>, <a href="#rfc.xref.Part1.51">10.17</a></li>
     4999                        <li><em>Section 5.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.17">2</a>, <a href="#rfc.xref.Part1.31">3.3</a>, <a href="#rfc.xref.Part1.46">7.1</a>, <a href="#rfc.xref.Part1.51">9.17</a></li>
    50045000                        <li><em>Section 6.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.27">3.1</a></li>
    5005                         <li><em>Section 6.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.20">2.3.7</a>, <a href="#rfc.xref.Part1.49">10.9</a>, <a href="#rfc.xref.Part1.57">C</a></li>
    5006                         <li><em>Section 6.4.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.32">4.3.1</a>, <a href="#rfc.xref.Part1.47">10.3</a></li>
     5001                        <li><em>Section 6.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.20">2.3.7</a>, <a href="#rfc.xref.Part1.49">9.9</a>, <a href="#rfc.xref.Part1.57">C</a></li>
     5002                        <li><em>Section 6.4.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.32">4.3.1</a>, <a href="#rfc.xref.Part1.47">9.3</a></li>
    50075003                        <li><em>Section 6.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.33">4.3.2</a>, <a href="#rfc.xref.Part1.36">4.6.15</a></li>
    50085004                        <li><em>Section 7.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.21">2.3.7</a></li>
    5009                         <li><em>Section 9</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.55">13</a></li>
     5005                        <li><em>Section 9</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.55">12</a></li>
    50105006                     </ul>
    50115007                  </li>
    5012                   <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="#rfc.xref.Part4.11">8.1</a>, <a href="#rfc.xref.Part4.12">8.1</a>, <a href="#Part4"><b>14.1</b></a>, <a href="#rfc.xref.Part4.13">E.2</a><ul>
    5013                         <li><em>Section 2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.12">8.1</a></li>
    5014                         <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.11">8.1</a></li>
     5008                  <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="#rfc.xref.Part4.11">7.2</a>, <a href="#rfc.xref.Part4.12">7.2</a>, <a href="#Part4"><b>13.1</b></a>, <a href="#rfc.xref.Part4.13">E.2</a><ul>
     5009                        <li><em>Section 2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.12">7.2</a></li>
     5010                        <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.11">7.2</a></li>
    50155011                        <li><em>Section 3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">3.2</a></li>
    50165012                        <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.3">3.2</a></li>
    … …  
    50225018                     </ul>
    50235019                  </li>
    5024                   <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="#rfc.xref.Part5.8">7.1</a>, <a href="#Part5"><b>14.1</b></a><ul>
     5020                  <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="#rfc.xref.Part5.8">6.1</a>, <a href="#Part5"><b>13.1</b></a><ul>
    50255021                        <li><em>Section 3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.5">4.1</a></li>
    50265022                        <li><em>Section 3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.6">4.1</a></li>
    50275023                        <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.7">4.1</a></li>
    50285024                        <li><em>Section 5.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.4">3.3</a></li>
    5029                         <li><em>Section 5.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.8">7.1</a></li>
     5025                        <li><em>Section 5.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.8">6.1</a></li>
    50305026                        <li><em>Section 5.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.2">3.2</a></li>
    50315027                        <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>
    50325028                     </ul>
    50335029                  </li>
    5034                   <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="#rfc.xref.Part6.18">8.1</a>, <a href="#rfc.xref.Part6.19">9.1</a>, <a href="#Part6"><b>14.1</b></a><ul>
     5030                  <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="#rfc.xref.Part6.18">7.2</a>, <a href="#rfc.xref.Part6.19">8.1</a>, <a href="#Part6"><b>13.1</b></a><ul>
    50355031                        <li><em>Section 2.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.4">2.3.4</a></li>
    50365032                        <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>
    … …  
    50395035                        <li><em>Section 3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.8">3.3</a></li>
    50405036                        <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.12">4.4.4</a></li>
    5041                         <li><em>Section 3.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.18">8.1</a></li>
    5042                         <li><em>Section 3.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.9">3.3</a>, <a href="#rfc.xref.Part6.19">9.1</a></li>
     5037                        <li><em>Section 3.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.18">7.2</a></li>
     5038                        <li><em>Section 3.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.9">3.3</a>, <a href="#rfc.xref.Part6.19">8.1</a></li>
    50435039                        <li><em>Section 3.6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.13">4.4.4</a></li>
    50445040                     </ul>
    50455041                  </li>
    5046                   <li><em>Part7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.1">3.2</a>, <a href="#rfc.xref.Part7.2">3.2</a>, <a href="#rfc.xref.Part7.3">3.3</a>, <a href="#rfc.xref.Part7.4">3.3</a>, <a href="#rfc.xref.Part7.5">4.1</a>, <a href="#rfc.xref.Part7.6">4.1</a>, <a href="#rfc.xref.Part7.7">4.1</a>, <a href="#Part7"><b>14.1</b></a><ul>
     5042                  <li><em>Part7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.1">3.2</a>, <a href="#rfc.xref.Part7.2">3.2</a>, <a href="#rfc.xref.Part7.3">3.3</a>, <a href="#rfc.xref.Part7.4">3.3</a>, <a href="#rfc.xref.Part7.5">4.1</a>, <a href="#rfc.xref.Part7.6">4.1</a>, <a href="#rfc.xref.Part7.7">4.1</a>, <a href="#Part7"><b>13.1</b></a><ul>
    50475043                        <li><em>Section 3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.5">4.1</a></li>
    50485044                        <li><em>Section 3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.6">4.1</a></li>
    … …  
    50545050                     </ul>
    50555051                  </li>
    5056                   <li>payload&nbsp;&nbsp;<a href="#rfc.iref.p.3">7</a></li>
    5057                   <li>POST method&nbsp;&nbsp;<a href="#rfc.iref.p.1"><b>2.3.4</b></a>, <a href="#rfc.xref.POST.1">11.1</a>, <a href="#rfc.xref.POST.2">C</a></li>
    5058                   <li>PUT method&nbsp;&nbsp;<a href="#rfc.iref.p.2"><b>2.3.5</b></a>, <a href="#rfc.xref.PUT.1">11.1</a>, <a href="#rfc.xref.PUT.2">C</a></li>
     5052                  <li>payload&nbsp;&nbsp;<a href="#rfc.iref.p.3">6</a></li>
     5053                  <li>POST method&nbsp;&nbsp;<a href="#rfc.iref.p.1"><b>2.3.4</b></a>, <a href="#rfc.xref.POST.1">10.1</a>, <a href="#rfc.xref.POST.2">C</a></li>
     5054                  <li>PUT method&nbsp;&nbsp;<a href="#rfc.iref.p.2"><b>2.3.5</b></a>, <a href="#rfc.xref.PUT.1">10.1</a>, <a href="#rfc.xref.PUT.2">C</a></li>
    50595055               </ul>
    50605056            </li>
    50615057            <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul>
    5062                   <li>Referer header field&nbsp;&nbsp;<a href="#rfc.xref.header.referer.1">3.2</a>, <a href="#rfc.iref.r.2"><b>10.7</b></a>, <a href="#rfc.xref.header.referer.2">11.3</a>, <a href="#rfc.xref.header.referer.3">C</a></li>
    5063                   <li>representation&nbsp;&nbsp;<a href="#rfc.iref.r.1">8</a></li>
    5064                   <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.3"><b>10.8</b></a>, <a href="#rfc.xref.header.retry-after.3">11.3</a></li>
    5065                   <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>14.2</b></a><ul>
    5066                         <li><em>Section 5.2.14</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1123.2">6.1</a></li>
     5058                  <li>Referer header field&nbsp;&nbsp;<a href="#rfc.xref.header.referer.1">3.2</a>, <a href="#rfc.iref.r.2"><b>9.7</b></a>, <a href="#rfc.xref.header.referer.2">10.3</a>, <a href="#rfc.xref.header.referer.3">C</a></li>
     5059                  <li>representation&nbsp;&nbsp;<a href="#rfc.iref.r.1">7</a></li>
     5060                  <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.3"><b>9.8</b></a>, <a href="#rfc.xref.header.retry-after.3">10.3</a></li>
     5061                  <li><em>RFC1123</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1123.1">5.1</a>, <a href="#rfc.xref.RFC1123.2">5.1</a>, <a href="#RFC1123"><b>13.2</b></a><ul>
     5062                        <li><em>Section 5.2.14</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1123.2">5.1</a></li>
    50675063                     </ul>
    50685064                  </li>
    5069                   <li><em>RFC1945</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1945.1">4.5</a>, <a href="#RFC1945"><b>14.2</b></a>, <a href="#rfc.xref.RFC1945.2">B</a><ul>
     5065                  <li><em>RFC1945</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1945.1">4.5</a>, <a href="#RFC1945"><b>13.2</b></a>, <a href="#rfc.xref.RFC1945.2">B</a><ul>
    50705066                        <li><em>Section 9.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1945.1">4.5</a></li>
    50715067                     </ul>
    50725068                  </li>
    5073                   <li><em>RFC1950</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1950.1">11.4</a>, <a href="#RFC1950"><b>14.1</b></a></li>
    5074                   <li><em>RFC1951</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1951.1">11.4</a>, <a href="#RFC1951"><b>14.1</b></a></li>
    5075                   <li><em>RFC1952</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1952.1">11.4</a>, <a href="#RFC1952"><b>14.1</b></a></li>
    5076                   <li><em>RFC2045</em>&nbsp;&nbsp;<a href="#RFC2045"><b>14.1</b></a>, <a href="#rfc.xref.RFC2045.1">A</a>, <a href="#rfc.xref.RFC2045.2">A.1</a></li>
    5077                   <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="#rfc.xref.RFC2046.3">8.2</a>, <a href="#RFC2046"><b>14.1</b></a>, <a href="#rfc.xref.RFC2046.4">A.2</a><ul>
    5078                         <li><em>Section 4.5.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2046.3">8.2</a></li>
    5079                         <li><em>Section 5.1.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2046.2">6.5.2</a></li>
     5069                  <li><em>RFC1950</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1950.1">10.4</a>, <a href="#RFC1950"><b>13.1</b></a></li>
     5070                  <li><em>RFC1951</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1951.1">10.4</a>, <a href="#RFC1951"><b>13.1</b></a></li>
     5071                  <li><em>RFC1952</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1952.1">10.4</a>, <a href="#RFC1952"><b>13.1</b></a></li>
     5072                  <li><em>RFC2045</em>&nbsp;&nbsp;<a href="#RFC2045"><b>13.1</b></a>, <a href="#rfc.xref.RFC2045.1">A</a>, <a href="#rfc.xref.RFC2045.2">A.1</a></li>
     5073                  <li><em>RFC2046</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2046.1">5.5</a>, <a href="#rfc.xref.RFC2046.2">5.5.2</a>, <a href="#rfc.xref.RFC2046.3">7.3</a>, <a href="#RFC2046"><b>13.1</b></a>, <a href="#rfc.xref.RFC2046.4">A.2</a><ul>
     5074                        <li><em>Section 4.5.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2046.3">7.3</a></li>
     5075                        <li><em>Section 5.1.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2046.2">5.5.2</a></li>
    50805076                     </ul>
    50815077                  </li>
    5082                   <li><em>RFC2049</em>&nbsp;&nbsp;<a href="#RFC2049"><b>14.2</b></a>, <a href="#rfc.xref.RFC2049.1">A.2</a><ul>
     5078                  <li><em>RFC2049</em>&nbsp;&nbsp;<a href="#RFC2049"><b>13.2</b></a>, <a href="#rfc.xref.RFC2049.1">A.2</a><ul>
    50835079                        <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2049.1">A.2</a></li>
    50845080                     </ul>
    50855081                  </li>
    5086                   <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>14.2</b></a>, <a href="#rfc.xref.RFC2068.3">B</a><ul>
     5082                  <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>13.2</b></a>, <a href="#rfc.xref.RFC2068.3">B</a><ul>
    50875083                        <li><em>Section 10.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2068.2">4.5</a></li>
    50885084                        <li><em>Section 10.3.4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2068.1">4.5</a></li>
    50895085                     </ul>
    50905086                  </li>
    5091                   <li><em>RFC2076</em>&nbsp;&nbsp;<a href="#RFC2076"><b>14.2</b></a>, <a href="#rfc.xref.RFC2076.1">B</a></li>
    5092                   <li><em>RFC2119</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2119.1">1.2</a>, <a href="#RFC2119"><b>14.1</b></a></li>
    5093                   <li><em>RFC2277</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2277.1">6.3</a>, <a href="#RFC2277"><b>14.2</b></a></li>
    5094                   <li><em>RFC2295</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2295.1">9</a>, <a href="#RFC2295"><b>14.1</b></a></li>
    5095                   <li><em>RFC2388</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2388.1">6.5.2</a>, <a href="#RFC2388"><b>14.2</b></a></li>
    5096                   <li><em>RFC2557</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2557.1">10.17</a>, <a href="#RFC2557"><b>14.2</b></a>, <a href="#rfc.xref.RFC2557.2">A.7</a><ul>
    5097                         <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2557.1">10.17</a></li>
     5087                  <li><em>RFC2076</em>&nbsp;&nbsp;<a href="#RFC2076"><b>13.2</b></a>, <a href="#rfc.xref.RFC2076.1">B</a></li>
     5088                  <li><em>RFC2119</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2119.1">1.2</a>, <a href="#RFC2119"><b>13.1</b></a></li>
     5089                  <li><em>RFC2277</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2277.1">5.3</a>, <a href="#RFC2277"><b>13.2</b></a></li>
     5090                  <li><em>RFC2295</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2295.1">8</a>, <a href="#RFC2295"><b>13.1</b></a></li>
     5091                  <li><em>RFC2388</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2388.1">5.5.2</a>, <a href="#RFC2388"><b>13.2</b></a></li>
     5092                  <li><em>RFC2557</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2557.1">9.17</a>, <a href="#RFC2557"><b>13.2</b></a>, <a href="#rfc.xref.RFC2557.2">A.7</a><ul>
     5093                        <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2557.1">9.17</a></li>
    50985094                     </ul>
    50995095                  </li>
    5100                   <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">10.14</a>, <a href="#RFC2616"><b>14.2</b></a>, <a href="#rfc.xref.RFC2616.4">E.1</a><ul>
     5096                  <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">9.14</a>, <a href="#RFC2616"><b>13.2</b></a>, <a href="#rfc.xref.RFC2616.4">E.1</a><ul>
    51015097                        <li><em>Section 10.3.8</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.2">4.5</a></li>
    5102                         <li><em>Section 14.4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.3">10.14</a></li>
     5098                        <li><em>Section 14.4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.3">9.14</a></li>
    51035099                     </ul>
    51045100                  </li>
    5105                   <li><em>RFC2817</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2817.1">11.2</a>, <a href="#RFC2817"><b>14.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>
    5106                         <li><em>Section 7.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2817.1">11.2</a>, <a href="#rfc.xref.RFC2817.3">C</a></li>
     5101                  <li><em>RFC2817</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2817.1">10.2</a>, <a href="#RFC2817"><b>13.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>
     5102                        <li><em>Section 7.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2817.1">10.2</a>, <a href="#rfc.xref.RFC2817.3">C</a></li>
    51075103                     </ul>
    51085104                  </li>
    5109                   <li><em>RFC3629</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3629.1">6.3</a>, <a href="#RFC3629"><b>14.2</b></a></li>
    5110                   <li><em>RFC3864</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3864.1">3.1</a>, <a href="#rfc.xref.RFC3864.2">3.1</a>, <a href="#rfc.xref.RFC3864.3">11.3</a>, <a href="#RFC3864"><b>14.2</b></a><ul>
     5105                  <li><em>RFC3629</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3629.1">5.3</a>, <a href="#RFC3629"><b>13.2</b></a></li>
     5106                  <li><em>RFC3864</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3864.1">3.1</a>, <a href="#rfc.xref.RFC3864.2">3.1</a>, <a href="#rfc.xref.RFC3864.3">10.3</a>, <a href="#RFC3864"><b>13.2</b></a><ul>
    51115107                        <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3864.2">3.1</a></li>
    51125108                     </ul>
    51135109                  </li>
    5114                   <li><em>RFC3986</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.1">10.5</a>, <a href="#rfc.xref.RFC3986.2">10.5</a>, <a href="#RFC3986"><b>14.1</b></a><ul>
    5115                         <li><em>Section 4.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.1">10.5</a></li>
    5116                         <li><em>Section 5</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.2">10.5</a></li>
     5110                  <li><em>RFC3986</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.1">9.5</a>, <a href="#rfc.xref.RFC3986.2">9.5</a>, <a href="#RFC3986"><b>13.1</b></a><ul>
     5111                        <li><em>Section 4.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.1">9.5</a></li>
     5112                        <li><em>Section 5</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.2">9.5</a></li>
    51175113                     </ul>
    51185114                  </li>
    5119                   <li><em>RFC4288</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC4288.1">6.5</a>, <a href="#RFC4288"><b>14.1</b></a></li>
    5120                   <li><em>RFC4647</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC4647.1">10.14</a>, <a href="#rfc.xref.RFC4647.2">10.14</a>, <a href="#rfc.xref.RFC4647.3">10.14</a>, <a href="#rfc.xref.RFC4647.4">10.14</a>, <a href="#RFC4647"><b>14.1</b></a><ul>
    5121                         <li><em>Section 2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC4647.1">10.14</a></li>
    5122                         <li><em>Section 2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC4647.2">10.14</a></li>
    5123                         <li><em>Section 3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC4647.3">10.14</a></li>
    5124                         <li><em>Section 3.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC4647.4">10.14</a></li>
     5115                  <li><em>RFC4288</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC4288.1">5.5</a>, <a href="#RFC4288"><b>13.1</b></a></li>
     5116                  <li><em>RFC4647</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC4647.1">9.14</a>, <a href="#rfc.xref.RFC4647.2">9.14</a>, <a href="#rfc.xref.RFC4647.3">9.14</a>, <a href="#rfc.xref.RFC4647.4">9.14</a>, <a href="#RFC4647"><b>13.1</b></a><ul>
     5117                        <li><em>Section 2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC4647.1">9.14</a></li>
     5118                        <li><em>Section 2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC4647.2">9.14</a></li>
     5119                        <li><em>Section 3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC4647.3">9.14</a></li>
     5120                        <li><em>Section 3.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC4647.4">9.14</a></li>
    51255121                     </ul>
    51265122                  </li>
    5127                   <li><em>RFC5226</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5226.1">2.2</a>, <a href="#rfc.xref.RFC5226.2">4.2</a>, <a href="#rfc.xref.RFC5226.3">6.4.1</a>, <a href="#RFC5226"><b>14.2</b></a><ul>
    5128                         <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5226.1">2.2</a>, <a href="#rfc.xref.RFC5226.2">4.2</a>, <a href="#rfc.xref.RFC5226.3">6.4.1</a></li>
     5123                  <li><em>RFC5226</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5226.1">2.2</a>, <a href="#rfc.xref.RFC5226.2">4.2</a>, <a href="#rfc.xref.RFC5226.3">5.4.1</a>, <a href="#RFC5226"><b>13.2</b></a><ul>
     5124                        <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5226.1">2.2</a>, <a href="#rfc.xref.RFC5226.2">4.2</a>, <a href="#rfc.xref.RFC5226.3">5.4.1</a></li>
    51295125                     </ul>
    51305126                  </li>
    5131                   <li><em>RFC5234</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.1">1.3</a>, <a href="#rfc.xref.RFC5234.2">1.3</a>, <a href="#rfc.xref.RFC5234.3">3.1</a>, <a href="#RFC5234"><b>14.1</b></a><ul>
     5127                  <li><em>RFC5234</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.1">1.3</a>, <a href="#rfc.xref.RFC5234.2">1.3</a>, <a href="#rfc.xref.RFC5234.3">3.1</a>, <a href="#RFC5234"><b>13.1</b></a><ul>
    51325128                        <li><em>Appendix B.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.2">1.3</a></li>
    51335129                     </ul>
    51345130                  </li>
    5135                   <li><em>RFC5322</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5322.1">6.1</a>, <a href="#rfc.xref.RFC5322.2">10.2</a>, <a href="#rfc.xref.RFC5322.3">10.4</a>, <a href="#rfc.xref.RFC5322.4">10.4</a>, <a href="#RFC5322"><b>14.2</b></a>, <a href="#rfc.xref.RFC5322.5">A</a><ul>
    5136                         <li><em>Section 3.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5322.1">6.1</a></li>
    5137                         <li><em>Section 3.4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5322.3">10.4</a>, <a href="#rfc.xref.RFC5322.4">10.4</a></li>
    5138                         <li><em>Section 3.6.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5322.2">10.2</a></li>
     5131                  <li><em>RFC5322</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5322.1">5.1</a>, <a href="#rfc.xref.RFC5322.2">9.2</a>, <a href="#rfc.xref.RFC5322.3">9.4</a>, <a href="#rfc.xref.RFC5322.4">9.4</a>, <a href="#RFC5322"><b>13.2</b></a>, <a href="#rfc.xref.RFC5322.5">A</a><ul>
     5132                        <li><em>Section 3.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5322.1">5.1</a></li>
     5133                        <li><em>Section 3.4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5322.3">9.4</a>, <a href="#rfc.xref.RFC5322.4">9.4</a></li>
     5134                        <li><em>Section 3.6.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5322.2">9.2</a></li>
    51395135                     </ul>
    51405136                  </li>
    5141                   <li><em>RFC5646</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5646.1">6.6</a>, <a href="#rfc.xref.RFC5646.2">6.6</a>, <a href="#rfc.xref.RFC5646.3">6.6</a>, <a href="#RFC5646"><b>14.1</b></a><ul>
    5142                         <li><em>Section 2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5646.2">6.6</a></li>
     5137                  <li><em>RFC5646</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5646.1">5.6</a>, <a href="#rfc.xref.RFC5646.2">5.6</a>, <a href="#rfc.xref.RFC5646.3">5.6</a>, <a href="#RFC5646"><b>13.1</b></a><ul>
     5138                        <li><em>Section 2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5646.2">5.6</a></li>
    51435139                     </ul>
    51445140                  </li>
    5145                   <li><em>RFC5789</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5789.1">2.3.5</a>, <a href="#RFC5789"><b>14.2</b></a></li>
    5146                   <li><em>RFC5987</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5987.1">3.1</a>, <a href="#RFC5987"><b>14.2</b></a></li>
    5147                   <li><em>RFC6151</em>&nbsp;&nbsp;<a href="#RFC6151"><b>14.2</b></a>, <a href="#rfc.xref.RFC6151.1">C</a></li>
    5148                   <li><em>RFC6266</em>&nbsp;&nbsp;<a href="#RFC6266"><b>14.2</b></a>, <a href="#rfc.xref.RFC6266.1">B</a>, <a href="#rfc.xref.RFC6266.2">C</a></li>
     5141                  <li><em>RFC5789</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5789.1">2.3.5</a>, <a href="#RFC5789"><b>13.2</b></a></li>
     5142                  <li><em>RFC5987</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5987.1">3.1</a>, <a href="#RFC5987"><b>13.2</b></a></li>
     5143                  <li><em>RFC6151</em>&nbsp;&nbsp;<a href="#RFC6151"><b>13.2</b></a>, <a href="#rfc.xref.RFC6151.1">C</a></li>
     5144                  <li><em>RFC6266</em>&nbsp;&nbsp;<a href="#RFC6266"><b>13.2</b></a>, <a href="#rfc.xref.RFC6266.1">B</a>, <a href="#rfc.xref.RFC6266.2">C</a></li>
    51495145               </ul>
    51505146            </li>
    … …  
    51525148                  <li>Safe Methods&nbsp;&nbsp;<a href="#rfc.iref.s.2"><b>2.1.1</b></a></li>
    51535149                  <li>selected representation&nbsp;&nbsp;<a href="#rfc.iref.s.1"><b>1.1</b></a></li>
    5154                   <li>Server header field&nbsp;&nbsp;<a href="#rfc.xref.header.server.1">3.3</a>, <a href="#rfc.iref.s.39"><b>10.9</b></a>, <a href="#rfc.xref.header.server.2">11.3</a>, <a href="#rfc.xref.header.server.3">12.1</a>, <a href="#rfc.xref.header.server.4">C</a></li>
     5150                  <li>Server header field&nbsp;&nbsp;<a href="#rfc.xref.header.server.1">3.3</a>, <a href="#rfc.iref.s.39"><b>9.9</b></a>, <a href="#rfc.xref.header.server.2">10.3</a>, <a href="#rfc.xref.header.server.3">11.1</a>, <a href="#rfc.xref.header.server.4">C</a></li>
    51555151                  <li>Status Codes&nbsp;&nbsp;
    51565152                     <ul>
    5157                         <li>100 Continue&nbsp;&nbsp;<a href="#rfc.xref.status.100.1">4.1</a>, <a href="#rfc.iref.s.3"><b>4.3.1</b></a>, <a href="#rfc.xref.status.100.2">11.2</a></li>
    5158                         <li>101 Switching Protocols&nbsp;&nbsp;<a href="#rfc.xref.status.101.1">4.1</a>, <a href="#rfc.iref.s.4"><b>4.3.2</b></a>, <a href="#rfc.xref.status.101.2">11.2</a></li>
    5159                         <li>200 OK&nbsp;&nbsp;<a href="#rfc.xref.status.200.1">4.1</a>, <a href="#rfc.iref.s.5"><b>4.4.1</b></a>, <a href="#rfc.xref.status.200.2">11.2</a></li>
    5160                         <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">11.2</a></li>
    5161                         <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">11.2</a></li>
    5162                         <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">11.2</a>, <a href="#rfc.xref.status.203.3">C</a></li>
    5163                         <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">11.2</a></li>
    5164                         <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">11.2</a></li>
    5165                         <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">11.2</a></li>
    5166                         <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">11.2</a>, <a href="#rfc.xref.status.301.3">C</a></li>
    5167                         <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">11.2</a>, <a href="#rfc.xref.status.302.3">C</a></li>
    5168                         <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">11.2</a></li>
    5169                         <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">11.2</a>, <a href="#rfc.xref.status.305.3">C</a></li>
    5170                         <li>306 (Unused)&nbsp;&nbsp;<a href="#rfc.iref.s.16"><b>4.5.6</b></a>, <a href="#rfc.xref.status.306.1">11.2</a></li>
    5171                         <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">11.2</a>, <a href="#rfc.xref.status.307.3">C</a></li>
    5172                         <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">11.2</a></li>
    5173                         <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">11.2</a></li>
    5174                         <li>403 Forbidden&nbsp;&nbsp;<a href="#rfc.xref.status.403.1">4.1</a>, <a href="#rfc.iref.s.20"><b>4.6.3</b></a>, <a href="#rfc.xref.status.403.2">11.2</a></li>
    5175                         <li>404 Not Found&nbsp;&nbsp;<a href="#rfc.xref.status.404.1">4.1</a>, <a href="#rfc.iref.s.21"><b>4.6.4</b></a>, <a href="#rfc.xref.status.404.2">11.2</a></li>
    5176                         <li>405 Method Not Allowed&nbsp;&nbsp;<a href="#rfc.xref.status.405.1">4.1</a>, <a href="#rfc.iref.s.22"><b>4.6.5</b></a>, <a href="#rfc.xref.status.405.2">11.2</a></li>
    5177                         <li>406 Not Acceptable&nbsp;&nbsp;<a href="#rfc.xref.status.406.1">4.1</a>, <a href="#rfc.iref.s.23"><b>4.6.6</b></a>, <a href="#rfc.xref.status.406.2">11.2</a></li>
    5178                         <li>408 Request Timeout&nbsp;&nbsp;<a href="#rfc.xref.status.408.1">4.1</a>, <a href="#rfc.iref.s.24"><b>4.6.7</b></a>, <a href="#rfc.xref.status.408.2">11.2</a></li>
    5179                         <li>409 Conflict&nbsp;&nbsp;<a href="#rfc.xref.status.409.1">4.1</a>, <a href="#rfc.iref.s.25"><b>4.6.8</b></a>, <a href="#rfc.xref.status.409.2">11.2</a></li>
    5180                         <li>410 Gone&nbsp;&nbsp;<a href="#rfc.xref.status.410.1">4.1</a>, <a href="#rfc.iref.s.26"><b>4.6.9</b></a>, <a href="#rfc.xref.status.410.2">11.2</a></li>
    5181                         <li>411 Length Required&nbsp;&nbsp;<a href="#rfc.xref.status.411.1">4.1</a>, <a href="#rfc.iref.s.27"><b>4.6.10</b></a>, <a href="#rfc.xref.status.411.2">11.2</a></li>
    5182                         <li>413 Request Representation Too Large&nbsp;&nbsp;<a href="#rfc.xref.status.413.1">4.1</a>, <a href="#rfc.iref.s.28"><b>4.6.11</b></a>, <a href="#rfc.xref.status.413.2">11.2</a></li>
    5183                         <li>414 URI Too Long&nbsp;&nbsp;<a href="#rfc.xref.status.414.1">4.1</a>, <a href="#rfc.iref.s.29"><b>4.6.12</b></a>, <a href="#rfc.xref.status.414.2">11.2</a></li>
    5184                         <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">11.2</a></li>
    5185                         <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">11.2</a></li>
    5186                         <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">11.2</a>, <a href="#rfc.xref.status.426.3">C</a></li>
    5187                         <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">11.2</a></li>
    5188                         <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">11.2</a></li>
    5189                         <li>502 Bad Gateway&nbsp;&nbsp;<a href="#rfc.xref.status.502.1">4.1</a>, <a href="#rfc.iref.s.35"><b>4.7.3</b></a>, <a href="#rfc.xref.status.502.2">11.2</a></li>
    5190                         <li>503 Service Unavailable&nbsp;&nbsp;<a href="#rfc.xref.status.503.1">4.1</a>, <a href="#rfc.iref.s.36"><b>4.7.4</b></a>, <a href="#rfc.xref.status.503.2">11.2</a></li>
    5191                         <li>504 Gateway Timeout&nbsp;&nbsp;<a href="#rfc.xref.status.504.1">4.1</a>, <a href="#rfc.iref.s.37"><b>4.7.5</b></a>, <a href="#rfc.xref.status.504.2">11.2</a></li>
    5192                         <li>505 HTTP Version Not Supported&nbsp;&nbsp;<a href="#rfc.xref.status.505.1">4.1</a>, <a href="#rfc.iref.s.38"><b>4.7.6</b></a>, <a href="#rfc.xref.status.505.2">11.2</a></li>
     5153                        <li>100 Continue&nbsp;&nbsp;<a href="#rfc.xref.status.100.1">4.1</a>, <a href="#rfc.iref.s.3"><b>4.3.1</b></a>, <a href="#rfc.xref.status.100.2">10.2</a></li>
     5154                        <li>101 Switching Protocols&nbsp;&nbsp;<a href="#rfc.xref.status.101.1">4.1</a>, <a href="#rfc.iref.s.4"><b>4.3.2</b></a>, <a href="#rfc.xref.status.101.2">10.2</a></li>
     5155                        <li>200 OK&nbsp;&nbsp;<a href="#rfc.xref.status.200.1">4.1</a>, <a href="#rfc.iref.s.5"><b>4.4.1</b></a>, <a href="#rfc.xref.status.200.2">10.2</a></li>
     5156                        <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">10.2</a></li>
     5157                        <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">10.2</a></li>
     5158                        <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">10.2</a>, <a href="#rfc.xref.status.203.3">C</a></li>
     5159                        <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">10.2</a></li>
     5160                        <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">10.2</a></li>
     5161                        <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">10.2</a></li>
     5162                        <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">10.2</a>, <a href="#rfc.xref.status.301.3">C</a></li>
     5163                        <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">10.2</a>, <a href="#rfc.xref.status.302.3">C</a></li>
     5164                        <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">10.2</a></li>
     5165                        <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">10.2</a>, <a href="#rfc.xref.status.305.3">C</a></li>
     5166                        <li>306 (Unused)&nbsp;&nbsp;<a href="#rfc.iref.s.16"><b>4.5.6</b></a>, <a href="#rfc.xref.status.306.1">10.2</a></li>
     5167                        <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">10.2</a>, <a href="#rfc.xref.status.307.3">C</a></li>
     5168                        <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">10.2</a></li>
     5169                        <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">10.2</a></li>
     5170                        <li>403 Forbidden&nbsp;&nbsp;<a href="#rfc.xref.status.403.1">4.1</a>, <a href="#rfc.iref.s.20"><b>4.6.3</b></a>, <a href="#rfc.xref.status.403.2">10.2</a></li>
     5171                        <li>404 Not Found&nbsp;&nbsp;<a href="#rfc.xref.status.404.1">4.1</a>, <a href="#rfc.iref.s.21"><b>4.6.4</b></a>, <a href="#rfc.xref.status.404.2">10.2</a></li>
     5172                        <li>405 Method Not Allowed&nbsp;&nbsp;<a href="#rfc.xref.status.405.1">4.1</a>, <a href="#rfc.iref.s.22"><b>4.6.5</b></a>, <a href="#rfc.xref.status.405.2">10.2</a></li>
     5173                        <li>406 Not Acceptable&nbsp;&nbsp;<a href="#rfc.xref.status.406.1">4.1</a>, <a href="#rfc.iref.s.23"><b>4.6.6</b></a>, <a href="#rfc.xref.status.406.2">10.2</a></li>
     5174                        <li>408 Request Timeout&nbsp;&nbsp;<a href="#rfc.xref.status.408.1">4.1</a>, <a href="#rfc.iref.s.24"><b>4.6.7</b></a>, <a href="#rfc.xref.status.408.2">10.2</a></li>
     5175                        <li>409 Conflict&nbsp;&nbsp;<a href="#rfc.xref.status.409.1">4.1</a>, <a href="#rfc.iref.s.25"><b>4.6.8</b></a>, <a href="#rfc.xref.status.409.2">10.2</a></li>
     5176                        <li>410 Gone&nbsp;&nbsp;<a href="#rfc.xref.status.410.1">4.1</a>, <a href="#rfc.iref.s.26"><b>4.6.9</b></a>, <a href="#rfc.xref.status.410.2">10.2</a></li>
     5177                        <li>411 Length Required&nbsp;&nbsp;<a href="#rfc.xref.status.411.1">4.1</a>, <a href="#rfc.iref.s.27"><b>4.6.10</b></a>, <a href="#rfc.xref.status.411.2">10.2</a></li>
     5178                        <li>413 Request Representation Too Large&nbsp;&nbsp;<a href="#rfc.xref.status.413.1">4.1</a>, <a href="#rfc.iref.s.28"><b>4.6.11</b></a>, <a href="#rfc.xref.status.413.2">10.2</a></li>
     5179                        <li>414 URI Too Long&nbsp;&nbsp;<a href="#rfc.xref.status.414.1">4.1</a>, <a href="#rfc.iref.s.29"><b>4.6.12</b></a>, <a href="#rfc.xref.status.414.2">10.2</a></li>
     5180                        <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">10.2</a></li>
     5181                        <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">10.2</a></li>
     5182                        <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">10.2</a>, <a href="#rfc.xref.status.426.3">C</a></li>
     5183                        <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">10.2</a></li>
     5184                        <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">10.2</a></li>
     5185                        <li>502 Bad Gateway&nbsp;&nbsp;<a href="#rfc.xref.status.502.1">4.1</a>, <a href="#rfc.iref.s.35"><b>4.7.3</b></a>, <a href="#rfc.xref.status.502.2">10.2</a></li>
     5186                        <li>503 Service Unavailable&nbsp;&nbsp;<a href="#rfc.xref.status.503.1">4.1</a>, <a href="#rfc.iref.s.36"><b>4.7.4</b></a>, <a href="#rfc.xref.status.503.2">10.2</a></li>
     5187                        <li>504 Gateway Timeout&nbsp;&nbsp;<a href="#rfc.xref.status.504.1">4.1</a>, <a href="#rfc.iref.s.37"><b>4.7.5</b></a>, <a href="#rfc.xref.status.504.2">10.2</a></li>
     5188                        <li>505 HTTP Version Not Supported&nbsp;&nbsp;<a href="#rfc.xref.status.505.1">4.1</a>, <a href="#rfc.iref.s.38"><b>4.7.6</b></a>, <a href="#rfc.xref.status.505.2">10.2</a></li>
    51935189                     </ul>
    51945190                  </li>
    … …  
    51965192            </li>
    51975193            <li><a id="rfc.index.T" href="#rfc.index.T"><b>T</b></a><ul>
    5198                   <li>TRACE method&nbsp;&nbsp;<a href="#rfc.iref.t.1"><b>2.3.7</b></a>, <a href="#rfc.xref.TRACE.1">10.6</a>, <a href="#rfc.xref.TRACE.2">11.1</a>, <a href="#rfc.xref.TRACE.3">12.1</a></li>
     5194                  <li>TRACE method&nbsp;&nbsp;<a href="#rfc.iref.t.1"><b>2.3.7</b></a>, <a href="#rfc.xref.TRACE.1">9.6</a>, <a href="#rfc.xref.TRACE.2">10.1</a>, <a href="#rfc.xref.TRACE.3">11.1</a></li>
    51995195               </ul>
    52005196            </li>
    52015197            <li><a id="rfc.index.U" href="#rfc.index.U"><b>U</b></a><ul>
    5202                   <li>User-Agent header field&nbsp;&nbsp;<a href="#rfc.xref.header.user-agent.1">3.2</a>, <a href="#rfc.xref.header.user-agent.2">9.1</a>, <a href="#rfc.iref.u.1"><b>10.10</b></a>, <a href="#rfc.xref.header.user-agent.3">11.3</a>, <a href="#rfc.xref.header.user-agent.4">12.1</a></li>
     5198                  <li>User-Agent header field&nbsp;&nbsp;<a href="#rfc.xref.header.user-agent.1">3.2</a>, <a href="#rfc.xref.header.user-agent.2">8.1</a>, <a href="#rfc.iref.u.1"><b>9.10</b></a>, <a href="#rfc.xref.header.user-agent.3">10.3</a>, <a href="#rfc.xref.header.user-agent.4">11.1</a></li>
    52035199               </ul>
    52045200            </li>

  • draft-ietf-httpbis/experiment/p2-semantics.xml

    r1630 r1631  
    20932093</section>
    20942094
    2095 <section title="Representation" anchor="representation">
    2096 <t>
    2097    Request and Response messages &MAY; transfer a representation if not otherwise
    2098    restricted by the request method or response status code. A representation
    2099    consists of metadata (representation header fields) and data (representation
    2100    body).  When a complete or partial representation is enclosed in an HTTP message,
    2101    it is referred to as the payload of the message. HTTP representations
    2102    are defined in <xref target="payload"/>.
    2103 </t>
    2104 <t>
    2105    A representation body is only present in a message when a message body is
    2106    present, as described in &message-body;. The representation body is obtained
    2107    from the message body by decoding any Transfer-Encoding that might
    2108    have been applied to ensure safe and proper transfer of the message.
    2109 </t>
    2110 
    2111 <section title="Identifying the Resource Associated with a Representation" anchor="identifying.response.associated.with.representation">
    2112 <t>
    2113    It is sometimes necessary to determine an identifier for the resource
    2114    associated with a representation.
    2115 </t>
    2116 <t>
    2117    An HTTP request representation, when present, is always associated with an
    2118    anonymous (i.e., unidentified) resource.
    2119 </t>
    2120 <t>
    2121    In the common case, an HTTP response is a representation of the target
    2122    resource (see &effective-request-uri;). However, this is not always the
    2123    case. To determine the URI of the resource a response is associated with,
    2124    the following rules are used (with the first applicable one being selected):
    2125 </t>
    2126 <t><list style="numbers">
    2127    <t>If the response status code is 200 or 203 and the request method was GET,
    2128    the response payload is a representation of the target resource.</t>
    2129    <t>If the response status code is 204, 206, or 304 and the request method was GET
    2130    or HEAD, the response payload is a partial representation of the target
    2131    resource.</t>
    2132    <t>If the response has a Content-Location header field, and that URI is the same
    2133    as the effective request URI, the response payload is a representation of the
    2134    target resource.</t>
    2135    <t>If the response has a Content-Location header field, and that URI is not the
    2136    same as the effective request URI, then the response asserts that its
    2137    payload is a representation of the resource identified by the
    2138    Content-Location URI. However, such an assertion cannot be trusted unless
    2139    it can be verified by other means (not defined by HTTP).</t>
    2140    <t>Otherwise, the response is a representation of an anonymous (i.e.,
    2141    unidentified) resource.</t>
    2142 </list></t>
    2143 <t>
    2144   <cref anchor="TODO-req-uri">
    2145    The comparison function is going to have to be defined somewhere,
    2146    because we already need to compare URIs for things like cache invalidation.</cref>
    2147 </t>
    2148 </section>
    2149 
    2150 </section>
    2151 
    21522095
    21532096<section title="Common Protocol Parameters" anchor="common.protocol.parameters">
    … …  
    26322575</section>
    26332576
    2634 <section title="Representation" anchor="representation-TODO">
     2577<section title="Representation">
    26352578<iref item="representation"/>
    26362579<t>
    … …  
    26562599   describes the error and what next steps are suggested for resolving it.
    26572600</t>
     2601<t>
     2602   Request and Response messages &MAY; transfer a representation if not otherwise
     2603   restricted by the request method or response status code. A representation
     2604   consists of metadata (representation header fields) and data (representation
     2605   body).  When a complete or partial representation is enclosed in an HTTP message,
     2606   it is referred to as the payload of the message.<cref>MOVEDFIXME</cref>
     2607</t>
     2608<t>
     2609   A representation body is only present in a message when a message body is
     2610   present, as described in &message-body;. The representation body is obtained
     2611   from the message body by decoding any Transfer-Encoding that might
     2612   have been applied to ensure safe and proper transfer of the message.<cref>MOVEDFIXME</cref>
     2613</t>
     2614
     2615<section title="Identifying the Resource Associated with a Representation" anchor="identifying.response.associated.with.representation">
     2616<t>
     2617   It is sometimes necessary to determine an identifier for the resource
     2618   associated with a representation.
     2619</t>
     2620<t>
     2621   An HTTP request representation, when present, is always associated with an
     2622   anonymous (i.e., unidentified) resource.
     2623</t>
     2624<t>
     2625   In the common case, an HTTP response is a representation of the target
     2626   resource (see &effective-request-uri;). However, this is not always the
     2627   case. To determine the URI of the resource a response is associated with,
     2628   the following rules are used (with the first applicable one being selected):
     2629</t>
     2630<t><list style="numbers">
     2631   <t>If the response status code is 200 or 203 and the request method was GET,
     2632   the response payload is a representation of the target resource.</t>
     2633   <t>If the response status code is 204, 206, or 304 and the request method was GET
     2634   or HEAD, the response payload is a partial representation of the target
     2635   resource.</t>
     2636   <t>If the response has a Content-Location header field, and that URI is the same
     2637   as the effective request URI, the response payload is a representation of the
     2638   target resource.</t>
     2639   <t>If the response has a Content-Location header field, and that URI is not the
     2640   same as the effective request URI, then the response asserts that its
     2641   payload is a representation of the resource identified by the
     2642   Content-Location URI. However, such an assertion cannot be trusted unless
     2643   it can be verified by other means (not defined by HTTP).</t>
     2644   <t>Otherwise, the response is a representation of an anonymous (i.e.,
     2645   unidentified) resource.</t>
     2646</list></t>
     2647<t>
     2648  <cref anchor="TODO-req-uri">
     2649   The comparison function is going to have to be defined somewhere,
     2650   because we already need to compare URIs for things like cache invalidation.</cref>
     2651</t>
     2652</section>
    26582653
    26592654<section title="Representation Header Fields" anchor="representation.header.fields">

  • draft-ietf-httpbis/experiment/p4-conditional.html

    r1630 r1631  
    686686      <div id="rfc.figure.u.1"></div><pre class="inline">  <a href="#notation" class="smpl">OWS</a>           = &lt;OWS, defined in <a href="#Part1" id="rfc.xref.Part1.4"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.1</a>&gt;
    687687  <a href="#notation" class="smpl">obs-text</a>      = &lt;obs-text, defined in <a href="#Part1" id="rfc.xref.Part1.5"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a>&gt;
    688   <a href="#notation" class="smpl">HTTP-date</a>     = &lt;HTTP-date, defined in <a href="#Part2" id="rfc.xref.Part2.2"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#http.date" title="Date/Time Formats">Section 6.1</a>&gt;
     688  <a href="#notation" class="smpl">HTTP-date</a>     = &lt;HTTP-date, defined in <a href="#Part2" id="rfc.xref.Part2.2"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#http.date" title="Date/Time Formats">Section 5.1</a>&gt;
    689689</pre><div id="rfc.iref.m.1"></div>
    690690      <div id="rfc.iref.v.1"></div>
    … …  
    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">Section 9</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 10.13</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">Section 8</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 9.13</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>
    … …  
    11231123         as if it were the payload of a 200 response. The 304 response <em class="bcp14">MUST NOT</em> contain a message-body, and thus is always terminated by the first empty line after the header fields.
    11241124      </p>
    1125       <p id="rfc.section.4.1.p.2">A 304 response <em class="bcp14">MUST</em> include a Date header field (<a href="p2-semantics.html#header.date" title="Date">Section 10.2</a> of <a href="#Part2" id="rfc.xref.Part2.5"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) unless the origin server does not have a clock that can provide a reasonable approximation of the current time. If a 200
     1125      <p id="rfc.section.4.1.p.2">A 304 response <em class="bcp14">MUST</em> include a Date header field (<a href="p2-semantics.html#header.date" title="Date">Section 9.2</a> of <a href="#Part2" id="rfc.xref.Part2.5"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) unless the origin server does not have a clock that can provide a reasonable approximation of the current time. If a 200
    11261126         response to the same request would have included any of the header fields Cache-Control, Content-Location, ETag, Expires,
    11271127         or Vary, then those same header fields <em class="bcp14">MUST</em> be sent in a 304 response.
    … …  
    14241424                  </li>
    14251425                  <li><em>Part2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.1">1.2</a>, <a href="#rfc.xref.Part2.2">1.2</a>, <a href="#rfc.xref.Part2.3">2.3.3</a>, <a href="#rfc.xref.Part2.4">2.3.3</a>, <a href="#rfc.xref.Part2.5">4.1</a>, <a href="#Part2"><b>8.1</b></a><ul>
    1426                         <li><em>Section 6.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.2">1.2</a></li>
    1427                         <li><em>Section 9</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.3">2.3.3</a></li>
    1428                         <li><em>Section 10.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.5">4.1</a></li>
    1429                         <li><em>Section 10.13</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.4">2.3.3</a></li>
     1426                        <li><em>Section 5.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.2">1.2</a></li>
     1427                        <li><em>Section 8</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.3">2.3.3</a></li>
     1428                        <li><em>Section 9.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.5">4.1</a></li>
     1429                        <li><em>Section 9.13</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.4">2.3.3</a></li>
    14301430                     </ul>
    14311431                  </li>
Note: See TracChangeset for help on using the changeset viewer.