Changeset 1905


Ignore:
Timestamp:
Sep 18, 2012, 2:26:12 AM (7 years ago)
Author:
fielding@…
Message:

(editorial) define payload within representation

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

Legend:

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

    r1904 r1905  
    907907         or an intranet-to-Internet privacy filter. Such transformations are presumed to be desired by the client (or client organization)
    908908         that selected the proxy and are beyond the scope of this specification. However, when a proxy is not intended to transform
    909          a given message, we use the term "<dfn>non-transforming proxy</dfn>" to target requirements that preserve HTTP message semantics. See <a href="p2-semantics.html#status.203" title="203 Non-Authoritative Information">Section 7.3.4</a> of <a href="#Part2" id="rfc.xref.Part2.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a> and <a href="p6-cache.html#header.warning" title="Warning">Section 7.5</a> of <a href="#Part6" id="rfc.xref.Part6.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a> for status and warning codes related to transformations.
     909         a given message, we use the term "<dfn>non-transforming proxy</dfn>" to target requirements that preserve HTTP message semantics. See <a href="p2-semantics.html#status.203" title="203 Non-Authoritative Information">Section 6.3.4</a> of <a href="#Part2" id="rfc.xref.Part2.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a> and <a href="p6-cache.html#header.warning" title="Warning">Section 7.5</a> of <a href="#Part6" id="rfc.xref.Part6.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a> for status and warning codes related to transformations.
    910910      </p>
    911911      <p id="rfc.section.2.3.p.7"><span id="rfc.iref.g.13"></span><span id="rfc.iref.r.4"></span>  <span id="rfc.iref.a.1"></span> A "<dfn>gateway</dfn>" (a.k.a., "<dfn>reverse proxy</dfn>") is a receiving agent that acts as a layer above some other server(s) and translates the received requests to the underlying
     
    10771077      </p>
    10781078      <p id="rfc.section.2.7.1.p.6">When an "http" URI is used within a context that calls for access to the indicated resource, a client <em class="bcp14">MAY</em> attempt access by resolving the host to an IP address, establishing a TCP connection to that address on the indicated port,
    1079          and sending an HTTP request message (<a href="#http.message" title="Message Format">Section&nbsp;3</a>) containing the URI's identifying data (<a href="#message.routing" title="Message Routing">Section&nbsp;5</a>) to the server. If the server responds to that request with a non-interim HTTP response message, as described in <a href="p2-semantics.html#status.codes" title="Response Status Codes">Section 7</a> of <a href="#Part2" id="rfc.xref.Part2.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>, then that response is considered an authoritative answer to the client's request.
     1079         and sending an HTTP request message (<a href="#http.message" title="Message Format">Section&nbsp;3</a>) containing the URI's identifying data (<a href="#message.routing" title="Message Routing">Section&nbsp;5</a>) to the server. If the server responds to that request with a non-interim HTTP response message, as described in <a href="p2-semantics.html#status.codes" title="Response Status Codes">Section 6</a> of <a href="#Part2" id="rfc.xref.Part2.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>, then that response is considered an authoritative answer to the client's request.
    10801080      </p>
    10811081      <p id="rfc.section.2.7.1.p.7">Although HTTP is independent of the transport protocol, the "http" scheme is specific to TCP-based services because the name
     
    11751175      </div>
    11761176      <div id="rfc.figure.u.14"></div><pre class="inline"><span id="rfc.iref.g.29"></span>  <a href="#method" class="smpl">method</a>         = <a href="#rule.token.separators" class="smpl">token</a>
    1177 </pre><p id="rfc.section.3.1.1.p.6">The methods defined by this specification can be found in <a href="p2-semantics.html#methods" title="Request Methods">Section 5</a> of <a href="#Part2" id="rfc.xref.Part2.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>, along with information regarding the HTTP method registry and considerations for defining new methods.
     1177</pre><p id="rfc.section.3.1.1.p.6">The methods defined by this specification can be found in <a href="p2-semantics.html#methods" title="Request Methods">Section 4</a> of <a href="#Part2" id="rfc.xref.Part2.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>, along with information regarding the HTTP method registry and considerations for defining new methods.
    11781178      </p>
    11791179      <div id="rfc.iref.r.6"></div>
     
    11881188      </p>
    11891189      <p id="rfc.section.3.1.1.p.10">HTTP does not place a pre-defined limit on the length of a request-line. A server that receives a method longer than any that
    1190          it implements <em class="bcp14">SHOULD</em> respond with either a <a href="p2-semantics.html#status.405" class="smpl">405 (Method Not Allowed)</a>, if it is an origin server, or a <a href="p2-semantics.html#status.501" class="smpl">501 (Not Implemented)</a> status code. A server <em class="bcp14">MUST</em> be prepared to receive URIs of unbounded length and respond with the <a href="p2-semantics.html#status.414" class="smpl">414 (URI Too Long)</a> status code if the received request-target would be longer than the server wishes to handle (see <a href="p2-semantics.html#status.414" title="414 URI Too Long">Section 7.5.12</a> of <a href="#Part2" id="rfc.xref.Part2.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>).
     1190         it implements <em class="bcp14">SHOULD</em> respond with either a <a href="p2-semantics.html#status.405" class="smpl">405 (Method Not Allowed)</a>, if it is an origin server, or a <a href="p2-semantics.html#status.501" class="smpl">501 (Not Implemented)</a> status code. A server <em class="bcp14">MUST</em> be prepared to receive URIs of unbounded length and respond with the <a href="p2-semantics.html#status.414" class="smpl">414 (URI Too Long)</a> status code if the received request-target would be longer than the server wishes to handle (see <a href="p2-semantics.html#status.414" title="414 URI Too Long">Section 6.5.12</a> of <a href="#Part2" id="rfc.xref.Part2.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>).
    11911191      </p>
    11921192      <p id="rfc.section.3.1.1.p.11">Various ad-hoc limitations on request-line length are found in practice. It is <em class="bcp14">RECOMMENDED</em> that all HTTP senders and recipients support, at a minimum, request-line lengths of up to 8000 octets.
     
    12011201      <p id="rfc.section.3.1.2.p.4">The status-code element is a 3-digit integer code describing the result of the server's attempt to understand and satisfy
    12021202         the client's corresponding request. The rest of the response message is to be interpreted in light of the semantics defined
    1203          for that status code. See <a href="p2-semantics.html#status.codes" title="Response Status Codes">Section 7</a> of <a href="#Part2" id="rfc.xref.Part2.8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a> for information about the semantics of status codes, including the classes of status code (indicated by the first digit),
     1203         for that status code. See <a href="p2-semantics.html#status.codes" title="Response Status Codes">Section 6</a> of <a href="#Part2" id="rfc.xref.Part2.8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a> for information about the semantics of status codes, including the classes of status code (indicated by the first digit),
    12041204         the status codes defined by this specification, considerations for the definition of new status codes, and the IANA registry.
    12051205      </p>
     
    12221222                 ; see <a href="#field.parsing" title="Field Parsing">Section&nbsp;3.2.2</a>
    12231223</pre><p id="rfc.section.3.2.p.3">The field-name token labels the corresponding field-value as having the semantics defined by that header field. For example,
    1224          the <a href="p2-semantics.html#header.date" class="smpl">Date</a> header field is defined in <a href="p2-semantics.html#header.date" title="Date">Section 8.2.1</a> of <a href="#Part2" id="rfc.xref.Part2.9"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a> as containing the origination timestamp for the message in which it appears.
     1224         the <a href="p2-semantics.html#header.date" class="smpl">Date</a> header field is defined in <a href="p2-semantics.html#header.date" title="Date">Section 7.2.1</a> of <a href="#Part2" id="rfc.xref.Part2.9"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a> as containing the origination timestamp for the message in which it appears.
    12251225      </p>
    12261226      <p id="rfc.section.3.2.p.4">HTTP header fields are fully extensible: there is no limit on the introduction of new field names, each presumably defining
     
    12301230         them.
    12311231      </p>
    1232       <p id="rfc.section.3.2.p.5">New HTTP header fields <em class="bcp14">SHOULD</em> be registered with IANA in the Message Header Field Registry, as described in <a href="p2-semantics.html#header.field.registry" title="Header Field Registry">Section 10.3</a> of <a href="#Part2" id="rfc.xref.Part2.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>. Unrecognized header fields <em class="bcp14">MUST</em> be forwarded by a proxy unless the field-name is listed in the <a href="#header.connection" class="smpl">Connection</a> header field (<a href="#header.connection" id="rfc.xref.header.connection.3" title="Connection">Section&nbsp;6.1</a>) or the proxy is specifically configured to block or otherwise transform such fields. Unrecognized header fields <em class="bcp14">SHOULD</em> be ignored by other recipients.
     1232      <p id="rfc.section.3.2.p.5">New HTTP header fields <em class="bcp14">SHOULD</em> be registered with IANA in the Message Header Field Registry, as described in <a href="p2-semantics.html#header.field.registry" title="Header Field Registry">Section 9.3</a> of <a href="#Part2" id="rfc.xref.Part2.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>. Unrecognized header fields <em class="bcp14">MUST</em> be forwarded by a proxy unless the field-name is listed in the <a href="#header.connection" class="smpl">Connection</a> header field (<a href="#header.connection" id="rfc.xref.header.connection.3" title="Connection">Section&nbsp;6.1</a>) or the proxy is specifically configured to block or otherwise transform such fields. Unrecognized header fields <em class="bcp14">SHOULD</em> be ignored by other recipients.
    12331233      </p>
    12341234      <p id="rfc.section.3.2.p.6">The order in which header fields with differing field names are received is not significant. However, it is "good practice"
     
    13811381      <p id="rfc.section.3.3.1.p.6">If more than one Transfer-Encoding header field is present in a message, the multiple field-values <em class="bcp14">MUST</em> be combined into one field-value, according to the algorithm defined in <a href="#header.fields" title="Header Fields">Section&nbsp;3.2</a>, before determining the message body length.
    13821382      </p>
    1383       <p id="rfc.section.3.3.1.p.7">Unlike <a href="p2-semantics.html#header.content-encoding" class="smpl">Content-Encoding</a> (<a href="p2-semantics.html#content.codings" title="Content Codings">Section 9.4</a> of <a href="#Part2" id="rfc.xref.Part2.11"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>), Transfer-Encoding is a property of the message, not of the payload, and thus <em class="bcp14">MAY</em> be added or removed by any implementation along the request/response chain. Additional information about the encoding parameters <em class="bcp14">MAY</em> be provided by other header fields not defined by this specification.
     1383      <p id="rfc.section.3.3.1.p.7">Unlike <a href="p2-semantics.html#header.content-encoding" class="smpl">Content-Encoding</a> (<a href="p2-semantics.html#content.codings" title="Content Codings">Section 8.4</a> of <a href="#Part2" id="rfc.xref.Part2.11"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>), Transfer-Encoding is a property of the message, not of the payload, and thus <em class="bcp14">MAY</em> be added or removed by any implementation along the request/response chain. Additional information about the encoding parameters <em class="bcp14">MAY</em> be provided by other header fields not defined by this specification.
    13841384      </p>
    13851385      <p id="rfc.section.3.3.1.p.8">Transfer-Encoding <em class="bcp14">MAY</em> be sent in a response to a HEAD request or in a <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a> response (<a href="p4-conditional.html#status.304" title="304 Not Modified">Section 4.1</a> of <a href="#Part4" id="rfc.xref.Part4.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>) to a GET request, neither of which includes a message body, to indicate that the origin server would have applied a transfer
     
    16551655      </p>
    16561656      <p id="rfc.section.4.3.p.7">When multiple transfer-codings are acceptable, the client <em class="bcp14">MAY</em> rank the codings by preference using a case-insensitive "q" parameter (similar to the qvalues used in content negotiation
    1657          fields, <a href="p2-semantics.html#quality.values" title="Quality Values">Section 6.3.1</a> of <a href="#Part2" id="rfc.xref.Part2.12"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>). The rank value is a real number in the range 0 through 1, where 0.001 is the least preferred and 1 is the most preferred;
     1657         fields, <a href="p2-semantics.html#quality.values" title="Quality Values">Section 5.3.1</a> of <a href="#Part2" id="rfc.xref.Part2.12"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>). The rank value is a real number in the range 0 through 1, where 0.001 is the least preferred and 1 is the most preferred;
    16581658         a value of 0 means "not acceptable".
    16591659      </p>
     
    17351735      </p>
    17361736      <div id="authority-form">
    1737          <p id="rfc.section.5.3.p.13"><span id="rfc.iref.a.3"></span> The authority-form of request-target is only used for CONNECT requests (<a href="p2-semantics.html#CONNECT" title="CONNECT">Section 5.3.6</a> of <a href="#Part2" id="rfc.xref.Part2.14"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>). When making a CONNECT request to establish a tunnel through one or more proxies, a client <em class="bcp14">MUST</em> send only the target URI's authority component (excluding any userinfo) as the request-target. For example,
     1737         <p id="rfc.section.5.3.p.13"><span id="rfc.iref.a.3"></span> The authority-form of request-target is only used for CONNECT requests (<a href="p2-semantics.html#CONNECT" title="CONNECT">Section 4.3.6</a> of <a href="#Part2" id="rfc.xref.Part2.14"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>). When making a CONNECT request to establish a tunnel through one or more proxies, a client <em class="bcp14">MUST</em> send only the target URI's authority component (excluding any userinfo) as the request-target. For example,
    17381738         </p>
    17391739      </div>
    17401740      <div id="rfc.figure.u.41"></div><pre class="text2">CONNECT www.example.com:80 HTTP/1.1
    17411741</pre><div id="asterisk-form">
    1742          <p id="rfc.section.5.3.p.15"><span id="rfc.iref.a.4"></span> The asterisk-form of request-target is only used for a server-wide OPTIONS request (<a href="p2-semantics.html#OPTIONS" title="OPTIONS">Section 5.3.7</a> of <a href="#Part2" id="rfc.xref.Part2.15"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>). When a client wishes to request OPTIONS for the server as a whole, as opposed to a specific named resource of that server,
     1742         <p id="rfc.section.5.3.p.15"><span id="rfc.iref.a.4"></span> The asterisk-form of request-target is only used for a server-wide OPTIONS request (<a href="p2-semantics.html#OPTIONS" title="OPTIONS">Section 4.3.7</a> of <a href="#Part2" id="rfc.xref.Part2.15"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>). When a client wishes to request OPTIONS for the server as a whole, as opposed to a specific named resource of that server,
    17431743            the client <em class="bcp14">MUST</em> send only "*" (%x2A) as the request-target. For example,
    17441744         </p>
     
    18761876         except as noted above to replace an empty path with "/" or "*".
    18771877      </p>
    1878       <p id="rfc.section.5.8.p.3">A non-transforming proxy <em class="bcp14">MUST</em> preserve the message payload (<a href="#Part2" id="rfc.xref.Part2.16"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>), though it <em class="bcp14">MAY</em> change the message body through application or removal of a transfer-coding (<a href="#transfer.codings" title="Transfer Codings">Section&nbsp;4</a>).
     1878      <p id="rfc.section.5.8.p.3">A non-transforming proxy <em class="bcp14">MUST</em> preserve the message payload (<a href="p2-semantics.html#payload" title="Message Payload">Section 3.1</a> of <a href="#Part2" id="rfc.xref.Part2.16"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>), though it <em class="bcp14">MAY</em> change the message body through application or removal of a transfer-coding (<a href="#transfer.codings" title="Transfer Codings">Section&nbsp;4</a>).
    18791879      </p>
    18801880      <p id="rfc.section.5.8.p.4">A non-transforming proxy <em class="bcp14">SHOULD NOT</em> modify header fields that provide information about the end points of the communication chain, the resource state, or the
     
    18841884      </p>
    18851885      <ul>
    1886          <li><a href="p2-semantics.html#header.allow" class="smpl">Allow</a> (<a href="p2-semantics.html#header.allow" title="Allow">Section 8.4.1</a> of <a href="#Part2" id="rfc.xref.Part2.17"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>)
    1887          </li>
    1888          <li><a href="p2-semantics.html#header.content-location" class="smpl">Content-Location</a> (<a href="p2-semantics.html#header.content-location" title="Content-Location">Section 3.2.4</a> of <a href="#Part2" id="rfc.xref.Part2.18"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>)
     1886         <li><a href="p2-semantics.html#header.allow" class="smpl">Allow</a> (<a href="p2-semantics.html#header.allow" title="Allow">Section 7.4.1</a> of <a href="#Part2" id="rfc.xref.Part2.17"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>)
     1887         </li>
     1888         <li><a href="p2-semantics.html#header.content-location" class="smpl">Content-Location</a> (<a href="p2-semantics.html#header.content-location" title="Content-Location">Section 3.3.4</a> of <a href="#Part2" id="rfc.xref.Part2.18"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>)
    18891889         </li>
    18901890         <li>Content-MD5 (<a href="http://tools.ietf.org/html/rfc2616#section-14.15">Section 14.15</a> of <a href="#RFC2616" id="rfc.xref.RFC2616.3"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>)
     
    18941894         <li><a href="p4-conditional.html#header.last-modified" class="smpl">Last-Modified</a> (<a href="p4-conditional.html#header.last-modified" title="Last-Modified">Section 2.2</a> of <a href="#Part4" id="rfc.xref.Part4.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>)
    18951895         </li>
    1896          <li><a href="p2-semantics.html#header.server" class="smpl">Server</a> (<a href="p2-semantics.html#header.server" title="Server">Section 8.4.2</a> of <a href="#Part2" id="rfc.xref.Part2.19"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>)
     1896         <li><a href="p2-semantics.html#header.server" class="smpl">Server</a> (<a href="p2-semantics.html#header.server" title="Server">Section 7.4.2</a> of <a href="#Part2" id="rfc.xref.Part2.19"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>)
    18971897         </li>
    18981898      </ul>
     
    19021902      </p>
    19031903      <ul>
    1904          <li><a href="p2-semantics.html#header.content-encoding" class="smpl">Content-Encoding</a> (<a href="p2-semantics.html#header.content-encoding" title="Content-Encoding">Section 3.2.2</a> of <a href="#Part2" id="rfc.xref.Part2.20"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>)
     1904         <li><a href="p2-semantics.html#header.content-encoding" class="smpl">Content-Encoding</a> (<a href="p2-semantics.html#header.content-encoding" title="Content-Encoding">Section 3.3.2</a> of <a href="#Part2" id="rfc.xref.Part2.20"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>)
    19051905         </li>
    19061906         <li><a href="p5-range.html#header.content-range" class="smpl">Content-Range</a> (<a href="p5-range.html#header.content-range" title="Content-Range">Section 5.2</a> of <a href="#Part5" id="rfc.xref.Part5.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a>)
    19071907         </li>
    1908          <li><a href="p2-semantics.html#header.content-type" class="smpl">Content-Type</a> (<a href="p2-semantics.html#header.content-type" title="Content-Type">Section 3.2.1</a> of <a href="#Part2" id="rfc.xref.Part2.21"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>)
     1908         <li><a href="p2-semantics.html#header.content-type" class="smpl">Content-Type</a> (<a href="p2-semantics.html#header.content-type" title="Content-Type">Section 3.3.1</a> of <a href="#Part2" id="rfc.xref.Part2.21"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>)
    19091909         </li>
    19101910      </ul>
     
    19191919      <p id="rfc.section.5.9.p.1">HTTP does not include a request identifier for associating a given request message with its corresponding one or more response
    19201920         messages. Hence, it relies on the order of response arrival to correspond exactly to the order in which requests are made
    1921          on the same connection. More than one response message per request only occurs when one or more informational responses (<a href="p2-semantics.html#status.1xx" class="smpl">1xx</a>, see <a href="p2-semantics.html#status.1xx" title="Informational 1xx">Section 7.2</a> of <a href="#Part2" id="rfc.xref.Part2.22"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>) precede a final response to the same request.
     1921         on the same connection. More than one response message per request only occurs when one or more informational responses (<a href="p2-semantics.html#status.1xx" class="smpl">1xx</a>, see <a href="p2-semantics.html#status.1xx" title="Informational 1xx">Section 6.2</a> of <a href="#Part2" id="rfc.xref.Part2.22"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>) precede a final response to the same request.
    19221922      </p>
    19231923      <p id="rfc.section.5.9.p.2">A client that uses persistent connections and sends more than one request per connection <em class="bcp14">MUST</em> maintain a list of outstanding requests in the order sent on that connection and <em class="bcp14">MUST</em> associate each received response message to the highest ordered request that has not yet received a final (non-<a href="p2-semantics.html#status.1xx" class="smpl">1xx</a>) response.
     
    20402040      <p id="rfc.section.6.2.2.1.p.2">Clients which assume persistent connections and pipeline immediately after connection establishment <em class="bcp14">SHOULD</em> be prepared to retry their connection if the first pipelined attempt fails. If a client does such a retry, it <em class="bcp14">MUST NOT</em> pipeline before it knows the connection is persistent. Clients <em class="bcp14">MUST</em> also be prepared to resend their requests if the server closes the connection before sending all of the corresponding responses.
    20412041      </p>
    2042       <p id="rfc.section.6.2.2.1.p.3">Clients <em class="bcp14">SHOULD NOT</em> pipeline requests using non-idempotent request methods or non-idempotent sequences of request methods (see <a href="p2-semantics.html#idempotent.methods" title="Idempotent Methods">Section 5.2.2</a> of <a href="#Part2" id="rfc.xref.Part2.23"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>). Otherwise, a premature termination of the transport connection could lead to indeterminate results. A client wishing to
     2042      <p id="rfc.section.6.2.2.1.p.3">Clients <em class="bcp14">SHOULD NOT</em> pipeline requests using non-idempotent request methods or non-idempotent sequences of request methods (see <a href="p2-semantics.html#idempotent.methods" title="Idempotent Methods">Section 4.2.2</a> of <a href="#Part2" id="rfc.xref.Part2.23"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>). Otherwise, a premature termination of the transport connection could lead to indeterminate results. A client wishing to
    20432043         send a non-idempotent request <em class="bcp14">SHOULD</em> wait to send that request until it has received the response status line for the previous request.
    20442044      </p>
    20452045      <h4 id="rfc.section.6.2.2.2"><a href="#rfc.section.6.2.2.2">6.2.2.2</a>&nbsp;<a id="persistent.retrying.requests" href="#persistent.retrying.requests">Retrying Requests</a></h4>
    20462046      <p id="rfc.section.6.2.2.2.p.1">Senders can close the transport connection at any time. Therefore, clients, servers, and proxies <em class="bcp14">MUST</em> be able to recover from asynchronous close events. Client software <em class="bcp14">MAY</em> reopen the transport connection and retransmit the aborted sequence of requests without user interaction so long as the request
    2047          sequence is idempotent (see <a href="p2-semantics.html#idempotent.methods" title="Idempotent Methods">Section 5.2.2</a> of <a href="#Part2" id="rfc.xref.Part2.24"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>). Non-idempotent request methods or sequences <em class="bcp14">MUST NOT</em> be automatically retried, although user agents <em class="bcp14">MAY</em> offer a human operator the choice of retrying the request(s). Confirmation by user-agent software with semantic understanding
     2047         sequence is idempotent (see <a href="p2-semantics.html#idempotent.methods" title="Idempotent Methods">Section 4.2.2</a> of <a href="#Part2" id="rfc.xref.Part2.24"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>). Non-idempotent request methods or sequences <em class="bcp14">MUST NOT</em> be automatically retried, although user agents <em class="bcp14">MAY</em> offer a human operator the choice of retrying the request(s). Confirmation by user-agent software with semantic understanding
    20482048         of the application <em class="bcp14">MAY</em> substitute for user confirmation. The automatic retry <em class="bcp14">SHOULD NOT</em> be repeated if the second sequence of requests fails.
    20492049      </p>
     
    21382138      </p>
    21392139      <p id="rfc.section.6.3.p.9">The Upgrade header field only applies to switching application-level protocols on the existing connection; it cannot be used
    2140          to switch to a protocol on a different connection. For that purpose, it is more appropriate to use a <a href="p2-semantics.html#status.3xx" class="smpl">3xx (Redirection)</a> response (<a href="p2-semantics.html#status.3xx" title="Redirection 3xx">Section 7.4</a> of <a href="#Part2" id="rfc.xref.Part2.25"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>).
     2140         to switch to a protocol on a different connection. For that purpose, it is more appropriate to use a <a href="p2-semantics.html#status.3xx" class="smpl">3xx (Redirection)</a> response (<a href="p2-semantics.html#status.3xx" title="Redirection 3xx">Section 6.4</a> of <a href="#Part2" id="rfc.xref.Part2.25"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>).
    21412141      </p>
    21422142      <p id="rfc.section.6.3.p.10">This specification only defines the protocol name "HTTP" for use by the family of Hypertext Transfer Protocols, as defined
     
    23992399         <li>Pointer to specification text</li>
    24002400      </ul>
    2401       <p id="rfc.section.7.4.p.3">Names of transfer codings <em class="bcp14">MUST NOT</em> overlap with names of content codings (<a href="p2-semantics.html#content.codings" title="Content Codings">Section 9.4</a> of <a href="#Part2" id="rfc.xref.Part2.26"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>) unless the encoding transformation is identical, as is the case for the compression codings defined in <a href="#compression.codings" title="Compression Codings">Section&nbsp;4.2</a>.
     2401      <p id="rfc.section.7.4.p.3">Names of transfer codings <em class="bcp14">MUST NOT</em> overlap with names of content codings (<a href="p2-semantics.html#content.codings" title="Content Codings">Section 8.4</a> of <a href="#Part2" id="rfc.xref.Part2.26"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>) unless the encoding transformation is identical, as is the case for the compression codings defined in <a href="#compression.codings" title="Compression Codings">Section&nbsp;4.2</a>.
    24022402      </p>
    24032403      <p id="rfc.section.7.4.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.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>), and <em class="bcp14">MUST</em> conform to the purpose of transfer coding defined in this section. Use of program names for the identification of encoding
     
    25542554         that most implementations will choose substantially higher limits.
    25552555      </p>
    2556       <p id="rfc.section.8.6.p.3">This specification also provides a way for servers to reject messages that have request-targets that are too long (<a href="p2-semantics.html#status.414" title="414 URI Too Long">Section 7.5.12</a> of <a href="#Part2" id="rfc.xref.Part2.27"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>) or request entities that are too large (<a href="p2-semantics.html#status.4xx" title="Client Error 4xx">Section 7.5</a> of <a href="#Part2" id="rfc.xref.Part2.28"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>).
     2556      <p id="rfc.section.8.6.p.3">This specification also provides a way for servers to reject messages that have request-targets that are too long (<a href="p2-semantics.html#status.414" title="414 URI Too Long">Section 6.5.12</a> of <a href="#Part2" id="rfc.xref.Part2.27"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>) or request entities that are too large (<a href="p2-semantics.html#status.4xx" title="Client Error 4xx">Section 6.5</a> of <a href="#Part2" id="rfc.xref.Part2.28"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>).
    25572557      </p>
    25582558      <p id="rfc.section.8.6.p.4">Recipients <em class="bcp14">SHOULD</em> carefully limit the extent to which they read other fields, including (but not limited to) request methods, response status
     
    36323632                  <li><em>Part2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.1">1</a>, <a href="#rfc.xref.Part2.2">2.1</a>, <a href="#rfc.xref.Part2.3">2.3</a>, <a href="#rfc.xref.Part2.4">2.7</a>, <a href="#rfc.xref.Part2.5">2.7.1</a>, <a href="#rfc.xref.Part2.6">3.1.1</a>, <a href="#rfc.xref.Part2.7">3.1.1</a>, <a href="#rfc.xref.Part2.8">3.1.2</a>, <a href="#rfc.xref.Part2.9">3.2</a>, <a href="#rfc.xref.Part2.10">3.2</a>, <a href="#rfc.xref.Part2.11">3.3.1</a>, <a href="#rfc.xref.Part2.12">4.3</a>, <a href="#rfc.xref.Part2.13">5.1</a>, <a href="#rfc.xref.Part2.14">5.3</a>, <a href="#rfc.xref.Part2.15">5.3</a>, <a href="#rfc.xref.Part2.16">5.8</a>, <a href="#rfc.xref.Part2.17">5.8</a>, <a href="#rfc.xref.Part2.18">5.8</a>, <a href="#rfc.xref.Part2.19">5.8</a>, <a href="#rfc.xref.Part2.20">5.8</a>, <a href="#rfc.xref.Part2.21">5.8</a>, <a href="#rfc.xref.Part2.22">5.9</a>, <a href="#rfc.xref.Part2.23">6.2.2.1</a>, <a href="#rfc.xref.Part2.24">6.2.2.2</a>, <a href="#rfc.xref.Part2.25">6.3</a>, <a href="#rfc.xref.Part2.26">7.4</a>, <a href="#rfc.xref.Part2.27">8.6</a>, <a href="#rfc.xref.Part2.28">8.6</a>, <a href="#Part2"><b>10.1</b></a><ul>
    36333633                        <li><em>Section 2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.4">2.7</a></li>
    3634                         <li><em>Section 3.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.21">5.8</a></li>
    3635                         <li><em>Section 3.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.20">5.8</a></li>
    3636                         <li><em>Section 3.2.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.18">5.8</a></li>
    3637                         <li><em>Section 5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.6">3.1.1</a></li>
    3638                         <li><em>Section 5.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.23">6.2.2.1</a>, <a href="#rfc.xref.Part2.24">6.2.2.2</a></li>
    3639                         <li><em>Section 5.3.6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.14">5.3</a></li>
    3640                         <li><em>Section 5.3.7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.15">5.3</a></li>
    3641                         <li><em>Section 6.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.12">4.3</a></li>
    3642                         <li><em>Section 7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.5">2.7.1</a>, <a href="#rfc.xref.Part2.8">3.1.2</a></li>
    3643                         <li><em>Section 7.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.22">5.9</a></li>
    3644                         <li><em>Section 7.3.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.3">2.3</a></li>
    3645                         <li><em>Section 7.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.25">6.3</a></li>
    3646                         <li><em>Section 7.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.28">8.6</a></li>
    3647                         <li><em>Section 7.5.12</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.7">3.1.1</a>, <a href="#rfc.xref.Part2.27">8.6</a></li>
    3648                         <li><em>Section 8.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.9">3.2</a></li>
    3649                         <li><em>Section 8.4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.17">5.8</a></li>
    3650                         <li><em>Section 8.4.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.19">5.8</a></li>
    3651                         <li><em>Section 9.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.11">3.3.1</a>, <a href="#rfc.xref.Part2.26">7.4</a></li>
    3652                         <li><em>Section 10.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.10">3.2</a></li>
     3634                        <li><em>Section 3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.16">5.8</a></li>
     3635                        <li><em>Section 3.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.21">5.8</a></li>
     3636                        <li><em>Section 3.3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.20">5.8</a></li>
     3637                        <li><em>Section 3.3.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.18">5.8</a></li>
     3638                        <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.6">3.1.1</a></li>
     3639                        <li><em>Section 4.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.23">6.2.2.1</a>, <a href="#rfc.xref.Part2.24">6.2.2.2</a></li>
     3640                        <li><em>Section 4.3.6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.14">5.3</a></li>
     3641                        <li><em>Section 4.3.7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.15">5.3</a></li>
     3642                        <li><em>Section 5.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.12">4.3</a></li>
     3643                        <li><em>Section 6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.5">2.7.1</a>, <a href="#rfc.xref.Part2.8">3.1.2</a></li>
     3644                        <li><em>Section 6.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.22">5.9</a></li>
     3645                        <li><em>Section 6.3.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.3">2.3</a></li>
     3646                        <li><em>Section 6.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.25">6.3</a></li>
     3647                        <li><em>Section 6.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.28">8.6</a></li>
     3648                        <li><em>Section 6.5.12</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.7">3.1.1</a>, <a href="#rfc.xref.Part2.27">8.6</a></li>
     3649                        <li><em>Section 7.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.9">3.2</a></li>
     3650                        <li><em>Section 7.4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.17">5.8</a></li>
     3651                        <li><em>Section 7.4.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.19">5.8</a></li>
     3652                        <li><em>Section 8.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.11">3.3.1</a>, <a href="#rfc.xref.Part2.26">7.4</a></li>
     3653                        <li><em>Section 9.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.10">3.2</a></li>
    36533654                        <li><em>Appendix A</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.2">2.1</a></li>
    36543655                     </ul>
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r1904 r1905  
    1919  <!ENTITY caching-overview       "<xref target='Part6' x:rel='#caching.overview' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    2020  <!ENTITY cache-incomplete       "<xref target='Part6' x:rel='#response.cacheability' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    21   <!ENTITY payload                "<xref target='Part2' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     21  <!ENTITY payload                "<xref target='Part2' x:rel='#payload' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    2222  <!ENTITY media-types            "<xref target='Part2' x:rel='#media.types' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    2323  <!ENTITY content-codings        "<xref target='Part2' x:rel='#content.codings' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
  • draft-ietf-httpbis/latest/p2-semantics.html

    r1901 r1905  
    449449  }
    450450  @bottom-center {
    451        content: "Expires March 21, 2013";
     451       content: "Expires March 22, 2013";
    452452  }
    453453  @bottom-right {
     
    474474      <link rel="Chapter" title="2 Resource" href="#rfc.section.2">
    475475      <link rel="Chapter" title="3 Representation" href="#rfc.section.3">
    476       <link rel="Chapter" title="4 Payload" href="#rfc.section.4">
    477       <link rel="Chapter" title="5 Request Methods" href="#rfc.section.5">
    478       <link rel="Chapter" title="6 Request Header Fields" href="#rfc.section.6">
    479       <link rel="Chapter" title="7 Response Status Codes" href="#rfc.section.7">
    480       <link rel="Chapter" title="8 Response Header Fields" href="#rfc.section.8">
    481       <link rel="Chapter" title="9 Protocol Parameters" href="#rfc.section.9">
    482       <link rel="Chapter" title="10 IANA Considerations" href="#rfc.section.10">
    483       <link rel="Chapter" title="11 Security Considerations" href="#rfc.section.11">
    484       <link rel="Chapter" title="12 Acknowledgments" href="#rfc.section.12">
    485       <link rel="Chapter" href="#rfc.section.13" title="13 References">
     476      <link rel="Chapter" title="4 Request Methods" href="#rfc.section.4">
     477      <link rel="Chapter" title="5 Request Header Fields" href="#rfc.section.5">
     478      <link rel="Chapter" title="6 Response Status Codes" href="#rfc.section.6">
     479      <link rel="Chapter" title="7 Response Header Fields" href="#rfc.section.7">
     480      <link rel="Chapter" title="8 Protocol Parameters" href="#rfc.section.8">
     481      <link rel="Chapter" title="9 IANA Considerations" href="#rfc.section.9">
     482      <link rel="Chapter" title="10 Security Considerations" href="#rfc.section.10">
     483      <link rel="Chapter" title="11 Acknowledgments" href="#rfc.section.11">
     484      <link rel="Chapter" href="#rfc.section.12" title="12 References">
    486485      <link rel="Appendix" title="A Differences between HTTP and MIME" href="#rfc.section.A">
    487486      <link rel="Appendix" title="B Additional Features" href="#rfc.section.B">
     
    498497      <meta name="dct.creator" content="Reschke, J. F.">
    499498      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
    500       <meta name="dct.issued" scheme="ISO8601" content="2012-09-17">
     499      <meta name="dct.issued" scheme="ISO8601" content="2012-09-18">
    501500      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    502501      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines the semantics of HTTP/1.1 messages, as expressed by request methods, request header fields, response status codes, and response header fields, along with the payload of messages (metadata and body content) and mechanisms for content negotiation.">
     
    529528            </tr>
    530529            <tr>
    531                <td class="left">Expires: March 21, 2013</td>
     530               <td class="left">Expires: March 22, 2013</td>
    532531               <td class="right">greenbytes</td>
    533532            </tr>
    534533            <tr>
    535534               <td class="left"></td>
    536                <td class="right">September 17, 2012</td>
     535               <td class="right">September 18, 2012</td>
    537536            </tr>
    538537         </tbody>
     
    561560         in progress”.
    562561      </p>
    563       <p>This Internet-Draft will expire on March 21, 2013.</p>
     562      <p>This Internet-Draft will expire on March 22, 2013.</p>
    564563      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    565564      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    586585         <li><a href="#rfc.section.2">2.</a>&nbsp;&nbsp;&nbsp;<a href="#resource">Resource</a></li>
    587586         <li><a href="#rfc.section.3">3.</a>&nbsp;&nbsp;&nbsp;<a href="#representation">Representation</a><ul>
    588                <li><a href="#rfc.section.3.1">3.1</a>&nbsp;&nbsp;&nbsp;<a href="#associating.representation.with.resource">Associating a Representation with its Resource</a></li>
    589                <li><a href="#rfc.section.3.2">3.2</a>&nbsp;&nbsp;&nbsp;<a href="#representation.header.fields">Representation Header Fields</a><ul>
    590                      <li><a href="#rfc.section.3.2.1">3.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#header.content-type">Content-Type</a></li>
    591                      <li><a href="#rfc.section.3.2.2">3.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.content-encoding">Content-Encoding</a></li>
    592                      <li><a href="#rfc.section.3.2.3">3.2.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.content-language">Content-Language</a></li>
    593                      <li><a href="#rfc.section.3.2.4">3.2.4</a>&nbsp;&nbsp;&nbsp;<a href="#header.content-location">Content-Location</a></li>
     587               <li><a href="#rfc.section.3.1">3.1</a>&nbsp;&nbsp;&nbsp;<a href="#payload">Message Payload</a></li>
     588               <li><a href="#rfc.section.3.2">3.2</a>&nbsp;&nbsp;&nbsp;<a href="#associating.representation.with.resource">Associating a Representation with its Resource</a></li>
     589               <li><a href="#rfc.section.3.3">3.3</a>&nbsp;&nbsp;&nbsp;<a href="#representation.header.fields">Representation Header Fields</a><ul>
     590                     <li><a href="#rfc.section.3.3.1">3.3.1</a>&nbsp;&nbsp;&nbsp;<a href="#header.content-type">Content-Type</a></li>
     591                     <li><a href="#rfc.section.3.3.2">3.3.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.content-encoding">Content-Encoding</a></li>
     592                     <li><a href="#rfc.section.3.3.3">3.3.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.content-language">Content-Language</a></li>
     593                     <li><a href="#rfc.section.3.3.4">3.3.4</a>&nbsp;&nbsp;&nbsp;<a href="#header.content-location">Content-Location</a></li>
    594594                  </ul>
    595595               </li>
    596                <li><a href="#rfc.section.3.3">3.3</a>&nbsp;&nbsp;&nbsp;<a href="#selected.representation">Selected Representation Header Fields</a></li>
    597                <li><a href="#rfc.section.3.4">3.4</a>&nbsp;&nbsp;&nbsp;<a href="#representation.data">Representation Data</a></li>
    598                <li><a href="#rfc.section.3.5">3.5</a>&nbsp;&nbsp;&nbsp;<a href="#content.negotiation">Content Negotiation</a><ul>
    599                      <li><a href="#rfc.section.3.5.1">3.5.1</a>&nbsp;&nbsp;&nbsp;<a href="#proactive.negotiation">Proactive Negotiation</a></li>
    600                      <li><a href="#rfc.section.3.5.2">3.5.2</a>&nbsp;&nbsp;&nbsp;<a href="#reactive.negotiation">Reactive Negotiation</a></li>
     596               <li><a href="#rfc.section.3.4">3.4</a>&nbsp;&nbsp;&nbsp;<a href="#selected.representation">Selected Representation Header Fields</a></li>
     597               <li><a href="#rfc.section.3.5">3.5</a>&nbsp;&nbsp;&nbsp;<a href="#representation.data">Representation Data</a></li>
     598               <li><a href="#rfc.section.3.6">3.6</a>&nbsp;&nbsp;&nbsp;<a href="#content.negotiation">Content Negotiation</a><ul>
     599                     <li><a href="#rfc.section.3.6.1">3.6.1</a>&nbsp;&nbsp;&nbsp;<a href="#proactive.negotiation">Proactive Negotiation</a></li>
     600                     <li><a href="#rfc.section.3.6.2">3.6.2</a>&nbsp;&nbsp;&nbsp;<a href="#reactive.negotiation">Reactive Negotiation</a></li>
    601601                  </ul>
    602602               </li>
    603603            </ul>
    604604         </li>
    605          <li><a href="#rfc.section.4">4.</a>&nbsp;&nbsp;&nbsp;<a href="#payload">Payload</a><ul>
    606                <li><a href="#rfc.section.4.1">4.1</a>&nbsp;&nbsp;&nbsp;<a href="#payload.header.fields">Payload Header Fields</a></li>
    607                <li><a href="#rfc.section.4.2">4.2</a>&nbsp;&nbsp;&nbsp;<a href="#payload.body">Payload Body</a></li>
    608             </ul>
    609          </li>
    610          <li><a href="#rfc.section.5">5.</a>&nbsp;&nbsp;&nbsp;<a href="#methods">Request Methods</a><ul>
    611                <li><a href="#rfc.section.5.1">5.1</a>&nbsp;&nbsp;&nbsp;<a href="#method.overview">Overview</a></li>
    612                <li><a href="#rfc.section.5.2">5.2</a>&nbsp;&nbsp;&nbsp;<a href="#method.properties">Common Method Properties</a><ul>
    613                      <li><a href="#rfc.section.5.2.1">5.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#safe.methods">Safe Methods</a></li>
    614                      <li><a href="#rfc.section.5.2.2">5.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#idempotent.methods">Idempotent Methods</a></li>
    615                      <li><a href="#rfc.section.5.2.3">5.2.3</a>&nbsp;&nbsp;&nbsp;<a href="#cacheable.methods">Cacheable Methods</a></li>
     605         <li><a href="#rfc.section.4">4.</a>&nbsp;&nbsp;&nbsp;<a href="#methods">Request Methods</a><ul>
     606               <li><a href="#rfc.section.4.1">4.1</a>&nbsp;&nbsp;&nbsp;<a href="#method.overview">Overview</a></li>
     607               <li><a href="#rfc.section.4.2">4.2</a>&nbsp;&nbsp;&nbsp;<a href="#method.properties">Common Method Properties</a><ul>
     608                     <li><a href="#rfc.section.4.2.1">4.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#safe.methods">Safe Methods</a></li>
     609                     <li><a href="#rfc.section.4.2.2">4.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#idempotent.methods">Idempotent Methods</a></li>
     610                     <li><a href="#rfc.section.4.2.3">4.2.3</a>&nbsp;&nbsp;&nbsp;<a href="#cacheable.methods">Cacheable Methods</a></li>
    616611                  </ul>
    617612               </li>
    618                <li><a href="#rfc.section.5.3">5.3</a>&nbsp;&nbsp;&nbsp;<a href="#method.definitions">Method Definitions</a><ul>
    619                      <li><a href="#rfc.section.5.3.1">5.3.1</a>&nbsp;&nbsp;&nbsp;<a href="#GET">GET</a></li>
    620                      <li><a href="#rfc.section.5.3.2">5.3.2</a>&nbsp;&nbsp;&nbsp;<a href="#HEAD">HEAD</a></li>
    621                      <li><a href="#rfc.section.5.3.3">5.3.3</a>&nbsp;&nbsp;&nbsp;<a href="#POST">POST</a></li>
    622                      <li><a href="#rfc.section.5.3.4">5.3.4</a>&nbsp;&nbsp;&nbsp;<a href="#PUT">PUT</a></li>
    623                      <li><a href="#rfc.section.5.3.5">5.3.5</a>&nbsp;&nbsp;&nbsp;<a href="#DELETE">DELETE</a></li>
    624                      <li><a href="#rfc.section.5.3.6">5.3.6</a>&nbsp;&nbsp;&nbsp;<a href="#CONNECT">CONNECT</a></li>
    625                      <li><a href="#rfc.section.5.3.7">5.3.7</a>&nbsp;&nbsp;&nbsp;<a href="#OPTIONS">OPTIONS</a></li>
    626                      <li><a href="#rfc.section.5.3.8">5.3.8</a>&nbsp;&nbsp;&nbsp;<a href="#TRACE">TRACE</a></li>
     613               <li><a href="#rfc.section.4.3">4.3</a>&nbsp;&nbsp;&nbsp;<a href="#method.definitions">Method Definitions</a><ul>
     614                     <li><a href="#rfc.section.4.3.1">4.3.1</a>&nbsp;&nbsp;&nbsp;<a href="#GET">GET</a></li>
     615                     <li><a href="#rfc.section.4.3.2">4.3.2</a>&nbsp;&nbsp;&nbsp;<a href="#HEAD">HEAD</a></li>
     616                     <li><a href="#rfc.section.4.3.3">4.3.3</a>&nbsp;&nbsp;&nbsp;<a href="#POST">POST</a></li>
     617                     <li><a href="#rfc.section.4.3.4">4.3.4</a>&nbsp;&nbsp;&nbsp;<a href="#PUT">PUT</a></li>
     618                     <li><a href="#rfc.section.4.3.5">4.3.5</a>&nbsp;&nbsp;&nbsp;<a href="#DELETE">DELETE</a></li>
     619                     <li><a href="#rfc.section.4.3.6">4.3.6</a>&nbsp;&nbsp;&nbsp;<a href="#CONNECT">CONNECT</a></li>
     620                     <li><a href="#rfc.section.4.3.7">4.3.7</a>&nbsp;&nbsp;&nbsp;<a href="#OPTIONS">OPTIONS</a></li>
     621                     <li><a href="#rfc.section.4.3.8">4.3.8</a>&nbsp;&nbsp;&nbsp;<a href="#TRACE">TRACE</a></li>
    627622                  </ul>
    628623               </li>
    629624            </ul>
    630625         </li>
    631          <li><a href="#rfc.section.6">6.</a>&nbsp;&nbsp;&nbsp;<a href="#request.header.fields">Request Header Fields</a><ul>
    632                <li><a href="#rfc.section.6.1">6.1</a>&nbsp;&nbsp;&nbsp;<a href="#request.controls">Controls</a><ul>
    633                      <li><a href="#rfc.section.6.1.1">6.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#header.max-forwards">Max-Forwards</a></li>
    634                      <li><a href="#rfc.section.6.1.2">6.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.expect">Expect</a><ul>
    635                            <li><a href="#rfc.section.6.1.2.1">6.1.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#use.of.the.100.status">Use of the 100 (Continue) Status</a></li>
     626         <li><a href="#rfc.section.5">5.</a>&nbsp;&nbsp;&nbsp;<a href="#request.header.fields">Request Header Fields</a><ul>
     627               <li><a href="#rfc.section.5.1">5.1</a>&nbsp;&nbsp;&nbsp;<a href="#request.controls">Controls</a><ul>
     628                     <li><a href="#rfc.section.5.1.1">5.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#header.max-forwards">Max-Forwards</a></li>
     629                     <li><a href="#rfc.section.5.1.2">5.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.expect">Expect</a><ul>
     630                           <li><a href="#rfc.section.5.1.2.1">5.1.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#use.of.the.100.status">Use of the 100 (Continue) Status</a></li>
    636631                        </ul>
    637632                     </li>
    638633                  </ul>
    639634               </li>
    640                <li><a href="#rfc.section.6.2">6.2</a>&nbsp;&nbsp;&nbsp;<a href="#request.conditionals">Conditionals</a></li>
    641                <li><a href="#rfc.section.6.3">6.3</a>&nbsp;&nbsp;&nbsp;<a href="#request.conneg">Content Negotiation</a><ul>
    642                      <li><a href="#rfc.section.6.3.1">6.3.1</a>&nbsp;&nbsp;&nbsp;<a href="#quality.values">Quality Values</a></li>
    643                      <li><a href="#rfc.section.6.3.2">6.3.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.accept">Accept</a></li>
    644                      <li><a href="#rfc.section.6.3.3">6.3.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.accept-charset">Accept-Charset</a></li>
    645                      <li><a href="#rfc.section.6.3.4">6.3.4</a>&nbsp;&nbsp;&nbsp;<a href="#header.accept-encoding">Accept-Encoding</a></li>
    646                      <li><a href="#rfc.section.6.3.5">6.3.5</a>&nbsp;&nbsp;&nbsp;<a href="#header.accept-language">Accept-Language</a></li>
     635               <li><a href="#rfc.section.5.2">5.2</a>&nbsp;&nbsp;&nbsp;<a href="#request.conditionals">Conditionals</a></li>
     636               <li><a href="#rfc.section.5.3">5.3</a>&nbsp;&nbsp;&nbsp;<a href="#request.conneg">Content Negotiation</a><ul>
     637                     <li><a href="#rfc.section.5.3.1">5.3.1</a>&nbsp;&nbsp;&nbsp;<a href="#quality.values">Quality Values</a></li>
     638                     <li><a href="#rfc.section.5.3.2">5.3.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.accept">Accept</a></li>
     639                     <li><a href="#rfc.section.5.3.3">5.3.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.accept-charset">Accept-Charset</a></li>
     640                     <li><a href="#rfc.section.5.3.4">5.3.4</a>&nbsp;&nbsp;&nbsp;<a href="#header.accept-encoding">Accept-Encoding</a></li>
     641                     <li><a href="#rfc.section.5.3.5">5.3.5</a>&nbsp;&nbsp;&nbsp;<a href="#header.accept-language">Accept-Language</a></li>
    647642                  </ul>
    648643               </li>
    649                <li><a href="#rfc.section.6.4">6.4</a>&nbsp;&nbsp;&nbsp;<a href="#request.auth">Authentication</a></li>
    650                <li><a href="#rfc.section.6.5">6.5</a>&nbsp;&nbsp;&nbsp;<a href="#request.context">Context</a><ul>
    651                      <li><a href="#rfc.section.6.5.1">6.5.1</a>&nbsp;&nbsp;&nbsp;<a href="#header.from">From</a></li>
    652                      <li><a href="#rfc.section.6.5.2">6.5.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.referer">Referer</a></li>
    653                      <li><a href="#rfc.section.6.5.3">6.5.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.user-agent">User-Agent</a></li>
     644               <li><a href="#rfc.section.5.4">5.4</a>&nbsp;&nbsp;&nbsp;<a href="#request.auth">Authentication</a></li>
     645               <li><a href="#rfc.section.5.5">5.5</a>&nbsp;&nbsp;&nbsp;<a href="#request.context">Context</a><ul>
     646                     <li><a href="#rfc.section.5.5.1">5.5.1</a>&nbsp;&nbsp;&nbsp;<a href="#header.from">From</a></li>
     647                     <li><a href="#rfc.section.5.5.2">5.5.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.referer">Referer</a></li>
     648                     <li><a href="#rfc.section.5.5.3">5.5.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.user-agent">User-Agent</a></li>
    654649                  </ul>
    655650               </li>
    656651            </ul>
    657652         </li>
    658          <li><a href="#rfc.section.7">7.</a>&nbsp;&nbsp;&nbsp;<a href="#status.codes">Response Status Codes</a><ul>
    659                <li><a href="#rfc.section.7.1">7.1</a>&nbsp;&nbsp;&nbsp;<a href="#overview.of.status.codes">Overview of Status Codes</a></li>
    660                <li><a href="#rfc.section.7.2">7.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.1xx">Informational 1xx</a><ul>
    661                      <li><a href="#rfc.section.7.2.1">7.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.100">100 Continue</a></li>
    662                      <li><a href="#rfc.section.7.2.2">7.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.101">101 Switching Protocols</a></li>
     653         <li><a href="#rfc.section.6">6.</a>&nbsp;&nbsp;&nbsp;<a href="#status.codes">Response Status Codes</a><ul>
     654               <li><a href="#rfc.section.6.1">6.1</a>&nbsp;&nbsp;&nbsp;<a href="#overview.of.status.codes">Overview of Status Codes</a></li>
     655               <li><a href="#rfc.section.6.2">6.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.1xx">Informational 1xx</a><ul>
     656                     <li><a href="#rfc.section.6.2.1">6.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.100">100 Continue</a></li>
     657                     <li><a href="#rfc.section.6.2.2">6.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.101">101 Switching Protocols</a></li>
    663658                  </ul>
    664659               </li>
    665                <li><a href="#rfc.section.7.3">7.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.2xx">Successful 2xx</a><ul>
    666                      <li><a href="#rfc.section.7.3.1">7.3.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.200">200 OK</a></li>
    667                      <li><a href="#rfc.section.7.3.2">7.3.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.201">201 Created</a></li>
    668                      <li><a href="#rfc.section.7.3.3">7.3.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.202">202 Accepted</a></li>
    669                      <li><a href="#rfc.section.7.3.4">7.3.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.203">203 Non-Authoritative Information</a></li>
    670                      <li><a href="#rfc.section.7.3.5">7.3.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.204">204 No Content</a></li>
    671                      <li><a href="#rfc.section.7.3.6">7.3.6</a>&nbsp;&nbsp;&nbsp;<a href="#status.205">205 Reset Content</a></li>
     660               <li><a href="#rfc.section.6.3">6.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.2xx">Successful 2xx</a><ul>
     661                     <li><a href="#rfc.section.6.3.1">6.3.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.200">200 OK</a></li>
     662                     <li><a href="#rfc.section.6.3.2">6.3.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.201">201 Created</a></li>
     663                     <li><a href="#rfc.section.6.3.3">6.3.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.202">202 Accepted</a></li>
     664                     <li><a href="#rfc.section.6.3.4">6.3.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.203">203 Non-Authoritative Information</a></li>
     665                     <li><a href="#rfc.section.6.3.5">6.3.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.204">204 No Content</a></li>
     666                     <li><a href="#rfc.section.6.3.6">6.3.6</a>&nbsp;&nbsp;&nbsp;<a href="#status.205">205 Reset Content</a></li>
    672667                  </ul>
    673668               </li>
    674                <li><a href="#rfc.section.7.4">7.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.3xx">Redirection 3xx</a><ul>
    675                      <li><a href="#rfc.section.7.4.1">7.4.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.300">300 Multiple Choices</a></li>
    676                      <li><a href="#rfc.section.7.4.2">7.4.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.301">301 Moved Permanently</a></li>
    677                      <li><a href="#rfc.section.7.4.3">7.4.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.302">302 Found</a></li>
    678                      <li><a href="#rfc.section.7.4.4">7.4.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.303">303 See Other</a></li>
    679                      <li><a href="#rfc.section.7.4.5">7.4.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.305">305 Use Proxy</a></li>
    680                      <li><a href="#rfc.section.7.4.6">7.4.6</a>&nbsp;&nbsp;&nbsp;<a href="#status.306">306 (Unused)</a></li>
    681                      <li><a href="#rfc.section.7.4.7">7.4.7</a>&nbsp;&nbsp;&nbsp;<a href="#status.307">307 Temporary Redirect</a></li>
     669               <li><a href="#rfc.section.6.4">6.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.3xx">Redirection 3xx</a><ul>
     670                     <li><a href="#rfc.section.6.4.1">6.4.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.300">300 Multiple Choices</a></li>
     671                     <li><a href="#rfc.section.6.4.2">6.4.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.301">301 Moved Permanently</a></li>
     672                     <li><a href="#rfc.section.6.4.3">6.4.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.302">302 Found</a></li>
     673                     <li><a href="#rfc.section.6.4.4">6.4.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.303">303 See Other</a></li>
     674                     <li><a href="#rfc.section.6.4.5">6.4.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.305">305 Use Proxy</a></li>
     675                     <li><a href="#rfc.section.6.4.6">6.4.6</a>&nbsp;&nbsp;&nbsp;<a href="#status.306">306 (Unused)</a></li>
     676                     <li><a href="#rfc.section.6.4.7">6.4.7</a>&nbsp;&nbsp;&nbsp;<a href="#status.307">307 Temporary Redirect</a></li>
    682677                  </ul>
    683678               </li>
    684                <li><a href="#rfc.section.7.5">7.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.4xx">Client Error 4xx</a><ul>
    685                      <li><a href="#rfc.section.7.5.1">7.5.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.400">400 Bad Request</a></li>
    686                      <li><a href="#rfc.section.7.5.2">7.5.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.402">402 Payment Required</a></li>
    687                      <li><a href="#rfc.section.7.5.3">7.5.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.403">403 Forbidden</a></li>
    688                      <li><a href="#rfc.section.7.5.4">7.5.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.404">404 Not Found</a></li>
    689                      <li><a href="#rfc.section.7.5.5">7.5.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.405">405 Method Not Allowed</a></li>
    690                      <li><a href="#rfc.section.7.5.6">7.5.6</a>&nbsp;&nbsp;&nbsp;<a href="#status.406">406 Not Acceptable</a></li>
    691                      <li><a href="#rfc.section.7.5.7">7.5.7</a>&nbsp;&nbsp;&nbsp;<a href="#status.408">408 Request Timeout</a></li>
    692                      <li><a href="#rfc.section.7.5.8">7.5.8</a>&nbsp;&nbsp;&nbsp;<a href="#status.409">409 Conflict</a></li>
    693                      <li><a href="#rfc.section.7.5.9">7.5.9</a>&nbsp;&nbsp;&nbsp;<a href="#status.410">410 Gone</a></li>
    694                      <li><a href="#rfc.section.7.5.10">7.5.10</a>&nbsp;&nbsp;&nbsp;<a href="#status.411">411 Length Required</a></li>
    695                      <li><a href="#rfc.section.7.5.11">7.5.11</a>&nbsp;&nbsp;&nbsp;<a href="#status.413">413 Request Representation Too Large</a></li>
    696                      <li><a href="#rfc.section.7.5.12">7.5.12</a>&nbsp;&nbsp;&nbsp;<a href="#status.414">414 URI Too Long</a></li>
    697                      <li><a href="#rfc.section.7.5.13">7.5.13</a>&nbsp;&nbsp;&nbsp;<a href="#status.415">415 Unsupported Media Type</a></li>
    698                      <li><a href="#rfc.section.7.5.14">7.5.14</a>&nbsp;&nbsp;&nbsp;<a href="#status.417">417 Expectation Failed</a></li>
    699                      <li><a href="#rfc.section.7.5.15">7.5.15</a>&nbsp;&nbsp;&nbsp;<a href="#status.426">426 Upgrade Required</a></li>
     679               <li><a href="#rfc.section.6.5">6.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.4xx">Client Error 4xx</a><ul>
     680                     <li><a href="#rfc.section.6.5.1">6.5.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.400">400 Bad Request</a></li>
     681                     <li><a href="#rfc.section.6.5.2">6.5.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.402">402 Payment Required</a></li>
     682                     <li><a href="#rfc.section.6.5.3">6.5.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.403">403 Forbidden</a></li>
     683                     <li><a href="#rfc.section.6.5.4">6.5.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.404">404 Not Found</a></li>
     684                     <li><a href="#rfc.section.6.5.5">6.5.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.405">405 Method Not Allowed</a></li>
     685                     <li><a href="#rfc.section.6.5.6">6.5.6</a>&nbsp;&nbsp;&nbsp;<a href="#status.406">406 Not Acceptable</a></li>
     686                     <li><a href="#rfc.section.6.5.7">6.5.7</a>&nbsp;&nbsp;&nbsp;<a href="#status.408">408 Request Timeout</a></li>
     687                     <li><a href="#rfc.section.6.5.8">6.5.8</a>&nbsp;&nbsp;&nbsp;<a href="#status.409">409 Conflict</a></li>
     688                     <li><a href="#rfc.section.6.5.9">6.5.9</a>&nbsp;&nbsp;&nbsp;<a href="#status.410">410 Gone</a></li>
     689                     <li><a href="#rfc.section.6.5.10">6.5.10</a>&nbsp;&nbsp;&nbsp;<a href="#status.411">411 Length Required</a></li>
     690                     <li><a href="#rfc.section.6.5.11">6.5.11</a>&nbsp;&nbsp;&nbsp;<a href="#status.413">413 Request Representation Too Large</a></li>
     691                     <li><a href="#rfc.section.6.5.12">6.5.12</a>&nbsp;&nbsp;&nbsp;<a href="#status.414">414 URI Too Long</a></li>
     692                     <li><a href="#rfc.section.6.5.13">6.5.13</a>&nbsp;&nbsp;&nbsp;<a href="#status.415">415 Unsupported Media Type</a></li>
     693                     <li><a href="#rfc.section.6.5.14">6.5.14</a>&nbsp;&nbsp;&nbsp;<a href="#status.417">417 Expectation Failed</a></li>
     694                     <li><a href="#rfc.section.6.5.15">6.5.15</a>&nbsp;&nbsp;&nbsp;<a href="#status.426">426 Upgrade Required</a></li>
    700695                  </ul>
    701696               </li>
    702                <li><a href="#rfc.section.7.6">7.6</a>&nbsp;&nbsp;&nbsp;<a href="#status.5xx">Server Error 5xx</a><ul>
    703                      <li><a href="#rfc.section.7.6.1">7.6.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.500">500 Internal Server Error</a></li>
    704                      <li><a href="#rfc.section.7.6.2">7.6.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.501">501 Not Implemented</a></li>
    705                      <li><a href="#rfc.section.7.6.3">7.6.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.502">502 Bad Gateway</a></li>
    706                      <li><a href="#rfc.section.7.6.4">7.6.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.503">503 Service Unavailable</a></li>
    707                      <li><a href="#rfc.section.7.6.5">7.6.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.504">504 Gateway Timeout</a></li>
    708                      <li><a href="#rfc.section.7.6.6">7.6.6</a>&nbsp;&nbsp;&nbsp;<a href="#status.505">505 HTTP Version Not Supported</a></li>
     697               <li><a href="#rfc.section.6.6">6.6</a>&nbsp;&nbsp;&nbsp;<a href="#status.5xx">Server Error 5xx</a><ul>
     698                     <li><a href="#rfc.section.6.6.1">6.6.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.500">500 Internal Server Error</a></li>
     699                     <li><a href="#rfc.section.6.6.2">6.6.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.501">501 Not Implemented</a></li>
     700                     <li><a href="#rfc.section.6.6.3">6.6.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.502">502 Bad Gateway</a></li>
     701                     <li><a href="#rfc.section.6.6.4">6.6.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.503">503 Service Unavailable</a></li>
     702                     <li><a href="#rfc.section.6.6.5">6.6.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.504">504 Gateway Timeout</a></li>
     703                     <li><a href="#rfc.section.6.6.6">6.6.6</a>&nbsp;&nbsp;&nbsp;<a href="#status.505">505 HTTP Version Not Supported</a></li>
    709704                  </ul>
    710705               </li>
    711706            </ul>
    712707         </li>
    713          <li><a href="#rfc.section.8">8.</a>&nbsp;&nbsp;&nbsp;<a href="#response.header.fields">Response Header Fields</a><ul>
    714                <li><a href="#rfc.section.8.1">8.1</a>&nbsp;&nbsp;&nbsp;<a href="#response.control.data">Control Data</a><ul>
    715                      <li><a href="#rfc.section.8.1.1">8.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#header.location">Location</a></li>
    716                      <li><a href="#rfc.section.8.1.2">8.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.retry-after">Retry-After</a></li>
     708         <li><a href="#rfc.section.7">7.</a>&nbsp;&nbsp;&nbsp;<a href="#response.header.fields">Response Header Fields</a><ul>
     709               <li><a href="#rfc.section.7.1">7.1</a>&nbsp;&nbsp;&nbsp;<a href="#response.control.data">Control Data</a><ul>
     710                     <li><a href="#rfc.section.7.1.1">7.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#header.location">Location</a></li>
     711                     <li><a href="#rfc.section.7.1.2">7.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.retry-after">Retry-After</a></li>
    717712                  </ul>
    718713               </li>
    719                <li><a href="#rfc.section.8.2">8.2</a>&nbsp;&nbsp;&nbsp;<a href="#response.cache.related">Cache-related</a><ul>
    720                      <li><a href="#rfc.section.8.2.1">8.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#header.date">Date</a></li>
    721                      <li><a href="#rfc.section.8.2.2">8.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.vary">Vary</a></li>
     714               <li><a href="#rfc.section.7.2">7.2</a>&nbsp;&nbsp;&nbsp;<a href="#response.cache.related">Cache-related</a><ul>
     715                     <li><a href="#rfc.section.7.2.1">7.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#header.date">Date</a></li>
     716                     <li><a href="#rfc.section.7.2.2">7.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.vary">Vary</a></li>
    722717                  </ul>
    723718               </li>
    724                <li><a href="#rfc.section.8.3">8.3</a>&nbsp;&nbsp;&nbsp;<a href="#response.auth">Authentication Challenges</a></li>
    725                <li><a href="#rfc.section.8.4">8.4</a>&nbsp;&nbsp;&nbsp;<a href="#response.inform">Informative</a><ul>
    726                      <li><a href="#rfc.section.8.4.1">8.4.1</a>&nbsp;&nbsp;&nbsp;<a href="#header.allow">Allow</a></li>
    727                      <li><a href="#rfc.section.8.4.2">8.4.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.server">Server</a></li>
     719               <li><a href="#rfc.section.7.3">7.3</a>&nbsp;&nbsp;&nbsp;<a href="#response.auth">Authentication Challenges</a></li>
     720               <li><a href="#rfc.section.7.4">7.4</a>&nbsp;&nbsp;&nbsp;<a href="#response.inform">Informative</a><ul>
     721                     <li><a href="#rfc.section.7.4.1">7.4.1</a>&nbsp;&nbsp;&nbsp;<a href="#header.allow">Allow</a></li>
     722                     <li><a href="#rfc.section.7.4.2">7.4.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.server">Server</a></li>
    728723                  </ul>
    729724               </li>
    730725            </ul>
    731726         </li>
    732          <li><a href="#rfc.section.9">9.</a>&nbsp;&nbsp;&nbsp;<a href="#protocol.parameters">Protocol Parameters</a><ul>
    733                <li><a href="#rfc.section.9.1">9.1</a>&nbsp;&nbsp;&nbsp;<a href="#http.date">Date/Time Formats</a></li>
    734                <li><a href="#rfc.section.9.2">9.2</a>&nbsp;&nbsp;&nbsp;<a href="#product.tokens">Product Tokens</a></li>
    735                <li><a href="#rfc.section.9.3">9.3</a>&nbsp;&nbsp;&nbsp;<a href="#character.sets">Character Encodings (charset)</a></li>
    736                <li><a href="#rfc.section.9.4">9.4</a>&nbsp;&nbsp;&nbsp;<a href="#content.codings">Content Codings</a></li>
    737                <li><a href="#rfc.section.9.5">9.5</a>&nbsp;&nbsp;&nbsp;<a href="#media.types">Media Types</a><ul>
    738                      <li><a href="#rfc.section.9.5.1">9.5.1</a>&nbsp;&nbsp;&nbsp;<a href="#canonicalization.and.text.defaults">Canonicalization and Text Defaults</a></li>
    739                      <li><a href="#rfc.section.9.5.2">9.5.2</a>&nbsp;&nbsp;&nbsp;<a href="#multipart.types">Multipart Types</a></li>
     727         <li><a href="#rfc.section.8">8.</a>&nbsp;&nbsp;&nbsp;<a href="#protocol.parameters">Protocol Parameters</a><ul>
     728               <li><a href="#rfc.section.8.1">8.1</a>&nbsp;&nbsp;&nbsp;<a href="#http.date">Date/Time Formats</a></li>
     729               <li><a href="#rfc.section.8.2">8.2</a>&nbsp;&nbsp;&nbsp;<a href="#product.tokens">Product Tokens</a></li>
     730               <li><a href="#rfc.section.8.3">8.3</a>&nbsp;&nbsp;&nbsp;<a href="#character.sets">Character Encodings (charset)</a></li>
     731               <li><a href="#rfc.section.8.4">8.4</a>&nbsp;&nbsp;&nbsp;<a href="#content.codings">Content Codings</a></li>
     732               <li><a href="#rfc.section.8.5">8.5</a>&nbsp;&nbsp;&nbsp;<a href="#media.types">Media Types</a><ul>
     733                     <li><a href="#rfc.section.8.5.1">8.5.1</a>&nbsp;&nbsp;&nbsp;<a href="#canonicalization.and.text.defaults">Canonicalization and Text Defaults</a></li>
     734                     <li><a href="#rfc.section.8.5.2">8.5.2</a>&nbsp;&nbsp;&nbsp;<a href="#multipart.types">Multipart Types</a></li>
    740735                  </ul>
    741736               </li>
    742                <li><a href="#rfc.section.9.6">9.6</a>&nbsp;&nbsp;&nbsp;<a href="#language.tags">Language Tags</a></li>
     737               <li><a href="#rfc.section.8.6">8.6</a>&nbsp;&nbsp;&nbsp;<a href="#language.tags">Language Tags</a></li>
    743738            </ul>
    744739         </li>
    745          <li><a href="#rfc.section.10">10.</a>&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a><ul>
    746                <li><a href="#rfc.section.10.1">10.1</a>&nbsp;&nbsp;&nbsp;<a href="#method.registry">Method Registry</a><ul>
    747                      <li><a href="#rfc.section.10.1.1">10.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#method.procedure">Procedure</a></li>
    748                      <li><a href="#rfc.section.10.1.2">10.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#considerations.for.new.methods">Considerations for New Methods</a></li>
    749                      <li><a href="#rfc.section.10.1.3">10.1.3</a>&nbsp;&nbsp;&nbsp;<a href="#method.registration">Registrations</a></li>
     740         <li><a href="#rfc.section.9">9.</a>&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a><ul>
     741               <li><a href="#rfc.section.9.1">9.1</a>&nbsp;&nbsp;&nbsp;<a href="#method.registry">Method Registry</a><ul>
     742                     <li><a href="#rfc.section.9.1.1">9.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#method.procedure">Procedure</a></li>
     743                     <li><a href="#rfc.section.9.1.2">9.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#considerations.for.new.methods">Considerations for New Methods</a></li>
     744                     <li><a href="#rfc.section.9.1.3">9.1.3</a>&nbsp;&nbsp;&nbsp;<a href="#method.registration">Registrations</a></li>
    750745                  </ul>
    751746               </li>
    752                <li><a href="#rfc.section.10.2">10.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.code.registry">Status Code Registry</a><ul>
    753                      <li><a href="#rfc.section.10.2.1">10.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.code.procedure">Procedure</a></li>
    754                      <li><a href="#rfc.section.10.2.2">10.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#considerations.for.new.status.codes">Considerations for New Status Codes</a></li>
    755                      <li><a href="#rfc.section.10.2.3">10.2.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.code.registration">Registrations</a></li>
     747               <li><a href="#rfc.section.9.2">9.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.code.registry">Status Code Registry</a><ul>
     748                     <li><a href="#rfc.section.9.2.1">9.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.code.procedure">Procedure</a></li>
     749                     <li><a href="#rfc.section.9.2.2">9.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#considerations.for.new.status.codes">Considerations for New Status Codes</a></li>
     750                     <li><a href="#rfc.section.9.2.3">9.2.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.code.registration">Registrations</a></li>
    756751                  </ul>
    757752               </li>
    758                <li><a href="#rfc.section.10.3">10.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.field.registry">Header Field Registry</a><ul>
    759                      <li><a href="#rfc.section.10.3.1">10.3.1</a>&nbsp;&nbsp;&nbsp;<a href="#considerations.for.new.header.fields">Considerations for New Header Fields</a></li>
    760                      <li><a href="#rfc.section.10.3.2">10.3.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.field.registration">Registrations</a></li>
     753               <li><a href="#rfc.section.9.3">9.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.field.registry">Header Field Registry</a><ul>
     754                     <li><a href="#rfc.section.9.3.1">9.3.1</a>&nbsp;&nbsp;&nbsp;<a href="#considerations.for.new.header.fields">Considerations for New Header Fields</a></li>
     755                     <li><a href="#rfc.section.9.3.2">9.3.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.field.registration">Registrations</a></li>
    761756                  </ul>
    762757               </li>
    763                <li><a href="#rfc.section.10.4">10.4</a>&nbsp;&nbsp;&nbsp;<a href="#content.coding.registry">Content Coding Registry</a><ul>
    764                      <li><a href="#rfc.section.10.4.1">10.4.1</a>&nbsp;&nbsp;&nbsp;<a href="#content.coding.procedure">Procedure</a></li>
    765                      <li><a href="#rfc.section.10.4.2">10.4.2</a>&nbsp;&nbsp;&nbsp;<a href="#content.coding.registration">Registrations</a></li>
     758               <li><a href="#rfc.section.9.4">9.4</a>&nbsp;&nbsp;&nbsp;<a href="#content.coding.registry">Content Coding Registry</a><ul>
     759                     <li><a href="#rfc.section.9.4.1">9.4.1</a>&nbsp;&nbsp;&nbsp;<a href="#content.coding.procedure">Procedure</a></li>
     760                     <li><a href="#rfc.section.9.4.2">9.4.2</a>&nbsp;&nbsp;&nbsp;<a href="#content.coding.registration">Registrations</a></li>
    766761                  </ul>
    767762               </li>
    768763            </ul>
    769764         </li>
    770          <li><a href="#rfc.section.11">11.</a>&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a><ul>
    771                <li><a href="#rfc.section.11.1">11.1</a>&nbsp;&nbsp;&nbsp;<a href="#security.sensitive">Transfer of Sensitive Information</a></li>
    772                <li><a href="#rfc.section.11.2">11.2</a>&nbsp;&nbsp;&nbsp;<a href="#encoding.sensitive.information.in.uris">Encoding Sensitive Information in URIs</a></li>
    773                <li><a href="#rfc.section.11.3">11.3</a>&nbsp;&nbsp;&nbsp;<a href="#location.spoofing-leakage">Location Header Fields: Spoofing and Information Leakage</a></li>
    774                <li><a href="#rfc.section.11.4">11.4</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.11.4">Security Considerations for CONNECT</a></li>
    775                <li><a href="#rfc.section.11.5">11.5</a>&nbsp;&nbsp;&nbsp;<a href="#privacy.issues.connected.to.accept.header.fields">Privacy Issues Connected to Accept Header Fields</a></li>
     765         <li><a href="#rfc.section.10">10.</a>&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a><ul>
     766               <li><a href="#rfc.section.10.1">10.1</a>&nbsp;&nbsp;&nbsp;<a href="#security.sensitive">Transfer of Sensitive Information</a></li>
     767               <li><a href="#rfc.section.10.2">10.2</a>&nbsp;&nbsp;&nbsp;<a href="#encoding.sensitive.information.in.uris">Encoding Sensitive Information in URIs</a></li>
     768               <li><a href="#rfc.section.10.3">10.3</a>&nbsp;&nbsp;&nbsp;<a href="#location.spoofing-leakage">Location Header Fields: Spoofing and Information Leakage</a></li>
     769               <li><a href="#rfc.section.10.4">10.4</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.10.4">Security Considerations for CONNECT</a></li>
     770               <li><a href="#rfc.section.10.5">10.5</a>&nbsp;&nbsp;&nbsp;<a href="#privacy.issues.connected.to.accept.header.fields">Privacy Issues Connected to Accept Header Fields</a></li>
    776771            </ul>
    777772         </li>
    778          <li><a href="#rfc.section.12">12.</a>&nbsp;&nbsp;&nbsp;<a href="#acks">Acknowledgments</a></li>
    779          <li><a href="#rfc.section.13">13.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
    780                <li><a href="#rfc.section.13.1">13.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
    781                <li><a href="#rfc.section.13.2">13.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
     773         <li><a href="#rfc.section.11">11.</a>&nbsp;&nbsp;&nbsp;<a href="#acks">Acknowledgments</a></li>
     774         <li><a href="#rfc.section.12">12.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
     775               <li><a href="#rfc.section.12.1">12.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
     776               <li><a href="#rfc.section.12.2">12.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
    782777            </ul>
    783778         </li>
     
    848843      </p>
    849844      <p id="rfc.section.1.p.2">HTTP provides a uniform interface for interacting with resources regardless of their type, nature, or implementation. HTTP
    850          semantics includes the intentions defined by each request method (<a href="#methods" title="Request Methods">Section&nbsp;5</a>), extensions to those semantics that might be described in request header fields (<a href="#request.header.fields" title="Request Header Fields">Section&nbsp;6</a>), the meaning of status codes to indicate a machine-readable response (<a href="#status.codes" title="Response Status Codes">Section&nbsp;7</a>), and other control data and resource metadata that might be given in response header fields (<a href="#response.header.fields" title="Response Header Fields">Section&nbsp;8</a>).
     845         semantics includes the intentions defined by each request method (<a href="#methods" title="Request Methods">Section&nbsp;4</a>), extensions to those semantics that might be described in request header fields (<a href="#request.header.fields" title="Request Header Fields">Section&nbsp;5</a>), the meaning of status codes to indicate a machine-readable response (<a href="#status.codes" title="Response Status Codes">Section&nbsp;6</a>), and other control data and resource metadata that might be given in response header fields (<a href="#response.header.fields" title="Response Header Fields">Section&nbsp;7</a>).
    851846      </p>
    852847      <p id="rfc.section.1.p.3"><span id="rfc.iref.c.1"></span> In addition, this document defines the payload of messages (a.k.a., content), the associated metadata header fields that define
     
    871866      </p>
    872867      <p id="rfc.section.2.p.3">One design goal of HTTP is to separate resource identification from request semantics, which is made possible by vesting the
    873          request semantics in the request method (<a href="#methods" title="Request Methods">Section&nbsp;5</a>) and a few request-modifying header fields (<a href="#request.header.fields" title="Request Header Fields">Section&nbsp;6</a>). Resource owners <em class="bcp14">SHOULD NOT</em> include request semantics within a URI, such as by specifying an action to invoke within the path or query components of the
     868         request semantics in the request method (<a href="#methods" title="Request Methods">Section&nbsp;4</a>) and a few request-modifying header fields (<a href="#request.header.fields" title="Request Header Fields">Section&nbsp;5</a>). Resource owners <em class="bcp14">SHOULD NOT</em> include request semantics within a URI, such as by specifying an action to invoke within the path or query components of the
    874869         effective request URI, unless those semantics are disabled when they are inconsistent with the request method.
    875870      </p>
     
    885880         (representation body).
    886881      </p>
    887       <p id="rfc.section.3.p.3">HTTP messages can transfer a full or partial representation in the payload (<a href="#payload" title="Payload">Section&nbsp;4</a>) if not otherwise restricted by the request method or response status code. In a request, the purpose of such a representation
    888          is defined by the method semantics. In a response, the purpose is defined by both the request method and the response status
    889          code.
    890       </p>
    891       <p id="rfc.section.3.p.4">For example, a representation in the payload of a PUT request (<a href="#PUT" id="rfc.xref.PUT.1" title="PUT">Section&nbsp;5.3.4</a>) represents the desired state of the target resource if the request is successfully applied, whereas a representation in
    892          the payload of a POST request (<a href="#POST" id="rfc.xref.POST.1" title="POST">Section&nbsp;5.3.3</a>) represents an anonymous resource for providing data to be processed, such as the information that a user entered within
     882      <div id="rfc.iref.p.1"></div>
     883      <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a id="payload" href="#payload">Message Payload</a></h2>
     884      <p id="rfc.section.3.1.p.1">Some HTTP messages transfer a complete or partial representation as the message "<dfn>payload</dfn>". In some cases, a payload might only contain the associated representation's header fields (e.g., responses to HEAD) or
     885         only some part(s) of the representation body (e.g., the <a href="p5-range.html#status.206" class="smpl">206 (Partial Content)</a> status code).
     886      </p>
     887      <p id="rfc.section.3.1.p.2">The purpose of a payload in a request is defined by the method semantics. In a response, the payload's purpose is defined
     888         by both the request method and the response status code.
     889      </p>
     890      <p id="rfc.section.3.1.p.3">For example, a representation in the payload of a PUT request (<a href="#PUT" id="rfc.xref.PUT.1" title="PUT">Section&nbsp;4.3.4</a>) represents the desired state of the target resource if the request is successfully applied, whereas a representation in
     891         the payload of a POST request (<a href="#POST" id="rfc.xref.POST.1" title="POST">Section&nbsp;4.3.3</a>) represents an anonymous resource for providing data to be processed, such as the information that a user entered within
    893892         an HTML form.
    894893      </p>
    895       <p id="rfc.section.3.p.5">Likewise, the payload of a <a href="#status.200" class="smpl">200 (OK)</a> response to GET (<a href="#GET" id="rfc.xref.GET.1" title="GET">Section&nbsp;5.3.1</a>) contains a representation of the target resource, as observed at the time of the message origination date (<a href="#header.date" id="rfc.xref.header.date.1" title="Date">Section&nbsp;8.2.1</a>), whereas the same status code in a response to POST might contain either a representation of the processing result or a
     894      <p id="rfc.section.3.1.p.4">Likewise, the payload of a <a href="#status.200" class="smpl">200 (OK)</a> response to GET (<a href="#GET" id="rfc.xref.GET.1" title="GET">Section&nbsp;4.3.1</a>) contains a representation of the target resource, as observed at the time of the message origination date (<a href="#header.date" id="rfc.xref.header.date.1" title="Date">Section&nbsp;7.2.1</a>), whereas the same status code in a response to POST might contain either a representation of the processing result or a
    896895         current representation of the target resource after applying the processing. Some responses only contain the representation's
    897896         header fields as the payload. Response messages with an error status code usually contain a representation that describes
    898897         the error and what next steps are suggested for resolving it.
    899898      </p>
    900       <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a id="associating.representation.with.resource" href="#associating.representation.with.resource">Associating a Representation with its Resource</a></h2>
    901       <p id="rfc.section.3.1.p.1">It is sometimes necessary to determine an identifier for the resource associated with a representation.</p>
    902       <p id="rfc.section.3.1.p.2">An HTTP request representation, when present, is always associated with an anonymous (i.e., unidentified) resource.</p>
    903       <p id="rfc.section.3.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.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>). However, this is not always the case. To determine the URI of the resource a response is associated with, the following
     899      <p id="rfc.section.3.1.p.5">Header fields that specifically describe the payload, rather than the associated representation, are referred to as "payload
     900         header fields". Payload header fields are defined in other parts of this specification, due to their impact on message parsing.
     901      </p>
     902      <div id="rfc.table.u.1">
     903         <table class="tt full left" cellpadding="3" cellspacing="0">
     904            <thead>
     905               <tr>
     906                  <th>Header Field Name</th>
     907                  <th>Defined in...</th>
     908               </tr>
     909            </thead>
     910            <tbody>
     911               <tr>
     912                  <td class="left">Content-Length</td>
     913                  <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.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a></td>
     914               </tr>
     915               <tr>
     916                  <td class="left">Content-Range</td>
     917                  <td class="left"><a href="p5-range.html#header.content-range" title="Content-Range">Section 5.2</a> of <a href="#Part5" id="rfc.xref.Part5.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a></td>
     918               </tr>
     919               <tr>
     920                  <td class="left">Transfer-Encoding</td>
     921                  <td class="left"><a href="p1-messaging.html#header.transfer-encoding" title="Transfer-Encoding">Section 3.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a></td>
     922               </tr>
     923            </tbody>
     924         </table>
     925      </div>
     926      <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a id="associating.representation.with.resource" href="#associating.representation.with.resource">Associating a Representation with its Resource</a></h2>
     927      <p id="rfc.section.3.2.p.1">It is sometimes necessary to determine an identifier for the resource associated with a representation.</p>
     928      <p id="rfc.section.3.2.p.2">An HTTP request representation, when present, is always associated with an anonymous (i.e., unidentified) resource.</p>
     929      <p id="rfc.section.3.2.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.9"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>). However, this is not always the case. To determine the URI of the resource a response is associated with, the following
    904930         rules are used (with the first applicable one being selected):
    905931      </p>
     
    919945         <li>Otherwise, the response is a representation of an anonymous (i.e., unidentified) resource.</li>
    920946      </ol>
    921       <p id="rfc.section.3.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
     947      <p id="rfc.section.3.2.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
    922948            cache invalidation.]</span>
    923949      </p>
    924       <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a id="representation.header.fields" href="#representation.header.fields">Representation Header Fields</a></h2>
    925       <p id="rfc.section.3.2.p.1">Representation header fields define metadata about the representation data enclosed in the message body or, if no message
     950      <h2 id="rfc.section.3.3"><a href="#rfc.section.3.3">3.3</a>&nbsp;<a id="representation.header.fields" href="#representation.header.fields">Representation Header Fields</a></h2>
     951      <p id="rfc.section.3.3.p.1">Representation header fields define metadata about the representation data enclosed in the message body or, if no message
    926952         body is present, about the representation that would have been transferred in a <a href="#status.200" class="smpl">200 (OK)</a> response to a simultaneous GET request with the same effective request URI.
    927953      </p>
    928       <p id="rfc.section.3.2.p.2">The following header fields are defined as representation metadata:</p>
    929       <div id="rfc.table.u.1">
     954      <p id="rfc.section.3.3.p.2">The following header fields are defined as representation metadata:</p>
     955      <div id="rfc.table.u.2">
    930956         <table class="tt full left" cellpadding="3" cellspacing="0">
    931957            <thead>
     
    938964               <tr>
    939965                  <td class="left">Content-Type</td>
    940                   <td class="left"><a href="#header.content-type" id="rfc.xref.header.content-type.1" title="Content-Type">Section&nbsp;3.2.1</a></td>
     966                  <td class="left"><a href="#header.content-type" id="rfc.xref.header.content-type.1" title="Content-Type">Section&nbsp;3.3.1</a></td>
    941967               </tr>
    942968               <tr>
    943969                  <td class="left">Content-Encoding</td>
    944                   <td class="left"><a href="#header.content-encoding" id="rfc.xref.header.content-encoding.1" title="Content-Encoding">Section&nbsp;3.2.2</a></td>
     970                  <td class="left"><a href="#header.content-encoding" id="rfc.xref.header.content-encoding.1" title="Content-Encoding">Section&nbsp;3.3.2</a></td>
    945971               </tr>
    946972               <tr>
    947973                  <td class="left">Content-Language</td>
    948                   <td class="left"><a href="#header.content-language" id="rfc.xref.header.content-language.1" title="Content-Language">Section&nbsp;3.2.3</a></td>
     974                  <td class="left"><a href="#header.content-language" id="rfc.xref.header.content-language.1" title="Content-Language">Section&nbsp;3.3.3</a></td>
    949975               </tr>
    950976               <tr>
    951977                  <td class="left">Content-Location</td>
    952                   <td class="left"><a href="#header.content-location" id="rfc.xref.header.content-location.1" title="Content-Location">Section&nbsp;3.2.4</a></td>
     978                  <td class="left"><a href="#header.content-location" id="rfc.xref.header.content-location.1" title="Content-Location">Section&nbsp;3.3.4</a></td>
    953979               </tr>
    954980               <tr>
     
    960986      </div>
    961987      <div id="rfc.iref.c.2"></div>
    962       <h3 id="rfc.section.3.2.1"><a href="#rfc.section.3.2.1">3.2.1</a>&nbsp;<a id="header.content-type" href="#header.content-type">Content-Type</a></h3>
    963       <p id="rfc.section.3.2.1.p.1">The "Content-Type" header field indicates the media type of the representation. In the case of responses to the HEAD method,
     988      <h3 id="rfc.section.3.3.1"><a href="#rfc.section.3.3.1">3.3.1</a>&nbsp;<a id="header.content-type" href="#header.content-type">Content-Type</a></h3>
     989      <p id="rfc.section.3.3.1.p.1">The "Content-Type" header field indicates the media type of the representation. In the case of responses to the HEAD method,
    964990         the media type is that which would have been sent had the request been a GET.
    965991      </p>
    966992      <div id="rfc.figure.u.1"></div><pre class="inline"><span id="rfc.iref.g.1"></span>  <a href="#header.content-type" class="smpl">Content-Type</a> = <a href="#media.types" class="smpl">media-type</a>
    967 </pre><p id="rfc.section.3.2.1.p.3">Media types are defined in <a href="#media.types" title="Media Types">Section&nbsp;9.5</a>. An example of the field is
     993</pre><p id="rfc.section.3.3.1.p.3">Media types are defined in <a href="#media.types" title="Media Types">Section&nbsp;8.5</a>. An example of the field is
    968994      </p>
    969995      <div id="rfc.figure.u.2"></div><pre class="text">  Content-Type: text/html; charset=ISO-8859-4
    970 </pre><p id="rfc.section.3.2.1.p.5">Further discussion of Content-Type is provided in <a href="#representation.data" title="Representation Data">Section&nbsp;3.4</a>.
     996</pre><p id="rfc.section.3.3.1.p.5">Further discussion of Content-Type is provided in <a href="#representation.data" title="Representation Data">Section&nbsp;3.5</a>.
    971997      </p>
    972998      <div id="rfc.iref.c.3"></div>
    973       <h3 id="rfc.section.3.2.2"><a href="#rfc.section.3.2.2">3.2.2</a>&nbsp;<a id="header.content-encoding" href="#header.content-encoding">Content-Encoding</a></h3>
    974       <p id="rfc.section.3.2.2.p.1">The "Content-Encoding" header field indicates what content-codings have been applied to the representation beyond those inherent
     999      <h3 id="rfc.section.3.3.2"><a href="#rfc.section.3.3.2">3.3.2</a>&nbsp;<a id="header.content-encoding" href="#header.content-encoding">Content-Encoding</a></h3>
     1000      <p id="rfc.section.3.3.2.p.1">The "Content-Encoding" header field indicates what content-codings have been applied to the representation beyond those inherent
    9751001         in the media type, and thus what decoding mechanisms have to be applied in order to obtain the media-type referenced by the <a href="#header.content-type" class="smpl">Content-Type</a> header field. Content-Encoding is primarily used to allow a representation to be compressed without losing the identity of
    9761002         its underlying media type.
    9771003      </p>
    9781004      <div id="rfc.figure.u.3"></div><pre class="inline"><span id="rfc.iref.g.2"></span>  <a href="#header.content-encoding" class="smpl">Content-Encoding</a> = 1#<a href="#content.codings" class="smpl">content-coding</a>
    979 </pre><p id="rfc.section.3.2.2.p.3">Content codings are defined in <a href="#content.codings" title="Content Codings">Section&nbsp;9.4</a>. An example of its use is
     1005</pre><p id="rfc.section.3.3.2.p.3">Content codings are defined in <a href="#content.codings" title="Content Codings">Section&nbsp;8.4</a>. An example of its use is
    9801006      </p>
    9811007      <div id="rfc.figure.u.4"></div><pre class="text">  Content-Encoding: gzip
    982 </pre><p id="rfc.section.3.2.2.p.5">The content-coding is a characteristic of the representation. Typically, the representation body is stored with this encoding
     1008</pre><p id="rfc.section.3.3.2.p.5">The content-coding is a characteristic of the representation. Typically, the representation body is stored with this encoding
    9831009         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
    9841010         directive is present in the message.
    9851011      </p>
    986       <p id="rfc.section.3.2.2.p.6">If the media type includes an inherent encoding, such as a data format that is always compressed, then that encoding would
     1012      <p id="rfc.section.3.3.2.p.6">If the media type includes an inherent encoding, such as a data format that is always compressed, then that encoding would
    9871013         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
    9881014         would only be listed if, for some bizarre reason, it is applied a second time to form the representation. Likewise, an origin
     
    9911017         as ..." dialog instead of automatic decompression and rendering of content).
    9921018      </p>
    993       <p id="rfc.section.3.2.2.p.7">A representation that has a content-coding applied to it <em class="bcp14">MUST</em> include a Content-Encoding header field that lists the content-coding(s) applied.
    994       </p>
    995       <p id="rfc.section.3.2.2.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.
    996       </p>
    997       <p id="rfc.section.3.2.2.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).
     1019      <p id="rfc.section.3.3.2.p.7">A representation that has a content-coding applied to it <em class="bcp14">MUST</em> include a Content-Encoding header field that lists the content-coding(s) applied.
     1020      </p>
     1021      <p id="rfc.section.3.3.2.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.
     1022      </p>
     1023      <p id="rfc.section.3.3.2.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).
    9981024      </p>
    9991025      <div id="rfc.iref.c.4"></div>
    1000       <h3 id="rfc.section.3.2.3"><a href="#rfc.section.3.2.3">3.2.3</a>&nbsp;<a id="header.content-language" href="#header.content-language">Content-Language</a></h3>
    1001       <p id="rfc.section.3.2.3.p.1">The "Content-Language" header field describes the natural language(s) of the intended audience for the representation. Note
     1026      <h3 id="rfc.section.3.3.3"><a href="#rfc.section.3.3.3">3.3.3</a>&nbsp;<a id="header.content-language" href="#header.content-language">Content-Language</a></h3>
     1027      <p id="rfc.section.3.3.3.p.1">The "Content-Language" header field describes the natural language(s) of the intended audience for the representation. Note
    10021028         that this might not be equivalent to all the languages used within the representation.
    10031029      </p>
    10041030      <div id="rfc.figure.u.5"></div><pre class="inline"><span id="rfc.iref.g.3"></span>  <a href="#header.content-language" class="smpl">Content-Language</a> = 1#<a href="#language.tags" class="smpl">language-tag</a>
    1005 </pre><p id="rfc.section.3.2.3.p.3">Language tags are defined in <a href="#language.tags" title="Language Tags">Section&nbsp;9.6</a>. The primary purpose of Content-Language is to allow a user to identify and differentiate representations according to the
     1031</pre><p id="rfc.section.3.3.3.p.3">Language tags are defined in <a href="#language.tags" title="Language Tags">Section&nbsp;8.6</a>. The primary purpose of Content-Language is to allow a user to identify and differentiate representations according to the
    10061032         user's own preferred language. Thus, if the body content is intended only for a Danish-literate audience, the appropriate
    10071033         field is
    10081034      </p>
    10091035      <div id="rfc.figure.u.6"></div><pre class="text">  Content-Language: da
    1010 </pre><p id="rfc.section.3.2.3.p.5">If no Content-Language is specified, the default is that the content is intended for all language audiences. This might mean
     1036</pre><p id="rfc.section.3.3.3.p.5">If no Content-Language is specified, the default is that the content is intended for all language audiences. This might mean
    10111037         that the sender does not consider it to be specific to any natural language, or that the sender does not know for which language
    10121038         it is intended.
    10131039      </p>
    1014       <p id="rfc.section.3.2.3.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
     1040      <p id="rfc.section.3.3.3.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
    10151041         simultaneously in the original Maori and English versions, would call for
    10161042      </p>
    10171043      <div id="rfc.figure.u.7"></div><pre class="text">  Content-Language: mi, en
    1018 </pre><p id="rfc.section.3.2.3.p.8">However, just because multiple languages are present within a representation does not mean that it is intended for multiple
     1044</pre><p id="rfc.section.3.3.3.p.8">However, just because multiple languages are present within a representation does not mean that it is intended for multiple
    10191045         linguistic audiences. An example would be a beginner's language primer, such as "A First Lesson in Latin", which is clearly
    10201046         intended to be used by an English-literate audience. In this case, the Content-Language would properly only include "en".
    10211047      </p>
    1022       <p id="rfc.section.3.2.3.p.9">Content-Language <em class="bcp14">MAY</em> be applied to any media type — it is not limited to textual documents.
     1048      <p id="rfc.section.3.3.3.p.9">Content-Language <em class="bcp14">MAY</em> be applied to any media type — it is not limited to textual documents.
    10231049      </p>
    10241050      <div id="rfc.iref.c.5"></div>
    1025       <h3 id="rfc.section.3.2.4"><a href="#rfc.section.3.2.4">3.2.4</a>&nbsp;<a id="header.content-location" href="#header.content-location">Content-Location</a></h3>
    1026       <p id="rfc.section.3.2.4.p.1">The "Content-Location" header field supplies a URI that can be used as a specific identifier for the representation in this
     1051      <h3 id="rfc.section.3.3.4"><a href="#rfc.section.3.3.4">3.3.4</a>&nbsp;<a id="header.content-location" href="#header.content-location">Content-Location</a></h3>
     1052      <p id="rfc.section.3.3.4.p.1">The "Content-Location" header field supplies a URI that can be used as a specific identifier for the representation in this
    10271053         message. In other words, if one were to perform a GET on this URI at the time of this message's generation, then a <a href="#status.200" class="smpl">200 (OK)</a> response would contain the same representation that is enclosed as payload in this message.
    10281054      </p>
    10291055      <div id="rfc.figure.u.8"></div><pre class="inline"><span id="rfc.iref.g.4"></span>  <a href="#header.content-location" class="smpl">Content-Location</a> = <a href="#imported.abnf" class="smpl">absolute-URI</a> / <a href="#imported.abnf" class="smpl">partial-URI</a>
    1030 </pre><p id="rfc.section.3.2.4.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.8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[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
     1056</pre><p id="rfc.section.3.3.4.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.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[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
    10311057         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.
    10321058      </p>
    1033       <p id="rfc.section.3.2.4.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
     1059      <p id="rfc.section.3.3.4.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
    10341060         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
    10351061         when no Content-Location is provided by the server. For a state-changing request like PUT or POST, it implies that the server's
     
    10381064         need for a subsequent GET request.
    10391065      </p>
    1040       <p id="rfc.section.3.2.4.p.5">If Content-Location is included in a response message and its value differs from the effective request URI, then the origin
     1066      <p id="rfc.section.3.3.4.p.5">If Content-Location is included in a response message and its value differs from the effective request URI, then the origin
    10411067         server is informing recipients that this representation has its own, presumably more specific, identifier. For a GET or HEAD
    10421068         request, this is an indication that the effective request URI identifies a resource that is subject to content negotiation
     
    10461072         the payload of the <a href="#status.200" class="smpl">200 (OK)</a> response; the Content-Location value provides an identifier for retrieving a copy of that same receipt in the future.
    10471073      </p>
    1048       <p id="rfc.section.3.2.4.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
     1074      <p id="rfc.section.3.3.4.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
    10491075         representation (prior to any subsequent modification of the content by that user agent). In other words, the user agent is
    10501076         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
     
    10541080         latter semantics, it would have applied the PUT directly to the Content-Location URI.
    10551081      </p>
    1056       <p id="rfc.section.3.2.4.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
     1082      <p id="rfc.section.3.3.4.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
    10571083         in other contexts, such as within source links or other metadata.
    10581084      </p>
    1059       <p id="rfc.section.3.2.4.p.8">A cache cannot assume that a representation with a Content-Location different from the URI used to retrieve it can be used
     1085      <p id="rfc.section.3.3.4.p.8">A cache cannot assume that a representation with a Content-Location different from the URI used to retrieve it can be used
    10601086         to respond to later requests on that Content-Location URI.
    10611087      </p>
    1062       <p id="rfc.section.3.2.4.p.9">If the Content-Location value is a partial URI, the partial URI is interpreted relative to the effective request URI.</p>
    1063       <h2 id="rfc.section.3.3"><a href="#rfc.section.3.3">3.3</a>&nbsp;<a id="selected.representation" href="#selected.representation">Selected Representation Header Fields</a></h2>
    1064       <p id="rfc.section.3.3.p.1"><span id="rfc.iref.s.1"></span> We use the term "<dfn>selected representation</dfn>" to refer to the the current representation of a target resource that would have been selected in a successful response if
     1088      <p id="rfc.section.3.3.4.p.9">If the Content-Location value is a partial URI, the partial URI is interpreted relative to the effective request URI.</p>
     1089      <h2 id="rfc.section.3.4"><a href="#rfc.section.3.4">3.4</a>&nbsp;<a id="selected.representation" href="#selected.representation">Selected Representation Header Fields</a></h2>
     1090      <p id="rfc.section.3.4.p.1"><span id="rfc.iref.s.1"></span> We use the term "<dfn>selected representation</dfn>" to refer to the the current representation of a target resource that would have been selected in a successful response if
    10651091         the same request had used the method GET and excluded any conditional request header fields.
    10661092      </p>
    1067       <p id="rfc.section.3.3.p.2">Additional header fields define metadata about the selected representation, which might differ from the representation included
     1093      <p id="rfc.section.3.4.p.2">Additional header fields define metadata about the selected representation, which might differ from the representation included
    10681094         in the message for responses to some state-changing methods. The following header fields are defined as selected representation
    10691095         metadata:
    10701096      </p>
    1071       <div id="rfc.table.u.2">
     1097      <div id="rfc.table.u.3">
    10721098         <table class="tt full left" cellpadding="3" cellspacing="0">
    10731099            <thead>
     
    10891115         </table>
    10901116      </div>
    1091       <h2 id="rfc.section.3.4"><a href="#rfc.section.3.4">3.4</a>&nbsp;<a id="representation.data" href="#representation.data">Representation Data</a></h2>
    1092       <p id="rfc.section.3.4.p.1">The representation body associated with an HTTP message is either provided as the payload body of the message or referred
     1117      <h2 id="rfc.section.3.5"><a href="#rfc.section.3.5">3.5</a>&nbsp;<a id="representation.data" href="#representation.data">Representation Data</a></h2>
     1118      <p id="rfc.section.3.5.p.1">The representation body associated with an HTTP message is either provided as the payload body of the message or referred
    10931119         to by the message semantics and the effective request URI. The representation data is in a format and encoding defined by
    10941120         the representation metadata header fields.
    10951121      </p>
    1096       <p id="rfc.section.3.4.p.2">The data type of the representation data is determined via the header fields <a href="#header.content-type" class="smpl">Content-Type</a> and <a href="#header.content-encoding" class="smpl">Content-Encoding</a>. These define a two-layer, ordered encoding model:
     1122      <p id="rfc.section.3.5.p.2">The data type of the representation data is determined via the header fields <a href="#header.content-type" class="smpl">Content-Type</a> and <a href="#header.content-encoding" class="smpl">Content-Encoding</a>. These define a two-layer, ordered encoding model:
    10971123      </p>
    10981124      <div id="rfc.figure.u.9"></div><pre class="text">  representation-data := Content-Encoding( Content-Type( bits ) )
    1099 </pre><p id="rfc.section.3.4.p.4"> <a href="#header.content-type" class="smpl">Content-Type</a> 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
     1125</pre><p id="rfc.section.3.5.p.4"> <a href="#header.content-type" class="smpl">Content-Type</a> 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
    11001126         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
    11011127         to the sender. If the Content-Type header field is not present, it indicates that the sender does not know the media type
    11021128         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.1"><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.
    11031129      </p>
    1104       <p id="rfc.section.3.4.p.5">In practice, resource owners do not always properly configure their origin server to provide the correct Content-Type for
     1130      <p id="rfc.section.3.5.p.5">In practice, resource owners do not always properly configure their origin server to provide the correct Content-Type for
    11051131         a given representation, with the result that some clients will examine a response body's content and override the specified
    11061132         type. Clients that do so risk drawing incorrect conclusions, which might expose additional security risks (e.g., "privilege
     
    11091135         such "content sniffing" when it is used.
    11101136      </p>
    1111       <p id="rfc.section.3.4.p.6"> <a href="#header.content-encoding" class="smpl">Content-Encoding</a> is used to indicate any additional content codings applied to the data, usually for the purpose of data compression, that
     1137      <p id="rfc.section.3.5.p.6"> <a href="#header.content-encoding" class="smpl">Content-Encoding</a> is used to indicate any additional content codings applied to the data, usually for the purpose of data compression, that
    11121138         are a property of the representation. If Content-Encoding is not present, then there is no additional encoding beyond that
    11131139         defined by the <a href="#header.content-type" class="smpl">Content-Type</a> header field.
    11141140      </p>
    1115       <h2 id="rfc.section.3.5"><a href="#rfc.section.3.5">3.5</a>&nbsp;<a id="content.negotiation" href="#content.negotiation">Content Negotiation</a></h2>
    1116       <p id="rfc.section.3.5.p.1">HTTP responses include a representation which contains information for interpretation, whether by a human user or for further
     1141      <h2 id="rfc.section.3.6"><a href="#rfc.section.3.6">3.6</a>&nbsp;<a id="content.negotiation" href="#content.negotiation">Content Negotiation</a></h2>
     1142      <p id="rfc.section.3.6.p.1">HTTP responses include a representation which contains information for interpretation, whether by a human user or for further
    11171143         processing. Often, the server has different ways of representing the same information; for example, in different formats,
    11181144         languages, or using different character encodings.
    11191145      </p>
    1120       <p id="rfc.section.3.5.p.2">HTTP clients and their users might have different or variable capabilities, characteristics or preferences which would influence
     1146      <p id="rfc.section.3.6.p.2">HTTP clients and their users might have different or variable capabilities, characteristics or preferences which would influence
    11211147         which representation, among those available from the server, would be best for the server to deliver. For this reason, HTTP
    11221148         provides mechanisms for "content negotiation" — a process of allowing selection of a representation of a given resource, when
    11231149         more than one is available.
    11241150      </p>
    1125       <p id="rfc.section.3.5.p.3">This specification defines two patterns of content negotiation; "proactive", where the server selects the representation based
     1151      <p id="rfc.section.3.6.p.3">This specification defines two patterns of content negotiation; "proactive", where the server selects the representation based
    11261152         upon the client's stated preferences, and "reactive" negotiation, where the server provides a list of representations for
    11271153         the client to choose from, based upon their metadata. In addition, there are other patterns: some applications use an "active
     
    11291155         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.
    11301156      </p>
    1131       <p id="rfc.section.3.5.p.4">These patterns are all widely used, and have trade-offs in applicability and practicality. In particular, when the number
     1157      <p id="rfc.section.3.6.p.4">These patterns are all widely used, and have trade-offs in applicability and practicality. In particular, when the number
    11321158         of preferences or capabilities to be expressed by a client are large (such as when many different formats are supported by
    11331159         a user-agent), proactive negotiation becomes unwieldy, and might not be appropriate. Conversely, when the number of representations
    11341160         to choose from is very large, reactive negotiation might not be appropriate.
    11351161      </p>
    1136       <p id="rfc.section.3.5.p.5">Note that, in all cases, the supplier of representations has the responsibility for determining which representations might
     1162      <p id="rfc.section.3.6.p.5">Note that, in all cases, the supplier of representations has the responsibility for determining which representations might
    11371163         be considered to be the "same information".
    11381164      </p>
    1139       <h3 id="rfc.section.3.5.1"><a href="#rfc.section.3.5.1">3.5.1</a>&nbsp;<a id="proactive.negotiation" href="#proactive.negotiation">Proactive Negotiation</a></h3>
    1140       <p id="rfc.section.3.5.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 proactive
     1165      <h3 id="rfc.section.3.6.1"><a href="#rfc.section.3.6.1">3.6.1</a>&nbsp;<a id="proactive.negotiation" href="#proactive.negotiation">Proactive Negotiation</a></h3>
     1166      <p id="rfc.section.3.6.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 proactive
    11411167         negotiation. Selection is based on the available representations of the response (the dimensions over which it can vary; e.g.,
    11421168         language, content-coding, etc.) and the contents of particular header fields in the request message or on other information
    11431169         pertaining to the request (such as the network address of the client).
    11441170      </p>
    1145       <p id="rfc.section.3.5.1.p.2">Proactive negotiation is advantageous when the algorithm for selecting from among the available representations is difficult
     1171      <p id="rfc.section.3.6.1.p.2">Proactive negotiation is advantageous when the algorithm for selecting from among the available representations is difficult
    11461172         to describe to the user agent, or when the server desires to send its "best guess" to the client along with the first response
    11471173         (hoping to avoid the round-trip delay of a subsequent request if the "best guess" is good enough for the user). In order to
    11481174         improve the server's guess, the user agent <em class="bcp14">MAY</em> include request header fields (<a href="#header.accept" class="smpl">Accept</a>, <a href="#header.accept-language" class="smpl">Accept-Language</a>, <a href="#header.accept-encoding" class="smpl">Accept-Encoding</a>, etc.) which describe its preferences for such a response.
    11491175      </p>
    1150       <p id="rfc.section.3.5.1.p.3">Proactive negotiation has disadvantages: </p>
     1176      <p id="rfc.section.3.6.1.p.3">Proactive negotiation has disadvantages: </p>
    11511177      <ol>
    11521178         <li>It is impossible for the server to accurately determine what might be "best" for any given user, since that would require
     
    11601186         <li>It might limit a public cache's ability to use the same response for multiple user's requests.</li>
    11611187      </ol>
    1162       <p id="rfc.section.3.5.1.p.4">Proactive negotiation allows the user agent to specify its preferences, but it cannot expect responses to always honor them.
     1188      <p id="rfc.section.3.6.1.p.4">Proactive negotiation allows the user agent to specify its preferences, but it cannot expect responses to always honor them.
    11631189         For example, the origin server might not implement proactive negotiation, or it might decide that sending a response that
    11641190         doesn't conform to them is better than sending a <a href="#status.406" class="smpl">406
    11651191            (Not Acceptable)</a> response.
    11661192      </p>
    1167       <p id="rfc.section.3.5.1.p.5">HTTP/1.1 includes the following header fields for enabling proactive negotiation through description of user agent capabilities
    1168          and user preferences: <a href="#header.accept" class="smpl">Accept</a> (<a href="#header.accept" id="rfc.xref.header.accept.1" title="Accept">Section&nbsp;6.3.2</a>), <a href="#header.accept-charset" class="smpl">Accept-Charset</a> (<a href="#header.accept-charset" id="rfc.xref.header.accept-charset.1" title="Accept-Charset">Section&nbsp;6.3.3</a>), <a href="#header.accept-encoding" class="smpl">Accept-Encoding</a> (<a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.1" title="Accept-Encoding">Section&nbsp;6.3.4</a>), <a href="#header.accept-language" class="smpl">Accept-Language</a> (<a href="#header.accept-language" id="rfc.xref.header.accept-language.1" title="Accept-Language">Section&nbsp;6.3.5</a>), and <a href="#header.user-agent" class="smpl">User-Agent</a> (<a href="#header.user-agent" id="rfc.xref.header.user-agent.1" title="User-Agent">Section&nbsp;6.5.3</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
     1193      <p id="rfc.section.3.6.1.p.5">HTTP/1.1 includes the following header fields for enabling proactive negotiation through description of user agent capabilities
     1194         and user preferences: <a href="#header.accept" class="smpl">Accept</a> (<a href="#header.accept" id="rfc.xref.header.accept.1" title="Accept">Section&nbsp;5.3.2</a>), <a href="#header.accept-charset" class="smpl">Accept-Charset</a> (<a href="#header.accept-charset" id="rfc.xref.header.accept-charset.1" title="Accept-Charset">Section&nbsp;5.3.3</a>), <a href="#header.accept-encoding" class="smpl">Accept-Encoding</a> (<a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.1" title="Accept-Encoding">Section&nbsp;5.3.4</a>), <a href="#header.accept-language" class="smpl">Accept-Language</a> (<a href="#header.accept-language" id="rfc.xref.header.accept-language.1" title="Accept-Language">Section&nbsp;5.3.5</a>), and <a href="#header.user-agent" class="smpl">User-Agent</a> (<a href="#header.user-agent" id="rfc.xref.header.user-agent.1" title="User-Agent">Section&nbsp;5.5.3</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
    11691195         within extension header fields not defined by this specification.
    11701196      </p>
    1171       <div class="note" id="rfc.section.3.5.1.p.6">
     1197      <div class="note" id="rfc.section.3.6.1.p.6">
    11721198         <p> <b>Note:</b> In practice, <a href="#header.user-agent" class="smpl">User-Agent</a> based negotiation is fragile, because new clients might not be recognized.
    11731199         </p>
    11741200      </div>
    1175       <p id="rfc.section.3.5.1.p.7">The <a href="#header.vary" class="smpl">Vary</a> header field (<a href="#header.vary" id="rfc.xref.header.vary.1" title="Vary">Section&nbsp;8.2.2</a>) can be used to express the parameters the server uses to select a representation that is subject to proactive negotiation.
    1176       </p>
    1177       <h3 id="rfc.section.3.5.2"><a href="#rfc.section.3.5.2">3.5.2</a>&nbsp;<a id="reactive.negotiation" href="#reactive.negotiation">Reactive Negotiation</a></h3>
    1178       <p id="rfc.section.3.5.2.p.1">With reactive negotiation, selection of the best representation for a response is performed by the user agent after receiving
     1201      <p id="rfc.section.3.6.1.p.7">The <a href="#header.vary" class="smpl">Vary</a> header field (<a href="#header.vary" id="rfc.xref.header.vary.1" title="Vary">Section&nbsp;7.2.2</a>) can be used to express the parameters the server uses to select a representation that is subject to proactive negotiation.
     1202      </p>
     1203      <h3 id="rfc.section.3.6.2"><a href="#rfc.section.3.6.2">3.6.2</a>&nbsp;<a id="reactive.negotiation" href="#reactive.negotiation">Reactive Negotiation</a></h3>
     1204      <p id="rfc.section.3.6.2.p.1">With reactive negotiation, selection of the best representation for a response is performed by the user agent after receiving
    11791205         an initial response from the origin server. Selection is based on a list of the available representations of the response
    11801206         included within the header fields or body of the initial response, with each representation identified by its own URI. Selection
     
    11821208         user selecting from a generated (possibly hypertext) menu.
    11831209      </p>
    1184       <p id="rfc.section.3.5.2.p.2">Reactive negotiation is advantageous when the response would vary over commonly-used dimensions (such as type, language, or
     1210      <p id="rfc.section.3.6.2.p.2">Reactive negotiation is advantageous when the response would vary over commonly-used dimensions (such as type, language, or
    11851211         encoding), when the origin server is unable to determine a user agent's capabilities from examining the request, and generally
    11861212         when public caches are used to distribute server load and reduce network usage.
    11871213      </p>
    1188       <p id="rfc.section.3.5.2.p.3">Reactive negotiation suffers from the disadvantage of needing a second request to obtain the best alternate representation.
     1214      <p id="rfc.section.3.6.2.p.3">Reactive negotiation suffers from the disadvantage of needing a second request to obtain the best alternate representation.
    11891215         This second request is only efficient when caching is used. In addition, this specification does not define any mechanism
    11901216         for supporting automatic selection, though it also does not prevent any such mechanism from being developed as an extension
    11911217         and used within HTTP/1.1.
    11921218      </p>
    1193       <p id="rfc.section.3.5.2.p.4">This specification defines the <a href="#status.300" class="smpl">300 (Multiple Choices)</a> and <a href="#status.406" class="smpl">406 (Not Acceptable)</a> status codes for enabling reactive negotiation when the server is unwilling or unable to provide a varying response using
     1219      <p id="rfc.section.3.6.2.p.4">This specification defines the <a href="#status.300" class="smpl">300 (Multiple Choices)</a> and <a href="#status.406" class="smpl">406 (Not Acceptable)</a> status codes for enabling reactive negotiation when the server is unwilling or unable to provide a varying response using
    11941220         proactive negotiation.
    11951221      </p>
    1196       <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a id="payload" href="#payload">Payload</a></h1>
    1197       <p id="rfc.section.4.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,
    1198          in the form of header fields, and data, in the form of the sequence of octets in the message body after any transfer-coding
    1199          has been decoded.
    1200       </p>
    1201       <div id="rfc.iref.p.1"></div>
    1202       <p id="rfc.section.4.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
    1203          because some messages contain only the associated representation's header fields (e.g., responses to HEAD) or only some part(s)
    1204          of the representation (e.g., the <a href="p5-range.html#status.206" class="smpl">206 (Partial Content)</a> status code).
    1205       </p>
    1206       <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a>&nbsp;<a id="payload.header.fields" href="#payload.header.fields">Payload Header Fields</a></h2>
    1207       <p id="rfc.section.4.1.p.1">HTTP header fields that specifically define the payload, rather than the associated representation, are referred to as "payload
    1208          header fields". The following payload header fields are defined by HTTP/1.1:
    1209       </p>
    1210       <div id="rfc.table.u.3">
    1211          <table class="tt full left" cellpadding="3" cellspacing="0">
    1212             <thead>
    1213                <tr>
    1214                   <th>Header Field Name</th>
    1215                   <th>Defined in...</th>
    1216                </tr>
    1217             </thead>
    1218             <tbody>
    1219                <tr>
    1220                   <td class="left">Content-Length</td>
    1221                   <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.9"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a></td>
    1222                </tr>
    1223                <tr>
    1224                   <td class="left">Content-Range</td>
    1225                   <td class="left"><a href="p5-range.html#header.content-range" title="Content-Range">Section 5.2</a> of <a href="#Part5" id="rfc.xref.Part5.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a></td>
    1226                </tr>
    1227             </tbody>
    1228          </table>
    1229       </div>
    1230       <h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a>&nbsp;<a id="payload.body" href="#payload.body">Payload Body</a></h2>
    1231       <p id="rfc.section.4.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.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>. The payload body is obtained from the message body by decoding any <a href="p1-messaging.html#header.transfer-encoding" class="smpl">Transfer-Encoding</a> that might have been applied to ensure safe and proper transfer of the message.
    1232       </p>
    1233       <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a id="methods" href="#methods">Request Methods</a></h1>
    1234       <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;<a id="method.overview" href="#method.overview">Overview</a></h2>
    1235       <p id="rfc.section.5.1.p.1">The request method token is the primary source of request semantics; it indicates the purpose for which the client has made
    1236          this request and what is expected by the client as a successful result. The request semantics <em class="bcp14">MAY</em> be further specialized by the semantics of some header fields when present in a request (<a href="#request.header.fields" title="Request Header Fields">Section&nbsp;6</a>) if those additional semantics do not conflict with the method.
     1222      <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a id="methods" href="#methods">Request Methods</a></h1>
     1223      <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a>&nbsp;<a id="method.overview" href="#method.overview">Overview</a></h2>
     1224      <p id="rfc.section.4.1.p.1">The request method token is the primary source of request semantics; it indicates the purpose for which the client has made
     1225         this request and what is expected by the client as a successful result. The request semantics <em class="bcp14">MAY</em> be further specialized by the semantics of some header fields when present in a request (<a href="#request.header.fields" title="Request Header Fields">Section&nbsp;5</a>) if those additional semantics do not conflict with the method.
    12371226      </p>
    12381227      <div id="rfc.figure.u.10"></div><pre class="inline"><span id="rfc.iref.g.5"></span>  <a href="#method.overview" class="smpl">method</a> = <a href="#imported.abnf" class="smpl">token</a>
    1239 </pre><p id="rfc.section.5.1.p.3">HTTP was originally designed to be usable as an interface to distributed object systems. The request method was envisioned
     1228</pre><p id="rfc.section.4.1.p.3">HTTP was originally designed to be usable as an interface to distributed object systems. The request method was envisioned
    12401229         as applying semantics to a target resource in much the same way as invoking a defined method on an identified object would
    12411230         apply semantics. The method token is case-sensitive because it might be used as a gateway to object-based systems with case-sensitive
    12421231         method names.
    12431232      </p>
    1244       <p id="rfc.section.5.1.p.4">Unlike distributed objects, the standardized request methods in HTTP are not resource-specific, since uniform interfaces provide
     1233      <p id="rfc.section.4.1.p.4">Unlike distributed objects, the standardized request methods in HTTP are not resource-specific, since uniform interfaces provide
    12451234         for better visibility and reuse in network-based systems <a href="#REST" id="rfc.xref.REST.2"><cite title="Architectural Styles and the Design of Network-based Software Architectures">[REST]</cite></a>. Once defined, a standardized method <em class="bcp14">MUST</em> have the same semantics when applied to any resource, though each resource determines for itself whether those semantics are
    12461235         implemented or allowed.
    12471236      </p>
    1248       <p id="rfc.section.5.1.p.5">This specification defines a number of standardized methods that are commonly used in HTTP, as outlined by the following table.
     1237      <p id="rfc.section.4.1.p.5">This specification defines a number of standardized methods that are commonly used in HTTP, as outlined by the following table.
    12491238         By convention, standardized methods are defined in all-uppercase ASCII letters.
    12501239      </p>
     
    12631252                  <td class="left">GET</td>
    12641253                  <td class="left">Transfer a current representation of the target resource.</td>
    1265                   <td class="left"><a href="#GET" id="rfc.xref.GET.2" title="GET">5.3.1</a></td>
     1254                  <td class="left"><a href="#GET" id="rfc.xref.GET.2" title="GET">4.3.1</a></td>
    12661255               </tr>
    12671256               <tr>
    12681257                  <td class="left">HEAD</td>
    12691258                  <td class="left">Same as GET, but do not include a message body in the response.</td>
    1270                   <td class="left"><a href="#HEAD" id="rfc.xref.HEAD.1" title="HEAD">5.3.2</a></td>
     1259                  <td class="left"><a href="#HEAD" id="rfc.xref.HEAD.1" title="HEAD">4.3.2</a></td>
    12711260               </tr>
    12721261               <tr>
    12731262                  <td class="left">POST</td>
    12741263                  <td class="left">Perform resource-specific processing on the request payload.</td>
    1275                   <td class="left"><a href="#POST" id="rfc.xref.POST.2" title="POST">5.3.3</a></td>
     1264                  <td class="left"><a href="#POST" id="rfc.xref.POST.2" title="POST">4.3.3</a></td>
    12761265               </tr>
    12771266               <tr>
    12781267                  <td class="left">PUT</td>
    12791268                  <td class="left">Replace all current representations of the target resource with the request payload.</td>
    1280                   <td class="left"><a href="#PUT" id="rfc.xref.PUT.2" title="PUT">5.3.4</a></td>
     1269                  <td class="left"><a href="#PUT" id="rfc.xref.PUT.2" title="PUT">4.3.4</a></td>
    12811270               </tr>
    12821271               <tr>
    12831272                  <td class="left">DELETE</td>
    12841273                  <td class="left">Remove all current representations of the target resource.</td>
    1285                   <td class="left"><a href="#DELETE" id="rfc.xref.DELETE.1" title="DELETE">5.3.5</a></td>
     1274                  <td class="left"><a href="#DELETE" id="rfc.xref.DELETE.1" title="DELETE">4.3.5</a></td>
    12861275               </tr>
    12871276               <tr>
    12881277                  <td class="left">CONNECT</td>
    12891278                  <td class="left">Establish a tunnel to the server identified by the target resource.</td>
    1290                   <td class="left"><a href="#CONNECT" id="rfc.xref.CONNECT.1" title="CONNECT">5.3.6</a></td>
     1279                  <td class="left"><a href="#CONNECT" id="rfc.xref.CONNECT.1" title="CONNECT">4.3.6</a></td>
    12911280               </tr>
    12921281               <tr>
    12931282                  <td class="left">OPTIONS</td>
    12941283                  <td class="left">Describe the communication options for the target resource.</td>
    1295                   <td class="left"><a href="#OPTIONS" id="rfc.xref.OPTIONS.1" title="OPTIONS">5.3.7</a></td>
     1284                  <td class="left"><a href="#OPTIONS" id="rfc.xref.OPTIONS.1" title="OPTIONS">4.3.7</a></td>
    12961285               </tr>
    12971286               <tr>
    12981287                  <td class="left">TRACE</td>
    12991288                  <td class="left">Perform a message loop-back test along the path to the target resource.</td>
    1300                   <td class="left"><a href="#TRACE" id="rfc.xref.TRACE.1" title="TRACE">5.3.8</a></td>
     1289                  <td class="left"><a href="#TRACE" id="rfc.xref.TRACE.1" title="TRACE">4.3.8</a></td>
    13011290               </tr>
    13021291            </tbody>
    13031292         </table>
    13041293      </div>
    1305       <p id="rfc.section.5.1.p.6">The methods GET and HEAD <em class="bcp14">MUST</em> be supported by all general-purpose servers. All other methods are <em class="bcp14">OPTIONAL</em>. When implemented, a server <em class="bcp14">MUST</em> implement the above methods according to the semantics defined for them in <a href="#method.definitions" title="Method Definitions">Section&nbsp;5.3</a>.
    1306       </p>
    1307       <p id="rfc.section.5.1.p.7">Additional methods <em class="bcp14">MAY</em> be used in HTTP; many have already been standardized outside the scope of this specification and registered within the HTTP
    1308          Method Registry maintained by IANA, as defined in <a href="#method.registry" title="Method Registry">Section&nbsp;10.1</a>.
    1309       </p>
    1310       <p id="rfc.section.5.1.p.8">The set of methods allowed by a target resource can be listed in an <a href="#header.allow" class="smpl">Allow</a> header field (<a href="#header.allow" id="rfc.xref.header.allow.1" title="Allow">Section&nbsp;8.4.1</a>). However, the set of allowed methods can change dynamically. When a request message is received that is unrecognized or
     1294      <p id="rfc.section.4.1.p.6">The methods GET and HEAD <em class="bcp14">MUST</em> be supported by all general-purpose servers. All other methods are <em class="bcp14">OPTIONAL</em>. When implemented, a server <em class="bcp14">MUST</em> implement the above methods according to the semantics defined for them in <a href="#method.definitions" title="Method Definitions">Section&nbsp;4.3</a>.
     1295      </p>
     1296      <p id="rfc.section.4.1.p.7">Additional methods <em class="bcp14">MAY</em> be used in HTTP; many have already been standardized outside the scope of this specification and registered within the HTTP
     1297         Method Registry maintained by IANA, as defined in <a href="#method.registry" title="Method Registry">Section&nbsp;9.1</a>.
     1298      </p>
     1299      <p id="rfc.section.4.1.p.8">The set of methods allowed by a target resource can be listed in an <a href="#header.allow" class="smpl">Allow</a> header field (<a href="#header.allow" id="rfc.xref.header.allow.1" title="Allow">Section&nbsp;7.4.1</a>). However, the set of allowed methods can change dynamically. When a request message is received that is unrecognized or
    13111300         not implemented by an origin server, the origin server <em class="bcp14">SHOULD</em> respond with the <a href="#status.501" class="smpl">501 (Not Implemented)</a> status code. When a request message is received that is known by an origin server but not allowed for the target resource,
    13121301         the origin server <em class="bcp14">SHOULD</em> respond with the <a href="#status.405" class="smpl">405 (Method Not Allowed)</a> status code.
    13131302      </p>
    1314       <h2 id="rfc.section.5.2"><a href="#rfc.section.5.2">5.2</a>&nbsp;<a id="method.properties" href="#method.properties">Common Method Properties</a></h2>
     1303      <h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a>&nbsp;<a id="method.properties" href="#method.properties">Common Method Properties</a></h2>
    13151304      <div id="rfc.iref.s.2"></div>
    1316       <h3 id="rfc.section.5.2.1"><a href="#rfc.section.5.2.1">5.2.1</a>&nbsp;<a id="safe.methods" href="#safe.methods">Safe Methods</a></h3>
    1317       <p id="rfc.section.5.2.1.p.1">Request methods are considered "<dfn id="safe">safe</dfn>" if their defined semantics are essentially read-only; i.e., the client does not request, and does not expect, any state
     1305      <h3 id="rfc.section.4.2.1"><a href="#rfc.section.4.2.1">4.2.1</a>&nbsp;<a id="safe.methods" href="#safe.methods">Safe Methods</a></h3>
     1306      <p id="rfc.section.4.2.1.p.1">Request methods are considered "<dfn id="safe">safe</dfn>" if their defined semantics are essentially read-only; i.e., the client does not request, and does not expect, any state
    13181307         change on the origin server as a result of applying a safe method to a target resource. Likewise, reasonable use of a safe
    13191308         method is not expected to cause any harm, loss of property, or unusual burden on the origin server.
    13201309      </p>
    1321       <p id="rfc.section.5.2.1.p.2">This definition of safe methods does not prevent an implementation from including behavior that is potentially harmful, not
     1310      <p id="rfc.section.4.2.1.p.2">This definition of safe methods does not prevent an implementation from including behavior that is potentially harmful, not
    13221311         entirely read-only, or which causes side-effects while invoking a safe method. What is important, however, is that the client
    13231312         did not request that additional behavior and cannot be held accountable for it. For example, most servers append request information
     
    13261315         the Web will often have the side-effect of charging an advertising account.
    13271316      </p>
    1328       <p id="rfc.section.5.2.1.p.3">The GET, HEAD, OPTIONS, and TRACE request methods are defined to be safe.</p>
    1329       <p id="rfc.section.5.2.1.p.4">The purpose of distinguishing between safe and unsafe methods is to allow automated retrieval processes (spiders) and cache
     1317      <p id="rfc.section.4.2.1.p.3">The GET, HEAD, OPTIONS, and TRACE request methods are defined to be safe.</p>
     1318      <p id="rfc.section.4.2.1.p.4">The purpose of distinguishing between safe and unsafe methods is to allow automated retrieval processes (spiders) and cache
    13301319         performance optimization (pre-fetching) to work without fear of causing harm. In addition, it allows a user agent to apply
    13311320         appropriate constraints on the automated use of unsafe methods when processing potentially untrusted content.
    13321321      </p>
    1333       <p id="rfc.section.5.2.1.p.5">A user agent <em class="bcp14">SHOULD</em> distinguish between safe and unsafe methods when presenting potential actions to a user, such that the user can be made aware
     1322      <p id="rfc.section.4.2.1.p.5">A user agent <em class="bcp14">SHOULD</em> distinguish between safe and unsafe methods when presenting potential actions to a user, such that the user can be made aware
    13341323         of an unsafe action before it is requested.
    13351324      </p>
    1336       <p id="rfc.section.5.2.1.p.6">When a resource is constructed such that parameters within the effective request URI have the effect of selecting an action,
     1325      <p id="rfc.section.4.2.1.p.6">When a resource is constructed such that parameters within the effective request URI have the effect of selecting an action,
    13371326         it is the resource owner's responsibility to ensure that the action is consistent with the request method semantics. For example,
    13381327         it is common for Web-based content editing software to use actions within query parameters, such as "page?do=delete". If the
     
    13421331      </p>
    13431332      <div id="rfc.iref.i.1"></div>
    1344       <h3 id="rfc.section.5.2.2"><a href="#rfc.section.5.2.2">5.2.2</a>&nbsp;<a id="idempotent.methods" href="#idempotent.methods">Idempotent Methods</a></h3>
    1345       <p id="rfc.section.5.2.2.p.1">Request methods are considered "<dfn id="idempotent">idempotent</dfn>" if the intended effect of multiple identical requests is the same as for a single request. PUT, DELETE, and all safe request
     1333      <h3 id="rfc.section.4.2.2"><a href="#rfc.section.4.2.2">4.2.2</a>&nbsp;<a id="idempotent.methods" href="#idempotent.methods">Idempotent Methods</a></h3>
     1334      <p id="rfc.section.4.2.2.p.1">Request methods are considered "<dfn id="idempotent">idempotent</dfn>" if the intended effect of multiple identical requests is the same as for a single request. PUT, DELETE, and all safe request
    13461335         methods are idempotent.
    13471336      </p>
    1348       <p id="rfc.section.5.2.2.p.2">Like the definition of safe, the idempotent property only applies to what has been requested by the user; a server is free
     1337      <p id="rfc.section.4.2.2.p.2">Like the definition of safe, the idempotent property only applies to what has been requested by the user; a server is free
    13491338         to log each request separately, retain a revision control history, or implement other non-idempotent side-effects for each
    13501339         idempotent request.
    13511340      </p>
    1352       <p id="rfc.section.5.2.2.p.3">Idempotent methods are distinguished because the request can be repeated automatically if a communication failure occurs before
     1341      <p id="rfc.section.4.2.2.p.3">Idempotent methods are distinguished because the request can be repeated automatically if a communication failure occurs before
    13531342         the client is able to read the server's response. For example, if a client sends a PUT request and the underlying connection
    13541343         is closed before any response is received, then it can establish a new connection and retry the idempotent request because
     
    13571346      </p>
    13581347      <div id="rfc.iref.c.6"></div>
    1359       <h3 id="rfc.section.5.2.3"><a href="#rfc.section.5.2.3">5.2.3</a>&nbsp;<a id="cacheable.methods" href="#cacheable.methods">Cacheable Methods</a></h3>
    1360       <p id="rfc.section.5.2.3.p.1">Request methods are considered "<dfn id="cacheable">cacheable</dfn>" if it is possible and useful to answer a current client request with a stored response from a prior request. GET and HEAD
     1348      <h3 id="rfc.section.4.2.3"><a href="#rfc.section.4.2.3">4.2.3</a>&nbsp;<a id="cacheable.methods" href="#cacheable.methods">Cacheable Methods</a></h3>
     1349      <p id="rfc.section.4.2.3.p.1">Request methods are considered "<dfn id="cacheable">cacheable</dfn>" if it is possible and useful to answer a current client request with a stored response from a prior request. GET and HEAD
    13611350         are defined to be cacheable. In general, safe methods that do not depend on a current or authoritative response are cacheable,
    13621351         though the overwhelming majority of caches only support GET and HEAD. HTTP requirements for cache behavior and cacheable responses
    13631352         are defined in <a href="#Part6" id="rfc.xref.Part6.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>.
    13641353      </p>
    1365       <h2 id="rfc.section.5.3"><a href="#rfc.section.5.3">5.3</a>&nbsp;<a id="method.definitions" href="#method.definitions">Method Definitions</a></h2>
    1366       <h3 id="rfc.section.5.3.1"><a href="#rfc.section.5.3.1">5.3.1</a>&nbsp;<a id="GET" href="#GET">GET</a></h3>
     1354      <h2 id="rfc.section.4.3"><a href="#rfc.section.4.3">4.3</a>&nbsp;<a id="method.definitions" href="#method.definitions">Method Definitions</a></h2>
     1355      <h3 id="rfc.section.4.3.1"><a href="#rfc.section.4.3.1">4.3.1</a>&nbsp;<a id="GET" href="#GET">GET</a></h3>
    13671356      <div id="rfc.iref.g.6"></div>
    1368       <p id="rfc.section.5.3.1.p.1">The GET method requests transfer of a current representation of the target resource.</p>
    1369       <p id="rfc.section.5.3.1.p.2">If the target resource is a data-producing process, it is the produced data which shall be returned as the representation
     1357      <p id="rfc.section.4.3.1.p.1">The GET method requests transfer of a current representation of the target resource.</p>
     1358      <p id="rfc.section.4.3.1.p.2">If the target resource is a data-producing process, it is the produced data which shall be returned as the representation
    13701359         in the response and not the source text of the process, unless that text happens to be the output of the process.
    13711360      </p>
    1372       <p id="rfc.section.5.3.1.p.3">The semantics of the GET method change to a "conditional GET" if the request message includes an <a href="p4-conditional.html#header.if-modified-since" class="smpl">If-Modified-Since</a>, <a href="p4-conditional.html#header.if-unmodified-since" class="smpl">If-Unmodified-Since</a>, <a href="p4-conditional.html#header.if-match" class="smpl">If-Match</a>, <a href="p4-conditional.html#header.if-none-match" class="smpl">If-None-Match</a>, or <a href="p5-range.html#header.if-range" class="smpl">If-Range</a> header field (<a href="#Part4" id="rfc.xref.Part4.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>). A conditional GET requests that the representation be transferred only under the circumstances described by the conditional
     1361      <p id="rfc.section.4.3.1.p.3">The semantics of the GET method change to a "conditional GET" if the request message includes an <a href="p4-conditional.html#header.if-modified-since" class="smpl">If-Modified-Since</a>, <a href="p4-conditional.html#header.if-unmodified-since" class="smpl">If-Unmodified-Since</a>, <a href="p4-conditional.html#header.if-match" class="smpl">If-Match</a>, <a href="p4-conditional.html#header.if-none-match" class="smpl">If-None-Match</a>, or <a href="p5-range.html#header.if-range" class="smpl">If-Range</a> header field (<a href="#Part4" id="rfc.xref.Part4.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>). A conditional GET requests that the representation be transferred only under the circumstances described by the conditional
    13731362         header field(s). The conditional GET request is intended to reduce unnecessary network usage by allowing cached representations
    13741363         to be refreshed without requiring multiple requests or transferring data already held by the client.
    13751364      </p>
    1376       <p id="rfc.section.5.3.1.p.4">The semantics of the GET method change to a "partial GET" if the request message includes a <a href="p5-range.html#range.retrieval.requests" class="smpl">Range</a> header field (<a href="#Part5" id="rfc.xref.Part5.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a>). A partial GET requests that only part of the representation be transferred, as described in <a href="p5-range.html#header.range" title="Range">Section 5.4</a> of <a href="#Part5" id="rfc.xref.Part5.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a>. The partial GET request is intended to reduce unnecessary network usage by allowing partially-retrieved representations
     1365      <p id="rfc.section.4.3.1.p.4">The semantics of the GET method change to a "partial GET" if the request message includes a <a href="p5-range.html#range.retrieval.requests" class="smpl">Range</a> header field (<a href="#Part5" id="rfc.xref.Part5.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a>). A partial GET requests that only part of the representation be transferred, as described in <a href="p5-range.html#header.range" title="Range">Section 5.4</a> of <a href="#Part5" id="rfc.xref.Part5.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a>. The partial GET request is intended to reduce unnecessary network usage by allowing partially-retrieved representations
    13771366         to be completed without transferring data already held by the client.
    13781367      </p>
    1379       <p id="rfc.section.5.3.1.p.5">Bodies on GET requests have no defined semantics. Note that sending a body on a GET request might cause some existing implementations
     1368      <p id="rfc.section.4.3.1.p.5">Bodies on GET requests have no defined semantics. Note that sending a body on a GET request might cause some existing implementations
    13801369         to reject the request.
    13811370      </p>
    1382       <p id="rfc.section.5.3.1.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.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
    1383       </p>
    1384       <p id="rfc.section.5.3.1.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.
    1385       </p>
    1386       <h3 id="rfc.section.5.3.2"><a href="#rfc.section.5.3.2">5.3.2</a>&nbsp;<a id="HEAD" href="#HEAD">HEAD</a></h3>
     1371      <p id="rfc.section.4.3.1.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.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
     1372      </p>
     1373      <p id="rfc.section.4.3.1.p.7">See <a href="#encoding.sensitive.information.in.uris" title="Encoding Sensitive Information in URIs">Section&nbsp;10.2</a> for security considerations when used for forms.
     1374      </p>
     1375      <h3 id="rfc.section.4.3.2"><a href="#rfc.section.4.3.2">4.3.2</a>&nbsp;<a id="HEAD" href="#HEAD">HEAD</a></h3>
    13871376      <div id="rfc.iref.h.1"></div>
    1388       <p id="rfc.section.5.3.2.p.1">The HEAD method is identical to GET except that the server <em class="bcp14">MUST NOT</em> return a message body in the response. The metadata contained in the HTTP header fields in response to a HEAD request <em class="bcp14">SHOULD</em> be identical to the information sent in response to a GET request. This method can be used for obtaining metadata about the
     1377      <p id="rfc.section.4.3.2.p.1">The HEAD method is identical to GET except that the server <em class="bcp14">MUST NOT</em> return a message body in the response. The metadata contained in the HTTP header fields in response to a HEAD request <em class="bcp14">SHOULD</em> be identical to the information sent in response to a GET request. This method can be used for obtaining metadata about the
    13891378         representation implied by the request without transferring the representation body. This method is often used for testing
    13901379         hypertext links for validity, accessibility, and recent modification.
    13911380      </p>
    1392       <p id="rfc.section.5.3.2.p.2">The response to a HEAD request is cacheable and <em class="bcp14">MAY</em> be used to satisfy a subsequent HEAD request. It also has potential side effects on previously stored responses to GET; see <a href="p6-cache.html#head.effects" title="Updating Caches with HEAD Responses">Section 5</a> of <a href="#Part6" id="rfc.xref.Part6.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>.
    1393       </p>
    1394       <p id="rfc.section.5.3.2.p.3">Bodies on HEAD requests have no defined semantics. Note that sending a body on a HEAD request might cause some existing implementations
     1381      <p id="rfc.section.4.3.2.p.2">The response to a HEAD request is cacheable and <em class="bcp14">MAY</em> be used to satisfy a subsequent HEAD request. It also has potential side effects on previously stored responses to GET; see <a href="p6-cache.html#head.effects" title="Updating Caches with HEAD Responses">Section 5</a> of <a href="#Part6" id="rfc.xref.Part6.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>.
     1382      </p>
     1383      <p id="rfc.section.4.3.2.p.3">Bodies on HEAD requests have no defined semantics. Note that sending a body on a HEAD request might cause some existing implementations
    13951384         to reject the request.
    13961385      </p>
    13971386      <div id="rfc.iref.p.2"></div>
    1398       <h3 id="rfc.section.5.3.3"><a href="#rfc.section.5.3.3">5.3.3</a>&nbsp;<a id="POST" href="#POST">POST</a></h3>
    1399       <p id="rfc.section.5.3.3.p.1">The POST method requests that the origin server accept the representation enclosed in the request as data to be processed
     1387      <h3 id="rfc.section.4.3.3"><a href="#rfc.section.4.3.3">4.3.3</a>&nbsp;<a id="POST" href="#POST">POST</a></h3>
     1388      <p id="rfc.section.4.3.3.p.1">The POST method requests that the origin server accept the representation enclosed in the request as data to be processed
    14001389         by the target resource. POST is designed to allow a uniform method to cover the following functions:
    14011390      </p>
     
    14061395         <li>Extending a database through an append operation.</li>
    14071396      </ul>
    1408       <p id="rfc.section.5.3.3.p.2">The actual function performed by the POST method is determined by the server and is usually dependent on the effective request
     1397      <p id="rfc.section.4.3.3.p.2">The actual function performed by the POST method is determined by the server and is usually dependent on the effective request
    14091398         URI.
    14101399      </p>
    1411       <p id="rfc.section.5.3.3.p.3">The action performed by the POST method might not result in a resource that can be identified by a URI. In this case, either <a href="#status.200" class="smpl">200 (OK)</a> or <a href="#status.204" class="smpl">204 (No Content)</a> is the appropriate response status code, depending on whether or not the response includes a representation that describes
     1400      <p id="rfc.section.4.3.3.p.3">The action performed by the POST method might not result in a resource that can be identified by a URI. In this case, either <a href="#status.200" class="smpl">200 (OK)</a> or <a href="#status.204" class="smpl">204 (No Content)</a> is the appropriate response status code, depending on whether or not the response includes a representation that describes
    14121401         the result.
    14131402      </p>
    1414       <p id="rfc.section.5.3.3.p.4">If a resource has been created on the origin server, the response <em class="bcp14">SHOULD</em> be <a href="#status.201" class="smpl">201 (Created)</a> and contain a representation which describes the status of the request and refers to the new resource, and a <a href="#header.location" class="smpl">Location</a> header field (see <a href="#header.location" id="rfc.xref.header.location.1" title="Location">Section&nbsp;8.1.1</a>).
    1415       </p>
    1416       <p id="rfc.section.5.3.3.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 4.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>). A cached POST response with a <a href="#header.content-location" class="smpl">Content-Location</a> header field (see <a href="#header.content-location" id="rfc.xref.header.content-location.2" title="Content-Location">Section&nbsp;3.2.4</a>) whose value is the effective Request URI <em class="bcp14">MAY</em> be used to satisfy subsequent GET and HEAD requests.
    1417       </p>
    1418       <p id="rfc.section.5.3.3.p.6">Note that POST caching is not widely implemented. However, the <a href="#status.303" class="smpl">303 (See Other)</a> response can be used to direct the user agent to retrieve a cacheable representation of the resource.
    1419       </p>
    1420       <h3 id="rfc.section.5.3.4"><a href="#rfc.section.5.3.4">5.3.4</a>&nbsp;<a id="PUT" href="#PUT">PUT</a></h3>
     1403      <p id="rfc.section.4.3.3.p.4">If a resource has been created on the origin server, the response <em class="bcp14">SHOULD</em> be <a href="#status.201" class="smpl">201 (Created)</a> and contain a representation which describes the status of the request and refers to the new resource, and a <a href="#header.location" class="smpl">Location</a> header field (see <a href="#header.location" id="rfc.xref.header.location.1" title="Location">Section&nbsp;7.1.1</a>).
     1404      </p>
     1405      <p id="rfc.section.4.3.3.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 4.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>). A cached POST response with a <a href="#header.content-location" class="smpl">Content-Location</a> header field (see <a href="#header.content-location" id="rfc.xref.header.content-location.2" title="Content-Location">Section&nbsp;3.3.4</a>) whose value is the effective Request URI <em class="bcp14">MAY</em> be used to satisfy subsequent GET and HEAD requests.
     1406      </p>
     1407      <p id="rfc.section.4.3.3.p.6">Note that POST caching is not widely implemented. However, the <a href="#status.303" class="smpl">303 (See Other)</a> response can be used to direct the user agent to retrieve a cacheable representation of the resource.
     1408      </p>
     1409      <h3 id="rfc.section.4.3.4"><a href="#rfc.section.4.3.4">4.3.4</a>&nbsp;<a id="PUT" href="#PUT">PUT</a></h3>
    14211410      <div id="rfc.iref.p.3"></div>
    1422       <p id="rfc.section.5.3.4.p.1">The PUT method requests that the state of the target resource be created or replaced with the state defined by the representation
     1411      <p id="rfc.section.4.3.4.p.1">The PUT method requests that the state of the target resource be created or replaced with the state defined by the representation
    14231412         enclosed in the request message payload. A successful PUT of a given representation would suggest that a subsequent GET on
    14241413         that same target resource will result in an equivalent representation being returned in a <a href="#status.200" class="smpl">200 (OK)</a> response. However, there is no guarantee that such a state change will be observable, since the target resource might be acted
     
    14271416         by the origin server.
    14281417      </p>
    1429       <p id="rfc.section.5.3.4.p.2">If the target resource does not have a current representation and the PUT successfully creates one, then the origin server <em class="bcp14">MUST</em> inform the user agent by sending a <a href="#status.201" class="smpl">201 (Created)</a> response. If the target resource does have a current representation and that representation is successfully modified in accordance
     1418      <p id="rfc.section.4.3.4.p.2">If the target resource does not have a current representation and the PUT successfully creates one, then the origin server <em class="bcp14">MUST</em> inform the user agent by sending a <a href="#status.201" class="smpl">201 (Created)</a> response. If the target resource does have a current representation and that representation is successfully modified in accordance
    14301419         with the state of the enclosed representation, then either a <a href="#status.200" class="smpl">200 (OK)</a> or <a href="#status.204" class="smpl">204 (No Content)</a> response <em class="bcp14">SHOULD</em> be sent to indicate successful completion of the request.
    14311420      </p>
    1432       <p id="rfc.section.5.3.4.p.3">Unrecognized header fields <em class="bcp14">SHOULD</em> be ignored (i.e., not saved as part of the resource state).
    1433       </p>
    1434       <p id="rfc.section.5.3.4.p.4">An origin server <em class="bcp14">SHOULD</em> verify that the PUT representation is consistent with any constraints which the server has for the target resource that cannot
     1421      <p id="rfc.section.4.3.4.p.3">Unrecognized header fields <em class="bcp14">SHOULD</em> be ignored (i.e., not saved as part of the resource state).
     1422      </p>
     1423      <p id="rfc.section.4.3.4.p.4">An origin server <em class="bcp14">SHOULD</em> verify that the PUT representation is consistent with any constraints which the server has for the target resource that cannot
    14351424         or will not be changed by the PUT. This is particularly important when the origin server uses internal configuration information
    14361425         related to the URI in order to set the values for representation metadata on GET responses. When a PUT representation is inconsistent
     
    14381427         appropriate error message containing sufficient information to explain why the representation is unsuitable. The <a href="#status.409" class="smpl">409 (Conflict)</a> or <a href="#status.415" class="smpl">415 (Unsupported Media Type)</a> status codes are suggested, with the latter being specific to constraints on <a href="#header.content-type" class="smpl">Content-Type</a> values.
    14391428      </p>
    1440       <p id="rfc.section.5.3.4.p.5">For example, if the target resource is configured to always have a <a href="#header.content-type" class="smpl">Content-Type</a> of "text/html" and the representation being PUT has a Content-Type of "image/jpeg", then the origin server <em class="bcp14">SHOULD</em> do one of:
     1429      <p id="rfc.section.4.3.4.p.5">For example, if the target resource is configured to always have a <a href="#header.content-type" class="smpl">Content-Type</a> of "text/html" and the representation being PUT has a Content-Type of "image/jpeg", then the origin server <em class="bcp14">SHOULD</em> do one of:
    14411430      </p>
    14421431      <ol class="la">
     
    14491438         </li>
    14501439      </ol>
    1451       <p id="rfc.section.5.3.4.p.6">HTTP does not define exactly how a PUT method affects the state of an origin server beyond what can be expressed by the intent
     1440      <p id="rfc.section.4.3.4.p.6">HTTP does not define exactly how a PUT method affects the state of an origin server beyond what can be expressed by the intent
    14521441         of the user agent request and the semantics of the origin server response. It does not define what a resource might be, in
    14531442         any sense of that word, beyond the interface provided via HTTP. It does not define how resource state is "stored", nor how
     
    14561445         the server.
    14571446      </p>
    1458       <p id="rfc.section.5.3.4.p.7">The fundamental difference between the POST and PUT methods is highlighted by the different intent for the target resource.
     1447      <p id="rfc.section.4.3.4.p.7">The fundamental difference between the POST and PUT methods is highlighted by the different intent for the target resource.
    14591448         The target resource in a POST request is intended to handle the enclosed representation as a data-accepting process, such
    14601449         as for a gateway to some other protocol or a document that accepts annotations. In contrast, the target resource in a PUT
     
    14621451         and visible to intermediaries, even though the exact effect is only known by the origin server.
    14631452      </p>
    1464       <p id="rfc.section.5.3.4.p.8">Proper interpretation of a PUT request presumes that the user agent knows what target resource is desired. A service that
     1453      <p id="rfc.section.4.3.4.p.8">Proper interpretation of a PUT request presumes that the user agent knows what target resource is desired. A service that
    14651454         is intended to select a proper URI on behalf of the client, after receiving a state-changing request, <em class="bcp14">SHOULD</em> be implemented using the POST method rather than PUT. If the origin server will not make the requested PUT state change to
    14661455         the target resource and instead wishes to have it applied to a different resource, such as when the resource has been moved
    14671456         to a different URI, then the origin server <em class="bcp14">MUST</em> send a <a href="#status.301" class="smpl">301 (Moved Permanently)</a> response; the user agent <em class="bcp14">MAY</em> then make its own decision regarding whether or not to redirect the request.
    14681457      </p>
    1469       <p id="rfc.section.5.3.4.p.9">A PUT request applied to the target resource <em class="bcp14">MAY</em> have side-effects on other resources. For example, an article might have a URI for identifying "the current version" (a resource)
     1458      <p id="rfc.section.4.3.4.p.9">A PUT request applied to the target resource <em class="bcp14">MAY</em> have side-effects on other resources. For example, an article might have a URI for identifying "the current version" (a resource)
    14701459         which is separate from the URIs identifying each particular version (different resources that at one point shared the same
    14711460         state as the current version resource). A successful PUT request on "the current version" URI might therefore create a new
     
    14731462         the related resources.
    14741463      </p>
    1475       <p id="rfc.section.5.3.4.p.10">An origin server <em class="bcp14">SHOULD</em> reject any PUT request that contains a <a href="p5-range.html#header.content-range" class="smpl">Content-Range</a> header field (<a href="p5-range.html#header.content-range" title="Content-Range">Section 5.2</a> of <a href="#Part5" id="rfc.xref.Part5.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a>), since it might be misinterpreted as partial content (or might be partial content that is being mistakenly PUT as a full
     1464      <p id="rfc.section.4.3.4.p.10">An origin server <em class="bcp14">SHOULD</em> reject any PUT request that contains a <a href="p5-range.html#header.content-range" class="smpl">Content-Range</a> header field (<a href="p5-range.html#header.content-range" title="Content-Range">Section 5.2</a> of <a href="#Part5" id="rfc.xref.Part5.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a>), since it might be misinterpreted as partial content (or might be partial content that is being mistakenly PUT as a full
    14761465         representation). Partial content updates are possible by targeting a separately identified resource with state that overlaps
    14771466         a portion of the larger resource, or by using a different method that has been specifically defined for partial updates (for
    14781467         example, the PATCH method defined in <a href="#RFC5789" id="rfc.xref.RFC5789.1"><cite title="PATCH Method for HTTP">[RFC5789]</cite></a>).
    14791468      </p>
    1480       <p id="rfc.section.5.3.4.p.11">Responses to the PUT method are not cacheable. If a PUT request passes through a cache that has one or more stored responses
     1469      <p id="rfc.section.4.3.4.p.11">Responses to the PUT method are not cacheable. If a PUT request passes through a cache that has one or more stored responses
    14811470         for the effective request URI, those stored responses will be invalidated (see <a href="p6-cache.html#invalidation.after.updates.or.deletions" title="Request Methods that Invalidate">Section 6</a> of <a href="#Part6" id="rfc.xref.Part6.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
    14821471      </p>
    1483       <h3 id="rfc.section.5.3.5"><a href="#rfc.section.5.3.5">5.3.5</a>&nbsp;<a id="DELETE" href="#DELETE">DELETE</a></h3>
     1472      <h3 id="rfc.section.4.3.5"><a href="#rfc.section.4.3.5">4.3.5</a>&nbsp;<a id="DELETE" href="#DELETE">DELETE</a></h3>
    14841473      <div id="rfc.iref.d.1"></div>
    1485       <p id="rfc.section.5.3.5.p.1">The DELETE method requests that the origin server delete the target resource. This method <em class="bcp14">MAY</em> be overridden by human intervention (or other means) on the origin server. The client cannot be guaranteed that the operation
     1474      <p id="rfc.section.4.3.5.p.1">The DELETE method requests that the origin server delete the target resource. This method <em class="bcp14">MAY</em> be overridden by human intervention (or other means) on the origin server. The client cannot be guaranteed that the operation
    14861475         has been carried out, even if the status code returned from the origin server indicates that the action has been completed
    14871476         successfully. However, the server <em class="bcp14">SHOULD NOT</em> indicate success unless, at the time the response is given, it intends to delete the resource or move it to an inaccessible
    14881477         location.
    14891478      </p>
    1490       <p id="rfc.section.5.3.5.p.2">A successful response <em class="bcp14">SHOULD</em> be <a href="#status.200" class="smpl">200 (OK)</a> if the response includes a representation describing the status, <a href="#status.202" class="smpl">202 (Accepted)</a> if the action has not yet been enacted, or <a href="#status.204" class="smpl">204 (No Content)</a> if the action has been enacted but the response does not include a representation.
    1491       </p>
    1492       <p id="rfc.section.5.3.5.p.3">Bodies on DELETE requests have no defined semantics. Note that sending a body on a DELETE request might cause some existing
     1479      <p id="rfc.section.4.3.5.p.2">A successful response <em class="bcp14">SHOULD</em> be <a href="#status.200" class="smpl">200 (OK)</a> if the response includes a representation describing the status, <a href="#status.202" class="smpl">202 (Accepted)</a> if the action has not yet been enacted, or <a href="#status.204" class="smpl">204 (No Content)</a> if the action has been enacted but the response does not include a representation.
     1480      </p>
     1481      <p id="rfc.section.4.3.5.p.3">Bodies on DELETE requests have no defined semantics. Note that sending a body on a DELETE request might cause some existing
    14931482         implementations to reject the request.
    14941483      </p>
    1495       <p id="rfc.section.5.3.5.p.4">Responses to the DELETE method are not cacheable. If a DELETE request passes through a cache that has one or more stored responses
     1484      <p id="rfc.section.4.3.5.p.4">Responses to the DELETE method are not cacheable. If a DELETE request passes through a cache that has one or more stored responses
    14961485         for the effective request URI, those stored responses will be invalidated (see <a href="p6-cache.html#invalidation.after.updates.or.deletions" title="Request Methods that Invalidate">Section 6</a> of <a href="#Part6" id="rfc.xref.Part6.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
    14971486      </p>
    14981487      <div id="rfc.iref.c.7"></div>
    1499       <h3 id="rfc.section.5.3.6"><a href="#rfc.section.5.3.6">5.3.6</a>&nbsp;<a id="CONNECT" href="#CONNECT">CONNECT</a></h3>
    1500       <p id="rfc.section.5.3.6.p.1">The CONNECT method requests that the proxy establish a tunnel to the request-target and, if successful, thereafter restrict
     1488      <h3 id="rfc.section.4.3.6"><a href="#rfc.section.4.3.6">4.3.6</a>&nbsp;<a id="CONNECT" href="#CONNECT">CONNECT</a></h3>
     1489      <p id="rfc.section.4.3.6.p.1">The CONNECT method requests that the proxy establish a tunnel to the request-target and, if successful, thereafter restrict
    15011490         its behavior to blind forwarding of packets until the connection is closed.
    15021491      </p>
    1503       <p id="rfc.section.5.3.6.p.2">When using CONNECT, the request-target <em class="bcp14">MUST</em> use the authority form (<a href="p1-messaging.html#request-target" title="Request Target">Section 5.3</a> of <a href="#Part1" id="rfc.xref.Part1.11"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>); i.e., the request-target consists of only the host name and port number of the tunnel destination, separated by a colon.
     1492      <p id="rfc.section.4.3.6.p.2">When using CONNECT, the request-target <em class="bcp14">MUST</em> use the authority form (<a href="p1-messaging.html#request-target" title="Request Target">Section 5.3</a> of <a href="#Part1" id="rfc.xref.Part1.11"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>); i.e., the request-target consists of only the host name and port number of the tunnel destination, separated by a colon.
    15041493         For example,
    15051494      </p>
     
    15071496Host: server.example.com:80
    15081497
    1509 </pre><p id="rfc.section.5.3.6.p.4">Any <a href="#status.2xx" class="smpl">2xx (Successful)</a> response to a CONNECT request indicates that the proxy has established a connection to the requested host and port, and has
     1498</pre><p id="rfc.section.4.3.6.p.4">Any <a href="#status.2xx" class="smpl">2xx (Successful)</a> response to a CONNECT request indicates that the proxy has established a connection to the requested host and port, and has
    15101499         switched to tunneling the current connection to that server connection. The tunneled data from the server begins immediately
    15111500         after the blank line that concludes the successful response's header block.
    15121501      </p>
    1513       <p id="rfc.section.5.3.6.p.5">A server <em class="bcp14">SHOULD NOT</em> send any <a href="p1-messaging.html#header.transfer-encoding" class="smpl">Transfer-Encoding</a> or <a href="p1-messaging.html#header.content-length" class="smpl">Content-Length</a> header fields in a successful response. A client <em class="bcp14">MUST</em> ignore any Content-Length or Transfer-Encoding header fields received in a successful response.
    1514       </p>
    1515       <p id="rfc.section.5.3.6.p.6">Any response other than a successful response indicates that the tunnel has not yet been formed and that the connection remains
     1502      <p id="rfc.section.4.3.6.p.5">A server <em class="bcp14">SHOULD NOT</em> send any <a href="p1-messaging.html#header.transfer-encoding" class="smpl">Transfer-Encoding</a> or <a href="p1-messaging.html#header.content-length" class="smpl">Content-Length</a> header fields in a successful response. A client <em class="bcp14">MUST</em> ignore any Content-Length or Transfer-Encoding header fields received in a successful response.
     1503      </p>
     1504      <p id="rfc.section.4.3.6.p.6">Any response other than a successful response indicates that the tunnel has not yet been formed and that the connection remains
    15161505         governed by HTTP.
    15171506      </p>
    1518       <p id="rfc.section.5.3.6.p.7">Proxy authentication might be used to establish the authority to create a tunnel:</p>
     1507      <p id="rfc.section.4.3.6.p.7">Proxy authentication might be used to establish the authority to create a tunnel:</p>
    15191508      <div id="rfc.figure.u.12"></div><pre class="text2">CONNECT server.example.com:80 HTTP/1.1
    15201509Host: server.example.com:80
    15211510Proxy-Authorization: basic aGVsbG86d29ybGQ=
    15221511
    1523 </pre><p id="rfc.section.5.3.6.p.9">A message body on a CONNECT request has no defined semantics. Sending a body on a CONNECT request might cause existing implementations
     1512</pre><p id="rfc.section.4.3.6.p.9">A message body on a CONNECT request has no defined semantics. Sending a body on a CONNECT request might cause existing implementations
    15241513         to reject the request.
    15251514      </p>
    1526       <p id="rfc.section.5.3.6.p.10">Similar to a pipelined HTTP/1.1 request, data to be tunneled from client to server <em class="bcp14">MAY</em> be sent immediately after the request (before a response is received). The usual caveats also apply: data can be discarded
     1515      <p id="rfc.section.4.3.6.p.10">Similar to a pipelined HTTP/1.1 request, data to be tunneled from client to server <em class="bcp14">MAY</em> be sent immediately after the request (before a response is received). The usual caveats also apply: data can be discarded
    15271516         if the eventual response is negative, and the connection can be reset with no response if more than one TCP segment is outstanding.
    15281517      </p>
    1529       <p id="rfc.section.5.3.6.p.11">It might be the case that the proxy itself can only reach the requested origin server through another proxy. In this case,
     1518      <p id="rfc.section.4.3.6.p.11">It might be the case that the proxy itself can only reach the requested origin server through another proxy. In this case,
    15301519         the first proxy <em class="bcp14">SHOULD</em> make a CONNECT request of that next proxy, requesting a tunnel to the authority. A proxy <em class="bcp14">MUST NOT</em> respond with any <a href="#status.2xx" class="smpl">2xx</a> status code unless it has either a direct or tunnel connection established to the authority.
    15311520      </p>
    1532       <p id="rfc.section.5.3.6.p.12">If at any point either one of the peers gets disconnected, any outstanding data that came from that peer will be passed to
     1521      <p id="rfc.section.4.3.6.p.12">If at any point either one of the peers gets disconnected, any outstanding data that came from that peer will be passed to
    15331522         the other one, and after that also the other connection will be terminated by the proxy. If there is outstanding data to that
    15341523         peer undelivered, that data will be discarded.
    15351524      </p>
    1536       <p id="rfc.section.5.3.6.p.13">An origin server which receives a CONNECT request for itself <em class="bcp14">MAY</em> respond with a <a href="#status.2xx" class="smpl">2xx</a> status code to indicate that a connection is established. However, most origin servers do not implement CONNECT.
    1537       </p>
    1538       <h3 id="rfc.section.5.3.7"><a href="#rfc.section.5.3.7">5.3.7</a>&nbsp;<a id="OPTIONS" href="#OPTIONS">OPTIONS</a></h3>
     1525      <p id="rfc.section.4.3.6.p.13">An origin server which receives a CONNECT request for itself <em class="bcp14">MAY</em> respond with a <a href="#status.2xx" class="smpl">2xx</a> status code to indicate that a connection is established. However, most origin servers do not implement CONNECT.
     1526      </p>
     1527      <h3 id="rfc.section.4.3.7"><a href="#rfc.section.4.3.7">4.3.7</a>&nbsp;<a id="OPTIONS" href="#OPTIONS">OPTIONS</a></h3>
    15391528      <div id="rfc.iref.o.1"></div>
    1540       <p id="rfc.section.5.3.7.p.1">The OPTIONS method requests information about the communication options available on the request/response chain identified
     1529      <p id="rfc.section.4.3.7.p.1">The OPTIONS method requests information about the communication options available on the request/response chain identified
    15411530         by the effective request URI. This method allows a client to determine the options and/or requirements associated with a resource,
    15421531         or the capabilities of a server, without implying a resource action or initiating a resource retrieval.
    15431532      </p>
    1544       <p id="rfc.section.5.3.7.p.2">Responses to the OPTIONS method are not cacheable.</p>
    1545       <p id="rfc.section.5.3.7.p.3">If the OPTIONS request includes a message body (as indicated by the presence of <a href="p1-messaging.html#header.content-length" class="smpl">Content-Length</a> or <a href="p1-messaging.html#header.transfer-encoding" class="smpl">Transfer-Encoding</a>), then the media type <em class="bcp14">MUST</em> be indicated by a <a href="#header.content-type" class="smpl">Content-Type</a> field. Although this specification does not define any use for such a body, future extensions to HTTP might use the OPTIONS
     1533      <p id="rfc.section.4.3.7.p.2">Responses to the OPTIONS method are not cacheable.</p>
     1534      <p id="rfc.section.4.3.7.p.3">If the OPTIONS request includes a message body (as indicated by the presence of <a href="p1-messaging.html#header.content-length" class="smpl">Content-Length</a> or <a href="p1-messaging.html#header.transfer-encoding" class="smpl">Transfer-Encoding</a>), then the media type <em class="bcp14">MUST</em> be indicated by a <a href="#header.content-type" class="smpl">Content-Type</a> field. Although this specification does not define any use for such a body, future extensions to HTTP might use the OPTIONS
    15461535         body to make more detailed queries on the server.
    15471536      </p>
    1548       <p id="rfc.section.5.3.7.p.4">If the request-target (<a href="p1-messaging.html#request-target" title="Request Target">Section 5.3</a> of <a href="#Part1" id="rfc.xref.Part1.12"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) is an asterisk ("*"), the OPTIONS request is intended to apply to the server in general rather than to a specific resource.
     1537      <p id="rfc.section.4.3.7.p.4">If the request-target (<a href="p1-messaging.html#request-target" title="Request Target">Section 5.3</a> of <a href="#Part1" id="rfc.xref.Part1.12"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) is an asterisk ("*"), the OPTIONS request is intended to apply to the server in general rather than to a specific resource.
    15491538         Since a server's communication options typically depend on the resource, the "*" request is only useful as a "ping" or "no-op"
    15501539         type of method; it does nothing beyond allowing the client to test the capabilities of the server. For example, this can be
    15511540         used to test a proxy for HTTP/1.1 conformance (or lack thereof).
    15521541      </p>
    1553       <p id="rfc.section.5.3.7.p.5">If the request-target is not an asterisk, the OPTIONS request applies only to the options that are available when communicating
     1542      <p id="rfc.section.4.3.7.p.5">If the request-target is not an asterisk, the OPTIONS request applies only to the options that are available when communicating
    15541543         with that resource.
    15551544      </p>
    1556       <p id="rfc.section.5.3.7.p.6">A <a href="#status.200" class="smpl">200 (OK)</a> response <em class="bcp14">SHOULD</em> include any header fields that indicate optional features implemented by the server and applicable to that resource (e.g., <a href="#header.allow" class="smpl">Allow</a>), possibly including extensions not defined by this specification. The response body, if any, <em class="bcp14">SHOULD</em> also include information about the communication options. The format for such a body is not defined by this specification,
     1545      <p id="rfc.section.4.3.7.p.6">A <a href="#status.200" class="smpl">200 (OK)</a> response <em class="bcp14">SHOULD</em> include any header fields that indicate optional features implemented by the server and applicable to that resource (e.g., <a href="#header.allow" class="smpl">Allow</a>), possibly including extensions not defined by this specification. The response body, if any, <em class="bcp14">SHOULD</em> also include information about the communication options. The format for such a body is not defined by this specification,
    15571546         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 <a href="p1-messaging.html#header.content-length" class="smpl">Content-Length</a> field with a field-value of "0".
    15581547      </p>
    1559       <p id="rfc.section.5.3.7.p.7">The <a href="#header.max-forwards" class="smpl">Max-Forwards</a> 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;6.1.1</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.
    1560       </p>
    1561       <h3 id="rfc.section.5.3.8"><a href="#rfc.section.5.3.8">5.3.8</a>&nbsp;<a id="TRACE" href="#TRACE">TRACE</a></h3>
     1548      <p id="rfc.section.4.3.7.p.7">The <a href="#header.max-forwards" class="smpl">Max-Forwards</a> 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;5.1.1</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.
     1549      </p>
     1550      <h3 id="rfc.section.4.3.8"><a href="#rfc.section.4.3.8">4.3.8</a>&nbsp;<a id="TRACE" href="#TRACE">TRACE</a></h3>
    15621551      <div id="rfc.iref.t.1"></div>
    1563       <p id="rfc.section.5.3.8.p.1">The TRACE method requests a remote, application-level 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 <a href="#status.200" class="smpl">200 (OK)</a> response. The final recipient is either the origin server or the first proxy to receive a <a href="#header.max-forwards" class="smpl">Max-Forwards</a> 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;6.1.1</a>). A TRACE request <em class="bcp14">MUST NOT</em> include a message body.
    1564       </p>
    1565       <p id="rfc.section.5.3.8.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
     1552      <p id="rfc.section.4.3.8.p.1">The TRACE method requests a remote, application-level 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 <a href="#status.200" class="smpl">200 (OK)</a> response. The final recipient is either the origin server or the first proxy to receive a <a href="#header.max-forwards" class="smpl">Max-Forwards</a> 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;5.1.1</a>). A TRACE request <em class="bcp14">MUST NOT</em> include a message body.
     1553      </p>
     1554      <p id="rfc.section.4.3.8.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
    15661555         or diagnostic information. The value of the <a href="p1-messaging.html#header.via" class="smpl">Via</a> header field (<a href="p1-messaging.html#header.via" title="Via">Section 5.7</a> of <a href="#Part1" id="rfc.xref.Part1.13"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) is of particular interest, since it acts as a trace of the request chain. Use of the <a href="#header.max-forwards" class="smpl">Max-Forwards</a> header field allows the client to limit the length of the request chain, which is useful for testing a chain of proxies forwarding
    15671556         messages in an infinite loop.
    15681557      </p>
    1569       <p id="rfc.section.5.3.8.p.3">If the request is valid, the response <em class="bcp14">SHOULD</em> have a <a href="#header.content-type" class="smpl">Content-Type</a> of "message/http" (see <a href="p1-messaging.html#internet.media.type.message.http" title="Internet Media Type message/http">Section 7.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.14"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) and contain a message body that encloses a copy of the entire request message. Responses to the TRACE method are not cacheable.
    1570       </p>
    1571       <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="request.header.fields" href="#request.header.fields">Request Header Fields</a></h1>
    1572       <p id="rfc.section.6.p.1">A client sends request header fields to provide more information about the request context, make the request conditional based
     1558      <p id="rfc.section.4.3.8.p.3">If the request is valid, the response <em class="bcp14">SHOULD</em> have a <a href="#header.content-type" class="smpl">Content-Type</a> of "message/http" (see <a href="p1-messaging.html#internet.media.type.message.http" title="Internet Media Type message/http">Section 7.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.14"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) and contain a message body that encloses a copy of the entire request message. Responses to the TRACE method are not cacheable.
     1559      </p>
     1560      <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a id="request.header.fields" href="#request.header.fields">Request Header Fields</a></h1>
     1561      <p id="rfc.section.5.p.1">A client sends request header fields to provide more information about the request context, make the request conditional based
    15731562         on the target resource state, suggest preferred formats for the response, supply authentication credentials, or modify the
    15741563         expected request processing. These fields act as request modifiers, similar to the parameters on a programming language method
    15751564         invocation.
    15761565      </p>
    1577       <h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a>&nbsp;<a id="request.controls" href="#request.controls">Controls</a></h2>
    1578       <p id="rfc.section.6.1.p.1">Controls are request header fields that direct specific handling of the request.</p>
     1566      <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;<a id="request.controls" href="#request.controls">Controls</a></h2>
     1567      <p id="rfc.section.5.1.p.1">Controls are request header fields that direct specific handling of the request.</p>
    15791568      <div id="rfc.table.u.4">
    15801569         <table class="tt full left" cellpadding="3" cellspacing="0">
     
    15921581               <tr>
    15931582                  <td class="left">Max-Forwards</td>
    1594                   <td class="left"><a href="#header.max-forwards" id="rfc.xref.header.max-forwards.3" title="Max-Forwards">Section&nbsp;6.1.1</a></td>
     1583                  <td class="left"><a href="#header.max-forwards" id="rfc.xref.header.max-forwards.3" title="Max-Forwards">Section&nbsp;5.1.1</a></td>
    15951584               </tr>
    15961585               <tr>
    15971586                  <td class="left">Expect</td>
    1598                   <td class="left"><a href="#header.expect" id="rfc.xref.header.expect.1" title="Expect">Section&nbsp;6.1.2</a></td>
     1587                  <td class="left"><a href="#header.expect" id="rfc.xref.header.expect.1" title="Expect">Section&nbsp;5.1.2</a></td>
    15991588               </tr>
    16001589               <tr>
     
    16061595      </div>
    16071596      <div id="rfc.iref.m.1"></div>
    1608       <h3 id="rfc.section.6.1.1"><a href="#rfc.section.6.1.1">6.1.1</a>&nbsp;<a id="header.max-forwards" href="#header.max-forwards">Max-Forwards</a></h3>
    1609       <p id="rfc.section.6.1.1.p.1">The "Max-Forwards" header field provides a mechanism with the TRACE (<a href="#TRACE" id="rfc.xref.TRACE.2" title="TRACE">Section&nbsp;5.3.8</a>) and OPTIONS (<a href="#OPTIONS" id="rfc.xref.OPTIONS.2" title="OPTIONS">Section&nbsp;5.3.7</a>) methods to limit the number of times that the request is forwarded by proxies. This can be useful when the client is attempting
     1597      <h3 id="rfc.section.5.1.1"><a href="#rfc.section.5.1.1">5.1.1</a>&nbsp;<a id="header.max-forwards" href="#header.max-forwards">Max-Forwards</a></h3>
     1598      <p id="rfc.section.5.1.1.p.1">The "Max-Forwards" header field provides a mechanism with the TRACE (<a href="#TRACE" id="rfc.xref.TRACE.2" title="TRACE">Section&nbsp;4.3.8</a>) and OPTIONS (<a href="#OPTIONS" id="rfc.xref.OPTIONS.2" title="OPTIONS">Section&nbsp;4.3.7</a>) methods to limit the number of times that the request is forwarded by proxies. This can be useful when the client is attempting
    16101599         to trace a request which appears to be failing or looping mid-chain.
    16111600      </p>
    16121601      <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.7"></span>  <a href="#header.max-forwards" class="smpl">Max-Forwards</a> = 1*<a href="#imported.abnf" class="smpl">DIGIT</a>
    1613 </pre><p id="rfc.section.6.1.1.p.3">The Max-Forwards value is a decimal integer indicating the remaining number of times this request message can be forwarded.</p>
    1614       <p id="rfc.section.6.1.1.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).
    1615       </p>
    1616       <p id="rfc.section.6.1.1.p.5">The Max-Forwards header field <em class="bcp14">MAY</em> be ignored for all other request methods.
     1602</pre><p id="rfc.section.5.1.1.p.3">The Max-Forwards value is a decimal integer indicating the remaining number of times this request message can be forwarded.</p>
     1603      <p id="rfc.section.5.1.1.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).
     1604      </p>
     1605      <p id="rfc.section.5.1.1.p.5">The Max-Forwards header field <em class="bcp14">MAY</em> be ignored for all other request methods.
    16171606      </p>
    16181607      <div id="rfc.iref.e.1"></div>
    1619       <h3 id="rfc.section.6.1.2"><a href="#rfc.section.6.1.2">6.1.2</a>&nbsp;<a id="header.expect" href="#header.expect">Expect</a></h3>
    1620       <p id="rfc.section.6.1.2.p.1">The "Expect" header field is used to indicate that particular server behaviors are required by the client.</p>
     1608      <h3 id="rfc.section.5.1.2"><a href="#rfc.section.5.1.2">5.1.2</a>&nbsp;<a id="header.expect" href="#header.expect">Expect</a></h3>
     1609      <p id="rfc.section.5.1.2.p.1">The "Expect" header field is used to indicate that particular server behaviors are required by the client.</p>
    16211610      <div id="rfc.figure.u.14"></div><pre class="inline"><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>  <a href="#header.expect" class="smpl">Expect</a>       = 1#<a href="#header.expect" class="smpl">expectation</a>
    16221611 
     
    16271616  <a href="#header.expect" class="smpl">expect-name</a>  = <a href="#imported.abnf" class="smpl">token</a>
    16281617  <a href="#header.expect" class="smpl">expect-value</a> = <a href="#imported.abnf" class="smpl">token</a> / <a href="#imported.abnf" class="smpl">quoted-string</a>
    1629 </pre><p id="rfc.section.6.1.2.p.3">If all received Expect header field(s) are syntactically valid but contain an expectation that the recipient does not understand
     1618</pre><p id="rfc.section.5.1.2.p.3">If all received Expect header field(s) are syntactically valid but contain an expectation that the recipient does not understand
    16301619         or cannot comply with, the recipient <em class="bcp14">MUST</em> respond with a <a href="#status.417" class="smpl">417 (Expectation Failed)</a> status code. A recipient of a syntactically invalid Expectation header field <em class="bcp14">MUST</em> respond with a <a href="#status.4xx" class="smpl">4xx</a> status code other than 417.
    16311620      </p>
    1632       <p id="rfc.section.6.1.2.p.4">The only expectation defined by this specification is:</p>
    1633       <p id="rfc.section.6.1.2.p.5"><span id="rfc.iref.32"></span><span id="rfc.iref.e.2"></span> 100-continue
     1621      <p id="rfc.section.5.1.2.p.4">The only expectation defined by this specification is:</p>
     1622      <p id="rfc.section.5.1.2.p.5"><span id="rfc.iref.32"></span><span id="rfc.iref.e.2"></span> 100-continue
    16341623      </p>
    16351624      <ul class="empty">
    16361625         <li>The "100-continue" expectation is defined below. It does not support any expect-params.</li>
    16371626      </ul>
    1638       <p id="rfc.section.6.1.2.p.6">Comparison is case-insensitive for names (expect-name), and case-sensitive for values (expect-value).</p>
    1639       <p id="rfc.section.6.1.2.p.7">The Expect mechanism is hop-by-hop: the above requirements apply to any server, including proxies. However, the Expect header
     1627      <p id="rfc.section.5.1.2.p.6">Comparison is case-insensitive for names (expect-name), and case-sensitive for values (expect-value).</p>
     1628      <p id="rfc.section.5.1.2.p.7">The Expect mechanism is hop-by-hop: the above requirements apply to any server, including proxies. However, the Expect header
    16401629         field itself is end-to-end; it <em class="bcp14">MUST</em> be forwarded if the request is forwarded.
    16411630      </p>
    1642       <p id="rfc.section.6.1.2.p.8">Many older HTTP/1.0 and HTTP/1.1 applications do not understand the Expect header field.</p>
    1643       <h4 id="rfc.section.6.1.2.1"><a href="#rfc.section.6.1.2.1">6.1.2.1</a>&nbsp;<a id="use.of.the.100.status" href="#use.of.the.100.status">Use of the 100 (Continue) Status</a></h4>
    1644       <p id="rfc.section.6.1.2.1.p.1">The purpose of the <a href="#status.100" class="smpl">100 (Continue)</a> status code (<a href="#status.100" id="rfc.xref.status.100.1" title="100 Continue">Section&nbsp;7.2.1</a>) is to allow a client that is sending a request message with a request body to determine if the origin server is willing
     1631      <p id="rfc.section.5.1.2.p.8">Many older HTTP/1.0 and HTTP/1.1 applications do not understand the Expect header field.</p>
     1632      <h4 id="rfc.section.5.1.2.1"><a href="#rfc.section.5.1.2.1">5.1.2.1</a>&nbsp;<a id="use.of.the.100.status" href="#use.of.the.100.status">Use of the 100 (Continue) Status</a></h4>
     1633      <p id="rfc.section.5.1.2.1.p.1">The purpose of the <a href="#status.100" class="smpl">100 (Continue)</a> status code (<a href="#status.100" id="rfc.xref.status.100.1" title="100 Continue">Section&nbsp;6.2.1</a>) is to allow a client that is sending a request message with a request body to determine if the origin server is willing
    16451634         to accept the request (based on the request header fields) before the client sends the request body. In some cases, it might
    16461635         either be inappropriate or highly inefficient for the client to send the body if the server will reject the message without
    16471636         looking at the body.
    16481637      </p>
    1649       <p id="rfc.section.6.1.2.1.p.2">Requirements for HTTP/1.1 clients: </p>
     1638      <p id="rfc.section.5.1.2.1.p.2">Requirements for HTTP/1.1 clients: </p>
    16501639      <ul>
    16511640         <li>If a client will wait for a <a href="#status.100" class="smpl">100 (Continue)</a> response before sending the request body, it <em class="bcp14">MUST</em> send an <a href="#header.expect" class="smpl">Expect</a> header field with the "100-continue" expectation.
     
    16541643         </li>
    16551644      </ul>
    1656       <p id="rfc.section.6.1.2.1.p.3">Because of the presence of older implementations, the protocol allows ambiguous situations in which a client might send "Expect:
     1645      <p id="rfc.section.5.1.2.1.p.3">Because of the presence of older implementations, the protocol allows ambiguous situations in which a client might send "Expect:
    16571646         100-continue" without receiving either a <a href="#status.417" class="smpl">417 (Expectation Failed)</a> or a <a href="#status.100" class="smpl">100 (Continue)</a> status code. Therefore, when a client sends this header field to an origin server (possibly via a proxy) from which it has
    16581647         never seen a <a href="#status.100" class="smpl">100 (Continue)</a> status code, the client <em class="bcp14">SHOULD NOT</em> wait for an indefinite period before sending the request body.
    16591648      </p>
    1660       <p id="rfc.section.6.1.2.1.p.4">Requirements for HTTP/1.1 origin servers: </p>
     1649      <p id="rfc.section.5.1.2.1.p.4">Requirements for HTTP/1.1 origin servers: </p>
    16611650      <ul>
    16621651         <li>Upon receiving a request which includes an <a href="#header.expect" class="smpl">Expect</a> header field with the "100-continue" expectation, an origin server <em class="bcp14">MUST</em> either respond with <a href="#status.100" class="smpl">100 (Continue)</a> status code and continue to read from the input stream, or respond with a final status code. The origin server <em class="bcp14">MUST NOT</em> wait for the request body before sending the <a href="#status.100" class="smpl">100 (Continue)</a> response. If it responds with a final status code, it <em class="bcp14">MAY</em> close the transport connection or it <em class="bcp14">MAY</em> continue to read and discard the rest of the request. It <em class="bcp14">MUST NOT</em> perform the request method if it returns a final status code.
     
    16781667         </li>
    16791668      </ul>
    1680       <p id="rfc.section.6.1.2.1.p.5">Requirements for HTTP/1.1 proxies: </p>
     1669      <p id="rfc.section.5.1.2.1.p.5">Requirements for HTTP/1.1 proxies: </p>
    16811670      <ul>
    16821671         <li>If a proxy receives a request that includes an <a href="#header.expect" class="smpl">Expect</a> header field with the "100-continue" expectation, and the proxy either knows that the next-hop server complies with HTTP/1.1
     
    16871676         <li>Proxies <em class="bcp14">SHOULD</em> maintain a record of the HTTP version numbers received from recently-referenced next-hop servers.
    16881677         </li>
    1689          <li>A proxy <em class="bcp14">MUST NOT</em> forward a <a href="#status.100" class="smpl">100 (Continue)</a> response if the request message was received from an HTTP/1.0 (or earlier) client and did not include an <a href="#header.expect" class="smpl">Expect</a> header field with the "100-continue" expectation. This requirement overrides the general rule for forwarding of <a href="#status.1xx" class="smpl">1xx</a> responses (see <a href="#status.100" id="rfc.xref.status.100.2" title="100 Continue">Section&nbsp;7.2.1</a>).
    1690          </li>
    1691       </ul>
    1692       <h2 id="rfc.section.6.2"><a href="#rfc.section.6.2">6.2</a>&nbsp;<a id="request.conditionals" href="#request.conditionals">Conditionals</a></h2>
    1693       <p id="rfc.section.6.2.p.1">Conditionals are request header fields that indicate a precondition to be tested before applying the method semantics to the
     1678         <li>A proxy <em class="bcp14">MUST NOT</em> forward a <a href="#status.100" class="smpl">100 (Continue)</a> response if the request message was received from an HTTP/1.0 (or earlier) client and did not include an <a href="#header.expect" class="smpl">Expect</a> header field with the "100-continue" expectation. This requirement overrides the general rule for forwarding of <a href="#status.1xx" class="smpl">1xx</a> responses (see <a href="#status.100" id="rfc.xref.status.100.2" title="100 Continue">Section&nbsp;6.2.1</a>).
     1679         </li>
     1680      </ul>
     1681      <h2 id="rfc.section.5.2"><a href="#rfc.section.5.2">5.2</a>&nbsp;<a id="request.conditionals" href="#request.conditionals">Conditionals</a></h2>
     1682      <p id="rfc.section.5.2.p.1">Conditionals are request header fields that indicate a precondition to be tested before applying the method semantics to the
    16941683         target resource. Each precondition is based on metadata that is expected to change if the selected representation of the target
    16951684         resource is changed. The HTTP/1.1 conditional request mechanisms are defined in <a href="#Part4" id="rfc.xref.Part4.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>.
     
    17271716         </table>
    17281717      </div>
    1729       <h2 id="rfc.section.6.3"><a href="#rfc.section.6.3">6.3</a>&nbsp;<a id="request.conneg" href="#request.conneg">Content Negotiation</a></h2>
     1718      <h2 id="rfc.section.5.3"><a href="#rfc.section.5.3">5.3</a>&nbsp;<a id="request.conneg" href="#request.conneg">Content Negotiation</a></h2>
    17301719      <div id="rfc.table.u.6">
    17311720         <table class="tt full left" cellpadding="3" cellspacing="0">
     
    17391728               <tr>
    17401729                  <td class="left">Accept</td>
    1741                   <td class="left"><a href="#header.accept" id="rfc.xref.header.accept.2" title="Accept">Section&nbsp;6.3.2</a></td>
     1730                  <td class="left"><a href="#header.accept" id="rfc.xref.header.accept.2" title="Accept">Section&nbsp;5.3.2</a></td>
    17421731               </tr>
    17431732               <tr>
    17441733                  <td class="left">Accept-Charset</td>
    1745                   <td class="left"><a href="#header.accept-charset" id="rfc.xref.header.accept-charset.2" title="Accept-Charset">Section&nbsp;6.3.3</a></td>
     1734                  <td class="left"><a href="#header.accept-charset" id="rfc.xref.header.accept-charset.2" title="Accept-Charset">Section&nbsp;5.3.3</a></td>
    17461735               </tr>
    17471736               <tr>
    17481737                  <td class="left">Accept-Encoding</td>
    1749                   <td class="left"><a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.2" title="Accept-Encoding">Section&nbsp;6.3.4</a></td>
     1738                  <td class="left"><a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.2" title="Accept-Encoding">Section&nbsp;5.3.4</a></td>
    17501739               </tr>
    17511740               <tr>
    17521741                  <td class="left">Accept-Language</td>
    1753                   <td class="left"><a href="#header.accept-language" id="rfc.xref.header.accept-language.2" title="Accept-Language">Section&nbsp;6.3.5</a></td>
     1742                  <td class="left"><a href="#header.accept-language" id="rfc.xref.header.accept-language.2" title="Accept-Language">Section&nbsp;5.3.5</a></td>
    17541743               </tr>
    17551744            </tbody>
    17561745         </table>
    17571746      </div>
    1758       <h3 id="rfc.section.6.3.1"><a href="#rfc.section.6.3.1">6.3.1</a>&nbsp;<a id="quality.values" href="#quality.values">Quality Values</a></h3>
    1759       <p id="rfc.section.6.3.1.p.1">Many of the request header fields for proactive content negotiation use a common parameter, named "q" (case-insensitive),
     1747      <h3 id="rfc.section.5.3.1"><a href="#rfc.section.5.3.1">5.3.1</a>&nbsp;<a id="quality.values" href="#quality.values">Quality Values</a></h3>
     1748      <p id="rfc.section.5.3.1.p.1">Many of the request header fields for proactive content negotiation use a common parameter, named "q" (case-insensitive),
    17601749         to assign a relative "weight" to the preference for that associated kind of content. This weight is referred to as a "quality
    17611750         value" (or "qvalue") because the same parameter name is often used within server configurations to assign a weight to the
    17621751         relative quality of the various representations that can be selected for a resource.
    17631752      </p>
    1764       <p id="rfc.section.6.3.1.p.2">The weight is normalized to a real number in the range 0 through 1, where 0.001 is the least preferred and 1 is the most preferred;
     1753      <p id="rfc.section.5.3.1.p.2">The weight is normalized to a real number in the range 0 through 1, where 0.001 is the least preferred and 1 is the most preferred;
    17651754         a value of 0 means "not acceptable". If no "q" parameter is present, the default weight is 1.
    17661755      </p>
     
    17681757  <a href="#quality.values" class="smpl">qvalue</a> = ( "0" [ "." 0*3<a href="#imported.abnf" class="smpl">DIGIT</a> ] )
    17691758         / ( "1" [ "." 0*3("0") ] )
    1770 </pre><p id="rfc.section.6.3.1.p.4">A sender of qvalue <em class="bcp14">MUST NOT</em> generate more than three digits after the decimal point. User configuration of these values ought to be limited in the same
     1759</pre><p id="rfc.section.5.3.1.p.4">A sender of qvalue <em class="bcp14">MUST NOT</em> generate more than three digits after the decimal point. User configuration of these values ought to be limited in the same
    17711760         fashion.
    17721761      </p>
    17731762      <div id="rfc.iref.a.1"></div>
    1774       <h3 id="rfc.section.6.3.2"><a href="#rfc.section.6.3.2">6.3.2</a>&nbsp;<a id="header.accept" href="#header.accept">Accept</a></h3>
    1775       <p id="rfc.section.6.3.2.p.1">The "Accept" header field can be used by user agents to specify response media types that are acceptable. Accept header fields
     1763      <h3 id="rfc.section.5.3.2"><a href="#rfc.section.5.3.2">5.3.2</a>&nbsp;<a id="header.accept" href="#header.accept">Accept</a></h3>
     1764      <p id="rfc.section.5.3.2.p.1">The "Accept" header field can be used by user agents to specify response media types that are acceptable. Accept header fields
    17761765         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
    17771766         for an in-line image.
     
    17851774  <a href="#header.accept" class="smpl">accept-params</a>  = <a href="#quality.values" class="smpl">weight</a> *( <a href="#header.accept" class="smpl">accept-ext</a> )
    17861775  <a href="#header.accept" class="smpl">accept-ext</a>     = <a href="#imported.abnf" class="smpl">OWS</a> ";" <a href="#imported.abnf" class="smpl">OWS</a> <a href="#imported.abnf" class="smpl">token</a> [ "=" <a href="#imported.abnf" class="smpl">word</a> ]
    1787 </pre><p id="rfc.section.6.3.2.p.3">The asterisk "*" character is used to group media types into ranges, with "*/*" indicating all media types and "type/*" indicating
     1776</pre><p id="rfc.section.5.3.2.p.3">The asterisk "*" character is used to group media types into ranges, with "*/*" indicating all media types and "type/*" indicating
    17881777         all subtypes of that type. The media-range <em class="bcp14">MAY</em> include media type parameters that are applicable to that range.
    17891778      </p>
    1790       <p id="rfc.section.6.3.2.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 weight, as defined in <a href="#quality.values" title="Quality Values">Section&nbsp;6.3.1</a>. The first "q" parameter (if any) separates the media-range parameter(s) from the accept-params.
    1791       </p>
    1792       <div class="note" id="rfc.section.6.3.2.p.5">
     1779      <p id="rfc.section.5.3.2.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 weight, as defined in <a href="#quality.values" title="Quality Values">Section&nbsp;5.3.1</a>. The first "q" parameter (if any) separates the media-range parameter(s) from the accept-params.
     1780      </p>
     1781      <div class="note" id="rfc.section.5.3.2.p.5">
    17931782         <p> <b>Note:</b> Use of the "q" parameter name to separate media type parameters from Accept extension parameters is due to historical practice.
    17941783            Although this prevents any media type parameter named "q" from being used with a media range, such an event is believed to
     
    17971786         </p>
    17981787      </div>
    1799       <p id="rfc.section.6.3.2.p.6">The example</p>
     1788      <p id="rfc.section.5.3.2.p.6">The example</p>
    18001789      <div id="rfc.figure.u.17"></div><pre class="text">  Accept: audio/*; q=0.2, audio/basic
    1801 </pre><p id="rfc.section.6.3.2.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
     1790</pre><p id="rfc.section.5.3.2.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
    18021791         quality".
    18031792      </p>
    1804       <p id="rfc.section.6.3.2.p.9">A request without any Accept header field implies that the user agent will accept any media type in response. If an Accept
     1793      <p id="rfc.section.5.3.2.p.9">A request without any Accept header field implies that the user agent will accept any media type in response. If an Accept
    18051794         header field is present in a request and none of the available representations for the response have a media type that is
    18061795         listed as acceptable, the origin server <em class="bcp14">MAY</em> either honor the Accept header field by sending a <a href="#status.406" class="smpl">406 (Not Acceptable)</a> response or disregard the Accept header field by treating the response as if it is not subject to content negotiation.
    18071796      </p>
    1808       <p id="rfc.section.6.3.2.p.10">A more elaborate example is</p>
     1797      <p id="rfc.section.5.3.2.p.10">A more elaborate example is</p>
    18091798      <div id="rfc.figure.u.18"></div><pre class="text">  Accept: text/plain; q=0.5, text/html,
    18101799          text/x-dvi; q=0.8, text/x-c
    1811 </pre><p id="rfc.section.6.3.2.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
     1800</pre><p id="rfc.section.5.3.2.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
    18121801         send the text/x-dvi representation, and if that does not exist, send the text/plain representation".
    18131802      </p>
    1814       <p id="rfc.section.6.3.2.p.13">Media ranges can be overridden by more specific media ranges or specific media types. If more than one media range applies
     1803      <p id="rfc.section.5.3.2.p.13">Media ranges can be overridden by more specific media ranges or specific media types. If more than one media range applies
    18151804         to a given type, the most specific reference has precedence. For example,
    18161805      </p>
    18171806      <div id="rfc.figure.u.19"></div><pre class="text">  Accept: text/*, text/plain, text/plain;format=flowed, */*
    1818 </pre><p id="rfc.section.6.3.2.p.15">have the following precedence: </p>
     1807</pre><p id="rfc.section.5.3.2.p.15">have the following precedence: </p>
    18191808      <ol>
    18201809         <li>text/plain;format=flowed</li>
     
    18231812         <li>*/*</li>
    18241813      </ol>
    1825       <p id="rfc.section.6.3.2.p.16">The media type quality factor associated with a given type is determined by finding the media range with the highest precedence
     1814      <p id="rfc.section.5.3.2.p.16">The media type quality factor associated with a given type is determined by finding the media range with the highest precedence
    18261815         which matches that type. For example,
    18271816      </p>
    18281817      <div id="rfc.figure.u.20"></div><pre class="text">  Accept: text/*;q=0.3, text/html;q=0.7, text/html;level=1,
    18291818          text/html;level=2;q=0.4, */*;q=0.5
    1830 </pre><p id="rfc.section.6.3.2.p.18">would cause the following values to be associated:</p>
     1819</pre><p id="rfc.section.5.3.2.p.18">would cause the following values to be associated:</p>
    18311820      <div id="rfc.table.u.7">
    18321821         <table class="tt full left" cellpadding="3" cellspacing="0">
     
    18651854         </table>
    18661855      </div>
    1867       <p id="rfc.section.6.3.2.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
     1856      <p id="rfc.section.5.3.2.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
    18681857         is a closed system which cannot interact with other rendering agents, this default set ought to be configurable by the user.
    18691858      </p>
    18701859      <div id="rfc.iref.a.2"></div>
    1871       <h3 id="rfc.section.6.3.3"><a href="#rfc.section.6.3.3">6.3.3</a>&nbsp;<a id="header.accept-charset" href="#header.accept-charset">Accept-Charset</a></h3>
    1872       <p id="rfc.section.6.3.3.p.1">The "Accept-Charset" header field can be used by user agents to indicate what character encodings are acceptable in a response
     1860      <h3 id="rfc.section.5.3.3"><a href="#rfc.section.5.3.3">5.3.3</a>&nbsp;<a id="header.accept-charset" href="#header.accept-charset">Accept-Charset</a></h3>
     1861      <p id="rfc.section.5.3.3.p.1">The "Accept-Charset" header field can be used by user agents to indicate what character encodings are acceptable in a response
    18731862         payload. This field allows clients capable of understanding more comprehensive or special-purpose character encodings to signal
    18741863         that capability to a server which is capable of representing documents in those character encodings.
    18751864      </p>
    18761865      <div id="rfc.figure.u.21"></div><pre class="inline"><span id="rfc.iref.g.19"></span>  <a href="#header.accept-charset" class="smpl">Accept-Charset</a> = 1#( ( <a href="#rule.charset" class="smpl">charset</a> / "*" ) [ <a href="#quality.values" class="smpl">weight</a> ] )
    1877 </pre><p id="rfc.section.6.3.3.p.3">Character encoding values (a.k.a., charsets) are described in <a href="#character.sets" title="Character Encodings (charset)">Section&nbsp;9.3</a>. Each charset <em class="bcp14">MAY</em> be given an associated quality value which represents the user's preference for that charset, as defined in <a href="#quality.values" title="Quality Values">Section&nbsp;6.3.1</a>. An example is
     1866</pre><p id="rfc.section.5.3.3.p.3">Character encoding values (a.k.a., charsets) are described in <a href="#character.sets" title="Character Encodings (charset)">Section&nbsp;8.3</a>. Each charset <em class="bcp14">MAY</em> be given an associated quality value which represents the user's preference for that charset, as defined in <a href="#quality.values" title="Quality Values">Section&nbsp;5.3.1</a>. An example is
    18781867      </p>
    18791868      <div id="rfc.figure.u.22"></div><pre class="text">  Accept-Charset: iso-8859-5, unicode-1-1;q=0.8
    1880 </pre><p id="rfc.section.6.3.3.p.5">The special value "*", if present in the Accept-Charset field, matches every character encoding which is not mentioned elsewhere
     1869</pre><p id="rfc.section.5.3.3.p.5">The special value "*", if present in the Accept-Charset field, matches every character encoding which is not mentioned elsewhere
    18811870         in the Accept-Charset field. If no "*" is present in an Accept-Charset field, then any character encodings not explicitly
    18821871         mentioned in the field are considered "not acceptable" to the client.
    18831872      </p>
    1884       <p id="rfc.section.6.3.3.p.6">A request without any Accept-Charset header field implies that the user agent will accept any character encoding in response.</p>
    1885       <p id="rfc.section.6.3.3.p.7">If an Accept-Charset header field is present in a request and none of the available representations for the response have
     1873      <p id="rfc.section.5.3.3.p.6">A request without any Accept-Charset header field implies that the user agent will accept any character encoding in response.</p>
     1874      <p id="rfc.section.5.3.3.p.7">If an Accept-Charset header field is present in a request and none of the available representations for the response have
    18861875         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 <a href="#status.406" class="smpl">406 (Not Acceptable)</a> response or disregard the Accept-Charset header field by treating the response as if it is not subject to content negotiation.
    18871876      </p>
    18881877      <div id="rfc.iref.a.3"></div>
    1889       <h3 id="rfc.section.6.3.4"><a href="#rfc.section.6.3.4">6.3.4</a>&nbsp;<a id="header.accept-encoding" href="#header.accept-encoding">Accept-Encoding</a></h3>
    1890       <p id="rfc.section.6.3.4.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;9.4</a>) are acceptable in the response. An "identity" token is used as a synonym for "no encoding" in order to communicate when
     1878      <h3 id="rfc.section.5.3.4"><a href="#rfc.section.5.3.4">5.3.4</a>&nbsp;<a id="header.accept-encoding" href="#header.accept-encoding">Accept-Encoding</a></h3>
     1879      <p id="rfc.section.5.3.4.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;8.4</a>) are acceptable in the response. An "identity" token is used as a synonym for "no encoding" in order to communicate when
    18911880         no encoding is preferred.
    18921881      </p>
    18931882      <div id="rfc.figure.u.23"></div><pre class="inline"><span id="rfc.iref.g.20"></span><span id="rfc.iref.g.21"></span>  <a href="#header.accept-encoding" class="smpl">Accept-Encoding</a>  = #( <a href="#header.accept-encoding" class="smpl">codings</a> [ <a href="#quality.values" class="smpl">weight</a> ] )
    18941883  <a href="#header.accept-encoding" class="smpl">codings</a>          = <a href="#content.codings" class="smpl">content-coding</a> / "identity" / "*"
    1895 </pre><p id="rfc.section.6.3.4.p.3">Each codings value <em class="bcp14">MAY</em> be given an associated quality value which represents the preference for that encoding, as defined in <a href="#quality.values" title="Quality Values">Section&nbsp;6.3.1</a>.
    1896       </p>
    1897       <p id="rfc.section.6.3.4.p.4">For example,</p>
     1884</pre><p id="rfc.section.5.3.4.p.3">Each codings value <em class="bcp14">MAY</em> be given an associated quality value which represents the preference for that encoding, as defined in <a href="#quality.values" title="Quality Values">Section&nbsp;5.3.1</a>.
     1885      </p>
     1886      <p id="rfc.section.5.3.4.p.4">For example,</p>
    18981887      <div id="rfc.figure.u.24"></div><pre class="text">  Accept-Encoding: compress, gzip
    18991888  Accept-Encoding:
     
    19011890  Accept-Encoding: compress;q=0.5, gzip;q=1.0
    19021891  Accept-Encoding: gzip;q=1.0, identity; q=0.5, *;q=0
    1903 </pre><p id="rfc.section.6.3.4.p.6">A server tests whether a content-coding for a given representation is acceptable, according to an Accept-Encoding field, using
     1892</pre><p id="rfc.section.5.3.4.p.6">A server tests whether a content-coding for a given representation is acceptable, according to an Accept-Encoding field, using
    19041893         these rules:
    19051894      </p>
     
    19121901         </li>
    19131902         <li>If the representation's content-coding is one of the content-codings listed in the Accept-Encoding field, then it is acceptable
    1914             unless it is accompanied by a qvalue of 0. (As defined in <a href="#quality.values" title="Quality Values">Section&nbsp;6.3.1</a>, a qvalue of 0 means "not acceptable".)
     1903            unless it is accompanied by a qvalue of 0. (As defined in <a href="#quality.values" title="Quality Values">Section&nbsp;5.3.1</a>, a qvalue of 0 means "not acceptable".)
    19151904         </li>
    19161905         <li>If multiple content-codings are acceptable, then the acceptable content-coding with the highest non-zero qvalue is preferred.</li>
    19171906      </ol>
    1918       <p id="rfc.section.6.3.4.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
     1907      <p id="rfc.section.5.3.4.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
    19191908         in response. If an Accept-Encoding header field is present in a request and none of the available representations for the
    19201909         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.
    19211910      </p>
    1922       <p id="rfc.section.6.3.4.p.8">A request without an Accept-Encoding header field implies that the user agent will accept any content-coding in response.</p>
    1923       <div class="note" id="rfc.section.6.3.4.p.9">
     1911      <p id="rfc.section.5.3.4.p.8">A request without an Accept-Encoding header field implies that the user agent will accept any content-coding in response.</p>
     1912      <div class="note" id="rfc.section.5.3.4.p.9">
    19241913         <p> <b>Note:</b> Most HTTP/1.0 applications do not recognize or obey qvalues associated with content-codings. This means that qvalues will
    19251914            not work and are not permitted with x-gzip or x-compress.
     
    19271916      </div>
    19281917      <div id="rfc.iref.a.4"></div>
    1929       <h3 id="rfc.section.6.3.5"><a href="#rfc.section.6.3.5">6.3.5</a>&nbsp;<a id="header.accept-language" href="#header.accept-language">Accept-Language</a></h3>
    1930       <p id="rfc.section.6.3.5.p.1">The "Accept-Language" header field can be used by user agents to indicate the set of natural languages that are preferred
    1931          in the response. Language tags are defined in <a href="#language.tags" title="Language Tags">Section&nbsp;9.6</a>.
     1918      <h3 id="rfc.section.5.3.5"><a href="#rfc.section.5.3.5">5.3.5</a>&nbsp;<a id="header.accept-language" href="#header.accept-language">Accept-Language</a></h3>
     1919      <p id="rfc.section.5.3.5.p.1">The "Accept-Language" header field can be used by user agents to indicate the set of natural languages that are preferred
     1920         in the response. Language tags are defined in <a href="#language.tags" title="Language Tags">Section&nbsp;8.6</a>.
    19321921      </p>
    19331922      <div id="rfc.figure.u.25"></div><pre class="inline"><span id="rfc.iref.g.22"></span><span id="rfc.iref.g.23"></span>  <a href="#header.accept-language" class="smpl">Accept-Language</a> = 1#( <a href="#header.accept-language" class="smpl">language-range</a> [ <a href="#quality.values" class="smpl">weight</a> ] )
    19341923  <a href="#header.accept-language" class="smpl">language-range</a>  =
    19351924            &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;
    1936 </pre><p id="rfc.section.6.3.5.p.3">Each language-range can be given an associated quality value which represents an estimate of the user's preference for the
    1937          languages specified by that range, as defined in <a href="#quality.values" title="Quality Values">Section&nbsp;6.3.1</a>. For example,
     1925</pre><p id="rfc.section.5.3.5.p.3">Each language-range can be given an associated quality value which represents an estimate of the user's preference for the
     1926         languages specified by that range, as defined in <a href="#quality.values" title="Quality Values">Section&nbsp;5.3.1</a>. For example,
    19381927      </p>
    19391928      <div id="rfc.figure.u.26"></div><pre class="text">  Accept-Language: da, en-gb;q=0.8, en;q=0.7
    1940 </pre><p id="rfc.section.6.3.5.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>)
    1941       </p>
    1942       <p id="rfc.section.6.3.5.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.
    1943       </p>
    1944       <div class="note" id="rfc.section.6.3.5.p.7">
     1929</pre><p id="rfc.section.5.3.5.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>)
     1930      </p>
     1931      <p id="rfc.section.5.3.5.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.
     1932      </p>
     1933      <div class="note" id="rfc.section.5.3.5.p.7">
    19451934         <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.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
    19461935         </p>
    19471936      </div>
    1948       <p id="rfc.section.6.3.5.p.8">It might be contrary to the privacy expectations of the user to send an Accept-Language header field with the complete linguistic
    1949          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>.
    1950       </p>
    1951       <p id="rfc.section.6.3.5.p.9">As intelligibility is highly dependent on the individual user, it is recommended that client applications make the choice
     1937      <p id="rfc.section.5.3.5.p.8">It might be contrary to the privacy expectations of the user to send an Accept-Language header field with the complete linguistic
     1938         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;10.5</a>.
     1939      </p>
     1940      <p id="rfc.section.5.3.5.p.9">As intelligibility is highly dependent on the individual user, it is recommended that client applications make the choice
    19521941         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.
    19531942      </p>
    1954       <div class="note" id="rfc.section.6.3.5.p.10">
     1943      <div class="note" id="rfc.section.5.3.5.p.10">
    19551944         <p> <b>Note:</b> When making the choice of linguistic preference available to the user, we remind implementers of the fact that users are not
    19561945            familiar with the details of language matching as described above, and ought to be provided appropriate guidance. As an example,
     
    19591948         </p>
    19601949      </div>
    1961       <h2 id="rfc.section.6.4"><a href="#rfc.section.6.4">6.4</a>&nbsp;<a id="request.auth" href="#request.auth">Authentication</a></h2>
     1950      <h2 id="rfc.section.5.4"><a href="#rfc.section.5.4">5.4</a>&nbsp;<a id="request.auth" href="#request.auth">Authentication</a></h2>
    19621951      <div id="rfc.table.u.8">
    19631952         <table class="tt full left" cellpadding="3" cellspacing="0">
     
    19801969         </table>
    19811970      </div>
    1982       <h2 id="rfc.section.6.5"><a href="#rfc.section.6.5">6.5</a>&nbsp;<a id="request.context" href="#request.context">Context</a></h2>
     1971      <h2 id="rfc.section.5.5"><a href="#rfc.section.5.5">5.5</a>&nbsp;<a id="request.context" href="#request.context">Context</a></h2>
    19831972      <div id="rfc.table.u.9">
    19841973         <table class="tt full left" cellpadding="3" cellspacing="0">
     
    19921981               <tr>
    19931982                  <td class="left">From</td>
    1994                   <td class="left"><a href="#header.from" id="rfc.xref.header.from.1" title="From">Section&nbsp;6.5.1</a></td>
     1983                  <td class="left"><a href="#header.from" id="rfc.xref.header.from.1" title="From">Section&nbsp;5.5.1</a></td>
    19951984               </tr>
    19961985               <tr>
    19971986                  <td class="left">Referer</td>
    1998                   <td class="left"><a href="#header.referer" id="rfc.xref.header.referer.1" title="Referer">Section&nbsp;6.5.2</a></td>
     1987                  <td class="left"><a href="#header.referer" id="rfc.xref.header.referer.1" title="Referer">Section&nbsp;5.5.2</a></td>
    19991988               </tr>
    20001989               <tr>
     
    20041993               <tr>
    20051994                  <td class="left">User-Agent</td>
    2006                   <td class="left"><a href="#header.user-agent" id="rfc.xref.header.user-agent.2" title="User-Agent">Section&nbsp;6.5.3</a></td>
     1995                  <td class="left"><a href="#header.user-agent" id="rfc.xref.header.user-agent.2" title="User-Agent">Section&nbsp;5.5.3</a></td>
    20071996               </tr>
    20081997            </tbody>
     
    20101999      </div>
    20112000      <div id="rfc.iref.f.1"></div>
    2012       <h3 id="rfc.section.6.5.1"><a href="#rfc.section.6.5.1">6.5.1</a>&nbsp;<a id="header.from" href="#header.from">From</a></h3>
    2013       <p id="rfc.section.6.5.1.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.1"><cite title="Internet Message Format">[RFC5322]</cite></a>:
     2001      <h3 id="rfc.section.5.5.1"><a href="#rfc.section.5.5.1">5.5.1</a>&nbsp;<a id="header.from" href="#header.from">From</a></h3>
     2002      <p id="rfc.section.5.5.1.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.1"><cite title="Internet Message Format">[RFC5322]</cite></a>:
    20142003      </p>
    20152004      <div id="rfc.figure.u.27"></div><pre class="inline"><span id="rfc.iref.g.24"></span>  <a href="#header.from" class="smpl">From</a>    = <a href="#header.from" class="smpl">mailbox</a>
    20162005 
    20172006  <a href="#header.from" class="smpl">mailbox</a> = &lt;mailbox, defined in <a href="#RFC5322" id="rfc.xref.RFC5322.2"><cite title="Internet Message Format">[RFC5322]</cite></a>, <a href="http://tools.ietf.org/html/rfc5322#section-3.4">Section 3.4</a>&gt;
    2018 </pre><p id="rfc.section.6.5.1.p.3">An example is:</p>
     2007</pre><p id="rfc.section.5.5.1.p.3">An example is:</p>
    20192008      <div id="rfc.figure.u.28"></div><pre class="text">  From: webmaster@example.org
    2020 </pre><p id="rfc.section.6.5.1.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
     2009</pre><p id="rfc.section.5.5.1.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
    20212010         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
    20222011         end.
    20232012      </p>
    2024       <p id="rfc.section.6.5.1.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
     2013      <p id="rfc.section.5.5.1.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
    20252014         issuer's address <em class="bcp14">SHOULD</em> be used.
    20262015      </p>
    2027       <p id="rfc.section.6.5.1.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
     2016      <p id="rfc.section.5.5.1.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
    20282017         security policy. It is strongly recommended that the user be able to disable, enable, and modify the value of this field at
    20292018         any time prior to a request.
    20302019      </p>
    20312020      <div id="rfc.iref.r.2"></div>
    2032       <h3 id="rfc.section.6.5.2"><a href="#rfc.section.6.5.2">6.5.2</a>&nbsp;<a id="header.referer" href="#header.referer">Referer</a></h3>
    2033       <p id="rfc.section.6.5.2.p.1">The "Referer" [sic] header field allows the client to specify the URI of the resource from which the target URI was obtained
     2021      <h3 id="rfc.section.5.5.2"><a href="#rfc.section.5.5.2">5.5.2</a>&nbsp;<a id="header.referer" href="#header.referer">Referer</a></h3>
     2022      <p id="rfc.section.5.5.2.p.1">The "Referer" [sic] header field allows the client to specify the URI of the resource from which the target URI was obtained
    20342023         (the "referrer", although the header field is misspelled.).
    20352024      </p>
    2036       <p id="rfc.section.6.5.2.p.2">The Referer header field allows servers to generate lists of back-links to resources for interest, logging, optimized caching,
     2025      <p id="rfc.section.5.5.2.p.2">The Referer header field allows servers to generate lists of back-links to resources for interest, logging, optimized caching,
    20372026         etc. It also allows obsolete or mistyped links to be traced for maintenance. Some servers use Referer as a means of controlling
    20382027         where they allow links from (so-called "deep linking"), but legitimate requests do not always contain a Referer header field.
    20392028      </p>
    2040       <p id="rfc.section.6.5.2.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
     2029      <p id="rfc.section.5.5.2.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
    20412030         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
    20422031         non-HTTP URIs (e.g., FTP).
    20432032      </p>
    20442033      <div id="rfc.figure.u.29"></div><pre class="inline"><span id="rfc.iref.g.25"></span>  <a href="#header.referer" class="smpl">Referer</a> = <a href="#imported.abnf" class="smpl">absolute-URI</a> / <a href="#imported.abnf" class="smpl">partial-URI</a>
    2045 </pre><p id="rfc.section.6.5.2.p.5">Example:</p>
     2034</pre><p id="rfc.section.5.5.2.p.5">Example:</p>
    20462035      <div id="rfc.figure.u.30"></div><pre class="text">  Referer: http://www.example.org/hypertext/Overview.html
    2047 </pre><p id="rfc.section.6.5.2.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.
     2036</pre><p id="rfc.section.5.5.2.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;10.2</a> for security considerations.
    20482037      </p>
    20492038      <div id="rfc.iref.u.1"></div>
    2050       <h3 id="rfc.section.6.5.3"><a href="#rfc.section.6.5.3">6.5.3</a>&nbsp;<a id="header.user-agent" href="#header.user-agent">User-Agent</a></h3>
    2051       <p id="rfc.section.6.5.3.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.
    2052       </p>
    2053       <p id="rfc.section.6.5.3.p.2">Typically, it is used for statistical purposes, the tracing of protocol violations, and tailoring responses to avoid particular
     2039      <h3 id="rfc.section.5.5.3"><a href="#rfc.section.5.5.3">5.5.3</a>&nbsp;<a id="header.user-agent" href="#header.user-agent">User-Agent</a></h3>
     2040      <p id="rfc.section.5.5.3.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.
     2041      </p>
     2042      <p id="rfc.section.5.5.3.p.2">Typically, it is used for statistical purposes, the tracing of protocol violations, and tailoring responses to avoid particular
    20542043         user agent limitations.
    20552044      </p>
    2056       <p id="rfc.section.6.5.3.p.3">The field can contain multiple product tokens (<a href="#product.tokens" title="Product Tokens">Section&nbsp;9.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.17"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) identifying the agent and its significant subproducts. By convention, the product tokens are listed in order of their significance
     2045      <p id="rfc.section.5.5.3.p.3">The field can contain multiple product tokens (<a href="#product.tokens" title="Product Tokens">Section&nbsp;8.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.17"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) identifying the agent and its significant subproducts. By convention, the product tokens are listed in order of their significance
    20572046         for identifying the application.
    20582047      </p>
    2059       <p id="rfc.section.6.5.3.p.4">Because this field is usually sent on every request a user agent makes, implementations are encouraged not to include needlessly
     2048      <p id="rfc.section.5.5.3.p.4">Because this field is usually sent on every request a user agent makes, implementations are encouraged not to include needlessly
    20602049         fine-grained detail, and to limit (or even prohibit) the addition of subproducts by third parties. Overly long and detailed
    20612050         User-Agent field values make requests larger and can also be used to identify ("fingerprint") the user against their wishes.
    20622051      </p>
    2063       <p id="rfc.section.6.5.3.p.5">Likewise, implementations are encouraged not to use the product tokens of other implementations in order to declare compatibility
     2052      <p id="rfc.section.5.5.3.p.5">Likewise, implementations are encouraged not to use the product tokens of other implementations in order to declare compatibility
    20642053         with them, as this circumvents the purpose of the field. Finally, they are encouraged not to use comments to identify products;
    20652054         doing so makes the field value more difficult to parse.
    20662055      </p>
    20672056      <div id="rfc.figure.u.31"></div><pre class="inline"><span id="rfc.iref.g.26"></span>  <a href="#header.user-agent" class="smpl">User-Agent</a> = <a href="#product.tokens" class="smpl">product</a> *( <a href="#imported.abnf" class="smpl">RWS</a> ( <a href="#product.tokens" class="smpl">product</a> / <a href="#imported.abnf" class="smpl">comment</a> ) )
    2068 </pre><p id="rfc.section.6.5.3.p.7">Example:</p>
     2057</pre><p id="rfc.section.5.5.3.p.7">Example:</p>
    20692058      <div id="rfc.figure.u.32"></div><pre class="text">  User-Agent: CERN-LineMode/2.15 libwww/2.17b3
    2070 </pre><h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a id="status.codes" href="#status.codes">Response Status Codes</a></h1>
    2071       <p id="rfc.section.7.p.1">The status-code element is a 3-digit integer result code of the attempt to understand and satisfy the request.</p>
    2072       <p id="rfc.section.7.p.2">HTTP status codes are extensible. HTTP applications are not required to understand the meaning of all registered status codes,
     2059</pre><h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="status.codes" href="#status.codes">Response Status Codes</a></h1>
     2060      <p id="rfc.section.6.p.1">The status-code element is a 3-digit integer result code of the attempt to understand and satisfy the request.</p>
     2061      <p id="rfc.section.6.p.2">HTTP status codes are extensible. HTTP applications are not required to understand the meaning of all registered status codes,
    20732062         though such understanding is obviously desirable. However, applications <em class="bcp14">MUST</em> understand the class of any status code, as indicated by the first digit, and treat any unrecognized response as being equivalent
    20742063         to the x00 status code of that class, with the exception that an unrecognized response <em class="bcp14">MUST NOT</em> be cached. For example, if an unrecognized status code of 431 is received by the client, it can safely assume that there was
     
    20762065         information which will explain the unusual status.
    20772066      </p>
    2078       <p id="rfc.section.7.p.3">The first digit of the status-code defines the class of response. The last two digits do not have any categorization role.
     2067      <p id="rfc.section.6.p.3">The first digit of the status-code defines the class of response. The last two digits do not have any categorization role.
    20792068         There are 5 values for the first digit:
    20802069      </p>
     
    20912080         </li>
    20922081      </ul>
    2093       <p id="rfc.section.7.p.4">For most status codes the response can carry a payload, in which case a <a href="#header.content-type" class="smpl">Content-Type</a> header field indicates the payload's media type (<a href="#header.content-type" id="rfc.xref.header.content-type.2" title="Content-Type">Section&nbsp;3.2.1</a>).
    2094       </p>
    2095       <h2 id="rfc.section.7.1"><a href="#rfc.section.7.1">7.1</a>&nbsp;<a id="overview.of.status.codes" href="#overview.of.status.codes">Overview of Status Codes</a></h2>
    2096       <p id="rfc.section.7.1.p.1">The status codes listed below are defined in this specification, <a href="p4-conditional.html#status.code.definitions" title="Status Code Definitions">Section 4</a> of <a href="#Part4" id="rfc.xref.Part4.9"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>, <a href="p5-range.html#status.code.definitions" title="Status Code Definitions">Section 3</a> of <a href="#Part5" id="rfc.xref.Part5.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a>, and <a href="p7-auth.html#status.code.definitions" title="Status Code Definitions">Section 3</a> of <a href="#Part7" id="rfc.xref.Part7.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[Part7]</cite></a>. The reason phrases listed here are only recommendations — they can be replaced by local equivalents without affecting the
     2082      <p id="rfc.section.6.p.4">For most status codes the response can carry a payload, in which case a <a href="#header.content-type" class="smpl">Content-Type</a> header field indicates the payload's media type (<a href="#header.content-type" id="rfc.xref.header.content-type.2" title="Content-Type">Section&nbsp;3.3.1</a>).
     2083      </p>
     2084      <h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a>&nbsp;<a id="overview.of.status.codes" href="#overview.of.status.codes">Overview of Status Codes</a></h2>
     2085      <p id="rfc.section.6.1.p.1">The status codes listed below are defined in this specification, <a href="p4-conditional.html#status.code.definitions" title="Status Code Definitions">Section 4</a> of <a href="#Part4" id="rfc.xref.Part4.9"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>, <a href="p5-range.html#status.code.definitions" title="Status Code Definitions">Section 3</a> of <a href="#Part5" id="rfc.xref.Part5.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a>, and <a href="p7-auth.html#status.code.definitions" title="Status Code Definitions">Section 3</a> of <a href="#Part7" id="rfc.xref.Part7.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[Part7]</cite></a>. The reason phrases listed here are only recommendations — they can be replaced by local equivalents without affecting the
    20972086         protocol.
    20982087      </p>
     
    21102099                  <td class="left">100</td>
    21112100                  <td class="left">Continue</td>
    2112                   <td class="left"><a href="#status.100" id="rfc.xref.status.100.3" title="100 Continue">Section&nbsp;7.2.1</a></td>
     2101                  <td class="left"><a href="#status.100" id="rfc.xref.status.100.3" title="100 Continue">Section&nbsp;6.2.1</a></td>
    21132102               </tr>
    21142103               <tr>
    21152104                  <td class="left">101</td>
    21162105                  <td class="left">Switching Protocols</td>
    2117                   <td class="left"><a href="#status.101" id="rfc.xref.status.101.1" title="101 Switching Protocols">Section&nbsp;7.2.2</a></td>
     2106                  <td class="left"><a href="#status.101" id="rfc.xref.status.101.1" title="101 Switching Protocols">Section&nbsp;6.2.2</a></td>
    21182107               </tr>
    21192108               <tr>
    21202109                  <td class="left">200</td>
    21212110                  <td class="left">OK</td>
    2122                   <td class="left"><a href="#status.200" id="rfc.xref.status.200.1" title="200 OK">Section&nbsp;7.3.1</a></td>
     2111                  <td class="left"><a href="#status.200" id="rfc.xref.status.200.1" title="200 OK">Section&nbsp;6.3.1</a></td>
    21232112               </tr>
    21242113               <tr>
    21252114                  <td class="left">201</td>
    21262115                  <td class="left">Created</td>
    2127                   <td class="left"><a href="#status.201" id="rfc.xref.status.201.1" title="201 Created">Section&nbsp;7.3.2</a></td>
     2116                  <td class="left"><a href="#status.201" id="rfc.xref.status.201.1" title="201 Created">Section&nbsp;6.3.2</a></td>
    21282117               </tr>
    21292118               <tr>
    21302119                  <td class="left">202</td>
    21312120                  <td class="left">Accepted</td>
    2132                   <td class="left"><a href="#status.202" id="rfc.xref.status.202.1" title="202 Accepted">Section&nbsp;7.3.3</a></td>
     2121                  <td class="left"><a href="#status.202" id="rfc.xref.status.202.1" title="202 Accepted">Section&nbsp;6.3.3</a></td>
    21332122               </tr>
    21342123               <tr>
    21352124                  <td class="left">203</td>
    21362125                  <td class="left">Non-Authoritative Information</td>
    2137                   <td class="left"><a href="#status.203" id="rfc.xref.status.203.1" title="203 Non-Authoritative Information">Section&nbsp;7.3.4</a></td>
     2126                  <td class="left"><a href="#status.203" id="rfc.xref.status.203.1" title="203 Non-Authoritative Information">Section&nbsp;6.3.4</a></td>
    21382127               </tr>
    21392128               <tr>
    21402129                  <td class="left">204</td>
    21412130                  <td class="left">No Content</td>
    2142                   <td class="left"><a href="#status.204" id="rfc.xref.status.204.1" title="204 No Content">Section&nbsp;7.3.5</a></td>
     2131                  <td class="left"><a href="#status.204" id="rfc.xref.status.204.1" title="204 No Content">Section&nbsp;6.3.5</a></td>
    21432132               </tr>
    21442133               <tr>
    21452134                  <td class="left">205</td>
    21462135                  <td class="left">Reset Content</td>
    2147                   <td class="left"><a href="#status.205" id="rfc.xref.status.205.1" title="205 Reset Content">Section&nbsp;7.3.6</a></td>
     2136                  <td class="left"><a href="#status.205" id="rfc.xref.status.205.1" title="205 Reset Content">Section&nbsp;6.3.6</a></td>
    21482137               </tr>
    21492138               <tr>
     
    21552144                  <td class="left">300</td>
    21562145                  <td class="left">Multiple Choices</td>
    2157                   <td class="left"><a href="#status.300" id="rfc.xref.status.300.1" title="300 Multiple Choices">Section&nbsp;7.4.1</a></td>
     2146                  <td class="left"><a href="#status.300" id="rfc.xref.status.300.1" title="300 Multiple Choices">Section&nbsp;6.4.1</a></td>
    21582147               </tr>
    21592148               <tr>
    21602149                  <td class="left">301</td>
    21612150                  <td class="left">Moved Permanently</td>
    2162                   <td class="left"><a href="#status.301" id="rfc.xref.status.301.1" title="301 Moved Permanently">Section&nbsp;7.4.2</a></td>
     2151                  <td class="left"><a href="#status.301" id="rfc.xref.status.301.1" title="301 Moved Permanently">Section&nbsp;6.4.2</a></td>
    21632152               </tr>
    21642153               <tr>
    21652154                  <td class="left">302</td>
    21662155                  <td class="left">Found</td>
    2167                   <td class="left"><a href="#status.302" id="rfc.xref.status.302.1" title="302 Found">Section&nbsp;7.4.3</a></td>
     2156                  <td class="left"><a href="#status.302" id="rfc.xref.status.302.1" title="302 Found">Section&nbsp;6.4.3</a></td>
    21682157               </tr>
    21692158               <tr>
    21702159                  <td class="left">303</td>
    21712160                  <td class="left">See Other</td>
    2172                   <td class="left"><a href="#status.303" id="rfc.xref.status.303.1" title="303 See Other">Section&nbsp;7.4.4</a></td>
     2161                  <td class="left"><a href="#status.303" id="rfc.xref.status.303.1" title="303 See Other">Section&nbsp;6.4.4</a></td>
    21732162               </tr>
    21742163               <tr>
     
    21802169                  <td class="left">305</td>
    21812170                  <td class="left">Use Proxy</td>
    2182                   <td class="left"><a href="#status.305" id="rfc.xref.status.305.1" title="305 Use Proxy">Section&nbsp;7.4.5</a></td>
     2171                  <td class="left"><a href="#status.305" id="rfc.xref.status.305.1" title="305 Use Proxy">Section&nbsp;6.4.5</a></td>
    21832172               </tr>
    21842173               <tr>
    21852174                  <td class="left">307</td>
    21862175                  <td class="left">Temporary Redirect</td>
    2187                   <td class="left"><a href="#status.307" id="rfc.xref.status.307.1" title="307 Temporary Redirect">Section&nbsp;7.4.7</a></td>
     2176                  <td class="left"><a href="#status.307" id="rfc.xref.status.307.1" title="307 Temporary Redirect">Section&nbsp;6.4.7</a></td>
    21882177               </tr>
    21892178               <tr>
    21902179                  <td class="left">400</td>
    21912180                  <td class="left">Bad Request</td>
    2192                   <td class="left"><a href="#status.400" id="rfc.xref.status.400.1" title="400 Bad Request">Section&nbsp;7.5.1</a></td>
     2181                  <td class="left"><a href="#status.400" id="rfc.xref.status.400.1" title="400 Bad Request">Section&nbsp;6.5.1</a></td>
    21932182               </tr>
    21942183               <tr>
     
    22002189                  <td class="left">402</td>
    22012190                  <td class="left">Payment Required</td>
    2202                   <td class="left"><a href="#status.402" id="rfc.xref.status.402.1" title="402 Payment Required">Section&nbsp;7.5.2</a></td>
     2191                  <td class="left"><a href="#status.402" id="rfc.xref.status.402.1" title="402 Payment Required">Section&nbsp;6.5.2</a></td>
    22032192               </tr>
    22042193               <tr>
    22052194                  <td class="left">403</td>
    22062195                  <td class="left">Forbidden</td>
    2207                   <td class="left"><a href="#status.403" id="rfc.xref.status.403.1" title="403 Forbidden">Section&nbsp;7.5.3</a></td>
     2196                  <td class="left"><a href="#status.403" id="rfc.xref.status.403.1" title="403 Forbidden">Section&nbsp;6.5.3</a></td>
    22082197               </tr>
    22092198               <tr>
    22102199                  <td class="left">404</td>
    22112200                  <td class="left">Not Found</td>
    2212                   <td class="left"><a href="#status.404" id="rfc.xref.status.404.1" title="404 Not Found">Section&nbsp;7.5.4</a></td>
     2201                  <td class="left"><a href="#status.404" id="rfc.xref.status.404.1" title="404 Not Found">Section&nbsp;6.5.4</a></td>
    22132202               </tr>
    22142203               <tr>
    22152204                  <td class="left">405</td>
    22162205                  <td class="left">Method Not Allowed</td>
    2217                   <td class="left"><a href="#status.405" id="rfc.xref.status.405.1" title="405 Method Not Allowed">Section&nbsp;7.5.5</a></td>
     2206                  <td class="left"><a href="#status.405" id="rfc.xref.status.405.1" title="405 Method Not Allowed">Section&nbsp;6.5.5</a></td>
    22182207               </tr>
    22192208               <tr>
    22202209                  <td class="left">406</td>
    22212210                  <td class="left">Not Acceptable</td>
    2222                   <td class="left"><a href="#status.406" id="rfc.xref.status.406.1" title="406 Not Acceptable">Section&nbsp;7.5.6</a></td>
     2211                  <td class="left"><a href="#status.406" id="rfc.xref.status.406.1" title="406 Not Acceptable">Section&nbsp;6.5.6</a></td>
    22232212               </tr>
    22242213               <tr>
     
    22302219                  <td class="left">408</td>
    22312220                  <td class="left">Request Time-out</td>
    2232                   <td class="left"><a href="#status.408" id="rfc.xref.status.408.1" title="408 Request Timeout">Section&nbsp;7.5.7</a></td>
     2221                  <td class="left"><a href="#status.408" id="rfc.xref.status.408.1" title="408 Request Timeout">Section&nbsp;6.5.7</a></td>
    22332222               </tr>
    22342223               <tr>
    22352224                  <td class="left">409</td>
    22362225                  <td class="left">Conflict</td>
    2237                   <td class="left"><a href="#status.409" id="rfc.xref.status.409.1" title="409 Conflict">Section&nbsp;7.5.8</a></td>
     2226                  <td class="left"><a href="#status.409" id="rfc.xref.status.409.1" title="409 Conflict">Section&nbsp;6.5.8</a></td>
    22382227               </tr>
    22392228               <tr>
    22402229                  <td class="left">410</td>
    22412230                  <td class="left">Gone</td>
    2242                   <td class="left"><a href="#status.410" id="rfc.xref.status.410.1" title="410 Gone">Section&nbsp;7.5.9</a></td>
     2231                  <td class="left"><a href="#status.410" id="rfc.xref.status.410.1" title="410 Gone">Section&nbsp;6.5.9</a></td>
    22432232               </tr>
    22442233               <tr>
    22452234                  <td class="left">411</td>
    22462235                  <td class="left">Length Required</td>
    2247                   <td class="left"><a href="#status.411" id="rfc.xref.status.411.1" title="411 Length Required">Section&nbsp;7.5.10</a></td>
     2236                  <td class="left"><a href="#status.411" id="rfc.xref.status.411.1" title="411 Length Required">Section&nbsp;6.5.10</a></td>
    22482237               </tr>
    22492238               <tr>
     
    22552244                  <td class="left">413</td>
    22562245                  <td class="left">Request Representation Too Large</td>
    2257                   <td class="left"><a href="#status.413" id="rfc.xref.status.413.1" title="413 Request Representation Too Large">Section&nbsp;7.5.11</a></td>
     2246                  <td class="left"><a href="#status.413" id="rfc.xref.status.413.1" title="413 Request Representation Too Large">Section&nbsp;6.5.11</a></td>
    22582247               </tr>
    22592248               <tr>
    22602249                  <td class="left">414</td>
    22612250                  <td class="left">URI Too Long</td>
    2262                   <td class="left"><a href="#status.414" id="rfc.xref.status.414.1" title="414 URI Too Long">Section&nbsp;7.5.12</a></td>
     2251                  <td class="left"><a href="#status.414" id="rfc.xref.status.414.1" title="414 URI Too Long">Section&nbsp;6.5.12</a></td>
    22632252               </tr>
    22642253               <tr>
    22652254                  <td class="left">415</td>
    22662255                  <td class="left">Unsupported Media Type</td>
    2267                   <td class="left"><a href="#status.415" id="rfc.xref.status.415.1" title="415 Unsupported Media Type">Section&nbsp;7.5.13</a></td>
     2256                  <td class="left"><a href="#status.415" id="rfc.xref.status.415.1" title="415 Unsupported Media Type">Section&nbsp;6.5.13</a></td>
    22682257               </tr>
    22692258               <tr>
     
    22752264                  <td class="left">417</td>
    22762265                  <td class="left">Expectation Failed</td>
    2277                   <td class="left"><a href="#status.417" id="rfc.xref.status.417.1" title="417 Expectation Failed">Section&nbsp;7.5.14</a></td>
     2266                  <td class="left"><a href="#status.417" id="rfc.xref.status.417.1" title="417 Expectation Failed">Section&nbsp;6.5.14</a></td>
    22782267               </tr>
    22792268               <tr>
    22802269                  <td class="left">426</td>
    22812270                  <td class="left">Upgrade Required</td>
    2282                   <td class="left"><a href="#status.426" id="rfc.xref.status.426.1" title="426 Upgrade Required">Section&nbsp;7.5.15</a></td>
     2271                  <td class="left"><a href="#status.426" id="rfc.xref.status.426.1" title="426 Upgrade Required">Section&nbsp;6.5.15</a></td>
    22832272               </tr>
    22842273               <tr>
    22852274                  <td class="left">500</td>
    22862275                  <td class="left">Internal Server Error</td>
    2287                   <td class="left"><a href="#status.500" id="rfc.xref.status.500.1" title="500 Internal Server Error">Section&nbsp;7.6.1</a></td>
     2276                  <td class="left"><a href="#status.500" id="rfc.xref.status.500.1" title="500 Internal Server Error">Section&nbsp;6.6.1</a></td>
    22882277               </tr>
    22892278               <tr>
    22902279                  <td class="left">501</td>
    22912280                  <td class="left">Not Implemented</td>
    2292                   <td class="left"><a href="#status.501" id="rfc.xref.status.501.1" title="501 Not Implemented">Section&nbsp;7.6.2</a></td>
     2281                  <td class="left"><a href="#status.501" id="rfc.xref.status.501.1" title="501 Not Implemented">Section&nbsp;6.6.2</a></td>
    22932282               </tr>
    22942283               <tr>
    22952284                  <td class="left">502</td>
    22962285                  <td class="left">Bad Gateway</td>
    2297                   <td class="left"><a href="#status.502" id="rfc.xref.status.502.1" title="502 Bad Gateway">Section&nbsp;7.6.3</a></td>
     2286                  <td class="left"><a href="#status.502" id="rfc.xref.status.502.1" title="502 Bad Gateway">Section&nbsp;6.6.3</a></td>
    22982287               </tr>
    22992288               <tr>
    23002289                  <td class="left">503</td>
    23012290                  <td class="left">Service Unavailable</td>
    2302                   <td class="left"><a href="#status.503" id="rfc.xref.status.503.1" title="503 Service Unavailable">Section&nbsp;7.6.4</a></td>
     2291                  <td class="left"><a href="#status.503" id="rfc.xref.status.503.1" title="503 Service Unavailable">Section&nbsp;6.6.4</a></td>
    23032292               </tr>
    23042293               <tr>
    23052294                  <td class="left">504</td>
    23062295                  <td class="left">Gateway Time-out</td>
    2307                   <td class="left"><a href="#status.504" id="rfc.xref.status.504.1" title="504 Gateway Timeout">Section&nbsp;7.6.5</a></td>
     2296                  <td class="left"><a href="#status.504" id="rfc.xref.status.504.1" title="504 Gateway Timeout">Section&nbsp;6.6.5</a></td>
    23082297               </tr>
    23092298               <tr>
    23102299                  <td class="left">505</td>
    23112300                  <td class="left">HTTP Version not supported</td>
    2312                   <td class="left"><a href="#status.505" id="rfc.xref.status.505.1" title="505 HTTP Version Not Supported">Section&nbsp;7.6.6</a></td>
     2301                  <td class="left"><a href="#status.505" id="rfc.xref.status.505.1" title="505 HTTP Version Not Supported">Section&nbsp;6.6.6</a></td>
    23132302               </tr>
    23142303            </tbody>
    23152304         </table>
    23162305      </div>
    2317       <p id="rfc.section.7.1.p.2">Note that this list is not exhaustive — it does not include extension status codes defined in other specifications.</p>
    2318       <h2 id="rfc.section.7.2"><a href="#rfc.section.7.2">7.2</a>&nbsp;<a id="status.1xx" href="#status.1xx">Informational 1xx</a></h2>
     2306      <p id="rfc.section.6.1.p.2">Note that this list is not exhaustive — it does not include extension status codes defined in other specifications.</p>
     2307      <h2 id="rfc.section.6.2"><a href="#rfc.section.6.2">6.2</a>&nbsp;<a id="status.1xx" href="#status.1xx">Informational 1xx</a></h2>
    23192308      <div id="rfc.iref.54"></div>
    23202309      <div id="rfc.iref.s.3"></div>
    2321       <p id="rfc.section.7.2.p.1">This class of status code indicates a provisional response, consisting only of the status-line and optional header fields,
     2310      <p id="rfc.section.6.2.p.1">This class of status code indicates a provisional response, consisting only of the status-line and optional header fields,
    23222311         and is terminated by an empty line. There are no required header fields for this class of status code. Since HTTP/1.0 did
    23232312         not define any 1xx status codes, servers <em class="bcp14">MUST NOT</em> send a 1xx response to an HTTP/1.0 client except under experimental conditions.
    23242313      </p>
    2325       <p id="rfc.section.7.2.p.2">A client <em class="bcp14">MUST</em> be prepared to accept one or more 1xx status responses prior to a regular response, even if the client does not expect a <a href="#status.100" class="smpl">100
     2314      <p id="rfc.section.6.2.p.2">A client <em class="bcp14">MUST</em> be prepared to accept one or more 1xx status responses prior to a regular response, even if the client does not expect a <a href="#status.100" class="smpl">100
    23262315            (Continue)</a> status message. Unexpected 1xx status responses <em class="bcp14">MAY</em> be ignored by a user agent.
    23272316      </p>
    2328       <p id="rfc.section.7.2.p.3">Proxies <em class="bcp14">MUST</em> forward 1xx responses, unless the connection between the proxy and its client has been closed, or unless the proxy itself
     2317      <p id="rfc.section.6.2.p.3">Proxies <em class="bcp14">MUST</em> forward 1xx responses, unless the connection between the proxy and its client has been closed, or unless the proxy itself
    23292318         requested the generation of the 1xx response. (For example, if a proxy adds an "Expect: 100-continue" field when it forwards
    23302319         a request, then it need not forward the corresponding <a href="#status.100" class="smpl">100 (Continue)</a> response(s).)
    23312320      </p>
    23322321      <div id="rfc.iref.55"></div>
    2333       <h3 id="rfc.section.7.2.1"><a href="#rfc.section.7.2.1">7.2.1</a>&nbsp;<a id="status.100" href="#status.100">100 Continue</a></h3>
    2334       <p id="rfc.section.7.2.1.p.1">The client <em class="bcp14">SHOULD</em> continue with its request. This interim response is used to inform the client that the initial part of the request has been
     2322      <h3 id="rfc.section.6.2.1"><a href="#rfc.section.6.2.1">6.2.1</a>&nbsp;<a id="status.100" href="#status.100">100 Continue</a></h3>
     2323      <p id="rfc.section.6.2.1.p.1">The client <em class="bcp14">SHOULD</em> continue with its request. This interim response is used to inform the client that the initial part of the request has been
    23352324         received and has not yet been rejected by the server. The client <em class="bcp14">SHOULD</em> continue by sending the remainder of the request or, if the request has already been completed, ignore this response. The
    2336          server <em class="bcp14">MUST</em> send a final response after the request has been completed. See <a href="#use.of.the.100.status" title="Use of the 100 (Continue) Status">Section&nbsp;6.1.2.1</a> for detailed discussion of the use and handling of this status code.
     2325         server <em class="bcp14">MUST</em> send a final response after the request has been completed. See <a href="#use.of.the.100.status" title="Use of the 100 (Continue) Status">Section&nbsp;5.1.2.1</a> for detailed discussion of the use and handling of this status code.
    23372326      </p>
    23382327      <div id="rfc.iref.55"></div>
    2339       <h3 id="rfc.section.7.2.2"><a href="#rfc.section.7.2.2">7.2.2</a>&nbsp;<a id="status.101" href="#status.101">101 Switching Protocols</a></h3>
    2340       <p id="rfc.section.7.2.2.p.1">The server understands and is willing to comply with the client's request, via the <a href="p1-messaging.html#header.upgrade" class="smpl">Upgrade</a> message header field (<a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 6.3</a> of <a href="#Part1" id="rfc.xref.Part1.18"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>), for a change in the application protocol being used on this connection. The server will switch protocols to those defined
     2328      <h3 id="rfc.section.6.2.2"><a href="#rfc.section.6.2.2">6.2.2</a>&nbsp;<a id="status.101" href="#status.101">101 Switching Protocols</a></h3>
     2329      <p id="rfc.section.6.2.2.p.1">The server understands and is willing to comply with the client's request, via the <a href="p1-messaging.html#header.upgrade" class="smpl">Upgrade</a> message header field (<a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 6.3</a> of <a href="#Part1" id="rfc.xref.Part1.18"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>), for a change in the application protocol being used on this connection. The server will switch protocols to those defined
    23412330         by the response's Upgrade header field immediately after the empty line which terminates the 101 response.
    23422331      </p>
    2343       <p id="rfc.section.7.2.2.p.2">The protocol <em class="bcp14">SHOULD</em> be switched only when it is advantageous to do so. For example, switching to a newer version of HTTP is advantageous over
     2332      <p id="rfc.section.6.2.2.p.2">The protocol <em class="bcp14">SHOULD</em> be switched only when it is advantageous to do so. For example, switching to a newer version of HTTP is advantageous over
    23442333         older versions, and switching to a real-time, synchronous protocol might be advantageous when delivering resources that use
    23452334         such features.
    23462335      </p>
    2347       <h2 id="rfc.section.7.3"><a href="#rfc.section.7.3">7.3</a>&nbsp;<a id="status.2xx" href="#status.2xx">Successful 2xx</a></h2>
     2336      <h2 id="rfc.section.6.3"><a href="#rfc.section.6.3">6.3</a>&nbsp;<a id="status.2xx" href="#status.2xx">Successful 2xx</a></h2>
    23482337      <div id="rfc.iref.55"></div>
    23492338      <div id="rfc.iref.s.4"></div>
    2350       <p id="rfc.section.7.3.p.1">This class of status code indicates that the client's request was successfully received, understood, and accepted.</p>
     2339      <p id="rfc.section.6.3.p.1">This class of status code indicates that the client's request was successfully received, understood, and accepted.</p>
    23512340      <div id="rfc.iref.56"></div>
    2352       <h3 id="rfc.section.7.3.1"><a href="#rfc.section.7.3.1">7.3.1</a>&nbsp;<a id="status.200" href="#status.200">200 OK</a></h3>
    2353       <p id="rfc.section.7.3.1.p.1">The request has succeeded. The payload returned with the response is dependent on the method used in the request, for example: </p>
     2341      <h3 id="rfc.section.6.3.1"><a href="#rfc.section.6.3.1">6.3.1</a>&nbsp;<a id="status.200" href="#status.200">200 OK</a></h3>
     2342      <p id="rfc.section.6.3.1.p.1">The request has succeeded. The payload returned with the response is dependent on the method used in the request, for example: </p>
    23542343      <dl>
    23552344         <dt>GET</dt>
     
    23622351         <dd>a representation containing the request message as received by the end server.</dd>
    23632352      </dl>
    2364       <p id="rfc.section.7.3.1.p.2">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.1.2</a> of <a href="#Part6" id="rfc.xref.Part6.8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>) to determine freshness for 200 responses.
     2353      <p id="rfc.section.6.3.1.p.2">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.1.2</a> of <a href="#Part6" id="rfc.xref.Part6.8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>) to determine freshness for 200 responses.
    23652354      </p>
    23662355      <div id="rfc.iref.56"></div>
    2367       <h3 id="rfc.section.7.3.2"><a href="#rfc.section.7.3.2">7.3.2</a>&nbsp;<a id="status.201" href="#status.201">201 Created</a></h3>
    2368       <p id="rfc.section.7.3.2.p.1">The request has been fulfilled and has resulted in one or more new resources being created.</p>
    2369       <p id="rfc.section.7.3.2.p.2">Newly created resources are typically linked to from the response payload, with the most relevant URI also being carried in
     2356      <h3 id="rfc.section.6.3.2"><a href="#rfc.section.6.3.2">6.3.2</a>&nbsp;<a id="status.201" href="#status.201">201 Created</a></h3>
     2357      <p id="rfc.section.6.3.2.p.1">The request has been fulfilled and has resulted in one or more new resources being created.</p>
     2358      <p id="rfc.section.6.3.2.p.2">Newly created resources are typically linked to from the response payload, with the most relevant URI also being carried in
    23702359         the <a href="#header.location" class="smpl">Location</a> header field. If the newly created resource's URI is the same as the Effective Request URI, this information can be omitted
    23712360         (e.g., in the case of a response to a PUT request).
    23722361      </p>
    2373       <p id="rfc.section.7.3.2.p.3">The origin server <em class="bcp14">MUST</em> create the resource(s) before returning the 201 status code. If the action cannot be carried out immediately, the server <em class="bcp14">SHOULD</em> respond with <a href="#status.202" class="smpl">202 (Accepted)</a> response instead.
    2374       </p>
    2375       <p id="rfc.section.7.3.2.p.4">A 201 response <em class="bcp14">MAY</em> contain an <a href="p4-conditional.html#header.etag" class="smpl">ETag</a> response header field indicating the current value of the entity-tag for the representation of the resource identified by
     2362      <p id="rfc.section.6.3.2.p.3">The origin server <em class="bcp14">MUST</em> create the resource(s) before returning the 201 status code. If the action cannot be carried out immediately, the server <em class="bcp14">SHOULD</em> respond with <a href="#status.202" class="smpl">202 (Accepted)</a> response instead.
     2363      </p>
     2364      <p id="rfc.section.6.3.2.p.4">A 201 response <em class="bcp14">MAY</em> contain an <a href="p4-conditional.html#header.etag" class="smpl">ETag</a> response header field indicating the current value of the entity-tag for the representation of the resource identified by
    23762365         the <a href="#header.location" class="smpl">Location</a> header field or, in case the Location header field was omitted, by the Effective Request URI (see <a href="p4-conditional.html#header.etag" title="ETag">Section 2.3</a> of <a href="#Part4" id="rfc.xref.Part4.12"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>).
    23772366      </p>
    23782367      <div id="rfc.iref.56"></div>
    2379       <h3 id="rfc.section.7.3.3"><a href="#rfc.section.7.3.3">7.3.3</a>&nbsp;<a id="status.202" href="#status.202">202 Accepted</a></h3>
    2380       <p id="rfc.section.7.3.3.p.1">The request has been accepted for processing, but the processing has not been completed. The request might or might not eventually
     2368      <h3 id="rfc.section.6.3.3"><a href="#rfc.section.6.3.3">6.3.3</a>&nbsp;<a id="status.202" href="#status.202">202 Accepted</a></h3>
     2369      <p id="rfc.section.6.3.3.p.1">The request has been accepted for processing, but the processing has not been completed. The request might or might not eventually
    23812370         be acted upon, as it might be disallowed when processing actually takes place. There is no facility for re-sending a status
    23822371         code from an asynchronous operation such as this.
    23832372      </p>
    2384       <p id="rfc.section.7.3.3.p.2">The 202 response is intentionally non-committal. Its purpose is to allow a server to accept a request for some other process
     2373      <p id="rfc.section.6.3.3.p.2">The 202 response is intentionally non-committal. Its purpose is to allow a server to accept a request for some other process
    23852374         (perhaps a batch-oriented process that is only run once per day) without requiring that the user agent's connection to the
    23862375         server persist until the process is completed. The representation returned with this response <em class="bcp14">SHOULD</em> include an indication of the request's current status and either a pointer to a status monitor or some estimate of when the
     
    23882377      </p>
    23892378      <div id="rfc.iref.56"></div>
    2390       <h3 id="rfc.section.7.3.4"><a href="#rfc.section.7.3.4">7.3.4</a>&nbsp;<a id="status.203" href="#status.203">203 Non-Authoritative Information</a></h3>
    2391       <p id="rfc.section.7.3.4.p.1">The representation in the response has been transformed or otherwise modified by a transforming proxy (<a href="p1-messaging.html#intermediaries" title="Intermediaries">Section 2.3</a> of <a href="#Part1" id="rfc.xref.Part1.19"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>). Note that the behavior of transforming intermediaries is controlled by the no-transform Cache-Control directive (<a href="p6-cache.html#header.cache-control" title="Cache-Control">Section 7.2</a> of <a href="#Part6" id="rfc.xref.Part6.9"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
    2392       </p>
    2393       <p id="rfc.section.7.3.4.p.2">This status code is only appropriate when the response status code would have been <a href="#status.200" class="smpl">200 (OK)</a> otherwise. When the status code before transformation would have been different, the 214 Transformation Applied warn-code
     2379      <h3 id="rfc.section.6.3.4"><a href="#rfc.section.6.3.4">6.3.4</a>&nbsp;<a id="status.203" href="#status.203">203 Non-Authoritative Information</a></h3>
     2380      <p id="rfc.section.6.3.4.p.1">The representation in the response has been transformed or otherwise modified by a transforming proxy (<a href="p1-messaging.html#intermediaries" title="Intermediaries">Section 2.3</a> of <a href="#Part1" id="rfc.xref.Part1.19"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>). Note that the behavior of transforming intermediaries is controlled by the no-transform Cache-Control directive (<a href="p6-cache.html#header.cache-control" title="Cache-Control">Section 7.2</a> of <a href="#Part6" id="rfc.xref.Part6.9"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
     2381      </p>
     2382      <p id="rfc.section.6.3.4.p.2">This status code is only appropriate when the response status code would have been <a href="#status.200" class="smpl">200 (OK)</a> otherwise. When the status code before transformation would have been different, the 214 Transformation Applied warn-code
    23942383         (<a href="p6-cache.html#header.warning" title="Warning">Section 7.5</a> of <a href="#Part6" id="rfc.xref.Part6.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>) is appropriate.
    23952384      </p>
    2396       <p id="rfc.section.7.3.4.p.3">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.1.2</a> of <a href="#Part6" id="rfc.xref.Part6.11"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>) to determine freshness for 203 responses.
     2385      <p id="rfc.section.6.3.4.p.3">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.1.2</a> of <a href="#Part6" id="rfc.xref.Part6.11"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>) to determine freshness for 203 responses.
    23972386      </p>
    23982387      <div id="rfc.iref.56"></div>
    2399       <h3 id="rfc.section.7.3.5"><a href="#rfc.section.7.3.5">7.3.5</a>&nbsp;<a id="status.204" href="#status.204">204 No Content</a></h3>
    2400       <p id="rfc.section.7.3.5.p.1">The 204 (No Content) status code indicates that the server has successfully fulfilled the request and that there is no additional
     2388      <h3 id="rfc.section.6.3.5"><a href="#rfc.section.6.3.5">6.3.5</a>&nbsp;<a id="status.204" href="#status.204">204 No Content</a></h3>
     2389      <p id="rfc.section.6.3.5.p.1">The 204 (No Content) status code indicates that the server has successfully fulfilled the request and that there is no additional
    24012390         content to return in the response payload body. Metadata in the response header fields refer to the target resource and its
    24022391         current representation after the requested action.
    24032392      </p>
    2404       <p id="rfc.section.7.3.5.p.2">For example, if a 204 status code is received in response to a PUT request and the response contains an <a href="p4-conditional.html#header.etag" class="smpl">ETag</a> header field, then the PUT was successful and the ETag field-value contains the entity-tag for the new representation of that
     2393      <p id="rfc.section.6.3.5.p.2">For example, if a 204 status code is received in response to a PUT request and the response contains an <a href="p4-conditional.html#header.etag" class="smpl">ETag</a> header field, then the PUT was successful and the ETag field-value contains the entity-tag for the new representation of that
    24052394         target resource.
    24062395      </p>
    2407       <p id="rfc.section.7.3.5.p.3">The 204 response allows a server to indicate that the action has been successfully applied to the target resource while implying
     2396      <p id="rfc.section.6.3.5.p.3">The 204 response allows a server to indicate that the action has been successfully applied to the target resource while implying
    24082397         that the user agent <em class="bcp14">SHOULD NOT</em> traverse away from its current "document view" (if any). The server assumes that the user agent will provide some indication
    24092398         of the success to its user, in accord with its own interface, and apply any new or updated metadata in the response to the
    24102399         active representation.
    24112400      </p>
    2412       <p id="rfc.section.7.3.5.p.4">For example, a 204 status code is commonly used with document editing interfaces corresponding to a "save" action, such that
     2401      <p id="rfc.section.6.3.5.p.4">For example, a 204 status code is commonly used with document editing interfaces corresponding to a "save" action, such that
    24132402         the document being saved remains available to the user for editing. It is also frequently used with interfaces that expect
    24142403         automated data transfers to be prevalent, such as within distributed version control systems.
    24152404      </p>
    2416       <p id="rfc.section.7.3.5.p.5">The 204 response <em class="bcp14">MUST NOT</em> include a message body, and thus is always terminated by the first empty line after the header fields.
     2405      <p id="rfc.section.6.3.5.p.5">The 204 response <em class="bcp14">MUST NOT</em> include a message body, and thus is always terminated by the first empty line after the header fields.
    24172406      </p>
    24182407      <div id="rfc.iref.56"></div>
    2419       <h3 id="rfc.section.7.3.6"><a href="#rfc.section.7.3.6">7.3.6</a>&nbsp;<a id="status.205" href="#status.205">205 Reset Content</a></h3>
    2420       <p id="rfc.section.7.3.6.p.1">The server has fulfilled the request and the user agent <em class="bcp14">SHOULD</em> reset the document view which caused the request to be sent. This response is primarily intended to allow input for actions
     2408      <h3 id="rfc.section.6.3.6"><a href="#rfc.section.6.3.6">6.3.6</a>&nbsp;<a id="status.205" href="#status.205">205 Reset Content</a></h3>
     2409      <p id="rfc.section.6.3.6.p.1">The server has fulfilled the request and the user agent <em class="bcp14">SHOULD</em> reset the document view which caused the request to be sent. This response is primarily intended to allow input for actions
    24212410         to take place via user input, followed by a clearing of the form in which the input is given so that the user can easily initiate
    24222411         another input action.
    24232412      </p>
    2424       <p id="rfc.section.7.3.6.p.2">The message body included with the response <em class="bcp14">MUST</em> be empty. Note that receivers still need to parse the response according to the algorithm defined in <a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.20"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.
    2425       </p>
    2426       <h2 id="rfc.section.7.4"><a href="#rfc.section.7.4">7.4</a>&nbsp;<a id="status.3xx" href="#status.3xx">Redirection 3xx</a></h2>
     2413      <p id="rfc.section.6.3.6.p.2">The message body included with the response <em class="bcp14">MUST</em> be empty. Note that receivers still need to parse the response according to the algorithm defined in <a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.20"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.
     2414      </p>
     2415      <h2 id="rfc.section.6.4"><a href="#rfc.section.6.4">6.4</a>&nbsp;<a id="status.3xx" href="#status.3xx">Redirection 3xx</a></h2>
    24272416      <div id="rfc.iref.56"></div>
    24282417      <div id="rfc.iref.s.5"></div>
    2429       <p id="rfc.section.7.4.p.1">This class of status code indicates that further action needs to be taken by the user agent in order to fulfill the request.
     2418      <p id="rfc.section.6.4.p.1">This class of status code indicates that further action needs to be taken by the user agent in order to fulfill the request.
    24302419         If the required action involves a subsequent HTTP request, it <em class="bcp14">MAY</em> be carried out by the user agent without interaction with the user if and only if the method used in the second request is
    2431          known to be "safe", as defined in <a href="#safe.methods" title="Safe Methods">Section&nbsp;5.2.1</a>.
    2432       </p>
    2433       <p id="rfc.section.7.4.p.2">There are several types of redirects: </p>
     2420         known to be "safe", as defined in <a href="#safe.methods" title="Safe Methods">Section&nbsp;4.2.1</a>.
     2421      </p>
     2422      <p id="rfc.section.6.4.p.2">There are several types of redirects: </p>
    24342423      <ol>
    24352424         <li>
     
    24452434         </li>
    24462435         <li>
    2447             <p>Redirection offering a choice of matching resources for use by reactive content negotiation (<a href="#reactive.negotiation" title="Reactive Negotiation">Section&nbsp;3.5.2</a>). This is status code <a href="#status.300" class="smpl">300 (Multiple Choices)</a>.
     2436            <p>Redirection offering a choice of matching resources for use by reactive content negotiation (<a href="#reactive.negotiation" title="Reactive Negotiation">Section&nbsp;3.6.2</a>). This is status code <a href="#status.300" class="smpl">300 (Multiple Choices)</a>.
    24482437            </p>
    24492438         </li>
     
    24542443         </li>
    24552444      </ol>
    2456       <div class="note" id="rfc.section.7.4.p.3">
     2445      <div class="note" id="rfc.section.6.4.p.3">
    24572446         <p> <b>Note:</b> In HTTP/1.0, only the status codes <a href="#status.301" class="smpl">301 (Moved Permanently)</a> and <a href="#status.302" class="smpl">302 (Found)</a> were defined for the first type of redirect, and the second type did not exist at all (<a href="#RFC1945" id="rfc.xref.RFC1945.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.0">[RFC1945]</cite></a>, <a href="http://tools.ietf.org/html/rfc1945#section-9.3">Section 9.3</a>). However it turned out that web forms using POST expected redirects to change the operation for the subsequent request to
    24582447            retrieval (GET). To address this use case, HTTP/1.1 introduced the second type of redirect with the status code <a href="#status.303" class="smpl">303 (See Other)</a> (<a href="#RFC2068" id="rfc.xref.RFC2068.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>, <a href="http://tools.ietf.org/html/rfc2068#section-10.3.4">Section 10.3.4</a>). As user agents did not change their behavior to maintain backwards compatibility, the first revision of HTTP/1.1 added
     
    24602449         </p>
    24612450      </div>
    2462       <p id="rfc.section.7.4.p.4">A <a href="#header.location" class="smpl">Location</a> 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.2" title="Location">Section&nbsp;8.1.1</a>.
    2463       </p>
    2464       <p id="rfc.section.7.4.p.5">Note that for methods not known to be "safe", as defined in <a href="#safe.methods" title="Safe Methods">Section&nbsp;5.2.1</a>, automatic redirection needs to done with care, since the redirect might change the conditions under which the request was
     2451      <p id="rfc.section.6.4.p.4">A <a href="#header.location" class="smpl">Location</a> 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.2" title="Location">Section&nbsp;7.1.1</a>.
     2452      </p>
     2453      <p id="rfc.section.6.4.p.5">Note that for methods not known to be "safe", as defined in <a href="#safe.methods" title="Safe Methods">Section&nbsp;4.2.1</a>, automatic redirection needs to done with care, since the redirect might change the conditions under which the request was
    24652454         issued.
    24662455      </p>
    2467       <p id="rfc.section.7.4.p.6">Clients <em class="bcp14">SHOULD</em> detect and intervene in cyclical redirections (i.e., "infinite" redirection loops).
    2468       </p>
    2469       <div class="note" id="rfc.section.7.4.p.7">
     2456      <p id="rfc.section.6.4.p.6">Clients <em class="bcp14">SHOULD</em> detect and intervene in cyclical redirections (i.e., "infinite" redirection loops).
     2457      </p>
     2458      <div class="note" id="rfc.section.6.4.p.7">
    24702459         <p> <b>Note:</b> An earlier version of this specification recommended a maximum of five redirections (<a href="#RFC2068" id="rfc.xref.RFC2068.3"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>, <a href="http://tools.ietf.org/html/rfc2068#section-10.3">Section 10.3</a>). Content developers need to be aware that some clients might implement such a fixed limitation.
    24712460         </p>
    24722461      </div>
    24732462      <div id="rfc.iref.57"></div>
    2474       <h3 id="rfc.section.7.4.1"><a href="#rfc.section.7.4.1">7.4.1</a>&nbsp;<a id="status.300" href="#status.300">300 Multiple Choices</a></h3>
    2475       <p id="rfc.section.7.4.1.p.1">The target resource has more than one representation, each with its own specific location, and reactive negotiation information
    2476          (<a href="#content.negotiation" title="Content Negotiation">Section&nbsp;3.5</a>) is being provided so that the user (or user agent) can select a preferred representation by redirecting its request to that
     2463      <h3 id="rfc.section.6.4.1"><a href="#rfc.section.6.4.1">6.4.1</a>&nbsp;<a id="status.300" href="#status.300">300 Multiple Choices</a></h3>
     2464      <p id="rfc.section.6.4.1.p.1">The target resource has more than one representation, each with its own specific location, and reactive negotiation information
     2465         (<a href="#content.negotiation" title="Content Negotiation">Section&nbsp;3.6</a>) is being provided so that the user (or user agent) can select a preferred representation by redirecting its request to that
    24772466         location.
    24782467      </p>
    2479       <p id="rfc.section.7.4.1.p.2">Unless it was a HEAD request, the response <em class="bcp14">SHOULD</em> include a representation containing a list of representation metadata and location(s) from which the user or user agent can
     2468      <p id="rfc.section.6.4.1.p.2">Unless it was a HEAD request, the response <em class="bcp14">SHOULD</em> include a representation containing a list of representation metadata and location(s) from which the user or user agent can
    24802469         choose the one most appropriate. Depending upon the format and the capabilities of the user agent, selection of the most appropriate
    24812470         choice <em class="bcp14">MAY</em> be performed automatically. However, this specification does not define any standard for such automatic selection.
    24822471      </p>
    2483       <p id="rfc.section.7.4.1.p.3">If the server has a preferred choice of representation, it <em class="bcp14">SHOULD</em> include the specific URI for that representation in the <a href="#header.location" class="smpl">Location</a> field; user agents <em class="bcp14">MAY</em> use the Location field value for automatic redirection.
    2484       </p>
    2485       <p id="rfc.section.7.4.1.p.4">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.1.2</a> of <a href="#Part6" id="rfc.xref.Part6.12"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>) to determine freshness for 300 responses.
     2472      <p id="rfc.section.6.4.1.p.3">If the server has a preferred choice of representation, it <em class="bcp14">SHOULD</em> include the specific URI for that representation in the <a href="#header.location" class="smpl">Location</a> field; user agents <em class="bcp14">MAY</em> use the Location field value for automatic redirection.
     2473      </p>
     2474      <p id="rfc.section.6.4.1.p.4">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.1.2</a> of <a href="#Part6" id="rfc.xref.Part6.12"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>) to determine freshness for 300 responses.
    24862475      </p>
    24872476      <div id="rfc.iref.57"></div>
    2488       <h3 id="rfc.section.7.4.2"><a href="#rfc.section.7.4.2">7.4.2</a>&nbsp;<a id="status.301" href="#status.301">301 Moved Permanently</a></h3>
    2489       <p id="rfc.section.7.4.2.p.1">The target resource has been assigned a new permanent URI and any future references to this resource <em class="bcp14">SHOULD</em> use one of the returned URIs. Clients with link editing capabilities ought to automatically re-link references to the effective
     2477      <h3 id="rfc.section.6.4.2"><a href="#rfc.section.6.4.2">6.4.2</a>&nbsp;<a id="status.301" href="#status.301">301 Moved Permanently</a></h3>
     2478      <p id="rfc.section.6.4.2.p.1">The target resource has been assigned a new permanent URI and any future references to this resource <em class="bcp14">SHOULD</em> use one of the returned URIs. Clients with link editing capabilities ought to automatically re-link references to the effective
    24902479         request URI to one or more of the new references returned by the server, where possible.
    24912480      </p>
    2492       <p id="rfc.section.7.4.2.p.2">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.1.2</a> of <a href="#Part6" id="rfc.xref.Part6.13"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>) to determine freshness for 301 responses.
    2493       </p>
    2494       <p id="rfc.section.7.4.2.p.3">The new permanent URI <em class="bcp14">SHOULD</em> be given by the <a href="#header.location" class="smpl">Location</a> field in the response. A response payload can contain a short hypertext note with a hyperlink to the new URI(s).
    2495       </p>
    2496       <div class="note" id="rfc.section.7.4.2.p.4">
     2481      <p id="rfc.section.6.4.2.p.2">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.1.2</a> of <a href="#Part6" id="rfc.xref.Part6.13"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>) to determine freshness for 301 responses.
     2482      </p>
     2483      <p id="rfc.section.6.4.2.p.3">The new permanent URI <em class="bcp14">SHOULD</em> be given by the <a href="#header.location" class="smpl">Location</a> field in the response. A response payload can contain a short hypertext note with a hyperlink to the new URI(s).
     2484      </p>
     2485      <div class="note" id="rfc.section.6.4.2.p.4">
    24972486         <p> <b>Note:</b> For historic reasons, user agents <em class="bcp14">MAY</em> change the request method from POST to GET for the subsequent request. If this behavior is undesired, status code <a href="#status.307" class="smpl">307 (Temporary Redirect)</a> can be used instead.
    24982487         </p>
    24992488      </div>
    25002489      <div id="rfc.iref.57"></div>
    2501       <h3 id="rfc.section.7.4.3"><a href="#rfc.section.7.4.3">7.4.3</a>&nbsp;<a id="status.302" href="#status.302">302 Found</a></h3>
    2502       <p id="rfc.section.7.4.3.p.1">The target resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the client <em class="bcp14">SHOULD</em> continue to use the effective request URI for future requests.
    2503       </p>
    2504       <p id="rfc.section.7.4.3.p.2">The temporary URI <em class="bcp14">SHOULD</em> be given by the <a href="#header.location" class="smpl">Location</a> field in the response. A response payload can contain a short hypertext note with a hyperlink to the new URI(s).
    2505       </p>
    2506       <div class="note" id="rfc.section.7.4.3.p.3">
     2490      <h3 id="rfc.section.6.4.3"><a href="#rfc.section.6.4.3">6.4.3</a>&nbsp;<a id="status.302" href="#status.302">302 Found</a></h3>
     2491      <p id="rfc.section.6.4.3.p.1">The target resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the client <em class="bcp14">SHOULD</em> continue to use the effective request URI for future requests.
     2492      </p>
     2493      <p id="rfc.section.6.4.3.p.2">The temporary URI <em class="bcp14">SHOULD</em> be given by the <a href="#header.location" class="smpl">Location</a> field in the response. A response payload can contain a short hypertext note with a hyperlink to the new URI(s).
     2494      </p>
     2495      <div class="note" id="rfc.section.6.4.3.p.3">
    25072496         <p> <b>Note:</b> For historic reasons, user agents <em class="bcp14">MAY</em> change the request method from POST to GET for the subsequent request. If this behavior is undesired, status code <a href="#status.307" class="smpl">307 (Temporary Redirect)</a> can be used instead.
    25082497         </p>
    25092498      </div>
    25102499      <div id="rfc.iref.57"></div>
    2511       <h3 id="rfc.section.7.4.4"><a href="#rfc.section.7.4.4">7.4.4</a>&nbsp;<a id="status.303" href="#status.303">303 See Other</a></h3>
    2512       <p id="rfc.section.7.4.4.p.1">The 303 status code indicates that the server is redirecting the user agent to a different resource, as indicated by a URI
     2500      <h3 id="rfc.section.6.4.4"><a href="#rfc.section.6.4.4">6.4.4</a>&nbsp;<a id="status.303" href="#status.303">303 See Other</a></h3>
     2501      <p id="rfc.section.6.4.4.p.1">The 303 status code indicates that the server is redirecting the user agent to a different resource, as indicated by a URI
    25132502         in the <a href="#header.location" class="smpl">Location</a> header field, that is intended to provide an indirect response to the original request. In order to satisfy the original request,
    25142503         a user agent <em class="bcp14">SHOULD</em> perform a retrieval request using the Location URI (a GET or HEAD request if using HTTP), which can itself be redirected further,
     
    25162505         not considered equivalent to the effective request URI.
    25172506      </p>
    2518       <p id="rfc.section.7.4.4.p.2">This status code is generally applicable to any HTTP method. It is primarily used to allow the output of a POST action to
     2507      <p id="rfc.section.6.4.4.p.2">This status code is generally applicable to any HTTP method. It is primarily used to allow the output of a POST action to
    25192508         redirect the user agent to a selected resource, since doing so provides the information corresponding to the POST response
    25202509         in a form that can be separately identified, bookmarked, and cached independent of the original request.
    25212510      </p>
    2522       <p id="rfc.section.7.4.4.p.3">A 303 response to a GET request indicates that the requested resource does not have a representation of its own that can be
     2511      <p id="rfc.section.6.4.4.p.3">A 303 response to a GET request indicates that the requested resource does not have a representation of its own that can be
    25232512         transferred by the server over HTTP. The <a href="#header.location" class="smpl">Location</a> URI indicates a resource that is descriptive of the target resource, such that the follow-on representation might be useful
    25242513         to recipients without implying that it adequately represents the target resource. Note that answers to the questions of what
     
    25262515         and thus entirely determined by the URI owner(s).
    25272516      </p>
    2528       <p id="rfc.section.7.4.4.p.4">Except for responses to a HEAD request, the representation of a 303 response <em class="bcp14">SHOULD</em> contain a short hypertext note with a hyperlink to the <a href="#header.location" class="smpl">Location</a> URI.
     2517      <p id="rfc.section.6.4.4.p.4">Except for responses to a HEAD request, the representation of a 303 response <em class="bcp14">SHOULD</em> contain a short hypertext note with a hyperlink to the <a href="#header.location" class="smpl">Location</a> URI.
    25292518      </p>
    25302519      <div id="rfc.iref.57"></div>
    2531       <h3 id="rfc.section.7.4.5"><a href="#rfc.section.7.4.5">7.4.5</a>&nbsp;<a id="status.305" href="#status.305">305 Use Proxy</a></h3>
    2532       <p id="rfc.section.7.4.5.p.1">The 305 status code was defined in a previous version of this specification (see <a href="#changes.from.rfc.2616" title="Changes from RFC 2616">Appendix&nbsp;C</a>), and is now deprecated.
     2520      <h3 id="rfc.section.6.4.5"><a href="#rfc.section.6.4.5">6.4.5</a>&nbsp;<a id="status.305" href="#status.305">305 Use Proxy</a></h3>
     2521      <p id="rfc.section.6.4.5.p.1">The 305 status code was defined in a previous version of this specification (see <a href="#changes.from.rfc.2616" title="Changes from RFC 2616">Appendix&nbsp;C</a>), and is now deprecated.
    25332522      </p>
    25342523      <div id="rfc.iref.57"></div>
    2535       <h3 id="rfc.section.7.4.6"><a href="#rfc.section.7.4.6">7.4.6</a>&nbsp;<a id="status.306" href="#status.306">306 (Unused)</a></h3>
    2536       <p id="rfc.section.7.4.6.p.1">The 306 status code was used in a previous version of the specification, is no longer used, and the code is reserved.</p>
     2524      <h3 id="rfc.section.6.4.6"><a href="#rfc.section.6.4.6">6.4.6</a>&nbsp;<a id="status.306" href="#status.306">306 (Unused)</a></h3>
     2525      <p id="rfc.section.6.4.6.p.1">The 306 status code was used in a previous version of the specification, is no longer used, and the code is reserved.</p>
    25372526      <div id="rfc.iref.57"></div>
    2538       <h3 id="rfc.section.7.4.7"><a href="#rfc.section.7.4.7">7.4.7</a>&nbsp;<a id="status.307" href="#status.307">307 Temporary Redirect</a></h3>
    2539       <p id="rfc.section.7.4.7.p.1">The target resource resides temporarily under a different URI. Since the redirection can change over time, the client <em class="bcp14">SHOULD</em> continue to use the effective request URI for future requests.
    2540       </p>
    2541       <p id="rfc.section.7.4.7.p.2">The temporary URI <em class="bcp14">SHOULD</em> be given by the <a href="#header.location" class="smpl">Location</a> field in the response. A response payload can contain a short hypertext note with a hyperlink to the new URI(s).
    2542       </p>
    2543       <div class="note" id="rfc.section.7.4.7.p.3">
     2527      <h3 id="rfc.section.6.4.7"><a href="#rfc.section.6.4.7">6.4.7</a>&nbsp;<a id="status.307" href="#status.307">307 Temporary Redirect</a></h3>
     2528      <p id="rfc.section.6.4.7.p.1">The target resource resides temporarily under a different URI. Since the redirection can change over time, the client <em class="bcp14">SHOULD</em> continue to use the effective request URI for future requests.
     2529      </p>
     2530      <p id="rfc.section.6.4.7.p.2">The temporary URI <em class="bcp14">SHOULD</em> be given by the <a href="#header.location" class="smpl">Location</a> field in the response. A response payload can contain a short hypertext note with a hyperlink to the new URI(s).
     2531      </p>
     2532      <div class="note" id="rfc.section.6.4.7.p.3">
    25442533         <p> <b>Note:</b> This status code is similar to <a href="#status.302" class="smpl">302 (Found)</a>, except that it does not allow rewriting the request method from POST to GET. This specification defines no equivalent counterpart
    25452534            for <a href="#status.301" class="smpl">301 (Moved
     
    25472536         </p>
    25482537      </div>
    2549       <h2 id="rfc.section.7.5"><a href="#rfc.section.7.5">7.5</a>&nbsp;<a id="status.4xx" href="#status.4xx">Client Error 4xx</a></h2>
     2538      <h2 id="rfc.section.6.5"><a href="#rfc.section.6.5">6.5</a>&nbsp;<a id="status.4xx" href="#status.4xx">Client Error 4xx</a></h2>
    25502539      <div id="rfc.iref.57"></div>
    25512540      <div id="rfc.iref.s.6"></div>
    2552       <p id="rfc.section.7.5.p.1">The 4xx class of status code is intended for cases in which the client seems to have erred. Except when responding to a HEAD
     2541      <p id="rfc.section.6.5.p.1">The 4xx class of status code is intended for cases in which the client seems to have erred. Except when responding to a HEAD
    25532542         request, the server <em class="bcp14">SHOULD</em> include a representation containing an explanation of the error situation, and whether it is a temporary or permanent condition.
    25542543         These status codes are applicable to any request method. User agents <em class="bcp14">SHOULD</em> display any included representation to the user.
    25552544      </p>
    25562545      <div id="rfc.iref.58"></div>
    2557       <h3 id="rfc.section.7.5.1"><a href="#rfc.section.7.5.1">7.5.1</a>&nbsp;<a id="status.400" href="#status.400">400 Bad Request</a></h3>
    2558       <p id="rfc.section.7.5.1.p.1">The server cannot or will not process the request, due to a client error (e.g., malformed syntax).</p>
     2546      <h3 id="rfc.section.6.5.1"><a href="#rfc.section.6.5.1">6.5.1</a>&nbsp;<a id="status.400" href="#status.400">400 Bad Request</a></h3>
     2547      <p id="rfc.section.6.5.1.p.1">The server cannot or will not process the request, due to a client error (e.g., malformed syntax).</p>
    25592548      <div id="rfc.iref.58"></div>
    2560       <h3 id="rfc.section.7.5.2"><a href="#rfc.section.7.5.2">7.5.2</a>&nbsp;<a id="status.402" href="#status.402">402 Payment Required</a></h3>
    2561       <p id="rfc.section.7.5.2.p.1">This code is reserved for future use.</p>
     2549      <h3 id="rfc.section.6.5.2"><a href="#rfc.section.6.5.2">6.5.2</a>&nbsp;<a id="status.402" href="#status.402">402 Payment Required</a></h3>
     2550      <p id="rfc.section.6.5.2.p.1">This code is reserved for future use.</p>
    25622551      <div id="rfc.iref.58"></div>
    2563       <h3 id="rfc.section.7.5.3"><a href="#rfc.section.7.5.3">7.5.3</a>&nbsp;<a id="status.403" href="#status.403">403 Forbidden</a></h3>
    2564       <p id="rfc.section.7.5.3.p.1">The server understood the request, but refuses to authorize it. Providing different user authentication credentials might
     2552      <h3 id="rfc.section.6.5.3"><a href="#rfc.section.6.5.3">6.5.3</a>&nbsp;<a id="status.403" href="#status.403">403 Forbidden</a></h3>
     2553      <p id="rfc.section.6.5.3.p.1">The server understood the request, but refuses to authorize it. Providing different user authentication credentials might
    25652554         be successful, but any credentials that were provided in the request are insufficient. The request <em class="bcp14">SHOULD NOT</em> be repeated with the same credentials.
    25662555      </p>
    2567       <p id="rfc.section.7.5.3.p.2">If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled, it <em class="bcp14">SHOULD</em> describe the reason for the refusal in the representation. If the server does not wish to make this information available
     2556      <p id="rfc.section.6.5.3.p.2">If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled, it <em class="bcp14">SHOULD</em> describe the reason for the refusal in the representation. If the server does not wish to make this information available
    25682557         to the client, the status code <a href="#status.404" class="smpl">404
    25692558            (Not Found)</a>  <em class="bcp14">MAY</em> be used instead.
    25702559      </p>
    25712560      <div id="rfc.iref.58"></div>
    2572       <h3 id="rfc.section.7.5.4"><a href="#rfc.section.7.5.4">7.5.4</a>&nbsp;<a id="status.404" href="#status.404">404 Not Found</a></h3>
    2573       <p id="rfc.section.7.5.4.p.1">The server has not found anything matching the effective request URI. No indication is given of whether the condition is temporary
     2561      <h3 id="rfc.section.6.5.4"><a href="#rfc.section.6.5.4">6.5.4</a>&nbsp;<a id="status.404" href="#status.404">404 Not Found</a></h3>
     2562      <p id="rfc.section.6.5.4.p.1">The server has not found anything matching the effective request URI. No indication is given of whether the condition is temporary
    25742563         or permanent. The <a href="#status.410" class="smpl">410 (Gone)</a> status code <em class="bcp14">SHOULD</em> be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable
    25752564         and has no forwarding address. This status code is commonly used when the server does not wish to reveal exactly why the request
     
    25772566      </p>
    25782567      <div id="rfc.iref.58"></div>
    2579       <h3 id="rfc.section.7.5.5"><a href="#rfc.section.7.5.5">7.5.5</a>&nbsp;<a id="status.405" href="#status.405">405 Method Not Allowed</a></h3>
    2580       <p id="rfc.section.7.5.5.p.1">The method specified in the request-line is not allowed for the target resource. The response <em class="bcp14">MUST</em> include an <a href="#header.allow" class="smpl">Allow</a> header field containing a list of valid methods for the requested resource.
     2568      <h3 id="rfc.section.6.5.5"><a href="#rfc.section.6.5.5">6.5.5</a>&nbsp;<a id="status.405" href="#status.405">405 Method Not Allowed</a></h3>
     2569      <p id="rfc.section.6.5.5.p.1">The method specified in the request-line is not allowed for the target resource. The response <em class="bcp14">MUST</em> include an <a href="#header.allow" class="smpl">Allow</a> header field containing a list of valid methods for the requested resource.
    25812570      </p>
    25822571      <div id="rfc.iref.58"></div>
    2583       <h3 id="rfc.section.7.5.6"><a href="#rfc.section.7.5.6">7.5.6</a>&nbsp;<a id="status.406" href="#status.406">406 Not Acceptable</a></h3>
    2584       <p id="rfc.section.7.5.6.p.1">The resource identified by the request is only capable of generating response representations which have content characteristics
     2572      <h3 id="rfc.section.6.5.6"><a href="#rfc.section.6.5.6">6.5.6</a>&nbsp;<a id="status.406" href="#status.406">406 Not Acceptable</a></h3>
     2573      <p id="rfc.section.6.5.6.p.1">The resource identified by the request is only capable of generating response representations which have content characteristics
    25852574         not acceptable according to the <a href="#header.accept" class="smpl">Accept</a> and Accept-* header fields sent in the request.
    25862575      </p>
    2587       <p id="rfc.section.7.5.6.p.2">Unless it was a HEAD request, the response <em class="bcp14">SHOULD</em> include a representation containing a list of available representation characteristics and location(s) from which the user
     2576      <p id="rfc.section.6.5.6.p.2">Unless it was a HEAD request, the response <em class="bcp14">SHOULD</em> include a representation containing a list of available representation characteristics and location(s) from which the user
    25882577         or user agent can choose the one most appropriate. Depending upon the format and the capabilities of the user agent, selection
    25892578         of the most appropriate choice <em class="bcp14">MAY</em> be performed automatically. However, this specification does not define any standard for such automatic selection.
    25902579      </p>
    2591       <div class="note" id="rfc.section.7.5.6.p.3">
     2580      <div class="note" id="rfc.section.6.5.6.p.3">
    25922581         <p> <b>Note:</b> HTTP/1.1 servers are allowed to return responses which are not acceptable according to the accept header fields sent in the
    25932582            request. In some cases, this might even be preferable to sending a 406 response. User agents are encouraged to inspect the
     
    25952584         </p>
    25962585      </div>
    2597       <p id="rfc.section.7.5.6.p.4">If the response could be unacceptable, a user agent <em class="bcp14">SHOULD</em> temporarily stop receipt of more data and query the user for a decision on further actions.
     2586      <p id="rfc.section.6.5.6.p.4">If the response could be unacceptable, a user agent <em class="bcp14">SHOULD</em> temporarily stop receipt of more data and query the user for a decision on further actions.
    25982587      </p>
    25992588      <div id="rfc.iref.58"></div>
    2600       <h3 id="rfc.section.7.5.7"><a href="#rfc.section.7.5.7">7.5.7</a>&nbsp;<a id="status.408" href="#status.408">408 Request Timeout</a></h3>
    2601       <p id="rfc.section.7.5.7.p.1">The client did not produce a request within the time that the server was prepared to wait. The client <em class="bcp14">MAY</em> repeat the request without modifications at any later time.
     2589      <h3 id="rfc.section.6.5.7"><a href="#rfc.section.6.5.7">6.5.7</a>&nbsp;<a id="status.408" href="#status.408">408 Request Timeout</a></h3>
     2590      <p id="rfc.section.6.5.7.p.1">The client did not produce a request within the time that the server was prepared to wait. The client <em class="bcp14">MAY</em> repeat the request without modifications at any later time.
    26022591      </p>
    26032592      <div id="rfc.iref.58"></div>
    2604       <h3 id="rfc.section.7.5.8"><a href="#rfc.section.7.5.8">7.5.8</a>&nbsp;<a id="status.409" href="#status.409">409 Conflict</a></h3>
    2605       <p id="rfc.section.7.5.8.p.1">The request could not be completed due to a conflict with the current state of the resource. This code is only allowed in
     2593      <h3 id="rfc.section.6.5.8"><a href="#rfc.section.6.5.8">6.5.8</a>&nbsp;<a id="status.409" href="#status.409">409 Conflict</a></h3>
     2594      <p id="rfc.section.6.5.8.p.1">The request could not be completed due to a conflict with the current state of the resource. This code is only allowed in
    26062595         situations where it is expected that the user might be able to resolve the conflict and resubmit the request. The response
    26072596         body <em class="bcp14">SHOULD</em> include enough information for the user to recognize the source of the conflict. Ideally, the response representation would
    26082597         include enough information for the user or user agent to fix the problem; however, that might not be possible and is not required.
    26092598      </p>
    2610       <p id="rfc.section.7.5.8.p.2">Conflicts are most likely to occur in response to a PUT request. For example, if versioning were being used and the representation
     2599      <p id="rfc.section.6.5.8.p.2">Conflicts are most likely to occur in response to a PUT request. For example, if versioning were being used and the representation
    26112600         being PUT included changes to a resource which conflict with those made by an earlier (third-party) request, the server might
    26122601         use the 409 response to indicate that it can't complete the request. In this case, the response representation would likely
     
    26142603      </p>
    26152604      <div id="rfc.iref.58"></div>
    2616       <h3 id="rfc.section.7.5.9"><a href="#rfc.section.7.5.9">7.5.9</a>&nbsp;<a id="status.410" href="#status.410">410 Gone</a></h3>
    2617       <p id="rfc.section.7.5.9.p.1">The target resource is no longer available at the server and no forwarding address is known. This condition is expected to
     2605      <h3 id="rfc.section.6.5.9"><a href="#rfc.section.6.5.9">6.5.9</a>&nbsp;<a id="status.410" href="#status.410">410 Gone</a></h3>
     2606      <p id="rfc.section.6.5.9.p.1">The target resource is no longer available at the server and no forwarding address is known. This condition is expected to
    26182607         be considered permanent. Clients with link editing capabilities <em class="bcp14">SHOULD</em> delete references to the effective request URI after user approval. If the server does not know, or has no facility to determine,
    26192608         whether or not the condition is permanent, the status code <a href="#status.404" class="smpl">404 (Not Found)</a>  <em class="bcp14">SHOULD</em> be used instead.
    26202609      </p>
    2621       <p id="rfc.section.7.5.9.p.2">The 410 response is primarily intended to assist the task of web maintenance by notifying the recipient that the resource
     2610      <p id="rfc.section.6.5.9.p.2">The 410 response is primarily intended to assist the task of web maintenance by notifying the recipient that the resource
    26222611         is intentionally unavailable and that the server owners desire that remote links to that resource be removed. Such an event
    26232612         is common for limited-time, promotional services and for resources belonging to individuals no longer working at the server's
     
    26252614         — that is left to the discretion of the server owner.
    26262615      </p>
    2627       <p id="rfc.section.7.5.9.p.3">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.1.2</a> of <a href="#Part6" id="rfc.xref.Part6.14"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>) to determine freshness for 410 responses.
     2616      <p id="rfc.section.6.5.9.p.3">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.1.2</a> of <a href="#Part6" id="rfc.xref.Part6.14"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>) to determine freshness for 410 responses.
    26282617      </p>
    26292618      <div id="rfc.iref.58"></div>
    2630       <h3 id="rfc.section.7.5.10"><a href="#rfc.section.7.5.10">7.5.10</a>&nbsp;<a id="status.411" href="#status.411">411 Length Required</a></h3>
    2631       <p id="rfc.section.7.5.10.p.1">The server refuses to accept the request without a defined <a href="p1-messaging.html#header.content-length" class="smpl">Content-Length</a>. The client <em class="bcp14">MAY</em> repeat the request if it adds a valid Content-Length header field containing the length of the message body in the request
     2619      <h3 id="rfc.section.6.5.10"><a href="#rfc.section.6.5.10">6.5.10</a>&nbsp;<a id="status.411" href="#status.411">411 Length Required</a></h3>
     2620      <p id="rfc.section.6.5.10.p.1">The server refuses to accept the request without a defined <a href="p1-messaging.html#header.content-length" class="smpl">Content-Length</a>. The client <em class="bcp14">MAY</em> repeat the request if it adds a valid Content-Length header field containing the length of the message body in the request
    26322621         message.
    26332622      </p>
    26342623      <div id="rfc.iref.58"></div>
    2635       <h3 id="rfc.section.7.5.11"><a href="#rfc.section.7.5.11">7.5.11</a>&nbsp;<a id="status.413" href="#status.413">413 Request Representation Too Large</a></h3>
    2636       <p id="rfc.section.7.5.11.p.1">The server is refusing to process a request because the request representation is larger than the server is willing or able
     2624      <h3 id="rfc.section.6.5.11"><a href="#rfc.section.6.5.11">6.5.11</a>&nbsp;<a id="status.413" href="#status.413">413 Request Representation Too Large</a></h3>
     2625      <p id="rfc.section.6.5.11.p.1">The server is refusing to process a request because the request representation is larger than the server is willing or able
    26372626         to process. The server <em class="bcp14">MAY</em> close the connection to prevent the client from continuing the request.
    26382627      </p>
    2639       <p id="rfc.section.7.5.11.p.2">If the condition is temporary, the server <em class="bcp14">SHOULD</em> include a <a href="#header.retry-after" class="smpl">Retry-After</a> header field to indicate that it is temporary and after what time the client <em class="bcp14">MAY</em> try again.
     2628      <p id="rfc.section.6.5.11.p.2">If the condition is temporary, the server <em class="bcp14">SHOULD</em> include a <a href="#header.retry-after" class="smpl">Retry-After</a> header field to indicate that it is temporary and after what time the client <em class="bcp14">MAY</em> try again.
    26402629      </p>
    26412630      <div id="rfc.iref.58"></div>
    2642       <h3 id="rfc.section.7.5.12"><a href="#rfc.section.7.5.12">7.5.12</a>&nbsp;<a id="status.414" href="#status.414">414 URI Too Long</a></h3>
    2643       <p id="rfc.section.7.5.12.p.1">The server is refusing to service the request because the effective request URI is longer than the server is willing to interpret.
     2631      <h3 id="rfc.section.6.5.12"><a href="#rfc.section.6.5.12">6.5.12</a>&nbsp;<a id="status.414" href="#status.414">414 URI Too Long</a></h3>
     2632      <p id="rfc.section.6.5.12.p.1">The server is refusing to service the request because the effective request URI is longer than the server is willing to interpret.
    26442633         This rare condition is only likely to occur when a client has improperly converted a POST request to a GET request with long
    26452634         query information, when the client has descended into a URI "black hole" of redirection (e.g., a redirected URI prefix that
     
    26482637      </p>
    26492638      <div id="rfc.iref.58"></div>
    2650       <h3 id="rfc.section.7.5.13"><a href="#rfc.section.7.5.13">7.5.13</a>&nbsp;<a id="status.415" href="#status.415">415 Unsupported Media Type</a></h3>
    2651       <p id="rfc.section.7.5.13.p.1">The server is refusing to service the request because the request payload is in a format not supported by this request method
     2639      <h3 id="rfc.section.6.5.13"><a href="#rfc.section.6.5.13">6.5.13</a>&nbsp;<a id="status.415" href="#status.415">415 Unsupported Media Type</a></h3>
     2640      <p id="rfc.section.6.5.13.p.1">The server is refusing to service the request because the request payload is in a format not supported by this request method
    26522641         on the target resource.
    26532642      </p>
    26542643      <div id="rfc.iref.58"></div>
    2655       <h3 id="rfc.section.7.5.14"><a href="#rfc.section.7.5.14">7.5.14</a>&nbsp;<a id="status.417" href="#status.417">417 Expectation Failed</a></h3>
    2656       <p id="rfc.section.7.5.14.p.1">The expectation given in an <a href="#header.expect" class="smpl">Expect</a> header field (see <a href="#header.expect" id="rfc.xref.header.expect.2" title="Expect">Section&nbsp;6.1.2</a>) could not be met by this server, or, if the server is a proxy, the server has unambiguous evidence that the request could
     2644      <h3 id="rfc.section.6.5.14"><a href="#rfc.section.6.5.14">6.5.14</a>&nbsp;<a id="status.417" href="#status.417">417 Expectation Failed</a></h3>
     2645      <p id="rfc.section.6.5.14.p.1">The expectation given in an <a href="#header.expect" class="smpl">Expect</a> header field (see <a href="#header.expect" id="rfc.xref.header.expect.2" title="Expect">Section&nbsp;5.1.2</a>) could not be met by this server, or, if the server is a proxy, the server has unambiguous evidence that the request could
    26572646         not be met by the next-hop server.
    26582647      </p>
    26592648      <div id="rfc.iref.58"></div>
    2660       <h3 id="rfc.section.7.5.15"><a href="#rfc.section.7.5.15">7.5.15</a>&nbsp;<a id="status.426" href="#status.426">426 Upgrade Required</a></h3>
    2661       <p id="rfc.section.7.5.15.p.1">The request can not be completed without a prior protocol upgrade. This response <em class="bcp14">MUST</em> include an <a href="p1-messaging.html#header.upgrade" class="smpl">Upgrade</a> header field (<a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 6.3</a> of <a href="#Part1" id="rfc.xref.Part1.21"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) specifying the required protocols.
     2649      <h3 id="rfc.section.6.5.15"><a href="#rfc.section.6.5.15">6.5.15</a>&nbsp;<a id="status.426" href="#status.426">426 Upgrade Required</a></h3>
     2650      <p id="rfc.section.6.5.15.p.1">The request can not be completed without a prior protocol upgrade. This response <em class="bcp14">MUST</em> include an <a href="p1-messaging.html#header.upgrade" class="smpl">Upgrade</a> header field (<a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 6.3</a> of <a href="#Part1" id="rfc.xref.Part1.21"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) specifying the required protocols.
    26622651      </p>
    26632652      <div id="rfc.figure.u.33"></div>
     
    26692658
    26702659<span id="s426body">This service requires use of the HTTP/3.0 protocol.
    2671 </span></pre><p id="rfc.section.7.5.15.p.3">The server <em class="bcp14">SHOULD</em> include a message body in the 426 response which indicates in human readable form the reason for the error and describes any
     2660</span></pre><p id="rfc.section.6.5.15.p.3">The server <em class="bcp14">SHOULD</em> include a message body in the 426 response which indicates in human readable form the reason for the error and describes any
    26722661         alternative courses which might be available to the user.
    26732662      </p>
    2674       <h2 id="rfc.section.7.6"><a href="#rfc.section.7.6">7.6</a>&nbsp;<a id="status.5xx" href="#status.5xx">Server Error 5xx</a></h2>
     2663      <h2 id="rfc.section.6.6"><a href="#rfc.section.6.6">6.6</a>&nbsp;<a id="status.5xx" href="#status.5xx">Server Error 5xx</a></h2>
    26752664      <div id="rfc.iref.58"></div>
    26762665      <div id="rfc.iref.s.7"></div>
    2677       <p id="rfc.section.7.6.p.1">Response status codes beginning with the digit "5" indicate cases in which the server is aware that it has erred or is incapable
     2666      <p id="rfc.section.6.6.p.1">Response status codes beginning with the digit "5" indicate cases in which the server is aware that it has erred or is incapable
    26782667         of performing the request. Except when responding to a HEAD request, the server <em class="bcp14">SHOULD</em> include a representation containing an explanation of the error situation, and whether it is a temporary or permanent condition.
    26792668         User agents <em class="bcp14">SHOULD</em> display any included representation to the user. These response codes are applicable to any request method.
    26802669      </p>
    26812670      <div id="rfc.iref.59"></div>
    2682       <h3 id="rfc.section.7.6.1"><a href="#rfc.section.7.6.1">7.6.1</a>&nbsp;<a id="status.500" href="#status.500">500 Internal Server Error</a></h3>
    2683       <p id="rfc.section.7.6.1.p.1">The server encountered an unexpected condition which prevented it from fulfilling the request.</p>
     2671      <h3 id="rfc.section.6.6.1"><a href="#rfc.section.6.6.1">6.6.1</a>&nbsp;<a id="status.500" href="#status.500">500 Internal Server Error</a></h3>
     2672      <p id="rfc.section.6.6.1.p.1">The server encountered an unexpected condition which prevented it from fulfilling the request.</p>
    26842673      <div id="rfc.iref.59"></div>
    2685       <h3 id="rfc.section.7.6.2"><a href="#rfc.section.7.6.2">7.6.2</a>&nbsp;<a id="status.501" href="#status.501">501 Not Implemented</a></h3>
    2686       <p id="rfc.section.7.6.2.p.1">The server does not support the functionality required to fulfill the request. This is the appropriate response when the server
     2674      <h3 id="rfc.section.6.6.2"><a href="#rfc.section.6.6.2">6.6.2</a>&nbsp;<a id="status.501" href="#status.501">501 Not Implemented</a></h3>
     2675      <p id="rfc.section.6.6.2.p.1">The server does not support the functionality required to fulfill the request. This is the appropriate response when the server
    26872676         does not recognize the request method and is not capable of supporting it for any resource.
    26882677      </p>
    26892678      <div id="rfc.iref.59"></div>
    2690       <h3 id="rfc.section.7.6.3"><a href="#rfc.section.7.6.3">7.6.3</a>&nbsp;<a id="status.502" href="#status.502">502 Bad Gateway</a></h3>
    2691       <p id="rfc.section.7.6.3.p.1">The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting
     2679      <h3 id="rfc.section.6.6.3"><a href="#rfc.section.6.6.3">6.6.3</a>&nbsp;<a id="status.502" href="#status.502">502 Bad Gateway</a></h3>
     2680      <p id="rfc.section.6.6.3.p.1">The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting
    26922681         to fulfill the request.
    26932682      </p>
    26942683      <div id="rfc.iref.59"></div>
    2695       <h3 id="rfc.section.7.6.4"><a href="#rfc.section.7.6.4">7.6.4</a>&nbsp;<a id="status.503" href="#status.503">503 Service Unavailable</a></h3>
    2696       <p id="rfc.section.7.6.4.p.1">The server is currently unable to handle the request due to a temporary overloading or maintenance of the server.</p>
    2697       <p id="rfc.section.7.6.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
    2698          delay <em class="bcp14">MAY</em> be indicated in a <a href="#header.retry-after" class="smpl">Retry-After</a> header field (<a href="#header.retry-after" id="rfc.xref.header.retry-after.1" title="Retry-After">Section&nbsp;8.1.2</a>). If no Retry-After is given, the client <em class="bcp14">SHOULD</em> handle the response as it would for a <a href="#status.500" class="smpl">500 (Internal
     2684      <h3 id="rfc.section.6.6.4"><a href="#rfc.section.6.6.4">6.6.4</a>&nbsp;<a id="status.503" href="#status.503">503 Service Unavailable</a></h3>
     2685      <p id="rfc.section.6.6.4.p.1">The server is currently unable to handle the request due to a temporary overloading or maintenance of the server.</p>
     2686      <p id="rfc.section.6.6.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
     2687         delay <em class="bcp14">MAY</em> be indicated in a <a href="#header.retry-after" class="smpl">Retry-After</a> header field (<a href="#header.retry-after" id="rfc.xref.header.retry-after.1" title="Retry-After">Section&nbsp;7.1.2</a>). If no Retry-After is given, the client <em class="bcp14">SHOULD</em> handle the response as it would for a <a href="#status.500" class="smpl">500 (Internal
    26992688            Server Error)</a> response.
    27002689      </p>
    2701       <div class="note" id="rfc.section.7.6.4.p.3">
     2690      <div class="note" id="rfc.section.6.6.4.p.3">
    27022691         <p> <b>Note:</b> The existence of the 503 status code does not imply that a server has to use it when becoming overloaded. Some servers might
    27032692            wish to simply refuse the connection.
     
    27052694      </div>
    27062695      <div id="rfc.iref.59"></div>
    2707       <h3 id="rfc.section.7.6.5"><a href="#rfc.section.7.6.5">7.6.5</a>&nbsp;<a id="status.504" href="#status.504">504 Gateway Timeout</a></h3>
    2708       <p id="rfc.section.7.6.5.p.1">The server, while acting as a gateway or proxy, did not receive a timely response from the upstream server specified by the
     2696      <h3 id="rfc.section.6.6.5"><a href="#rfc.section.6.6.5">6.6.5</a>&nbsp;<a id="status.504" href="#status.504">504 Gateway Timeout</a></h3>
     2697      <p id="rfc.section.6.6.5.p.1">The server, while acting as a gateway or proxy, did not receive a timely response from the upstream server specified by the
    27092698         URI (e.g., HTTP, FTP, LDAP) or some other auxiliary server (e.g., DNS) it needed to access in attempting to complete the request.
    27102699      </p>
    2711       <div class="note" id="rfc.section.7.6.5.p.2">
     2700      <div class="note" id="rfc.section.6.6.5.p.2">
    27122701         <p> <b>Note</b> to implementers: some deployed proxies are known to return <a href="#status.400" class="smpl">400 (Bad Request)</a> or <a href="#status.500" class="smpl">500 (Internal Server
    27132702               Error)</a> when DNS lookups time out.
     
    27152704      </div>
    27162705      <div id="rfc.iref.59"></div>
    2717       <h3 id="rfc.section.7.6.6"><a href="#rfc.section.7.6.6">7.6.6</a>&nbsp;<a id="status.505" href="#status.505">505 HTTP Version Not Supported</a></h3>
    2718       <p id="rfc.section.7.6.6.p.1">The server does not support, or refuses to support, the protocol version that was used in the request message. The server
     2706      <h3 id="rfc.section.6.6.6"><a href="#rfc.section.6.6.6">6.6.6</a>&nbsp;<a id="status.505" href="#status.505">505 HTTP Version Not Supported</a></h3>
     2707      <p id="rfc.section.6.6.6.p.1">The server does not support, or refuses to support, the protocol version that was used in the request message. The server
    27192708         is indicating that it is unable or unwilling to complete the request using the same major version as the client, as described
    27202709         in <a href="p1-messaging.html#http.version" title="Protocol Versioning">Section 2.6</a> of <a href="#Part1" id="rfc.xref.Part1.22"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[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.
    27212710      </p>
    2722       <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a id="response.header.fields" href="#response.header.fields">Response Header Fields</a></h1>
    2723       <p id="rfc.section.8.p.1">The response header fields allow the server to pass additional information about the response which cannot be placed in the
     2711      <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a id="response.header.fields" href="#response.header.fields">Response Header Fields</a></h1>
     2712      <p id="rfc.section.7.p.1">The response header fields allow the server to pass additional information about the response which cannot be placed in the
    27242713         status-line. These header fields give information about the server and about further access to the target resource (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.23"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>).
    27252714      </p>
    2726       <h2 id="rfc.section.8.1"><a href="#rfc.section.8.1">8.1</a>&nbsp;<a id="response.control.data" href="#response.control.data">Control Data</a></h2>
    2727       <p id="rfc.section.8.1.p.1">Response header fields can supply control data that supplements the status code or instructs the client where to go next.</p>
     2715      <h2 id="rfc.section.7.1"><a href="#rfc.section.7.1">7.1</a>&nbsp;<a id="response.control.data" href="#response.control.data">Control Data</a></h2>
     2716      <p id="rfc.section.7.1.p.1">Response header fields can supply control data that supplements the status code or instructs the client where to go next.</p>
    27282717      <div id="rfc.table.u.11">
    27292718         <table class="tt full left" cellpadding="3" cellspacing="0">
     
    27372726               <tr>
    27382727                  <td class="left">Location</td>
    2739                   <td class="left"><a href="#header.location" id="rfc.xref.header.location.3" title="Location">Section&nbsp;8.1.1</a></td>
     2728                  <td class="left"><a href="#header.location" id="rfc.xref.header.location.3" title="Location">Section&nbsp;7.1.1</a></td>
    27402729               </tr>
    27412730               <tr>
    27422731                  <td class="left">Retry-After</td>
    2743                   <td class="left"><a href="#header.retry-after" id="rfc.xref.header.retry-after.2" title="Retry-After">Section&nbsp;8.1.2</a></td>
     2732                  <td class="left"><a href="#header.retry-after" id="rfc.xref.header.retry-after.2" title="Retry-After">Section&nbsp;7.1.2</a></td>
    27442733               </tr>
    27452734            </tbody>
     
    27472736      </div>
    27482737      <div id="rfc.iref.l.1"></div>
    2749       <h3 id="rfc.section.8.1.1"><a href="#rfc.section.8.1.1">8.1.1</a>&nbsp;<a id="header.location" href="#header.location">Location</a></h3>
    2750       <p id="rfc.section.8.1.1.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.
     2738      <h3 id="rfc.section.7.1.1"><a href="#rfc.section.7.1.1">7.1.1</a>&nbsp;<a id="header.location" href="#header.location">Location</a></h3>
     2739      <p id="rfc.section.7.1.1.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.
    27512740      </p>
    27522741      <div id="rfc.figure.u.34"></div><pre class="inline"><span id="rfc.iref.g.27"></span>  <a href="#header.location" class="smpl">Location</a> = <a href="#imported.abnf" class="smpl">URI-reference</a>
    2753 </pre><p id="rfc.section.8.1.1.p.3">For <a href="#status.201" class="smpl">201 (Created)</a> responses, the Location is the URI of the new resource which was created by the request. For <a href="#status.3xx" class="smpl">3xx (Redirection)</a> responses, the location <em class="bcp14">SHOULD</em> indicate the server's preferred URI for automatic redirection to the resource.
    2754       </p>
    2755       <p id="rfc.section.8.1.1.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,
     2742</pre><p id="rfc.section.7.1.1.p.3">For <a href="#status.201" class="smpl">201 (Created)</a> responses, the Location is the URI of the new resource which was created by the request. For <a href="#status.3xx" class="smpl">3xx (Redirection)</a> responses, the location <em class="bcp14">SHOULD</em> indicate the server's preferred URI for automatic redirection to the resource.
     2743      </p>
     2744      <p id="rfc.section.7.1.1.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,
    27562745         then the original URI's fragment identifier is added to the final value.
    27572746      </p>
     
    27622751      <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
    27632752</pre>  <p>would result in a final value of "http://www.example.net/index.html#larry", preserving the original fragment identifier.</p>
    2764       <div class="note" id="rfc.section.8.1.1.p.7">
     2753      <div class="note" id="rfc.section.7.1.1.p.7">
    27652754         <p> <b>Note:</b> Some recipients attempt to recover from Location fields that are not valid URI references. This specification does not mandate
    27662755            or define such processing, but does allow it.
    27672756         </p>
    27682757      </div>
    2769       <p id="rfc.section.8.1.1.p.8">There are circumstances in which a fragment identifier in a Location URI would not be appropriate. For instance, when it appears
     2758      <p id="rfc.section.7.1.1.p.8">There are circumstances in which a fragment identifier in a Location URI would not be appropriate. For instance, when it appears
    27702759         in a <a href="#status.201" class="smpl">201
    27712760            (Created)</a> response, where the Location header field specifies the URI for the entire created resource.
    27722761      </p>
    2773       <div class="note" id="rfc.section.8.1.1.p.9">
    2774          <p> <b>Note:</b> The <a href="#header.content-location" class="smpl">Content-Location</a> header field (<a href="#header.content-location" id="rfc.xref.header.content-location.3" title="Content-Location">Section&nbsp;3.2.4</a>) differs from Location in that the Content-Location identifies the most specific resource corresponding to the enclosed representation.
     2762      <div class="note" id="rfc.section.7.1.1.p.9">
     2763         <p> <b>Note:</b> The <a href="#header.content-location" class="smpl">Content-Location</a> header field (<a href="#header.content-location" id="rfc.xref.header.content-location.3" title="Content-Location">Section&nbsp;3.3.4</a>) differs from Location in that the Content-Location identifies the most specific resource corresponding to the enclosed representation.
    27752764            It is therefore possible for a response to contain header fields for both Location and Content-Location.
    27762765         </p>
    27772766      </div>
    27782767      <div id="rfc.iref.r.3"></div>
    2779       <h3 id="rfc.section.8.1.2"><a href="#rfc.section.8.1.2">8.1.2</a>&nbsp;<a id="header.retry-after" href="#header.retry-after">Retry-After</a></h3>
    2780       <p id="rfc.section.8.1.2.p.1">The header "Retry-After" field can be used with a <a href="#status.503" class="smpl">503 (Service
     2768      <h3 id="rfc.section.7.1.2"><a href="#rfc.section.7.1.2">7.1.2</a>&nbsp;<a id="header.retry-after" href="#header.retry-after">Retry-After</a></h3>
     2769      <p id="rfc.section.7.1.2.p.1">The header "Retry-After" field can be used with a <a href="#status.503" class="smpl">503 (Service
    27812770            Unavailable)</a> response to indicate how long the service is expected to be unavailable to the requesting client. This field <em class="bcp14">MAY</em> also be used with any <a href="#status.3xx" class="smpl">3xx (Redirection)</a> response to indicate the minimum time the user-agent is asked to wait before issuing the redirected request.
    27822771      </p>
    2783       <p id="rfc.section.8.1.2.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>
     2772      <p id="rfc.section.7.1.2.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>
    27842773      <div id="rfc.figure.u.37"></div><pre class="inline"><span id="rfc.iref.g.28"></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>
    27852774</pre><div id="rule.delta-seconds">
    2786          <p id="rfc.section.8.1.2.p.4">  Time spans are non-negative decimal integers, representing time in seconds.</p>
     2775         <p id="rfc.section.7.1.2.p.4">  Time spans are non-negative decimal integers, representing time in seconds.</p>
    27872776      </div>
    27882777      <div id="rfc.figure.u.38"></div><pre class="inline"><span id="rfc.iref.g.29"></span>  <a href="#rule.delta-seconds" class="smpl">delta-seconds</a>  = 1*<a href="#imported.abnf" class="smpl">DIGIT</a>
    2789 </pre><p id="rfc.section.8.1.2.p.6">Two examples of its use are</p>
     2778</pre><p id="rfc.section.7.1.2.p.6">Two examples of its use are</p>
    27902779      <div id="rfc.figure.u.39"></div><pre class="text">  Retry-After: Fri, 31 Dec 1999 23:59:59 GMT
    27912780  Retry-After: 120
    2792 </pre><p id="rfc.section.8.1.2.p.8">In the latter example, the delay is 2 minutes.</p>
    2793       <h2 id="rfc.section.8.2"><a href="#rfc.section.8.2">8.2</a>&nbsp;<a id="response.cache.related" href="#response.cache.related">Cache-related</a></h2>
    2794       <p id="rfc.section.8.2.p.1">Cache-related response header fields provide metadata about the message in order to assist downstream caches.</p>
     2781</pre><p id="rfc.section.7.1.2.p.8">In the latter example, the delay is 2 minutes.</p>
     2782      <h2 id="rfc.section.7.2"><a href="#rfc.section.7.2">7.2</a>&nbsp;<a id="response.cache.related" href="#response.cache.related">Cache-related</a></h2>
     2783      <p id="rfc.section.7.2.p.1">Cache-related response header fields provide metadata about the message in order to assist downstream caches.</p>
    27952784      <div id="rfc.table.u.12">
    27962785         <table class="tt full left" cellpadding="3" cellspacing="0">
     
    28082797               <tr>
    28092798                  <td class="left">Date</td>
    2810                   <td class="left"><a href="#header.date" id="rfc.xref.header.date.2" title="Date">Section&nbsp;8.2.1</a></td>
     2799                  <td class="left"><a href="#header.date" id="rfc.xref.header.date.2" title="Date">Section&nbsp;7.2.1</a></td>
    28112800               </tr>
    28122801               <tr>
    28132802                  <td class="left">Vary</td>
    2814                   <td class="left"><a href="#header.vary" id="rfc.xref.header.vary.2" title="Vary">Section&nbsp;8.2.2</a></td>
     2803                  <td class="left"><a href="#header.vary" id="rfc.xref.header.vary.2" title="Vary">Section&nbsp;7.2.2</a></td>
    28152804               </tr>
    28162805            </tbody>
     
    28182807      </div>
    28192808      <div id="rfc.iref.d.2"></div>
    2820       <h3 id="rfc.section.8.2.1"><a href="#rfc.section.8.2.1">8.2.1</a>&nbsp;<a id="header.date" href="#header.date">Date</a></h3>
    2821       <p id="rfc.section.8.2.1.p.1">The "Date" header field represents the date and time at which the message was originated, having the same semantics as the
    2822          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.3"><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;9.1</a>; it <em class="bcp14">MUST</em> be sent in rfc1123-date format.
     2809      <h3 id="rfc.section.7.2.1"><a href="#rfc.section.7.2.1">7.2.1</a>&nbsp;<a id="header.date" href="#header.date">Date</a></h3>
     2810      <p id="rfc.section.7.2.1.p.1">The "Date" header field represents the date and time at which the message was originated, having the same semantics as the
     2811         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.3"><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;8.1</a>; it <em class="bcp14">MUST</em> be sent in rfc1123-date format.
    28232812      </p>
    28242813      <div id="rfc.figure.u.40"></div><pre class="inline"><span id="rfc.iref.g.30"></span>  <a href="#header.date" class="smpl">Date</a> = <a href="#http.date" class="smpl">HTTP-date</a>
    2825 </pre><p id="rfc.section.8.2.1.p.3">An example is</p>
     2814</pre><p id="rfc.section.7.2.1.p.3">An example is</p>
    28262815      <div id="rfc.figure.u.41"></div><pre class="text">  Date: Tue, 15 Nov 1994 08:12:31 GMT
    2827 </pre><p id="rfc.section.8.2.1.p.5">Origin servers <em class="bcp14">MUST</em> include a Date header field in all responses, except in these cases:
     2816</pre><p id="rfc.section.7.2.1.p.5">Origin servers <em class="bcp14">MUST</em> include a Date header field in all responses, except in these cases:
    28282817      </p>
    28292818      <ol>
     
    28362825         </li>
    28372826      </ol>
    2838       <p id="rfc.section.8.2.1.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.
    2839       </p>
    2840       <p id="rfc.section.8.2.1.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
     2827      <p id="rfc.section.7.2.1.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.
     2828      </p>
     2829      <p id="rfc.section.7.2.1.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
    28412830         when it doesn't convey any useful information (as is usually the case for requests that do not contain a payload).
    28422831      </p>
    2843       <p id="rfc.section.8.2.1.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
     2832      <p id="rfc.section.7.2.1.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
    28442833         of generating a reasonably accurate date and time. In theory, the date ought to represent the moment just before the payload
    28452834         is generated. In practice, the date can be generated at any time during the message origination without affecting its semantic
     
    28472836      </p>
    28482837      <div id="rfc.iref.v.1"></div>
    2849       <h3 id="rfc.section.8.2.2"><a href="#rfc.section.8.2.2">8.2.2</a>&nbsp;<a id="header.vary" href="#header.vary">Vary</a></h3>
    2850       <p id="rfc.section.8.2.2.p.1">The "Vary" header field conveys the set of header fields that were used to select the representation.</p>
    2851       <p id="rfc.section.8.2.2.p.2">Caches use this information as part of determining whether a stored response can be used to satisfy a given request (<a href="p6-cache.html#caching.negotiated.responses" title="Using Negotiated Responses">Section 4.3</a> of <a href="#Part6" id="rfc.xref.Part6.16"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
    2852       </p>
    2853       <p id="rfc.section.8.2.2.p.3">In uncacheable or stale responses, the Vary field value advises the user agent about the criteria that were used to select
     2838      <h3 id="rfc.section.7.2.2"><a href="#rfc.section.7.2.2">7.2.2</a>&nbsp;<a id="header.vary" href="#header.vary">Vary</a></h3>
     2839      <p id="rfc.section.7.2.2.p.1">The "Vary" header field conveys the set of header fields that were used to select the representation.</p>
     2840      <p id="rfc.section.7.2.2.p.2">Caches use this information as part of determining whether a stored response can be used to satisfy a given request (<a href="p6-cache.html#caching.negotiated.responses" title="Using Negotiated Responses">Section 4.3</a> of <a href="#Part6" id="rfc.xref.Part6.16"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
     2841      </p>
     2842      <p id="rfc.section.7.2.2.p.3">In uncacheable or stale responses, the Vary field value advises the user agent about the criteria that were used to select
    28542843         the representation.
    28552844      </p>
    28562845      <div id="rfc.figure.u.42"></div><pre class="inline"><span id="rfc.iref.g.31"></span>  <a href="#header.vary" class="smpl">Vary</a> = "*" / 1#<a href="#imported.abnf" class="smpl">field-name</a>
    2857 </pre><p id="rfc.section.8.2.2.p.5">The set of header fields named by the Vary field value is known as the selecting header fields.</p>
    2858       <p id="rfc.section.8.2.2.p.6">A server <em class="bcp14">SHOULD</em> include a Vary header field with any cacheable response that is subject to proactive negotiation. Doing so allows a cache
     2846</pre><p id="rfc.section.7.2.2.p.5">The set of header fields named by the Vary field value is known as the selecting header fields.</p>
     2847      <p id="rfc.section.7.2.2.p.6">A server <em class="bcp14">SHOULD</em> include a Vary header field with any cacheable response that is subject to proactive negotiation. Doing so allows a cache
    28592848         to properly interpret future requests on that resource and informs the user agent about the presence of negotiation on that
    28602849         resource. A server <em class="bcp14">MAY</em> include a Vary header field with a non-cacheable response that is subject to proactive negotiation, since this might provide
    28612850         the user agent with useful information about the dimensions over which the response varies at the time of the response.
    28622851      </p>
    2863       <p id="rfc.section.8.2.2.p.7">A Vary field value of "*" signals that unspecified parameters not limited to the header fields (e.g., the network address
     2852      <p id="rfc.section.7.2.2.p.7">A Vary field value of "*" signals that unspecified parameters not limited to the header fields (e.g., the network address
    28642853         of the client), play a role in the selection of the response representation; therefore, a cache cannot determine whether this
    28652854         response is appropriate. A proxy <em class="bcp14">MUST NOT</em> generate the "*" value.
    28662855      </p>
    2867       <p id="rfc.section.8.2.2.p.8">The field-names given are not limited to the set of standard header fields defined by this specification. Field names are
     2856      <p id="rfc.section.7.2.2.p.8">The field-names given are not limited to the set of standard header fields defined by this specification. Field names are
    28682857         case-insensitive.
    28692858      </p>
    2870       <h2 id="rfc.section.8.3"><a href="#rfc.section.8.3">8.3</a>&nbsp;<a id="response.auth" href="#response.auth">Authentication Challenges</a></h2>
    2871       <p id="rfc.section.8.3.p.1">Authentication challenges indicate what mechanisms are available for the client to provide authentication credentials in future
     2859      <h2 id="rfc.section.7.3"><a href="#rfc.section.7.3">7.3</a>&nbsp;<a id="response.auth" href="#response.auth">Authentication Challenges</a></h2>
     2860      <p id="rfc.section.7.3.p.1">Authentication challenges indicate what mechanisms are available for the client to provide authentication credentials in future
    28722861         requests.
    28732862      </p>
     
    28922881         </table>
    28932882      </div>
    2894       <h2 id="rfc.section.8.4"><a href="#rfc.section.8.4">8.4</a>&nbsp;<a id="response.inform" href="#response.inform">Informative</a></h2>
    2895       <p id="rfc.section.8.4.p.1">The remaining response header fields provide more information about the target resource for potential use in later requests.</p>
     2883      <h2 id="rfc.section.7.4"><a href="#rfc.section.7.4">7.4</a>&nbsp;<a id="response.inform" href="#response.inform">Informative</a></h2>
     2884      <p id="rfc.section.7.4.p.1">The remaining response header fields provide more information about the target resource for potential use in later requests.</p>
    28962885      <div id="rfc.table.u.14">
    28972886         <table class="tt full left" cellpadding="3" cellspacing="0">
     
    29092898               <tr>
    29102899                  <td class="left">Allow</td>
    2911                   <td class="left"><a href="#header.allow" id="rfc.xref.header.allow.2" title="Allow">Section&nbsp;8.4.1</a></td>
     2900                  <td class="left"><a href="#header.allow" id="rfc.xref.header.allow.2" title="Allow">Section&nbsp;7.4.1</a></td>
    29122901               </tr>
    29132902               <tr>
    29142903                  <td class="left">Server</td>
    2915                   <td class="left"><a href="#header.server" id="rfc.xref.header.server.1" title="Server">Section&nbsp;8.4.2</a></td>
     2904                  <td class="left"><a href="#header.server" id="rfc.xref.header.server.1" title="Server">Section&nbsp;7.4.2</a></td>
    29162905               </tr>
    29172906            </tbody>
     
    29192908      </div>
    29202909      <div id="rfc.iref.a.5"></div>
    2921       <h3 id="rfc.section.8.4.1"><a href="#rfc.section.8.4.1">8.4.1</a>&nbsp;<a id="header.allow" href="#header.allow">Allow</a></h3>
    2922       <p id="rfc.section.8.4.1.p.1">The "Allow" header field lists the set of methods advertised as supported by the target resource. The purpose of this field
     2910      <h3 id="rfc.section.7.4.1"><a href="#rfc.section.7.4.1">7.4.1</a>&nbsp;<a id="header.allow" href="#header.allow">Allow</a></h3>
     2911      <p id="rfc.section.7.4.1.p.1">The "Allow" header field lists the set of methods advertised as supported by the target resource. The purpose of this field
    29232912         is strictly to inform the recipient of valid request methods associated with the resource.
    29242913      </p>
    29252914      <div id="rfc.figure.u.43"></div><pre class="inline"><span id="rfc.iref.g.32"></span>  <a href="#header.allow" class="smpl">Allow</a> = #<a href="#method.overview" class="smpl">method</a>
    2926 </pre><p id="rfc.section.8.4.1.p.3">Example of use:</p>
     2915</pre><p id="rfc.section.7.4.1.p.3">Example of use:</p>
    29272916      <div id="rfc.figure.u.44"></div><pre class="text">  Allow: GET, HEAD, PUT
    2928 </pre><p id="rfc.section.8.4.1.p.5">The actual set of allowed methods is defined by the origin server at the time of each request.</p>
    2929       <p id="rfc.section.8.4.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
     2917</pre><p id="rfc.section.7.4.1.p.5">The actual set of allowed methods is defined by the origin server at the time of each request.</p>
     2918      <p id="rfc.section.7.4.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
    29302919         to the generic message handling rules.
    29312920      </p>
    29322921      <div id="rfc.iref.s.8"></div>
    2933       <h3 id="rfc.section.8.4.2"><a href="#rfc.section.8.4.2">8.4.2</a>&nbsp;<a id="header.server" href="#header.server">Server</a></h3>
    2934       <p id="rfc.section.8.4.2.p.1">The "Server" header field contains information about the software used by the origin server to handle the request.</p>
    2935       <p id="rfc.section.8.4.2.p.2">The field can contain multiple product tokens (<a href="#product.tokens" title="Product Tokens">Section&nbsp;9.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.24"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) identifying the server and any significant subproducts. The product tokens are listed in order of their significance for
     2922      <h3 id="rfc.section.7.4.2"><a href="#rfc.section.7.4.2">7.4.2</a>&nbsp;<a id="header.server" href="#header.server">Server</a></h3>
     2923      <p id="rfc.section.7.4.2.p.1">The "Server" header field contains information about the software used by the origin server to handle the request.</p>
     2924      <p id="rfc.section.7.4.2.p.2">The field can contain multiple product tokens (<a href="#product.tokens" title="Product Tokens">Section&nbsp;8.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.24"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) identifying the server and any significant subproducts. The product tokens are listed in order of their significance for
    29362925         identifying the application.
    29372926      </p>
    29382927      <div id="rfc.figure.u.45"></div><pre class="inline"><span id="rfc.iref.g.33"></span>  <a href="#header.server" class="smpl">Server</a> = <a href="#product.tokens" class="smpl">product</a> *( <a href="#imported.abnf" class="smpl">RWS</a> ( <a href="#product.tokens" class="smpl">product</a> / <a href="#imported.abnf" class="smpl">comment</a> ) )
    2939 </pre><p id="rfc.section.8.4.2.p.4">Example:</p>
     2928</pre><p id="rfc.section.7.4.2.p.4">Example:</p>
    29402929      <div id="rfc.figure.u.46"></div><pre class="text">  Server: CERN/3.0 libwww/2.17
    2941 </pre><p id="rfc.section.8.4.2.p.6">If the response is being forwarded through a proxy, the proxy application <em class="bcp14">MUST NOT</em> modify the <a href="#header.server" class="smpl">Server</a> header field. Instead, it <em class="bcp14">MUST</em> include a <a href="p1-messaging.html#header.via" class="smpl">Via</a> field (as described in <a href="p1-messaging.html#header.via" title="Via">Section 5.7</a> of <a href="#Part1" id="rfc.xref.Part1.25"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>).
    2942       </p>
    2943       <div class="note" id="rfc.section.8.4.2.p.7">
     2930</pre><p id="rfc.section.7.4.2.p.6">If the response is being forwarded through a proxy, the proxy application <em class="bcp14">MUST NOT</em> modify the <a href="#header.server" class="smpl">Server</a> header field. Instead, it <em class="bcp14">MUST</em> include a <a href="p1-messaging.html#header.via" class="smpl">Via</a> field (as described in <a href="p1-messaging.html#header.via" title="Via">Section 5.7</a> of <a href="#Part1" id="rfc.xref.Part1.25"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>).
     2931      </p>
     2932      <div class="note" id="rfc.section.7.4.2.p.7">
    29442933         <p> <b>Note:</b> Revealing the specific software version of the server might allow the server machine to become more vulnerable to attacks
    29452934            against software that is known to contain security holes. Server implementers are encouraged to make this field a configurable
     
    29472936         </p>
    29482937      </div>
    2949       <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a>&nbsp;<a id="protocol.parameters" href="#protocol.parameters">Protocol Parameters</a></h1>
    2950       <h2 id="rfc.section.9.1"><a href="#rfc.section.9.1">9.1</a>&nbsp;<a id="http.date" href="#http.date">Date/Time Formats</a></h2>
    2951       <p id="rfc.section.9.1.p.1">HTTP applications have historically allowed three different formats for date/time stamps. However, the preferred format is
     2938      <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a id="protocol.parameters" href="#protocol.parameters">Protocol Parameters</a></h1>
     2939      <h2 id="rfc.section.8.1"><a href="#rfc.section.8.1">8.1</a>&nbsp;<a id="http.date" href="#http.date">Date/Time Formats</a></h2>
     2940      <p id="rfc.section.8.1.p.1">HTTP applications have historically allowed three different formats for date/time stamps. However, the preferred format is
    29522941         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>:
    29532942      </p>
    29542943      <div id="rfc.figure.u.47"></div><pre class="text">Sun, 06 Nov 1994 08:49:37 GMT  ; RFC 1123
    2955 </pre><p id="rfc.section.9.1.p.3">The other formats are described here only for compatibility with obsolete implementations.</p>
     2944</pre><p id="rfc.section.8.1.p.3">The other formats are described here only for compatibility with obsolete implementations.</p>
    29562945      <div id="rfc.figure.u.48"></div><pre class="text">Sunday, 06-Nov-94 08:49:37 GMT ; obsolete RFC 850 format
    29572946Sun Nov  6 08:49:37 1994       ; ANSI C's asctime() format
    2958 </pre><p id="rfc.section.9.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.
    2959       </p>
    2960       <p id="rfc.section.9.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
     2947</pre><p id="rfc.section.8.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.
     2948      </p>
     2949      <p id="rfc.section.8.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
    29612950         Universal Time). This is indicated in the first two formats by the inclusion of "GMT" as the three-letter abbreviation for
    29622951         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.
     
    29642953      <div id="rfc.figure.u.49"></div><pre class="inline"><span id="rfc.iref.g.34"></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>
    29652954</pre><div id="preferred.date.format">
    2966          <p id="rfc.section.9.1.p.8">                    Preferred format:</p>
     2955         <p id="rfc.section.8.1.p.8">                    Preferred format:</p>
    29672956      </div>
    29682957      <div id="rfc.figure.u.50"></div><pre class="inline"><span id="rfc.iref.g.35"></span><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><span id="rfc.iref.g.41"></span><span id="rfc.iref.g.42"></span><span id="rfc.iref.g.43"></span><span id="rfc.iref.g.44"></span><span id="rfc.iref.g.45"></span><span id="rfc.iref.g.46"></span>  <a href="#preferred.date.format" class="smpl">rfc1123-date</a> = <a href="#preferred.date.format" class="smpl">day-name</a> "," <a href="#imported.abnf" class="smpl">SP</a> date1 <a href="#imported.abnf" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">time-of-day</a> <a href="#imported.abnf" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">GMT</a>
     
    30042993  <a href="#preferred.date.format" class="smpl">minute</a>       = 2<a href="#imported.abnf" class="smpl">DIGIT</a>               
    30052994  <a href="#preferred.date.format" class="smpl">second</a>       = 2<a href="#imported.abnf" class="smpl">DIGIT</a>               
    3006 </pre><p id="rfc.section.9.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.4"><cite title="Internet Message Format">[RFC5322]</cite></a>, <a href="http://tools.ietf.org/html/rfc5322#section-3.3">Section 3.3</a>).
     2995</pre><p id="rfc.section.8.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.4"><cite title="Internet Message Format">[RFC5322]</cite></a>, <a href="http://tools.ietf.org/html/rfc5322#section-3.3">Section 3.3</a>).
    30072996      </p>
    30082997      <div id="obsolete.date.formats">
    3009          <p id="rfc.section.9.1.p.11">              Obsolete formats:</p>
     2998         <p id="rfc.section.8.1.p.11">              Obsolete formats:</p>
    30102999      </div>
    30113000      <div id="rfc.figure.u.51"></div><pre class="inline"><span id="rfc.iref.g.47"></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>
     
    30243013  <a href="#obsolete.date.formats" class="smpl">date3</a>        = <a href="#preferred.date.format" class="smpl">month</a> <a href="#imported.abnf" class="smpl">SP</a> ( 2<a href="#imported.abnf" class="smpl">DIGIT</a> / ( <a href="#imported.abnf" class="smpl">SP</a> 1<a href="#imported.abnf" class="smpl">DIGIT</a> ))
    30253014                 ; month day (e.g., Jun  2)
    3026 </pre><div class="note" id="rfc.section.9.1.p.15">
     3015</pre><div class="note" id="rfc.section.8.1.p.15">
    30273016         <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,
    30283017            as is sometimes the case when retrieving or posting messages via proxies/gateways to SMTP or NNTP.
    30293018         </p>
    30303019      </div>
    3031       <div class="note" id="rfc.section.9.1.p.16">
     3020      <div class="note" id="rfc.section.8.1.p.16">
    30323021         <p> <b>Note:</b> HTTP requirements for the date/time stamp format apply only to their usage within the protocol stream. Clients and servers
    30333022            are not required to use these formats for user presentation, request logging, etc.
    30343023         </p>
    30353024      </div>
    3036       <h2 id="rfc.section.9.2"><a href="#rfc.section.9.2">9.2</a>&nbsp;<a id="product.tokens" href="#product.tokens">Product Tokens</a></h2>
    3037       <p id="rfc.section.9.2.p.1">Product tokens are used to allow communicating applications to identify themselves by software name and version. Most fields
     3025      <h2 id="rfc.section.8.2"><a href="#rfc.section.8.2">8.2</a>&nbsp;<a id="product.tokens" href="#product.tokens">Product Tokens</a></h2>
     3026      <p id="rfc.section.8.2.p.1">Product tokens are used to allow communicating applications to identify themselves by software name and version. Most fields
    30383027         using product tokens also allow sub-products which form a significant part of the application to be listed, separated by whitespace.
    30393028         By convention, the products are listed in order of their significance for identifying the application.
     
    30413030      <div id="rfc.figure.u.54"></div><pre class="inline"><span id="rfc.iref.g.50"></span><span id="rfc.iref.g.51"></span>  <a href="#product.tokens" class="smpl">product</a>         = <a href="#imported.abnf" class="smpl">token</a> ["/" <a href="#product.tokens" class="smpl">product-version</a>]
    30423031  <a href="#product.tokens" class="smpl">product-version</a> = <a href="#imported.abnf" class="smpl">token</a>
    3043 </pre><p id="rfc.section.9.2.p.3">Examples:</p>
     3032</pre><p id="rfc.section.8.2.p.3">Examples:</p>
    30443033      <div id="rfc.figure.u.55"></div><pre class="text">  User-Agent: CERN-LineMode/2.15 libwww/2.17b3
    30453034  Server: Apache/0.8.4
    3046 </pre><p id="rfc.section.9.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).
    3047       </p>
    3048       <h2 id="rfc.section.9.3"><a href="#rfc.section.9.3">9.3</a>&nbsp;<a id="character.sets" href="#character.sets">Character Encodings (charset)</a></h2>
    3049       <p id="rfc.section.9.3.p.1">HTTP uses charset names to indicate the character encoding of a textual representation.</p>
     3035</pre><p id="rfc.section.8.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).
     3036      </p>
     3037      <h2 id="rfc.section.8.3"><a href="#rfc.section.8.3">8.3</a>&nbsp;<a id="character.sets" href="#character.sets">Character Encodings (charset)</a></h2>
     3038      <p id="rfc.section.8.3.p.1">HTTP uses charset names to indicate the character encoding of a textual representation.</p>
    30503039      <div id="rule.charset">
    3051          <p id="rfc.section.9.3.p.2">  A character encoding is identified by a case-insensitive token. The complete set of tokens is defined by the IANA Character
     3040         <p id="rfc.section.8.3.p.2">  A character encoding is identified by a case-insensitive token. The complete set of tokens is defined by the IANA Character
    30523041            Set registry (&lt;<a href="http://www.iana.org/assignments/character-sets">http://www.iana.org/assignments/character-sets</a>&gt;).
    30533042         </p>
    30543043      </div>
    30553044      <div id="rfc.figure.u.56"></div><pre class="inline"><span id="rfc.iref.g.52"></span>  <a href="#rule.charset" class="smpl">charset</a> = <a href="#imported.abnf" class="smpl">token</a>
    3056 </pre><p id="rfc.section.9.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
     3045</pre><p id="rfc.section.8.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
    30573046         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.
    30583047      </p>
    3059       <p id="rfc.section.9.3.p.5">HTTP uses charset in two contexts: within an <a href="#header.accept-charset" class="smpl">Accept-Charset</a> request header field (in which the charset value is an unquoted token) and as the value of a parameter in a <a href="#header.content-type" class="smpl">Content-Type</a> header field (within a request or response), in which case the parameter value of the charset parameter can be quoted.
    3060       </p>
    3061       <p id="rfc.section.9.3.p.6">Implementers 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>.
    3062       </p>
    3063       <h2 id="rfc.section.9.4"><a href="#rfc.section.9.4">9.4</a>&nbsp;<a id="content.codings" href="#content.codings">Content Codings</a></h2>
    3064       <p id="rfc.section.9.4.p.1">Content coding values indicate an encoding transformation that has been or can be applied to a representation. Content codings
     3048      <p id="rfc.section.8.3.p.5">HTTP uses charset in two contexts: within an <a href="#header.accept-charset" class="smpl">Accept-Charset</a> request header field (in which the charset value is an unquoted token) and as the value of a parameter in a <a href="#header.content-type" class="smpl">Content-Type</a> header field (within a request or response), in which case the parameter value of the charset parameter can be quoted.
     3049      </p>
     3050      <p id="rfc.section.8.3.p.6">Implementers 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>.
     3051      </p>
     3052      <h2 id="rfc.section.8.4"><a href="#rfc.section.8.4">8.4</a>&nbsp;<a id="content.codings" href="#content.codings">Content Codings</a></h2>
     3053      <p id="rfc.section.8.4.p.1">Content coding values indicate an encoding transformation that has been or can be applied to a representation. Content codings
    30653054         are primarily used to allow a representation to be compressed or otherwise usefully transformed without losing the identity
    30663055         of its underlying media type and without loss of information. Frequently, the representation is stored in coded form, transmitted
     
    30683057      </p>
    30693058      <div id="rfc.figure.u.57"></div><pre class="inline"><span id="rfc.iref.g.53"></span>  <a href="#content.codings" class="smpl">content-coding</a>   = <a href="#imported.abnf" class="smpl">token</a>
    3070 </pre><p id="rfc.section.9.4.p.3">All content-coding values are case-insensitive. HTTP/1.1 uses content-coding values in the <a href="#header.accept-encoding" class="smpl">Accept-Encoding</a> (<a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.3" title="Accept-Encoding">Section&nbsp;6.3.4</a>) and <a href="#header.content-encoding" class="smpl">Content-Encoding</a> (<a href="#header.content-encoding" id="rfc.xref.header.content-encoding.2" title="Content-Encoding">Section&nbsp;3.2.2</a>) header fields. Although the value describes the content-coding, what is more important is that it indicates what decoding
     3059</pre><p id="rfc.section.8.4.p.3">All content-coding values are case-insensitive. HTTP/1.1 uses content-coding values in the <a href="#header.accept-encoding" class="smpl">Accept-Encoding</a> (<a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.3" title="Accept-Encoding">Section&nbsp;5.3.4</a>) and <a href="#header.content-encoding" class="smpl">Content-Encoding</a> (<a href="#header.content-encoding" id="rfc.xref.header.content-encoding.2" title="Content-Encoding">Section&nbsp;3.3.2</a>) header fields. Although the value describes the content-coding, what is more important is that it indicates what decoding
    30713060         mechanism will be required to remove the encoding.
    30723061      </p>
    3073       <p id="rfc.section.9.4.p.4">compress<span id="rfc.iref.c.8"></span> 
     3062      <p id="rfc.section.8.4.p.4">compress<span id="rfc.iref.c.8"></span> 
    30743063      </p>
    30753064      <ul class="empty">
     
    30773066         </li>
    30783067      </ul>
    3079       <p id="rfc.section.9.4.p.5">deflate<span id="rfc.iref.d.3"></span> 
     3068      <p id="rfc.section.8.4.p.5">deflate<span id="rfc.iref.d.3"></span> 
    30803069      </p>
    30813070      <ul class="empty">
     
    30833072         </li>
    30843073      </ul>
    3085       <p id="rfc.section.9.4.p.6">gzip<span id="rfc.iref.g.54"></span> 
     3074      <p id="rfc.section.8.4.p.6">gzip<span id="rfc.iref.g.54"></span> 
    30863075      </p>
    30873076      <ul class="empty">
     
    30893078         </li>
    30903079      </ul>
    3091       <h2 id="rfc.section.9.5"><a href="#rfc.section.9.5">9.5</a>&nbsp;<a id="media.types" href="#media.types">Media Types</a></h2>
    3092       <p id="rfc.section.9.5.p.1">HTTP uses Internet Media Types <a href="#RFC2046" id="rfc.xref.RFC2046.2"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a> in the <a href="#header.content-type" class="smpl">Content-Type</a> (<a href="#header.content-type" id="rfc.xref.header.content-type.3" title="Content-Type">Section&nbsp;3.2.1</a>) and <a href="#header.accept" class="smpl">Accept</a> (<a href="#header.accept" id="rfc.xref.header.accept.3" title="Accept">Section&nbsp;6.3.2</a>) header fields in order to provide open and extensible data typing and type negotiation.
     3080      <h2 id="rfc.section.8.5"><a href="#rfc.section.8.5">8.5</a>&nbsp;<a id="media.types" href="#media.types">Media Types</a></h2>
     3081      <p id="rfc.section.8.5.p.1">HTTP uses Internet Media Types <a href="#RFC2046" id="rfc.xref.RFC2046.2"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a> in the <a href="#header.content-type" class="smpl">Content-Type</a> (<a href="#header.content-type" id="rfc.xref.header.content-type.3" title="Content-Type">Section&nbsp;3.3.1</a>) and <a href="#header.accept" class="smpl">Accept</a> (<a href="#header.accept" id="rfc.xref.header.accept.3" title="Accept">Section&nbsp;5.3.2</a>) header fields in order to provide open and extensible data typing and type negotiation.
    30933082      </p>
    30943083      <div id="rfc.figure.u.58"></div><pre class="inline"><span id="rfc.iref.g.55"></span><span id="rfc.iref.g.56"></span><span id="rfc.iref.g.57"></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="#imported.abnf" class="smpl">OWS</a> ";" <a href="#imported.abnf" class="smpl">OWS</a> <a href="#rule.parameter" class="smpl">parameter</a> )
     
    30963085  <a href="#media.types" class="smpl">subtype</a>    = <a href="#imported.abnf" class="smpl">token</a>
    30973086</pre><div id="rule.parameter">
    3098          <p id="rfc.section.9.5.p.3">      The type/subtype <em class="bcp14">MAY</em> be followed by parameters in the form of attribute/value pairs.
     3087         <p id="rfc.section.8.5.p.3">      The type/subtype <em class="bcp14">MAY</em> be followed by parameters in the form of attribute/value pairs.
    30993088         </p>
    31003089      </div>
     
    31023091  <a href="#rule.parameter" class="smpl">attribute</a>      = <a href="#imported.abnf" class="smpl">token</a>
    31033092  <a href="#rule.parameter" class="smpl">value</a>          = <a href="#imported.abnf" class="smpl">word</a>
    3104 </pre><p id="rfc.section.9.5.p.5">The type, subtype, and parameter attribute names are case-insensitive. Parameter values might or might not be case-sensitive,
     3093</pre><p id="rfc.section.8.5.p.5">The type, subtype, and parameter attribute names are case-insensitive. Parameter values might or might not be case-sensitive,
    31053094         depending on the semantics of the parameter name. The presence or absence of a parameter might be significant to the processing
    31063095         of a media-type, depending on its definition within the media type registry.
    31073096      </p>
    3108       <p id="rfc.section.9.5.p.6">A parameter value that matches the <a href="#imported.abnf" class="smpl">token</a> production can be transmitted as either a token or within a quoted-string. The quoted and unquoted values are equivalent.
    3109       </p>
    3110       <p id="rfc.section.9.5.p.7">Media-type values are registered with the Internet Assigned Number Authority (IANA). The media type registration process is
     3097      <p id="rfc.section.8.5.p.6">A parameter value that matches the <a href="#imported.abnf" class="smpl">token</a> production can be transmitted as either a token or within a quoted-string. The quoted and unquoted values are equivalent.
     3098      </p>
     3099      <p id="rfc.section.8.5.p.7">Media-type values are registered with the Internet Assigned Number Authority (IANA). The media type registration process is
    31113100         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.
    31123101      </p>
    3113       <h3 id="rfc.section.9.5.1"><a href="#rfc.section.9.5.1">9.5.1</a>&nbsp;<a id="canonicalization.and.text.defaults" href="#canonicalization.and.text.defaults">Canonicalization and Text Defaults</a></h3>
    3114       <p id="rfc.section.9.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.
    3115       </p>
    3116       <p id="rfc.section.9.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
     3102      <h3 id="rfc.section.8.5.1"><a href="#rfc.section.8.5.1">8.5.1</a>&nbsp;<a id="canonicalization.and.text.defaults" href="#canonicalization.and.text.defaults">Canonicalization and Text Defaults</a></h3>
     3103      <p id="rfc.section.8.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.
     3104      </p>
     3105      <p id="rfc.section.8.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
    31173106         allows the transport of text media with plain CR or LF alone representing a line break when it is done consistently for an
    31183107         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
     
    31223111         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).
    31233112      </p>
    3124       <p id="rfc.section.9.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.
    3125       </p>
    3126       <h3 id="rfc.section.9.5.2"><a href="#rfc.section.9.5.2">9.5.2</a>&nbsp;<a id="multipart.types" href="#multipart.types">Multipart Types</a></h3>
    3127       <p id="rfc.section.9.5.2.p.1">MIME provides for a number of "multipart" types — encapsulations of one or more representations within a single message body.
     3113      <p id="rfc.section.8.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.
     3114      </p>
     3115      <h3 id="rfc.section.8.5.2"><a href="#rfc.section.8.5.2">8.5.2</a>&nbsp;<a id="multipart.types" href="#multipart.types">Multipart Types</a></h3>
     3116      <p id="rfc.section.8.5.2.p.1">MIME provides for a number of "multipart" types — encapsulations of one or more representations within a single message body.
    31283117         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.3"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a>, and include a boundary parameter as part of the media type value. The message body is itself a protocol element; a sender <em class="bcp14">MUST</em> generate only CRLF to represent line breaks between body-parts.
    31293118      </p>
    3130       <p id="rfc.section.9.5.2.p.2">In general, HTTP treats a multipart message body no differently than any other media type: strictly as payload. HTTP does
     3119      <p id="rfc.section.8.5.2.p.2">In general, HTTP treats a multipart message body no differently than any other media type: strictly as payload. HTTP does
    31313120         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
    31323121         each body-part of a multipart message body do not have any significance to HTTP beyond that defined by their MIME semantics.
    31333122      </p>
    3134       <p id="rfc.section.9.5.2.p.3">A recipient <em class="bcp14">MUST</em> treat an unrecognized multipart subtype as being equivalent to "multipart/mixed".
    3135       </p>
    3136       <div class="note" id="rfc.section.9.5.2.p.4">
     3123      <p id="rfc.section.8.5.2.p.3">A recipient <em class="bcp14">MUST</em> treat an unrecognized multipart subtype as being equivalent to "multipart/mixed".
     3124      </p>
     3125      <div class="note" id="rfc.section.8.5.2.p.4">
    31373126         <p> <b>Note:</b> The "multipart/form-data" type has been specifically defined for carrying form data suitable for processing via the POST request
    31383127            method, as described in <a href="#RFC2388" id="rfc.xref.RFC2388.1"><cite title="Returning Values from Forms: multipart/form-data">[RFC2388]</cite></a>.
    31393128         </p>
    31403129      </div>
    3141       <h2 id="rfc.section.9.6"><a href="#rfc.section.9.6">9.6</a>&nbsp;<a id="language.tags" href="#language.tags">Language Tags</a></h2>
    3142       <p id="rfc.section.9.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
     3130      <h2 id="rfc.section.8.6"><a href="#rfc.section.8.6">8.6</a>&nbsp;<a id="language.tags" href="#language.tags">Language Tags</a></h2>
     3131      <p id="rfc.section.8.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
    31433132         other human beings. Computer languages are explicitly excluded. HTTP uses language tags within the <a href="#header.accept-language" class="smpl">Accept-Language</a> and <a href="#header.content-language" class="smpl">Content-Language</a> fields.
    31443133      </p>
    3145       <p id="rfc.section.9.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
     3134      <p id="rfc.section.8.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
    31463135         of subtags:
    31473136      </p>
    31483137      <div id="rfc.figure.u.60"></div><pre class="inline"><span id="rfc.iref.g.61"></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;
    3149 </pre><p id="rfc.section.9.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
     3138</pre><p id="rfc.section.8.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
    31503139         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;).
    31513140      </p>
    31523141      <div id="rfc.figure.u.61"></div>
    31533142      <p>Example tags include:</p>  <pre class="text">  en, en-US, es-419, az-Arab, x-pig-latin, man-Nkoo-GN
    3154 </pre> <p id="rfc.section.9.6.p.6">See <a href="#RFC5646" id="rfc.xref.RFC5646.3"><cite title="Tags for Identifying Languages">[RFC5646]</cite></a> for further information.
    3155       </p>
    3156       <h1 id="rfc.section.10"><a href="#rfc.section.10">10.</a>&nbsp;<a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1>
    3157       <h2 id="rfc.section.10.1"><a href="#rfc.section.10.1">10.1</a>&nbsp;<a id="method.registry" href="#method.registry">Method Registry</a></h2>
    3158       <p id="rfc.section.10.1.p.1">The HTTP Method Registry defines the name space for the request method token (<a href="#methods" title="Request Methods">Section&nbsp;5</a>). The method registry is maintained at &lt;<a href="http://www.iana.org/assignments/http-methods">http://www.iana.org/assignments/http-methods</a>&gt;.
    3159       </p>
    3160       <h3 id="rfc.section.10.1.1"><a href="#rfc.section.10.1.1">10.1.1</a>&nbsp;<a id="method.procedure" href="#method.procedure">Procedure</a></h3>
    3161       <p id="rfc.section.10.1.1.p.1">HTTP method registrations <em class="bcp14">MUST</em> include the following fields:
    3162       </p>
    3163       <ul>
    3164          <li>Method Name (see <a href="#methods" title="Request Methods">Section&nbsp;5</a>)
    3165          </li>
    3166          <li>Safe ("yes" or "no", see <a href="#safe.methods" title="Safe Methods">Section&nbsp;5.2.1</a>)
    3167          </li>
    3168          <li>Idempotent ("yes" or "no", see <a href="#idempotent.methods" title="Idempotent Methods">Section&nbsp;5.2.2</a>)
     3143</pre> <p id="rfc.section.8.6.p.6">See <a href="#RFC5646" id="rfc.xref.RFC5646.3"><cite title="Tags for Identifying Languages">[RFC5646]</cite></a> for further information.
     3144      </p>
     3145      <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a>&nbsp;<a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1>
     3146      <h2 id="rfc.section.9.1"><a href="#rfc.section.9.1">9.1</a>&nbsp;<a id="method.registry" href="#method.registry">Method Registry</a></h2>
     3147      <p id="rfc.section.9.1.p.1">The HTTP Method Registry defines the name space for the request method token (<a href="#methods" title="Request Methods">Section&nbsp;4</a>). The method registry is maintained at &lt;<a href="http://www.iana.org/assignments/http-methods">http://www.iana.org/assignments/http-methods</a>&gt;.
     3148      </p>
     3149      <h3 id="rfc.section.9.1.1"><a href="#rfc.section.9.1.1">9.1.1</a>&nbsp;<a id="method.procedure" href="#method.procedure">Procedure</a></h3>
     3150      <p id="rfc.section.9.1.1.p.1">HTTP method registrations <em class="bcp14">MUST</em> include the following fields:
     3151      </p>
     3152      <ul>
     3153         <li>Method Name (see <a href="#methods" title="Request Methods">Section&nbsp;4</a>)
     3154         </li>
     3155         <li>Safe ("yes" or "no", see <a href="#safe.methods" title="Safe Methods">Section&nbsp;4.2.1</a>)
     3156         </li>
     3157         <li>Idempotent ("yes" or "no", see <a href="#idempotent.methods" title="Idempotent Methods">Section&nbsp;4.2.2</a>)
    31693158         </li>
    31703159         <li>Pointer to specification text</li>
    31713160      </ul>
    3172       <p id="rfc.section.10.1.1.p.2">Values to be added to this name space require IETF Review (see <a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>).
    3173       </p>
    3174       <h3 id="rfc.section.10.1.2"><a href="#rfc.section.10.1.2">10.1.2</a>&nbsp;<a id="considerations.for.new.methods" href="#considerations.for.new.methods">Considerations for New Methods</a></h3>
    3175       <p id="rfc.section.10.1.2.p.1">Standardized HTTP methods are generic; that is, they are potentially applicable to any resource, not just one particular media
     3161      <p id="rfc.section.9.1.1.p.2">Values to be added to this name space require IETF Review (see <a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>).
     3162      </p>
     3163      <h3 id="rfc.section.9.1.2"><a href="#rfc.section.9.1.2">9.1.2</a>&nbsp;<a id="considerations.for.new.methods" href="#considerations.for.new.methods">Considerations for New Methods</a></h3>
     3164      <p id="rfc.section.9.1.2.p.1">Standardized HTTP methods are generic; that is, they are potentially applicable to any resource, not just one particular media
    31763165         type, kind of resource, or application. As such, it is preferred that new HTTP methods be registered in a document that isn't
    31773166         specific to a single application or data format, since orthogonal technologies deserve orthogonal specification.
    31783167      </p>
    3179       <p id="rfc.section.10.1.2.p.2">Since HTTP message parsing (<a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.29"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) is independent of method semantics (aside from responses to HEAD), definitions of new HTTP methods cannot change the parsing
     3168      <p id="rfc.section.9.1.2.p.2">Since HTTP message parsing (<a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.29"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) is independent of method semantics (aside from responses to HEAD), definitions of new HTTP methods cannot change the parsing
    31803169         algorithm or prohibit the presence of a message body on either the request or the response message. Definitions of new methods
    31813170         can specify that only zero-length bodies are allowed, which would imply that each such messages would be required to contain
    31823171         a Content-Length header field with a value of "0".
    31833172      </p>
    3184       <p id="rfc.section.10.1.2.p.3">New method definitions need to indicate whether they are safe (<a href="#safe.methods" title="Safe Methods">Section&nbsp;5.2.1</a>), idempotent (<a href="#idempotent.methods" title="Idempotent Methods">Section&nbsp;5.2.2</a>), cacheable (<a href="#cacheable.methods" title="Cacheable Methods">Section&nbsp;5.2.3</a>), and what semantics are to be associated with the request body if any is present in the request. If a method is cacheable,
     3173      <p id="rfc.section.9.1.2.p.3">New method definitions need to indicate whether they are safe (<a href="#safe.methods" title="Safe Methods">Section&nbsp;4.2.1</a>), idempotent (<a href="#idempotent.methods" title="Idempotent Methods">Section&nbsp;4.2.2</a>), cacheable (<a href="#cacheable.methods" title="Cacheable Methods">Section&nbsp;4.2.3</a>), and what semantics are to be associated with the request body if any is present in the request. If a method is cacheable,
    31853174         the method definition ought to describe how, and under what conditions, a cache can store a response and use it to satisfy
    31863175         a subsequent request.
    31873176      </p>
    3188       <h3 id="rfc.section.10.1.3"><a href="#rfc.section.10.1.3">10.1.3</a>&nbsp;<a id="method.registration" href="#method.registration">Registrations</a></h3>
    3189       <p id="rfc.section.10.1.3.p.1">The HTTP Method Registry shall be populated with the registrations below:</p>
     3177      <h3 id="rfc.section.9.1.3"><a href="#rfc.section.9.1.3">9.1.3</a>&nbsp;<a id="method.registration" href="#method.registration">Registrations</a></h3>
     3178      <p id="rfc.section.9.1.3.p.1">The HTTP Method Registry shall be populated with the registrations below:</p>
    31903179      <div id="rfc.table.2">
    31913180         <div id="iana.method.registration.table"></div>
     
    32043193                  <td class="left">no</td>
    32053194                  <td class="left">no</td>
    3206                   <td class="left"> <a href="#CONNECT" id="rfc.xref.CONNECT.2" title="CONNECT">Section&nbsp;5.3.6</a>
     3195                  <td class="left"> <a href="#CONNECT" id="rfc.xref.CONNECT.2" title="CONNECT">Section&nbsp;4.3.6</a>
    32073196                  </td>
    32083197               </tr>
     
    32113200                  <td class="left">no</td>
    32123201                  <td class="left">yes</td>
    3213                   <td class="left"> <a href="#DELETE" id="rfc.xref.DELETE.2" title="DELETE">Section&nbsp;5.3.5</a>
     3202                  <td class="left"> <a href="#DELETE" id="rfc.xref.DELETE.2" title="DELETE">Section&nbsp;4.3.5</a>
    32143203                  </td>
    32153204               </tr>
     
    32183207                  <td class="left">yes</td>
    32193208                  <td class="left">yes</td>
    3220                   <td class="left"> <a href="#GET" id="rfc.xref.GET.3" title="GET">Section&nbsp;5.3.1</a>
     3209                  <td class="left"> <a href="#GET" id="rfc.xref.GET.3" title="GET">Section&nbsp;4.3.1</a>
    32213210                  </td>
    32223211               </tr>
     
    32253214                  <td class="left">yes</td>
    32263215                  <td class="left">yes</td>
    3227                   <td class="left"> <a href="#HEAD" id="rfc.xref.HEAD.2" title="HEAD">Section&nbsp;5.3.2</a>
     3216                  <td class="left"> <a href="#HEAD" id="rfc.xref.HEAD.2" title="HEAD">Section&nbsp;4.3.2</a>
    32283217                  </td>
    32293218               </tr>
     
    32323221                  <td class="left">yes</td>
    32333222                  <td class="left">yes</td>
    3234                   <td class="left"> <a href="#OPTIONS" id="rfc.xref.OPTIONS.3" title="OPTIONS">Section&nbsp;5.3.7</a>
     3223                  <td class="left"> <a href="#OPTIONS" id="rfc.xref.OPTIONS.3" title="OPTIONS">Section&nbsp;4.3.7</a>
    32353224                  </td>
    32363225               </tr>
     
    32393228                  <td class="left">no</td>
    32403229                  <td class="left">no</td>
    3241                   <td class="left"> <a href="#POST" id="rfc.xref.POST.3" title="POST">Section&nbsp;5.3.3</a>
     3230                &nbs