Changeset 1927


Ignore:
Timestamp:
Oct 1, 2012, 4:58:46 AM (7 years ago)
Author:
fielding@…
Message:

Clean up content codings and Content-Encoding sections

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

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.html

    r1926 r1927  
    10121012      </p>
    10131013      <h3 id="rfc.section.3.1.2"><a href="#rfc.section.3.1.2">3.1.2</a>&nbsp;<a id="data.encoding" href="#data.encoding">Data Encoding</a></h3>
     1014      <div id="rfc.iref.c.3"></div>
     1015      <div id="rfc.iref.c.4"></div>
     1016      <div id="rfc.iref.x.1"></div>
     1017      <div id="rfc.iref.d.1"></div>
     1018      <div id="rfc.iref.g.9"></div>
     1019      <div id="rfc.iref.x.2"></div>
    10141020      <h4 id="rfc.section.3.1.2.1"><a href="#rfc.section.3.1.2.1">3.1.2.1</a>&nbsp;<a id="content.codings" href="#content.codings">Content Codings</a></h4>
    10151021      <p id="rfc.section.3.1.2.1.p.1">Content coding values indicate an encoding transformation that has been or can be applied to a representation. Content codings
     
    10181024         directly, and only decoded by the recipient.
    10191025      </p>
    1020       <div id="rfc.figure.u.6"></div><pre class="inline"><span id="rfc.iref.g.9"></span>  <a href="#content.codings" class="smpl">content-coding</a>   = <a href="#imported.abnf" class="smpl">token</a>
    1021 </pre><p id="rfc.section.3.1.2.1.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.1" 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.1.2.2</a>) header fields. Although the value describes the content-coding, what is more important is that it indicates what decoding
    1022          mechanism will be required to remove the encoding.
    1023       </p>
    1024       <p id="rfc.section.3.1.2.1.p.4">compress<span id="rfc.iref.c.3"></span> 
    1025       </p>
     1026      <div id="rfc.figure.u.6"></div><pre class="inline"><span id="rfc.iref.g.10"></span>  <a href="#content.codings" class="smpl">content-coding</a>   = <a href="#imported.abnf" class="smpl">token</a>
     1027</pre><p id="rfc.section.3.1.2.1.p.3">All content-coding values are case-insensitive and <em class="bcp14">SHOULD</em> be registered within the HTTP Content Coding registry, as defined in <a href="#content.coding.registry" title="Content Coding Registry">Section&nbsp;9.4</a>. They are used in the <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>) 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.1.2.2</a>) header fields.
     1028      </p>
     1029      <p id="rfc.section.3.1.2.1.p.4">The following content-coding values are defined by this specification: </p>
    10261030      <ul class="empty">
    1027          <li>See <a href="p1-messaging.html#compress.coding" title="Compress Coding">Section 4.2.1</a> of <a href="#Part1" id="rfc.xref.Part1.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.
    1028          </li>
    1029       </ul>
    1030       <p id="rfc.section.3.1.2.1.p.5">deflate<span id="rfc.iref.d.1"></span> 
    1031       </p>
    1032       <ul class="empty">
    1033          <li>See <a href="p1-messaging.html#deflate.coding" title="Deflate Coding">Section 4.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.
    1034          </li>
    1035       </ul>
    1036       <p id="rfc.section.3.1.2.1.p.6">gzip<span id="rfc.iref.g.10"></span> 
    1037       </p>
    1038       <ul class="empty">
    1039          <li>See <a href="p1-messaging.html#gzip.coding" title="Gzip Coding">Section 4.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.9"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.
    1040          </li>
    1041       </ul>
    1042       <div id="rfc.iref.c.4"></div>
     1031         <li>compress (and x-compress): See <a href="p1-messaging.html#compress.coding" title="Compress Coding">Section 4.2.1</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>.
     1032         </li>
     1033         <li>deflate: See <a href="p1-messaging.html#deflate.coding" title="Deflate Coding">Section 4.2.2</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>.
     1034         </li>
     1035         <li>gzip (and x-gzip): See <a href="p1-messaging.html#gzip.coding" title="Gzip Coding">Section 4.2.3</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>.
     1036         </li>
     1037      </ul>
     1038      <div id="rfc.iref.c.5"></div>
    10431039      <h4 id="rfc.section.3.1.2.2"><a href="#rfc.section.3.1.2.2">3.1.2.2</a>&nbsp;<a id="header.content-encoding" href="#header.content-encoding">Content-Encoding</a></h4>
    1044       <p id="rfc.section.3.1.2.2.p.1">The "Content-Encoding" header field indicates what content-codings have been applied to the representation beyond those inherent
    1045          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
    1046          its underlying media type.
     1040      <p id="rfc.section.3.1.2.2.p.1">The "Content-Encoding" header field indicates what content codings have been applied to the representation, beyond those inherent
     1041         in the media type, and thus what decoding mechanisms have to be applied in order to obtain data in the media type referenced
     1042         by the <a href="#header.content-type" class="smpl">Content-Type</a> header field. Content-Encoding is primarily used to allow a representation's data to be compressed without losing the identity
     1043         of its underlying media type.
    10471044      </p>
    10481045      <div id="rfc.figure.u.7"></div><pre class="inline"><span id="rfc.iref.g.11"></span>  <a href="#header.content-encoding" class="smpl">Content-Encoding</a> = 1#<a href="#content.codings" class="smpl">content-coding</a>
    1049 </pre><p id="rfc.section.3.1.2.2.p.3">Content codings are defined in <a href="#content.codings" title="Content Codings">Section&nbsp;3.1.2.1</a>. An example of its use is
    1050       </p>
     1046</pre><p id="rfc.section.3.1.2.2.p.3">An example of its use is</p>
    10511047      <div id="rfc.figure.u.8"></div><pre class="text">  Content-Encoding: gzip
    1052 </pre><p id="rfc.section.3.1.2.2.p.5">The content-coding is a characteristic of the representation. Typically, the representation data is stored with this encoding
    1053          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
     1048</pre><p id="rfc.section.3.1.2.2.p.5">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.
     1049      </p>
     1050      <p id="rfc.section.3.1.2.2.p.6">Unlike Transfer-Encoding (<a href="p1-messaging.html#header.transfer-encoding" title="Transfer-Encoding">Section 3.3.1</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 codings listed in Content-Encoding are a characteristic of the representation; the representation is defined in terms
     1051         of the coded form, and all other metadata about the representation is about the coded form unless otherwise noted in the metadata
     1052         definition. Typically, the representation is only decoded just prior to rendering or analogous usage.
     1053      </p>
     1054      <p id="rfc.section.3.1.2.2.p.7">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
    10541055         directive is present in the message.
    10551056      </p>
    1056       <p id="rfc.section.3.1.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
    1057          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
    1058          would only be listed if, for some bizarre reason, it is applied a second time to form the representation. Likewise, an origin
    1059          server might choose to publish the same payload data as multiple representations that differ only in whether the coding is
    1060          defined as part of <a href="#header.content-type" class="smpl">Content-Type</a> or Content-Encoding, since some user agents will behave differently in their handling of each response (e.g., open a "Save
     1057      <p id="rfc.section.3.1.2.2.p.8">If the media type includes an inherent encoding, such as a data format that is always compressed, then that encoding would
     1058         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
     1059         coding would only be listed if, for some bizarre reason, it is applied a second time to form the representation. Likewise,
     1060         an origin server might choose to publish the same payload data as multiple representations that differ only in whether the
     1061         coding is defined as part of <a href="#header.content-type" class="smpl">Content-Type</a> or Content-Encoding, since some user agents will behave differently in their handling of each response (e.g., open a "Save
    10611062         as ..." dialog instead of automatic decompression and rendering of content).
    1062       </p>
    1063       <p id="rfc.section.3.1.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.
    1064       </p>
    1065       <p id="rfc.section.3.1.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.
    10661063      </p>
    10671064      <p id="rfc.section.3.1.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).
     
    10831080</pre> <p id="rfc.section.3.1.3.1.p.6">See <a href="#RFC5646" id="rfc.xref.RFC5646.3"><cite title="Tags for Identifying Languages">[RFC5646]</cite></a> for further information.
    10841081      </p>
    1085       <div id="rfc.iref.c.5"></div>
     1082      <div id="rfc.iref.c.6"></div>
    10861083      <h4 id="rfc.section.3.1.3.2"><a href="#rfc.section.3.1.3.2">3.1.3.2</a>&nbsp;<a id="header.content-language" href="#header.content-language">Content-Language</a></h4>
    10871084      <p id="rfc.section.3.1.3.2.p.1">The "Content-Language" header field describes the natural language(s) of the intended audience for the representation. Note
     
    11251122      </p>
    11261123      <ol>
    1127          <li>If the request is GET or HEAD and the response status code is <a href="#status.200" class="smpl">200 (OK)</a>, <a href="#status.204" class="smpl">204 (No Content)</a>, <a href="p5-range.html#status.206" class="smpl">206 (Partial Content)</a>, or <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a>, the payload's identifier is 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>).
     1124         <li>If the request is GET or HEAD and the response status code is <a href="#status.200" class="smpl">200 (OK)</a>, <a href="#status.204" class="smpl">204 (No Content)</a>, <a href="p5-range.html#status.206" class="smpl">206 (Partial Content)</a>, or <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a>, the payload's identifier is 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.11"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>).
    11281125         </li>
    11291126         <li>If the request is GET or HEAD and the response status code is <a href="#status.203" class="smpl">203 (Non-Authoritative Information)</a>, the payload is a potentially modified representation of the target resource; as such, the effective request URI might only
     
    11391136         <li>Otherwise, the payload is unidentified.</li>
    11401137      </ol>
    1141       <div id="rfc.iref.c.6"></div>
     1138      <div id="rfc.iref.c.7"></div>
    11421139      <h4 id="rfc.section.3.1.4.2"><a href="#rfc.section.3.1.4.2">3.1.4.2</a>&nbsp;<a id="header.content-location" href="#header.content-location">Content-Location</a></h4>
    11431140      <p id="rfc.section.3.1.4.2.p.1">The "Content-Location" header field references a URI that can be used as a specific identifier for the representation in this
     
    11451142      </p>
    11461143      <div id="rfc.figure.u.14"></div><pre class="inline"><span id="rfc.iref.g.14"></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>
    1147 </pre><p id="rfc.section.3.1.4.2.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.11"><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
     1144</pre><p id="rfc.section.3.1.4.2.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.12"><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
    11481145         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.
    11491146      </p>
     
    12221219               <tr>
    12231220                  <td class="left">Content-Length</td>
    1224                   <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.12"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a></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.13"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a></td>
    12251222               </tr>
    12261223               <tr>
     
    12301227               <tr>
    12311228                  <td class="left">Transfer-Encoding</td>
    1232                   <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.13"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a></td>
     1229                  <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.14"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a></td>
    12331230               </tr>
    12341231            </tbody>
     
    14531450         repeated failures would indicate a problem within the server.
    14541451      </p>
    1455       <div id="rfc.iref.c.7"></div>
     1452      <div id="rfc.iref.c.8"></div>
    14561453      <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>
    14571454      <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
     
    15931590         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>).
    15941591      </p>
    1595       <div id="rfc.iref.c.8"></div>
     1592      <div id="rfc.iref.c.9"></div>
    15961593      <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>
    15971594      <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
    15981595         its behavior to blind forwarding of packets until the connection is closed.
    15991596      </p>
    1600       <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.14"><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.
     1597      <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.15"><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.
    16011598         For example,
    16021599      </p>
     
    16431640         body to make more detailed queries on the server.
    16441641      </p>
    1645       <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.15"><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.
     1642      <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.16"><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.
    16461643         Since a server's communication options typically depend on the resource, the "*" request is only useful as a "ping" or "no-op"
    16471644         type of method; it does nothing beyond allowing the client to test the capabilities of the server. For example, this can be
     
    16611658      </p>
    16621659      <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
    1663          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.16"><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
     1660         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.17"><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
    16641661         messages in an infinite loop.
    16651662      </p>
    1666       <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.17"><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.
     1663      <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.18"><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.
    16671664      </p>
    16681665      <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>
     
    16851682               <tr>
    16861683                  <td class="left">Host</td>
    1687                   <td class="left"><a href="p1-messaging.html#header.host" title="Host">Section 5.4</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></td>
     1684                  <td class="left"><a href="p1-messaging.html#header.host" title="Host">Section 5.4</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></td>
    16881685               </tr>
    16891686               <tr>
     
    17281725      </p>
    17291726      <p id="rfc.section.6.1.2.p.4">The only expectation defined by this specification is:</p>
    1730       <p id="rfc.section.6.1.2.p.5"><span id="rfc.iref.45"></span><span id="rfc.iref.e.2"></span> 100-continue
     1727      <p id="rfc.section.6.1.2.p.5"><span id="rfc.iref.48"></span><span id="rfc.iref.e.2"></span> 100-continue
    17311728      </p>
    17321729      <ul class="empty">
     
    20972094               <tr>
    20982095                  <td class="left">TE</td>
    2099                   <td class="left"><a href="p1-messaging.html#header.te" title="TE">Section 4.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></td>
     2096                  <td class="left"><a href="p1-messaging.html#header.te" title="TE">Section 4.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></td>
    21002097               </tr>
    21012098               <tr>
     
    21512148         user agent limitations.
    21522149      </p>
    2153       <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;4</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.20"><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
     2150      <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;4</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.21"><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
    21542151         for identifying the application.
    21552152      </p>
     
    24142411      <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>
    24152412      <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>
    2416       <div id="rfc.iref.67"></div>
     2413      <div id="rfc.iref.70"></div>
    24172414      <div id="rfc.iref.s.2"></div>
    24182415      <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,
     
    24272424         a request, then it need not forward the corresponding <a href="#status.100" class="smpl">100 (Continue)</a> response(s).)
    24282425      </p>
    2429       <div id="rfc.iref.68"></div>
     2426      <div id="rfc.iref.71"></div>
    24302427      <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>
    24312428      <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
     
    24332430         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.
    24342431      </p>
    2435       <div id="rfc.iref.68"></div>
     2432      <div id="rfc.iref.71"></div>
    24362433      <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>
    2437       <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.21"><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
     2434      <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.22"><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
    24382435         by the response's Upgrade header field immediately after the empty line which terminates the 101 response.
    24392436      </p>
     
    24432440      </p>
    24442441      <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>
    2445       <div id="rfc.iref.68"></div>
     2442      <div id="rfc.iref.71"></div>
    24462443      <div id="rfc.iref.s.3"></div>
    24472444      <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>
    2448       <div id="rfc.iref.69"></div>
     2445      <div id="rfc.iref.72"></div>
    24492446      <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>
    24502447      <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>
     
    24612458      <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.
    24622459      </p>
    2463       <div id="rfc.iref.69"></div>
     2460      <div id="rfc.iref.72"></div>
    24642461      <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>
    24652462      <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>
     
    24732470         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.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>).
    24742471      </p>
    2475       <div id="rfc.iref.69"></div>
     2472      <div id="rfc.iref.72"></div>
    24762473      <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>
    24772474      <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
     
    24842481         user can expect the request to be fulfilled.
    24852482      </p>
    2486       <div id="rfc.iref.69"></div>
     2483      <div id="rfc.iref.72"></div>
    24872484      <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>
    2488       <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.22"><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>).
     2485      <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.23"><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>).
    24892486      </p>
    24902487      <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
     
    24932490      <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.
    24942491      </p>
    2495       <div id="rfc.iref.69"></div>
     2492      <div id="rfc.iref.72"></div>
    24962493      <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>
    24972494      <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
     
    25132510      <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.
    25142511      </p>
    2515       <div id="rfc.iref.69"></div>
     2512      <div id="rfc.iref.72"></div>
    25162513      <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>
    25172514      <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
     
    25192516         another input action.
    25202517      </p>
    2521       <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.23"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.
     2518      <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.24"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.
    25222519      </p>
    25232520      <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>
    2524       <div id="rfc.iref.69"></div>
     2521      <div id="rfc.iref.72"></div>
    25252522      <div id="rfc.iref.s.4"></div>
    25262523      <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.
     
    25682565         </p>
    25692566      </div>
    2570       <div id="rfc.iref.70"></div>
     2567      <div id="rfc.iref.73"></div>
    25712568      <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>
    25722569      <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
     
    25822579      <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.
    25832580      </p>
    2584       <div id="rfc.iref.70"></div>
     2581      <div id="rfc.iref.73"></div>
    25852582      <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>
    25862583      <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
     
    25952592         </p>
    25962593      </div>
    2597       <div id="rfc.iref.70"></div>
     2594      <div id="rfc.iref.73"></div>
    25982595      <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>
    25992596      <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.
     
    26052602         </p>
    26062603      </div>
    2607       <div id="rfc.iref.70"></div>
     2604      <div id="rfc.iref.73"></div>
    26082605      <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>
    26092606      <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
     
    26252622      <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.
    26262623      </p>
    2627       <div id="rfc.iref.70"></div>
     2624      <div id="rfc.iref.73"></div>
    26282625      <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>
    26292626      <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.
    26302627      </p>
    2631       <div id="rfc.iref.70"></div>
     2628      <div id="rfc.iref.73"></div>
    26322629      <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>
    26332630      <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>
    2634       <div id="rfc.iref.70"></div>
     2631      <div id="rfc.iref.73"></div>
    26352632      <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>
    26362633      <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.
     
    26452642      </div>
    26462643      <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>
    2647       <div id="rfc.iref.70"></div>
     2644      <div id="rfc.iref.73"></div>
    26482645      <div id="rfc.iref.s.5"></div>
    26492646      <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
     
    26512648         These status codes are applicable to any request method. User agents <em class="bcp14">SHOULD</em> display any included representation to the user.
    26522649      </p>
    2653       <div id="rfc.iref.71"></div>
     2650      <div id="rfc.iref.74"></div>
    26542651      <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>
    26552652      <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>
    2656       <div id="rfc.iref.71"></div>
     2653      <div id="rfc.iref.74"></div>
    26572654      <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>
    26582655      <p id="rfc.section.7.5.2.p.1">This code is reserved for future use.</p>
    2659       <div id="rfc.iref.71"></div>
     2656      <div id="rfc.iref.74"></div>
    26602657      <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>
    26612658      <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
     
    26662663            (Not Found)</a>  <em class="bcp14">MAY</em> be used instead.
    26672664      </p>
    2668       <div id="rfc.iref.71"></div>
     2665      <div id="rfc.iref.74"></div>
    26692666      <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>
    26702667      <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
     
    26732670         has been refused, or when no other response is applicable.
    26742671      </p>
    2675       <div id="rfc.iref.71"></div>
     2672      <div id="rfc.iref.74"></div>
    26762673      <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>
    26772674      <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.
    26782675      </p>
    2679       <div id="rfc.iref.71"></div>
     2676      <div id="rfc.iref.74"></div>
    26802677      <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>
    26812678      <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
     
    26942691      <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.
    26952692      </p>
    2696       <div id="rfc.iref.71"></div>
     2693      <div id="rfc.iref.74"></div>
    26972694      <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>
    26982695      <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.
    26992696      </p>
    2700       <div id="rfc.iref.71"></div>
     2697      <div id="rfc.iref.74"></div>
    27012698      <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>
    27022699      <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
     
    27092706         contain a list of the differences between the two versions.
    27102707      </p>
    2711       <div id="rfc.iref.71"></div>
     2708      <div id="rfc.iref.74"></div>
    27122709      <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>
    27132710      <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
     
    27232720      <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.
    27242721      </p>
    2725       <div id="rfc.iref.71"></div>
     2722      <div id="rfc.iref.74"></div>
    27262723      <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>
    27272724      <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
    27282725         message.
    27292726      </p>
    2730       <div id="rfc.iref.71"></div>
     2727      <div id="rfc.iref.74"></div>
    27312728      <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>
    27322729      <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
     
    27352732      <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.
    27362733      </p>
    2737       <div id="rfc.iref.71"></div>
     2734      <div id="rfc.iref.74"></div>
    27382735      <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>
    27392736      <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.
     
    27432740         in some servers using fixed-length buffers for reading or manipulating the request-target.
    27442741      </p>
    2745       <div id="rfc.iref.71"></div>
     2742      <div id="rfc.iref.74"></div>
    27462743      <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>
    27472744      <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
    27482745         on the target resource.
    27492746      </p>
    2750       <div id="rfc.iref.71"></div>
     2747      <div id="rfc.iref.74"></div>
    27512748      <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>
    27522749      <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
    27532750         not be met by the next-hop server.
    27542751      </p>
    2755       <div id="rfc.iref.71"></div>
     2752      <div id="rfc.iref.74"></div>
    27562753      <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>
    2757       <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.24"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) specifying the required protocols.
     2754      <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.25"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) specifying the required protocols.
    27582755      </p>
    27592756      <div id="rfc.figure.u.41"></div>
     
    27692766      </p>
    27702767      <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>
    2771       <div id="rfc.iref.71"></div>
     2768      <div id="rfc.iref.74"></div>
    27722769      <div id="rfc.iref.s.6"></div>
    27732770      <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
     
    27752772         User agents <em class="bcp14">SHOULD</em> display any included representation to the user. These response codes are applicable to any request method.
    27762773      </p>
    2777       <div id="rfc.iref.72"></div>
     2774      <div id="rfc.iref.75"></div>
    27782775      <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>
    27792776      <p id="rfc.section.7.6.1.p.1">The server encountered an unexpected condition which prevented it from fulfilling the request.</p>
    2780       <div id="rfc.iref.72"></div>
     2777      <div id="rfc.iref.75"></div>
    27812778      <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>
    27822779      <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
    27832780         does not recognize the request method and is not capable of supporting it for any resource.
    27842781      </p>
    2785       <div id="rfc.iref.72"></div>
     2782      <div id="rfc.iref.75"></div>
    27862783      <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>
    27872784      <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
    27882785         to fulfill the request.
    27892786      </p>
    2790       <div id="rfc.iref.72"></div>
     2787      <div id="rfc.iref.75"></div>
    27912788      <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>
    27922789      <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>
     
    28002797         </p>
    28012798      </div>
    2802       <div id="rfc.iref.72"></div>
     2799      <div id="rfc.iref.75"></div>
    28032800      <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>
    28042801      <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
     
    28102807         </p>
    28112808      </div>
    2812       <div id="rfc.iref.72"></div>
     2809      <div id="rfc.iref.75"></div>
    28132810      <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>
    28142811      <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
    28152812         is indicating that it is unable or unwilling to complete the request using the same major version as the client, as described
    2816          in <a href="p1-messaging.html#http.version" title="Protocol Versioning">Section 2.6</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>, 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.
     2813         in <a href="p1-messaging.html#http.version" title="Protocol Versioning">Section 2.6</a> of <a href="#Part1" id="rfc.xref.Part1.26"><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.
    28172814      </p>
    28182815      <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>
    28192816      <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
    2820          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.26"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>).
     2817         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.27"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>).
    28212818      </p>
    28222819      <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>
     
    31303127      <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>
    31313128      <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>
    3132       <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;4</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.27"><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
     3129      <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;4</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.28"><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
    31333130         identifying the application.
    31343131      </p>
     
    31363133</pre><p id="rfc.section.8.4.2.p.4">Example:</p>
    31373134      <div id="rfc.figure.u.61"></div><pre class="text">  Server: CERN/3.0 libwww/2.17
    3138 </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.28"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>).
     3135</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.29"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>).
    31393136      </p>
    31403137      <div class="note" id="rfc.section.8.4.2.p.7">
     
    31673164         to a single application or data format, since orthogonal technologies deserve orthogonal specification.
    31683165      </p>
    3169       <p id="rfc.section.9.1.2.p.2">Since 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>) needs to be independent of method semantics (aside from responses to HEAD), definitions of new methods cannot change the
     3166      <p id="rfc.section.9.1.2.p.2">Since message parsing (<a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.30"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) needs to be independent of method semantics (aside from responses to HEAD), definitions of new methods cannot change the
    31703167         parsing algorithm or prohibit the presence of a message body on either the request or the response message. Definitions of
    31713168         new methods can specify that only a zero-length message body is allowed by requiring a Content-Length header field with a
     
    35083505      <h3 id="rfc.section.9.3.1"><a href="#rfc.section.9.3.1">9.3.1</a>&nbsp;<a id="considerations.for.new.header.fields" href="#considerations.for.new.header.fields">Considerations for New Header Fields</a></h3>
    35093506      <p id="rfc.section.9.3.1.p.1">Header fields are key:value pairs that can be used to communicate data about the message, its payload, the target resource,
    3510          or the connection (i.e., control data). See <a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.30"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a> for a general definition of header field syntax in HTTP messages.
     3507         or the connection (i.e., control data). See <a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.31"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a> for a general definition of header field syntax in HTTP messages.
    35113508      </p>
    35123509      <p id="rfc.section.9.3.1.p.2">The requirements for header field names are defined in <a href="http://tools.ietf.org/html/rfc3864#section-4.1">Section 4.1</a> of <a href="#RFC3864" id="rfc.xref.RFC3864.2"><cite title="Registration Procedures for Message Header Fields">[RFC3864]</cite></a>. Authors of specifications defining new fields are advised to keep the name as short as practical, and not to prefix them
    35133510         with "X-" if they are to be registered (either immediately or in the future).
    35143511      </p>
    3515       <p id="rfc.section.9.3.1.p.3">New header field values typically have their syntax defined using ABNF (<a href="#RFC5234" id="rfc.xref.RFC5234.2"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>), using the extension defined in <a href="p1-messaging.html#abnf.extension" title="ABNF list extension: #rule">Appendix B</a> of <a href="#Part1" id="rfc.xref.Part1.31"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a> as necessary, and are usually constrained to the range of ASCII characters. Header fields needing a greater range of characters
     3512      <p id="rfc.section.9.3.1.p.3">New header field values typically have their syntax defined using ABNF (<a href="#RFC5234" id="rfc.xref.RFC5234.2"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>), using the extension defined in <a href="p1-messaging.html#abnf.extension" title="ABNF list extension: #rule">Appendix B</a> of <a href="#Part1" id="rfc.xref.Part1.32"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a> as necessary, and are usually constrained to the range of ASCII characters. Header fields needing a greater range of characters
    35163513         can use an encoding such as the one defined in <a href="#RFC5987" id="rfc.xref.RFC5987.1"><cite title="Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters">[RFC5987]</cite></a>.
    35173514      </p>
    35183515      <p id="rfc.section.9.3.1.p.4">Because commas (",") are used as a generic delimiter between field-values, they need to be treated with care if they are allowed
    35193516         in the field-value's payload. Typically, components that might contain a comma are protected with double-quotes using the
    3520          quoted-string ABNF production (<a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a> of <a href="#Part1" id="rfc.xref.Part1.32"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>).
     3517         quoted-string ABNF production (<a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a> of <a href="#Part1" id="rfc.xref.Part1.33"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>).
    35213518      </p>
    35223519      <p id="rfc.section.9.3.1.p.5">For example, a textual date and a URI (either of which might contain a comma) could be safely carried in field-values like
     
    35363533      <ul>
    35373534         <li>
    3538             <p>Whether the field is a single value, or whether it can be a list (delimited by commas; see <a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.33"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>).
     3535            <p>Whether the field is a single value, or whether it can be a list (delimited by commas; see <a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.34"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>).
    35393536            </p>
    35403537            <p>If it does not use the list syntax, document how to treat messages where the header field occurs multiple times (a sensible
     
    35523549         </li>
    35533550         <li>
    3554             <p>Whether it is appropriate to list the field-name in the <a href="p1-messaging.html#header.connection" class="smpl">Connection</a> header field (i.e., if the header field is to be hop-by-hop, see <a href="p1-messaging.html#header.connection" title="Connection">Section 6.1</a> of <a href="#Part1" id="rfc.xref.Part1.34"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>).
     3551            <p>Whether it is appropriate to list the field-name in the <a href="p1-messaging.html#header.connection" class="smpl">Connection</a> header field (i.e., if the header field is to be hop-by-hop, see <a href="p1-messaging.html#header.connection" title="Connection">Section 6.1</a> of <a href="#Part1" id="rfc.xref.Part1.35"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>).
    35553552            </p>
    35563553         </li>
     
    35633560         </li>
    35643561         <li>
    3565             <p>Whether the header field is useful or allowable in trailers (see <a href="p1-messaging.html#chunked.encoding" title="Chunked Transfer Coding">Section 4.1</a> of <a href="#Part1" id="rfc.xref.Part1.35"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>).
     3562            <p>Whether the header field is useful or allowable in trailers (see <a href="p1-messaging.html#chunked.encoding" title="Chunked Transfer Coding">Section 4.1</a> of <a href="#Part1" id="rfc.xref.Part1.36"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>).
    35663563            </p>
    35673564         </li>
     
    37293726      <p id="rfc.section.9.3.2.p.2">The change controller for the above registrations is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
    37303727      <h2 id="rfc.section.9.4"><a href="#rfc.section.9.4">9.4</a>&nbsp;<a id="content.coding.registry" href="#content.coding.registry">Content Coding Registry</a></h2>
    3731       <p id="rfc.section.9.4.p.1">The HTTP Content Coding Registry defines the name space for content coding names (<a href="p1-messaging.html#compression.codings" title="Compression Codings">Section 4.2</a> of <a href="#Part1" id="rfc.xref.Part1.36"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>). The content coding registry is maintained at &lt;<a href="http://www.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http-parameters</a>&gt;.
     3728      <p id="rfc.section.9.4.p.1">The HTTP Content Coding Registry defines the name space for content coding names (<a href="p1-messaging.html#compression.codings" title="Compression Codings">Section 4.2</a> of <a href="#Part1" id="rfc.xref.Part1.37"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>). The content coding registry is maintained at &lt;<a href="http://www.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http-parameters</a>&gt;.
    37323729      </p>
    37333730      <h3 id="rfc.section.9.4.1"><a href="#rfc.section.9.4.1">9.4.1</a>&nbsp;<a id="content.coding.procedure" href="#content.coding.procedure">Procedure</a></h3>
     
    37393736         <li>Pointer to specification text</li>
    37403737      </ul>
    3741       <p id="rfc.section.9.4.1.p.2">Names of content codings <em class="bcp14">MUST NOT</em> overlap with names of transfer codings (<a href="p1-messaging.html#transfer.codings" title="Transfer Codings">Section 4</a> of <a href="#Part1" id="rfc.xref.Part1.37"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>), unless the encoding transformation is identical (as is the case for the compression codings defined in <a href="p1-messaging.html#compression.codings" title="Compression Codings">Section 4.2</a> of <a href="#Part1" id="rfc.xref.Part1.38"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>).
     3738      <p id="rfc.section.9.4.1.p.2">Names of content codings <em class="bcp14">MUST NOT</em> overlap with names of transfer codings (<a href="p1-messaging.html#transfer.codings" title="Transfer Codings">Section 4</a> of <a href="#Part1" id="rfc.xref.Part1.38"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>), unless the encoding transformation is identical (as is the case for the compression codings defined in <a href="p1-messaging.html#compression.codings" title="Compression Codings">Section 4.2</a> of <a href="#Part1" id="rfc.xref.Part1.39"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>).
    37423739      </p>
    37433740      <p id="rfc.section.9.4.1.p.3">Values to be added to this name space require IETF Review (see <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a> of <a href="#RFC5226" id="rfc.xref.RFC5226.3"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>), and <em class="bcp14">MUST</em> conform to the purpose of content coding defined in this section.
     
    37593756                  <td class="left">compress</td>
    37603757                  <td class="left">UNIX "compress" program method</td>
    3761                   <td class="left"> <a href="p1-messaging.html#compress.coding" title="Compress Coding">Section 4.2.1</a> of <a href="#Part1" id="rfc.xref.Part1.39"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>
     3758                  <td class="left"> <a href="p1-messaging.html#compress.coding" title="Compress Coding">Section 4.2.1</a> of <a href="#Part1" id="rfc.xref.Part1.40"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>
    37623759                  </td>
    37633760               </tr>
     
    37663763                  <td class="left">"deflate" compression mechanism (<a href="#RFC1951" id="rfc.xref.RFC1951.1"><cite title="DEFLATE Compressed Data Format Specification version 1.3">[RFC1951]</cite></a>) used inside the "zlib" data format (<a href="#RFC1950" id="rfc.xref.RFC1950.1"><cite title="ZLIB Compressed Data Format Specification version 3.3">[RFC1950]</cite></a>)
    37673764                  </td>
    3768                   <td class="left"> <a href="p1-messaging.html#deflate.coding" title="Deflate Coding">Section 4.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.40"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>
     3765                  <td class="left"> <a href="p1-messaging.html#deflate.coding" title="Deflate Coding">Section 4.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.41"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>
    37693766                  </td>
    37703767               </tr>
     
    37723769                  <td class="left">gzip</td>
    37733770                  <td class="left">Same as GNU zip <a href="#RFC1952" id="rfc.xref.RFC1952.1"><cite title="GZIP file format specification version 4.3">[RFC1952]</cite></a></td>
    3774                   <td class="left"> <a href="p1-messaging.html#gzip.coding" title="Gzip Coding">Section 4.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.41"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>
     3771                  <td class="left"> <a href="p1-messaging.html#gzip.coding" title="Gzip Coding">Section 4.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.42"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>
    37753772                  </td>
    37763773               </tr>
     
    38643861      </p>
    38653862      <h1 id="rfc.section.11"><a href="#rfc.section.11">11.</a>&nbsp;<a id="acks" href="#acks">Acknowledgments</a></h1>
    3866       <p id="rfc.section.11.p.1">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 9</a> of <a href="#Part1" id="rfc.xref.Part1.42"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.
     3863      <p id="rfc.section.11.p.1">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 9</a> of <a href="#Part1" id="rfc.xref.Part1.43"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.
    38673864      </p>
    38683865      <h1 id="rfc.references"><a id="rfc.section.12" href="#rfc.section.12">12.</a> References
     
    41104107         However, this parameter is not part of the MIME standards).
    41114108      </p>
    4112       <div id="rfc.iref.c.9"></div>
     4109      <div id="rfc.iref.c.10"></div>
    41134110      <h2 id="rfc.section.A.5"><a href="#rfc.section.A.5">A.5</a>&nbsp;<a id="no.content-transfer-encoding" href="#no.content-transfer-encoding">No Content-Transfer-Encoding</a></h2>
    41144111      <p id="rfc.section.A.5.p.1">HTTP does not use the Content-Transfer-Encoding field of MIME. Proxies and gateways from MIME-compliant protocols to HTTP <em class="bcp14">MUST</em> remove any Content-Transfer-Encoding prior to delivering the response message to an HTTP client.
     
    41724169      </p>
    41734170      <p id="rfc.section.C.p.16">In the description of the "<a href="#header.server" class="smpl">Server</a>" header field, the "<a href="p1-messaging.html#header.via" class="smpl">Via</a>" field was described as a SHOULD. The requirement was and is stated correctly in the description of the Via header field
    4174          in <a href="p1-messaging.html#header.via" title="Via">Section 5.7</a> of <a href="#Part1" id="rfc.xref.Part1.43"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>. (<a href="#header.server" id="rfc.xref.header.server.4" title="Server">Section&nbsp;8.4.2</a>)
     4171         in <a href="p1-messaging.html#header.via" title="Via">Section 5.7</a> of <a href="#Part1" id="rfc.xref.Part1.44"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>. (<a href="#header.server" id="rfc.xref.header.server.4" title="Server">Section&nbsp;8.4.2</a>)
    41754172      </p>
    41764173      <p id="rfc.section.C.p.17">Clarify contexts that charset is used in. (<a href="#character.sets" title="Character Encodings (charset)">Section&nbsp;3.1.1.2</a>)
     
    41974194         (any visible US-ASCII character).
    41984195      </p>
    4199       <p id="rfc.section.D.p.2">The rules below are defined in <a href="#Part1" id="rfc.xref.Part1.44"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>:
    4200       </p>
    4201       <div id="rfc.figure.u.64"></div><pre class="inline">  <a href="#imported.abnf" class="smpl">BWS</a>           = &lt;BWS, defined in <a href="#Part1" id="rfc.xref.Part1.45"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.1</a>&gt;
    4202   <a href="#imported.abnf" class="smpl">OWS</a>           = &lt;OWS, defined in <a href="#Part1" id="rfc.xref.Part1.46"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.1</a>&gt;
    4203   <a href="#imported.abnf" class="smpl">RWS</a>           = &lt;RWS, defined in <a href="#Part1" id="rfc.xref.Part1.47"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.1</a>&gt;
    4204   <a href="#imported.abnf" class="smpl">URI-reference</a> = &lt;URI-reference, defined in <a href="#Part1" id="rfc.xref.Part1.48"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.7</a>&gt;
    4205   <a href="#imported.abnf" class="smpl">absolute-URI</a>  = &lt;absolute-URI, defined in <a href="#Part1" id="rfc.xref.Part1.49"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.7</a>&gt;
    4206   <a href="#imported.abnf" class="smpl">comment</a>       = &lt;comment, defined in <a href="#Part1" id="rfc.xref.Part1.50"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a>&gt;
    4207   <a href="#imported.abnf" class="smpl">field-name</a>    = &lt;comment, defined in <a href="#Part1" id="rfc.xref.Part1.51"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a>&gt;
    4208   <a href="#imported.abnf" class="smpl">partial-URI</a>   = &lt;partial-URI, defined in <a href="#Part1" id="rfc.xref.Part1.52"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.7</a>&gt;
    4209   <a href="#imported.abnf" class="smpl">quoted-string</a> = &lt;quoted-string, defined in <a href="#Part1" id="rfc.xref.Part1.53"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a>&gt;
    4210   <a href="#imported.abnf" class="smpl">token</a>         = &lt;token, defined in <a href="#Part1" id="rfc.xref.Part1.54"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a>&gt;
    4211   <a href="#imported.abnf" class="smpl">word</a>          = &lt;word, defined in <a href="#Part1" id="rfc.xref.Part1.55"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a>&gt;
     4196      <p id="rfc.section.D.p.2">The rules below are defined in <a href="#Part1" id="rfc.xref.Part1.45"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>:
     4197      </p>
     4198      <div id="rfc.figure.u.64"></div><pre class="inline">  <a href="#imported.abnf" class="smpl">BWS</a>           = &lt;BWS, defined in <a href="#Part1" id="rfc.xref.Part1.46"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.1</a>&gt;
     4199  <a href="#imported.abnf" class="smpl">OWS</a>           = &lt;OWS, defined in <a href="#Part1" id="rfc.xref.Part1.47"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.1</a>&gt;
     4200  <a href="#imported.abnf" class="smpl">RWS</a>           = &lt;RWS, defined in <a href="#Part1" id="rfc.xref.Part1.48"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.1</a>&gt;
     4201  <a href="#imported.abnf" class="smpl">URI-reference</a> = &lt;URI-reference, defined in <a href="#Part1" id="rfc.xref.Part1.49"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.7</a>&gt;
     4202  <a href="#imported.abnf" class="smpl">absolute-URI</a>  = &lt;absolute-URI, defined in <a href="#Part1" id="rfc.xref.Part1.50"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.7</a>&gt;
     4203  <a href="#imported.abnf" class="smpl">comment</a>       = &lt;comment, defined in <a href="#Part1" id="rfc.xref.Part1.51"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a>&gt;
     4204  <a href="#imported.abnf" class="smpl">field-name</a>    = &lt;comment, defined in <a href="#Part1" id="rfc.xref.Part1.52"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a>&gt;
     4205  <a href="#imported.abnf" class="smpl">partial-URI</a>   = &lt;partial-URI, defined in <a href="#Part1" id="rfc.xref.Part1.53"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.7</a>&gt;
     4206  <a href="#imported.abnf" class="smpl">quoted-string</a> = &lt;quoted-string, defined in <a href="#Part1" id="rfc.xref.Part1.54"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a>&gt;
     4207  <a href="#imported.abnf" class="smpl">token</a>         = &lt;token, defined in <a href="#Part1" id="rfc.xref.Part1.55"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a>&gt;
     4208  <a href="#imported.abnf" class="smpl">word</a>          = &lt;word, defined in <a href="#Part1" id="rfc.xref.Part1.56"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a>&gt;
    42124209</pre><h1 id="rfc.section.E"><a href="#rfc.section.E">E.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
    42134210      <div id="rfc.figure.u.65"></div> <pre class="inline"><a href="#header.accept" class="smpl">Accept</a> = [ ( "," / ( media-range [ accept-params ] ) ) *( OWS "," [
     
    49334930      </ul>
    49344931      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
    4935       <p class="noprint"><a href="#rfc.index.1">1</a> <a href="#rfc.index.2">2</a> <a href="#rfc.index.3">3</a> <a href="#rfc.index.4">4</a> <a href="#rfc.index.5">5</a> <a href="#rfc.index.A">A</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.D">D</a> <a href="#rfc.index.E">E</a> <a href="#rfc.index.F">F</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.L">L</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.O">O</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> <a href="#rfc.index.T">T</a> <a href="#rfc.index.U">U</a> <a href="#rfc.index.V">V</a>
     4932      <p class="noprint"><a href="#rfc.index.1">1</a> <a href="#rfc.index.2">2</a> <a href="#rfc.index.3">3</a> <a href="#rfc.index.4">4</a> <a href="#rfc.index.5">5</a> <a href="#rfc.index.A">A</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.D">D</a> <a href="#rfc.index.E">E</a> <a href="#rfc.index.F">F</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.L">L</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.O">O</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> <a href="#rfc.index.T">T</a> <a href="#rfc.index.U">U</a> <a href="#rfc.index.V">V</a> <a href="#rfc.index.X">X</a>
    49364933      </p>
    49374934      <div class="print2col">
    49384935         <ul class="ind">
    49394936            <li><a id="rfc.index.1" href="#rfc.index.1"><b>1</b></a><ul>
    4940                   <li>100 Continue (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.100.1">6.1.2.1</a>, <a href="#rfc.xref.status.100.2">6.1.2.1</a>, <a href="#rfc.xref.status.100.3">7.1</a>, <a href="#rfc.iref.68"><b>7.2.1</b></a>, <a href="#rfc.xref.status.100.4">9.2.3</a></li>
    4941                   <li>100-continue (expect value)&nbsp;&nbsp;<a href="#rfc.iref.45"><b>6.1.2</b></a></li>
    4942                   <li>101 Switching Protocols (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.101.1">7.1</a>, <a href="#rfc.iref.68"><b>7.2.2</b></a>, <a href="#rfc.xref.status.101.2">9.2.3</a></li>
    4943                   <li>1xx Informational (status code class)&nbsp;&nbsp;<a href="#rfc.iref.67"><b>7.2</b></a></li>
     4937                  <li>100 Continue (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.100.1">6.1.2.1</a>, <a href="#rfc.xref.status.100.2">6.1.2.1</a>, <a href="#rfc.xref.status.100.3">7.1</a>, <a href="#rfc.iref.71"><b>7.2.1</b></a>, <a href="#rfc.xref.status.100.4">9.2.3</a></li>
     4938                  <li>100-continue (expect value)&nbsp;&nbsp;<a href="#rfc.iref.48"><b>6.1.2</b></a></li>
     4939                  <li>101 Switching Protocols (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.101.1">7.1</a>, <a href="#rfc.iref.71"><b>7.2.2</b></a>, <a href="#rfc.xref.status.101.2">9.2.3</a></li>
     4940                  <li>1xx Informational (status code class)&nbsp;&nbsp;<a href="#rfc.iref.70"><b>7.2</b></a></li>
    49444941               </ul>
    49454942            </li>
    49464943            <li><a id="rfc.index.2" href="#rfc.index.2"><b>2</b></a><ul>
    4947                   <li>200 OK (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.200.1">7.1</a>, <a href="#rfc.iref.69"><b>7.3.1</b></a>, <a href="#rfc.xref.status.200.2">9.2.3</a></li>
    4948                   <li>201 Created (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.201.1">7.1</a>, <a href="#rfc.iref.69"><b>7.3.2</b></a>, <a href="#rfc.xref.status.201.2">9.2.3</a></li>
    4949                   <li>202 Accepted (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.202.1">7.1</a>, <a href="#rfc.iref.69"><b>7.3.3</b></a>, <a href="#rfc.xref.status.202.2">9.2.3</a></li>
    4950                   <li>203 Non-Authoritative Information (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.203.1">7.1</a>, <a href="#rfc.iref.69"><b>7.3.4</b></a>, <a href="#rfc.xref.status.203.2">9.2.3</a>, <a href="#rfc.xref.status.203.3">C</a></li>
    4951                   <li>204 No Content (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.204.1">7.1</a>, <a href="#rfc.iref.69"><b>7.3.5</b></a>, <a href="#rfc.xref.status.204.2">9.2.3</a></li>
    4952                   <li>205 Reset Content (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.205.1">7.1</a>, <a href="#rfc.iref.69"><b>7.3.6</b></a>, <a href="#rfc.xref.status.205.2">9.2.3</a></li>
    4953                   <li>2xx Successful (status code class)&nbsp;&nbsp;<a href="#rfc.iref.68"><b>7.3</b></a></li>
     4944                  <li>200 OK (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.200.1">7.1</a>, <a href="#rfc.iref.72"><b>7.3.1</b></a>, <a href="#rfc.xref.status.200.2">9.2.3</a></li>
     4945                  <li>201 Created (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.201.1">7.1</a>, <a href="#rfc.iref.72"><b>7.3.2</b></a>, <a href="#rfc.xref.status.201.2">9.2.3</a></li>
     4946                  <li>202 Accepted (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.202.1">7.1</a>, <a href="#rfc.iref.72"><b>7.3.3</b></a>, <a href="#rfc.xref.status.202.2">9.2.3</a></li>
     4947                  <li>203 Non-Authoritative Information (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.203.1">7.1</a>, <a href="#rfc.iref.72"><b>7.3.4</b></a>, <a href="#rfc.xref.status.203.2">9.2.3</a>, <a href="#rfc.xref.status.203.3">C</a></li>
     4948                  <li>204 No Content (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.204.1">7.1</a>, <a href="#rfc.iref.72"><b>7.3.5</b></a>, <a href="#rfc.xref.status.204.2">9.2.3</a></li>
     4949                  <li>205 Reset Content (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.205.1">7.1</a>, <a href="#rfc.iref.72"><b>7.3.6</b></a>, <a href="#rfc.xref.status.205.2">9.2.3</a></li>
     4950                  <li>2xx Successful (status code class)&nbsp;&nbsp;<a href="#rfc.iref.71"><b>7.3</b></a></li>
    49544951               </ul>
    49554952            </li>
    49564953            <li><a id="rfc.index.3" href="#rfc.index.3"><b>3</b></a><ul>
    4957                   <li>300 Multiple Choices (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.300.1">7.1</a>, <a href="#rfc.iref.70"><b>7.4.1</b></a>, <a href="#rfc.xref.status.300.2">9.2.3</a></li>
    4958                   <li>301 Moved Permanently (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.301.1">7.1</a>, <a href="#rfc.iref.70"><b>7.4.2</b></a>, <a href="#rfc.xref.status.301.2">9.2.3</a>, <a href="#rfc.xref.status.301.3">C</a></li>
    4959                   <li>302 Found (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.302.1">7.1</a>, <a href="#rfc.iref.70"><b>7.4.3</b></a>, <a href="#rfc.xref.status.302.2">9.2.3</a>, <a href="#rfc.xref.status.302.3">C</a></li>
    4960                   <li>303 See Other (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.303.1">7.1</a>, <a href="#rfc.iref.70"><b>7.4.4</b></a>, <a href="#rfc.xref.status.303.2">9.2.3</a></li>
    4961                   <li>305 Use Proxy (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.305.1">7.1</a>, <a href="#rfc.iref.70"><b>7.4.5</b></a>, <a href="#rfc.xref.status.305.2">9.2.3</a>, <a href="#rfc.xref.status.305.3">C</a></li>
    4962                   <li>306 (Unused) (status code)&nbsp;&nbsp;<a href="#rfc.iref.70"><b>7.4.6</b></a>, <a href="#rfc.xref.status.306.1">9.2.3</a></li>
    4963                   <li>307 Temporary Redirect (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.307.1">7.1</a>, <a href="#rfc.iref.70"><b>7.4.7</b></a>, <a href="#rfc.xref.status.307.2">9.2.3</a>, <a href="#rfc.xref.status.307.3">C</a></li>
    4964                   <li>3xx Redirection (status code class)&nbsp;&nbsp;<a href="#rfc.iref.69"><b>7.4</b></a>, <a href="#rfc.xref.status.3xx.1">C</a></li>
     4954                  <li>300 Multiple Choices (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.300.1">7.1</a>, <a href="#rfc.iref.73"><b>7.4.1</b></a>, <a href="#rfc.xref.status.300.2">9.2.3</a></li>
     4955                  <li>301 Moved Permanently (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.301.1">7.1</a>, <a href="#rfc.iref.73"><b>7.4.2</b></a>, <a href="#rfc.xref.status.301.2">9.2.3</a>, <a href="#rfc.xref.status.301.3">C</a></li>
     4956                  <li>302 Found (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.302.1">7.1</a>, <a href="#rfc.iref.73"><b>7.4.3</b></a>, <a href="#rfc.xref.status.302.2">9.2.3</a>, <a href="#rfc.xref.status.302.3">C</a></li>
     4957                  <li>303 See Other (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.303.1">7.1</a>, <a href="#rfc.iref.73"><b>7.4.4</b></a>, <a href="#rfc.xref.status.303.2">9.2.3</a></li>
     4958                  <li>305 Use Proxy (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.305.1">7.1</a>, <a href="#rfc.iref.73"><b>7.4.5</b></a>, <a href="#rfc.xref.status.305.2">9.2.3</a>, <a href="#rfc.xref.status.305.3">C</a></li>
     4959                  <li>306 (Unused) (status code)&nbsp;&nbsp;<a href="#rfc.iref.73"><b>7.4.6</b></a>, <a href="#rfc.xref.status.306.1">9.2.3</a></li>
     4960                  <li>307 Temporary Redirect (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.307.1">7.1</a>, <a href="#rfc.iref.73"><b>7.4.7</b></a>, <a href="#rfc.xref.status.307.2">9.2.3</a>, <a href="#rfc.xref.status.307.3">C</a></li>
     4961                  <li>3xx Redirection (status code class)&nbsp;&nbsp;<a href="#rfc.iref.72"><b>7.4</b></a>, <a href="#rfc.xref.status.3xx.1">C</a></li>
    49654962               </ul>
    49664963            </li>
    49674964            <li><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul>
    4968                   <li>400 Bad Request (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.400.1">7.1</a>, <a href="#rfc.iref.71"><b>7.5.1</b></a>, <a href="#rfc.xref.status.400.2">9.2.3</a></li>
    4969                   <li>402 Payment Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.402.1">7.1</a>, <a href="#rfc.iref.71"><b>7.5.2</b></a>, <a href="#rfc.xref.status.402.2">9.2.3</a></li>
    4970                   <li>403 Forbidden (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.403.1">7.1</a>, <a href="#rfc.iref.71"><b>7.5.3</b></a>, <a href="#rfc.xref.status.403.2">9.2.3</a></li>
    4971                   <li>404 Not Found (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.404.1">7.1</a>, <a href="#rfc.iref.71"><b>7.5.4</b></a>, <a href="#rfc.xref.status.404.2">9.2.3</a></li>
    4972                   <li>405 Method Not Allowed (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.405.1">7.1</a>, <a href="#rfc.iref.71"><b>7.5.5</b></a>, <a href="#rfc.xref.status.405.2">9.2.3</a></li>
    4973                   <li>406 Not Acceptable (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.406.1">7.1</a>, <a href="#rfc.iref.71"><b>7.5.6</b></a>, <a href="#rfc.xref.status.406.2">9.2.3</a></li>
    4974                   <li>408 Request Timeout (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.408.1">7.1</a>, <a href="#rfc.iref.71"><b>7.5.7</b></a>, <a href="#rfc.xref.status.408.2">9.2.3</a></li>
    4975                   <li>409 Conflict (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.409.1">7.1</a>, <a href="#rfc.iref.71"><b>7.5.8</b></a>, <a href="#rfc.xref.status.409.2">9.2.3</a></li>
    4976                   <li>410 Gone (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.410.1">7.1</a>, <a href="#rfc.iref.71"><b>7.5.9</b></a>, <a href="#rfc.xref.status.410.2">9.2.3</a></li>
    4977                   <li>411 Length Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.411.1">7.1</a>, <a href="#rfc.iref.71"><b>7.5.10</b></a>, <a href="#rfc.xref.status.411.2">9.2.3</a></li>
    4978                   <li>413 Request Representation Too Large (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.413.1">7.1</a>, <a href="#rfc.iref.71"><b>7.5.11</b></a>, <a href="#rfc.xref.status.413.2">9.2.3</a></li>
    4979                   <li>414 URI Too Long (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.414.1">7.1</a>, <a href="#rfc.iref.71"><b>7.5.12</b></a>, <a href="#rfc.xref.status.414.2">9.2.3</a></li>
    4980                   <li>415 Unsupported Media Type (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.415.1">7.1</a>, <a href="#rfc.iref.71"><b>7.5.13</b></a>, <a href="#rfc.xref.status.415.2">9.2.3</a></li>
    4981                   <li>417 Expectation Failed (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.417.1">7.1</a>, <a href="#rfc.iref.71"><b>7.5.14</b></a>, <a href="#rfc.xref.status.417.2">9.2.3</a></li>
    4982                   <li>426 Upgrade Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.426.1">7.1</a>, <a href="#rfc.iref.71"><b>7.5.15</b></a>, <a href="#rfc.xref.status.426.2">9.2.3</a>, <a href="#rfc.xref.status.426.3">C</a></li>
    4983                   <li>4xx Client Error (status code class)&nbsp;&nbsp;<a href="#rfc.iref.70"><b>7.5</b></a></li>
     4965                  <li>400 Bad Request (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.400.1">7.1</a>, <a href="#rfc.iref.74"><b>7.5.1</b></a>, <a href="#rfc.xref.status.400.2">9.2.3</a></li>
     4966                  <li>402 Payment Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.402.1">7.1</a>, <a href="#rfc.iref.74"><b>7.5.2</b></a>, <a href="#rfc.xref.status.402.2">9.2.3</a></li>
     4967                  <li>403 Forbidden (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.403.1">7.1</a>, <a href="#rfc.iref.74"><b>7.5.3</b></a>, <a href="#rfc.xref.status.403.2">9.2.3</a></li>
     4968                  <li>404 Not Found (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.404.1">7.1</a>, <a href="#rfc.iref.74"><b>7.5.4</b></a>, <a href="#rfc.xref.status.404.2">9.2.3</a></li>
     4969                  <li>405 Method Not Allowed (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.405.1">7.1</a>, <a href="#rfc.iref.74"><b>7.5.5</b></a>, <a href="#rfc.xref.status.405.2">9.2.3</a></li>
     4970                  <li>406 Not Acceptable (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.406.1">7.1</a>, <a href="#rfc.iref.74"><b>7.5.6</b></a>, <a href="#rfc.xref.status.406.2">9.2.3</a></li>
     4971                  <li>408 Request Timeout (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.408.1">7.1</a>, <a href="#rfc.iref.74"><b>7.5.7</b></a>, <a href="#rfc.xref.status.408.2">9.2.3</a></li>
     4972                  <li>409 Conflict (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.409.1">7.1</a>, <a href="#rfc.iref.74"><b>7.5.8</b></a>, <a href="#rfc.xref.status.409.2">9.2.3</a></li>
     4973                  <li>410 Gone (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.410.1">7.1</a>, <a href="#rfc.iref.74"><b>7.5.9</b></a>, <a href="#rfc.xref.status.410.2">9.2.3</a></li>
     4974                  <li>411 Length Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.411.1">7.1</a>, <a href="#rfc.iref.74"><b>7.5.10</b></a>, <a href="#rfc.xref.status.411.2">9.2.3</a></li>
     4975                  <li>413 Request Representation Too Large (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.413.1">7.1</a>, <a href="#rfc.iref.74"><b>7.5.11</b></a>, <a href="#rfc.xref.status.413.2">9.2.3</a></li>
     4976                  <li>414 URI Too Long (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.414.1">7.1</a>, <a href="#rfc.iref.74"><b>7.5.12</b></a>, <a href="#rfc.xref.status.414.2">9.2.3</a></li>
     4977                  <li>415 Unsupported Media Type (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.415.1">7.1</a>, <a href="#rfc.iref.74"><b>7.5.13</b></a>, <a href="#rfc.xref.status.415.2">9.2.3</a></li>
     4978                  <li>417 Expectation Failed (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.417.1">7.1</a>, <a href="#rfc.iref.74"><b>7.5.14</b></a>, <a href="#rfc.xref.status.417.2">9.2.3</a></li>
     4979                  <li>426 Upgrade Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.426.1">7.1</a>, <a href="#rfc.iref.74"><b>7.5.15</b></a>, <a href="#rfc.xref.status.426.2">9.2.3</a>, <a href="#rfc.xref.status.426.3">C</a></li>
     4980                  <li>4xx Client Error (status code class)&nbsp;&nbsp;<a href="#rfc.iref.73"><b>7.5</b></a></li>
    49844981               </ul>
    49854982            </li>
    49864983            <li><a id="rfc.index.5" href="#rfc.index.5"><b>5</b></a><ul>
    4987                   <li>500 Internal Server Error (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.500.1">7.1</a>, <a href="#rfc.iref.72"><b>7.6.1</b></a>, <a href="#rfc.xref.status.500.2">9.2.3</a></li>
    4988                   <li>501 Not Implemented (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.501.1">7.1</a>, <a href="#rfc.iref.72"><b>7.6.2</b></a>, <a href="#rfc.xref.status.501.2">9.2.3</a></li>
    4989                   <li>502 Bad Gateway (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.502.1">7.1</a>, <a href="#rfc.iref.72"><b>7.6.3</b></a>, <a href="#rfc.xref.status.502.2">9.2.3</a></li>
    4990                   <li>503 Service Unavailable (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.503.1">7.1</a>, <a href="#rfc.iref.72"><b>7.6.4</b></a>, <a href="#rfc.xref.status.503.2">9.2.3</a></li>
    4991                   <li>504 Gateway Timeout (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.504.1">7.1</a>, <a href="#rfc.iref.72"><b>7.6.5</b></a>, <a href="#rfc.xref.status.504.2">9.2.3</a></li>
    4992                   <li>505 HTTP Version Not Supported (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.505.1">7.1</a>, <a href="#rfc.iref.72"><b>7.6.6</b></a>, <a href="#rfc.xref.status.505.2">9.2.3</a></li>
    4993                   <li>5xx Server Error (status code class)&nbsp;&nbsp;<a href="#rfc.iref.71"><b>7.6</b></a></li>
     4984                  <li>500 Internal Server Error (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.500.1">7.1</a>, <a href="#rfc.iref.75"><b>7.6.1</b></a>, <a href="#rfc.xref.status.500.2">9.2.3</a></li>
     4985                  <li>501 Not Implemented (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.501.1">7.1</a>, <a href="#rfc.iref.75"><b>7.6.2</b></a>, <a href="#rfc.xref.status.501.2">9.2.3</a></li>
     4986                  <li>502 Bad Gateway (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.502.1">7.1</a>, <a href="#rfc.iref.75"><b>7.6.3</b></a>, <a href="#rfc.xref.status.502.2">9.2.3</a></li>
     4987                  <li>503 Service Unavailable (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.503.1">7.1</a>, <a href="#rfc.iref.75"><b>7.6.4</b></a>, <a href="#rfc.xref.status.503.2">9.2.3</a></li>
     4988                  <li>504 Gateway Timeout (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.504.1">7.1</a>, <a href="#rfc.iref.75"><b>7.6.5</b></a>, <a href="#rfc.xref.status.504.2">9.2.3</a></li>
     4989                  <li>505 HTTP Version Not Supported (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.505.1">7.1</a>, <a href="#rfc.iref.75"><b>7.6.6</b></a>, <a href="#rfc.xref.status.505.2">9.2.3</a></li>
     4990                  <li>5xx Server Error (status code class)&nbsp;&nbsp;<a href="#rfc.iref.74"><b>7.6</b></a></li>
    49944991               </ul>
    49954992            </li>
     
    50035000            </li>
    50045001            <li><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul>
    5005                   <li>cacheable&nbsp;&nbsp;<a href="#rfc.iref.c.7"><b>5.2.3</b></a></li>
    5006                   <li>compress (Coding Format)&nbsp;&nbsp;<a href="#rfc.iref.c.3">3.1.2.1</a></li>
    5007                   <li>CONNECT method&nbsp;&nbsp;<a href="#rfc.xref.CONNECT.1">5.1</a>, <a href="#rfc.iref.c.8"><b>5.3.6</b></a>, <a href="#rfc.xref.CONNECT.2">9.1.3</a>, <a href="#rfc.xref.CONNECT.3">C</a></li>
     5002                  <li>cacheable&nbsp;&nbsp;<a href="#rfc.iref.c.8"><b>5.2.3</b></a></li>
     5003                  <li>compress (content coding)&nbsp;&nbsp;<a href="#rfc.iref.c.4"><b>3.1.2.1</b></a></li>
     5004                  <li>CONNECT method&nbsp;&nbsp;<a href="#rfc.xref.CONNECT.1">5.1</a>, <a href="#rfc.iref.c.9"><b>5.3.6</b></a>, <a href="#rfc.xref.CONNECT.2">9.1.3</a>, <a href="#rfc.xref.CONNECT.3">C</a></li>
     5005                  <li>content coding&nbsp;&nbsp;<a href="#rfc.iref.c.3"><b>3.1.2.1</b></a></li>
    50085006                  <li>content negotiation&nbsp;&nbsp;<a href="#rfc.iref.c.1">1</a></li>
    5009                   <li>Content-Encoding header field&nbsp;&nbsp;<a href="#rfc.xref.header.content-encoding.1">3.1</a>, <a href="#rfc.xref.header.content-encoding.2">3.1.2.1</a>, <a href="#rfc.iref.c.4"><b>3.1.2.2</b></a>, <a href="#rfc.xref.header.content-encoding.3">9.3.2</a></li>
    5010                   <li>Content-Language header field&nbsp;&nbsp;<a href="#rfc.xref.header.content-language.1">3.1</a>, <a href="#rfc.iref.c.5"><b>3.1.3.2</b></a>, <a href="#rfc.xref.header.content-language.2">9.3.2</a></li>
    5011                   <li>Content-Location header field&nbsp;&nbsp;<a href="#rfc.xref.header.content-location.1">3.1</a>, <a href="#rfc.iref.c.6"><b>3.1.4.2</b></a>, <a href="#rfc.xref.header.content-location.2">5.3.3</a>, <a href="#rfc.xref.header.content-location.3">8.1.2</a>, <a href="#rfc.xref.header.content-location.4">9.3.2</a>, <a href="#rfc.xref.header.content-location.5">C</a></li>
    5012                   <li>Content-Transfer-Encoding header field&nbsp;&nbsp;<a href="#rfc.iref.c.9">A.5</a>, <a href="#rfc.xref.no.content-transfer-encoding.1">C</a></li>
     5007                  <li>Content-Encoding header field&nbsp;&nbsp;<a href="#rfc.xref.header.content-encoding.1">3.1</a>, <a href="#rfc.xref.header.content-encoding.2">3.1.2.1</a>, <a href="#rfc.iref.c.5"><b>3.1.2.2</b></a>, <a href="#rfc.xref.header.content-encoding.3">9.3.2</a></li>
     5008                  <li>Content-Language header field&nbsp;&nbsp;<a href="#rfc.xref.header.content-language.1">3.1</a>, <a href="#rfc.iref.c.6"><b>3.1.3.2</b></a>, <a href="#rfc.xref.header.content-language.2">9.3.2</a></li>
     5009                  <li>Content-Location header field&nbsp;&nbsp;<a href="#rfc.xref.header.content-location.1">3.1</a>, <a href="#rfc.iref.c.7"><b>3.1.4.2</b></a>, <a href="#rfc.xref.header.content-location.2">5.3.3</a>, <a href="#rfc.xref.header.content-location.3">8.1.2</a>, <a href="#rfc.xref.header.content-location.4">9.3.2</a>, <a href="#rfc.xref.header.content-location.5">C</a></li>
     5010                  <li>Content-Transfer-Encoding header field&nbsp;&nbsp;<a href="#rfc.iref.c.10">A.5</a>, <a href="#rfc.xref.no.content-transfer-encoding.1">C</a></li>
    50135011                  <li>Content-Type header field&nbsp;&nbsp;<a href="#rfc.xref.header.content-type.1">3.1</a>, <a href="#rfc.xref.header.content-type.2">3.1.1.1</a>, <a href="#rfc.iref.c.2"><b>3.1.1.5</b></a>, <a href="#rfc.xref.header.content-type.3">7</a>, <a href="#rfc.xref.header.content-type.4">9.3.1</a>, <a href="#rfc.xref.header.content-type.5">9.3.2</a></li>
    50145012               </ul>
     
    50165014            <li><a id="rfc.index.D" href="#rfc.index.D"><b>D</b></a><ul>
    50175015                  <li>Date header field&nbsp;&nbsp;<a href="#rfc.xref.header.date.1">3.3</a>, <a href="#rfc.xref.header.date.2">8.1</a>, <a href="#rfc.iref.d.3"><b>8.1.1.2</b></a>, <a href="#rfc.xref.header.date.3">9.3.2</a></li>
    5018                   <li>deflate (Coding Format)&nbsp;&nbsp;<a href="#rfc.iref.d.1">3.1.2.1</a></li>
     5016                  <li>deflate (content coding)&nbsp;&nbsp;<a href="#rfc.iref.d.1"><b>3.1.2.1</b></a></li>
    50195017                  <li>DELETE method&nbsp;&nbsp;<a href="#rfc.xref.DELETE.1">5.1</a>, <a href="#rfc.iref.d.2"><b>5.3.5</b></a>, <a href="#rfc.xref.DELETE.2">9.1.3</a></li>
    50205018               </ul>
     
    50485046                        <li><tt>charset</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.7"><b>3.1.1.2</b></a></li>
    50495047                        <li><tt>codings</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.33"><b>6.3.4</b></a></li>
    5050                         <li><tt>content-coding</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.9"><b>3.1.2.1</b></a></li>
     5048                        <li><tt>content-coding</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.10"><b>3.1.2.1</b></a></li>
    50515049                        <li><tt>Content-Encoding</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.11"><b>3.1.2.2</b></a></li>
    50525050                        <li><tt>Content-Language</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.13"><b>3.1.3.2</b></a></li>
     
    50995097                     </ul>
    51005098                  </li>
    5101                   <li>gzip (Coding Format)&nbsp;&nbsp;<a href="#rfc.iref.g.10">3.1.2.1</a></li>
     5099                  <li>gzip (content coding)&nbsp;&nbsp;<a href="#rfc.iref.g.9"><b>3.1.2.1</b></a></li>
    51025100               </ul>
    51035101            </li>
     
    51245122            </li>
    51255123            <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul>
    5126                   <li><em>Part1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1</a>, <a href="#rfc.xref.Part1.2">1.1</a>, <a href="#rfc.xref.Part1.3">1.2</a>, <a href="#rfc.xref.Part1.4">2</a>, <a href="#rfc.xref.Part1.5">2</a>, <a href="#rfc.xref.Part1.6">2</a>, <a href="#rfc.xref.Part1.7">3.1.2.1</a>, <a href="#rfc.xref.Part1.8">3.1.2.1</a>, <a href="#rfc.xref.Part1.9">3.1.2.1</a>, <a href="#rfc.xref.Part1.10">3.1.4.1</a>, <a href="#rfc.xref.Part1.11">3.1.4.2</a>, <a href="#rfc.xref.Part1.12">3.3</a>, <a href="#rfc.xref.Part1.13">3.3</a>, <a href="#rfc.xref.Part1.14">5.3.6</a>, <a href="#rfc.xref.Part1.15">5.3.7</a>, <a href="#rfc.xref.Part1.16">5.3.8</a>, <a href="#rfc.xref.Part1.17">5.3.8</a>, <a href="#rfc.xref.Part1.18">6.1</a>, <a href="#rfc.xref.Part1.19">6.5</a>, <a href="#rfc.xref.Part1.20">6.5.3</a>, <a href="#rfc.xref.Part1.21">7.2.2</a>, <a href="#rfc.xref.Part1.22">7.3.4</a>, <a href="#rfc.xref.Part1.23">7.3.6</a>, <a href="#rfc.xref.Part1.24">7.5.15</a>, <a href="#rfc.xref.Part1.25">7.6.6</a>, <a href="#rfc.xref.Part1.26">8</a>, <a href="#rfc.xref.Part1.27">8.4.2</a>, <a href="#rfc.xref.Part1.28">8.4.2</a>, <a href="#rfc.xref.Part1.29">9.1.2</a>, <a href="#rfc.xref.Part1.30">9.3.1</a>, <a href="#rfc.xref.Part1.31">9.3.1</a>, <a href="#rfc.xref.Part1.32">9.3.1</a>, <a href="#rfc.xref.Part1.33">9.3.1</a>, <a href="#rfc.xref.Part1.34">9.3.1</a>, <a href="#rfc.xref.Part1.35">9.3.1</a>, <a href="#rfc.xref.Part1.36">9.4</a>, <a href="#rfc.xref.Part1.37">9.4.1</a>, <a href="#rfc.xref.Part1.38">9.4.1</a>, <a href="#rfc.xref.Part1.39">9.4.2</a>, <a href="#rfc.xref.Part1.40">9.4.2</a>, <a href="#rfc.xref.Part1.41">9.4.2</a>, <a href="#rfc.xref.Part1.42">11</a>, <a href="#Part1"><b>12.1</b></a>, <a href="#rfc.xref.Part1.43">C</a>, <a href="#rfc.xref.Part1.44">D</a>, <a href="#rfc.xref.Part1.45">D</a>, <a href="#rfc.xref.Part1.46">D</a>, <a href="#rfc.xref.Part1.47">D</a>, <a href="#rfc.xref.Part1.48">D</a>, <a href="#rfc.xref.Part1.49">D</a>, <a href="#rfc.xref.Part1.50">D</a>, <a href="#rfc.xref.Part1.51">D</a>, <a href="#rfc.xref.Part1.52">D</a>, <a href="#rfc.xref.Part1.53">D</a>, <a href="#rfc.xref.Part1.54">D</a>, <a href="#rfc.xref.Part1.55">D</a><ul>
     5124                  <li><em>Part1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1</a>, <a href="#rfc.xref.Part1.2">1.1</a>, <a href="#rfc.xref.Part1.3">1.2</a>, <a href="#rfc.xref.Part1.4">2</a>, <a href="#rfc.xref.Part1.5">2</a>, <a href="#rfc.xref.Part1.6">2</a>, <a href="#rfc.xref.Part1.7">3.1.2.1</a>, <a href="#rfc.xref.Part1.8">3.1.2.1</a>, <a href="#rfc.xref.Part1.9">3.1.2.1</a>, <a href="#rfc.xref.Part1.10">3.1.2.2</a>, <a href="#rfc.xref.Part1.11">3.1.4.1</a>, <a href="#rfc.xref.Part1.12">3.1.4.2</a>, <a href="#rfc.xref.Part1.13">3.3</a>, <a href="#rfc.xref.Part1.14">3.3</a>, <a href="#rfc.xref.Part1.15">5.3.6</a>, <a href="#rfc.xref.Part1.16">5.3.7</a>, <a href="#rfc.xref.Part1.17">5.3.8</a>, <a href="#rfc.xref.Part1.18">5.3.8</a>, <a href="#rfc.xref.Part1.19">6.1</a>, <a href="#rfc.xref.Part1.20">6.5</a>, <a href="#rfc.xref.Part1.21">6.5.3</a>, <a href="#rfc.xref.Part1.22">7.2.2</a>, <a href="#rfc.xref.Part1.23">7.3.4</a>, <a href="#rfc.xref.Part1.24">7.3.6</a>, <a href="#rfc.xref.Part1.25">7.5.15</a>, <a href="#rfc.xref.Part1.26">7.6.6</a>, <a href="#rfc.xref.Part1.27">8</a>, <a href="#rfc.xref.Part1.28">8.4.2</a>, <a href="#rfc.xref.Part1.29">8.4.2</a>, <a href="#rfc.xref.Part1.30">9.1.2</a>, <a href="#rfc.xref.Part1.31">9.3.1</a>, <a href="#rfc.xref.Part1.32">9.3.1</a>, <a href="#rfc.xref.Part1.33">9.3.1</a>, <a href="#rfc.xref.Part1.34">9.3.1</a>, <a href="#rfc.xref.Part1.35">9.3.1</a>, <a href="#rfc.xref.Part1.36">9.3.1</a>, <a href="#rfc.xref.Part1.37">9.4</a>, <a href="#rfc.xref.Part1.38">9.4.1</a>, <a href="#rfc.xref.Part1.39">9.4.1</a>, <a href="#rfc.xref.Part1.40">9.4.2</a>, <a href="#rfc.xref.Part1.41">9.4.2</a>, <a href="#rfc.xref.Part1.42">9.4.2</a>, <a href="#rfc.xref.Part1.43">11</a>, <a href="#Part1"><b>12.1</b></a>, <a href="#rfc.xref.Part1.44">C</a>, <a href="#rfc.xref.Part1.45">D</a>, <a href="#rfc.xref.Part1.46">D</a>, <a href="#rfc.xref.Part1.47">D</a>, <a href="#rfc.xref.Part1.48">D</a>, <a href="#rfc.xref.Part1.49">D</a>, <a href="#rfc.xref.Part1.50">D</a>, <a href="#rfc.xref.Part1.51">D</a>, <a href="#rfc.xref.Part1.52">D</a>, <a href="#rfc.xref.Part1.53">D</a>, <a href="#rfc.xref.Part1.54">D</a>, <a href="#rfc.xref.Part1.55">D</a>, <a href="#rfc.xref.Part1.56">D</a><ul>
    51275125                        <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.3">1.2</a></li>
    5128                         <li><em>Section 2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.22">7.3.4</a></li>
     5126                        <li><em>Section 2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.23">7.3.4</a></li>
    51295127                        <li><em>Section 2.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.2">1.1</a></li>
    5130                         <li><em>Section 2.6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.25">7.6.6</a></li>
    5131                         <li><em>Section 2.7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.4">2</a>, <a href="#rfc.xref.Part1.48">D</a>, <a href="#rfc.xref.Part1.49">D</a>, <a href="#rfc.xref.Part1.52">D</a></li>
    5132                         <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.20">6.5.3</a>, <a href="#rfc.xref.Part1.27">8.4.2</a>, <a href="#rfc.xref.Part1.30">9.3.1</a>, <a href="#rfc.xref.Part1.33">9.3.1</a>, <a href="#rfc.xref.Part1.51">D</a></li>
    5133                         <li><em>Section 3.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.45">D</a>, <a href="#rfc.xref.Part1.46">D</a>, <a href="#rfc.xref.Part1.47">D</a></li>
    5134                         <li><em>Section 3.2.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.32">9.3.1</a>, <a href="#rfc.xref.Part1.50">D</a>, <a href="#rfc.xref.Part1.53">D</a>, <a href="#rfc.xref.Part1.54">D</a>, <a href="#rfc.xref.Part1.55">D</a></li>
    5135                         <li><em>Section 3.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.13">3.3</a></li>
    5136                         <li><em>Section 3.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.23">7.3.6</a>, <a href="#rfc.xref.Part1.29">9.1.2</a></li>
    5137                         <li><em>Section 3.3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.12">3.3</a></li>
    5138                         <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.37">9.4.1</a></li>
    5139                         <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.35">9.3.1</a></li>
    5140                         <li><em>Section 4.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.7">3.1.2.1</a>, <a href="#rfc.xref.Part1.39">9.4.2</a></li>
    5141                         <li><em>Section 4.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.36">9.4</a>, <a href="#rfc.xref.Part1.38">9.4.1</a></li>
    5142                         <li><em>Section 4.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.8">3.1.2.1</a>, <a href="#rfc.xref.Part1.40">9.4.2</a></li>
    5143                         <li><em>Section 4.2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.9">3.1.2.1</a>, <a href="#rfc.xref.Part1.41">9.4.2</a></li>
    5144                         <li><em>Section 4.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.19">6.5</a></li>
    5145                         <li><em>Section 5.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.5">2</a>, <a href="#rfc.xref.Part1.14">5.3.6</a>, <a href="#rfc.xref.Part1.15">5.3.7</a></li>
    5146                         <li><em>Section 5.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.18">6.1</a></li>
    5147                         <li><em>Section 5.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.6">2</a>, <a href="#rfc.xref.Part1.10">3.1.4.1</a>, <a href="#rfc.xref.Part1.11">3.1.4.2</a>, <a href="#rfc.xref.Part1.26">8</a></li>
    5148                         <li><em>Section 5.7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.16">5.3.8</a>, <a href="#rfc.xref.Part1.28">8.4.2</a>, <a href="#rfc.xref.Part1.43">C</a></li>
    5149                         <li><em>Section 6.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.34">9.3.1</a></li>
    5150                         <li><em>Section 6.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.21">7.2.2</a>, <a href="#rfc.xref.Part1.24">7.5.15</a></li>
    5151                         <li><em>Section 7.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.17">5.3.8</a></li>
    5152                         <li><em>Section 9</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.42">11</a></li>
    5153                         <li><em>Appendix B</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.31">9.3.1</a></li>
     5128                        <li><em>Section 2.6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.26">7.6.6</a></li>
     5129                        <li><em>Section 2.7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.4">2</a>, <a href="#rfc.xref.Part1.49">D</a>, <a href="#rfc.xref.Part1.50">D</a>, <a href="#rfc.xref.Part1.53">D</a></li>
     5130                        <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.21">6.5.3</a>, <a href="#rfc.xref.Part1.28">8.4.2</a>, <a href="#rfc.xref.Part1.31">9.3.1</a>, <a href="#rfc.xref.Part1.34">9.3.1</a>, <a href="#rfc.xref.Part1.52">D</a></li>
     5131                        <li><em>Section 3.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.46">D</a>, <a href="#rfc.xref.Part1.47">D</a>, <a href="#rfc.xref.Part1.48">D</a></li>
     5132                        <li><em>Section 3.2.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.33">9.3.1</a>, <a href="#rfc.xref.Part1.51">D</a>, <a href="#rfc.xref.Part1.54">D</a>, <a href="#rfc.xref.Part1.55">D</a>, <a href="#rfc.xref.Part1.56">D</a></li>
     5133                        <li><em>Section 3.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.10">3.1.2.2</a>, <a href="#rfc.xref.Part1.14">3.3</a></li>
     5134                        <li><em>Section 3.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.24">7.3.6</a>, <a href="#rfc.xref.Part1.30">9.1.2</a></li>
     5135                        <li><em>Section 3.3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.13">3.3</a></li>
     5136                        <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.38">9.4.1</a></li>
     5137                        <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.36">9.3.1</a></li>
     5138                        <li><em>Section 4.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.7">3.1.2.1</a>, <a href="#rfc.xref.Part1.40">9.4.2</a></li>
     5139                        <li><em>Section 4.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.37">9.4</a>, <a href="#rfc.xref.Part1.39">9.4.1</a></li>
     5140                        <li><em>Section 4.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.8">3.1.2.1</a>, <a href="#rfc.xref.Part1.41">9.4.2</a></li>
     5141                        <li><em>Section 4.2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.9">3.1.2.1</a>, <a href="#rfc.xref.Part1.42">9.4.2</a></li>
     5142                        <li><em>Section 4.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.20">6.5</a></li>
     5143                        <li><em>Section 5.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.5">2</a>, <a href="#rfc.xref.Part1.15">5.3.6</a>, <a href="#rfc.xref.Part1.16">5.3.7</a></li>
     5144                        <li><em>Section 5.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.19">6.1</a></li>
     5145                        <li><em>Section 5.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.6">2</a>, <a href="#rfc.xref.Part1.11">3.1.4.1</a>, <a href="#rfc.xref.Part1.12">3.1.4.2</a>, <a href="#rfc.xref.Part1.27">8</a></li>
     5146                        <li><em>Section 5.7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.17">5.3.8</a>, <a href="#rfc.xref.Part1.29">8.4.2</a>, <a href="#rfc.xref.Part1.44">C</a></li>
     5147                        <li><em>Section 6.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.35">9.3.1</a></li>
     5148                        <li><em>Section 6.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.22">7.2.2</a>, <a href="#rfc.xref.Part1.25">7.5.15</a></li>
     5149                        <li><em>Section 7.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.18">5.3.8</a></li>
     5150                        <li><em>Section 9</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.43">11</a></li>
     5151                        <li><em>Appendix B</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.32">9.3.1</a></li>
    51545152                     </ul>
    51555153                  </li>
     
    53225320               </ul>
    53235321            </li>
     5322            <li><a id="rfc.index.X" href="#rfc.index.X"><b>X</b></a><ul>
     5323                  <li>x-compress (content coding)&nbsp;&nbsp;<a href="#rfc.iref.x.1"><b>3.1.2.1</b></a></li>
     5324                  <li>x-gzip (content coding)&nbsp;&nbsp;<a href="#rfc.iref.x.2"><b>3.1.2.1</b></a></li>
     5325               </ul>
     5326            </li>
    53245327         </ul>
    53255328      </div>
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r1926 r1927  
    511511
    512512<section title="Content Codings" anchor="content.codings">
     513  <iref primary="true" item="content coding"/>
     514  <iref primary="true" item="compress (content coding)"/>
     515  <iref primary="true" item="x-compress (content coding)"/>
     516  <iref primary="true" item="deflate (content coding)"/>
     517  <iref primary="true" item="gzip (content coding)"/>
     518  <iref primary="true" item="x-gzip (content coding)"/>
    513519  <x:anchor-alias value="content-coding"/>
    514520<t>
     
    524530</artwork></figure>
    525531<t>
    526    All content-coding values are case-insensitive. HTTP/1.1 uses
    527    content-coding values in the <x:ref>Accept-Encoding</x:ref>
    528    (<xref target="header.accept-encoding"/>) and <x:ref>Content-Encoding</x:ref>
    529    (<xref target="header.content-encoding"/>) header fields. Although the value
    530    describes the content-coding, what is more important is that it
    531    indicates what decoding mechanism will be required to remove the
    532    encoding.
    533 </t>
    534 <t>
    535    compress<iref item="compress (Coding Format)"/>
    536   <list>
    537     <t>
    538       See &compress-coding;.
    539     </t>
    540   </list>
    541 </t>
    542 <t>
    543    deflate<iref item="deflate (Coding Format)"/>
    544   <list>
    545     <t>
    546       See &deflate-coding;.
    547     </t>
    548   </list>
    549 </t>
    550 <t>
    551    gzip<iref item="gzip (Coding Format)"/>
    552   <list>
    553     <t>
    554       See &gzip-coding;.
    555     </t>
    556   </list>
     532   All content-coding values are case-insensitive and &SHOULD; be registered
     533   within the HTTP Content Coding registry, as defined in
     534   <xref target="content.coding.registry"/>. They are used in the
     535   <x:ref>Accept-Encoding</x:ref> (<xref target="header.accept-encoding"/>)
     536   and <x:ref>Content-Encoding</x:ref> (<xref target="header.content-encoding"/>)
     537   header fields.
     538</t>
     539<t>
     540   The following content-coding values are defined by this specification:
     541   <list>
     542    <t>compress (and x-compress): See &compress-coding;.</t>
     543    <t>deflate: See &deflate-coding;.</t>
     544    <t>gzip (and x-gzip): See &gzip-coding;.</t>
     545   </list>
    557546</t>
    558547</section>
     
    562551  <x:anchor-alias value="Content-Encoding"/>
    563552<t>
    564    The "Content-Encoding" header field indicates what content-codings
    565    have been applied to the representation beyond those inherent in the media
    566    type, and thus what decoding mechanisms have to be applied in order to obtain
    567    the media-type referenced by the <x:ref>Content-Type</x:ref> header field.
    568    Content-Encoding is primarily used to allow a representation to be
     553   The "Content-Encoding" header field indicates what content codings
     554   have been applied to the representation, beyond those inherent in the media
     555   type, and thus what decoding mechanisms have to be applied in order to
     556   obtain data in the media type referenced by the <x:ref>Content-Type</x:ref>
     557   header field.
     558   Content-Encoding is primarily used to allow a representation's data to be
    569559   compressed without losing the identity of its underlying media type.
    570560</t>
     
    573563</artwork></figure>
    574564<t>
    575    Content codings are defined in <xref target="content.codings"/>. An example of its use is
     565   An example of its use is
    576566</t>
    577567<figure><artwork type="example">
     
    579569</artwork></figure>
    580570<t>
    581    The content-coding is a characteristic of the representation.
    582    Typically, the representation data is stored with this
    583    encoding and is only decoded before rendering or analogous usage.
    584    However, a transforming proxy &MAY; modify the content-coding if the
     571   If multiple encodings have been applied to a representation, the content
     572   codings &MUST; be listed in the order in which they were applied.
     573   Additional information about the encoding parameters &MAY; be provided
     574   by other header fields not defined by this specification.
     575</t>
     576<t>
     577   Unlike Transfer-Encoding (&header-transfer-encoding;), the codings listed
     578   in Content-Encoding are a characteristic of the representation; the
     579   representation is defined in terms of the coded form, and all other
     580   metadata about the representation is about the coded form unless otherwise
     581   noted in the metadata definition. Typically, the representation is only
     582   decoded just prior to rendering or analogous usage.
     583</t>
     584<t>
     585   A transforming proxy &MAY; modify the content coding if the
    585586   new coding is known to be acceptable to the recipient, unless the
    586587   "no-transform" cache-control directive is present in the message.
     
    590591   that is always compressed, then that encoding would not be restated as
    591592   a Content-Encoding even if it happens to be the same algorithm as one
    592    of the content-codings.  Such a content-coding would only be listed if,
     593   of the content codings.  Such a content coding would only be listed if,
    593594   for some bizarre reason, it is applied a second time to form the
    594595   representation.  Likewise, an origin server might choose to publish the
     
    598599   handling of each response (e.g., open a "Save as ..." dialog instead of
    599600   automatic decompression and rendering of content).
    600 </t>
    601 <t>
    602    A representation that has a content-coding applied to it &MUST; include
    603    a Content-Encoding header field that lists the content-coding(s) applied.
    604 </t>
    605 <t>
    606    If multiple encodings have been applied to a representation, the content
    607    codings &MUST; be listed in the order in which they were applied.
    608    Additional information about the encoding parameters &MAY; be provided
    609    by other header fields not defined by this specification.
    610601</t>
    611602<t>
Note: See TracChangeset for help on using the changeset viewer.