Ignore:
Timestamp:
06/05/14 08:10:18 (6 years ago)
Author:
julian.reschke@…
Message:

insert RFC numbers (#553)

File:
1 edited

Legend:

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

    r2628 r2629  
    463463  }
    464464  @bottom-center {
    465        content: "Expires November 2, 2014";
     465       content: "Expires November 7, 2014";
    466466  }
    467467  @bottom-right {
     
    508508      <meta name="dct.creator" content="Reschke, J. F.">
    509509      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
    510       <meta name="dct.issued" scheme="ISO8601" content="2014-05-01">
     510      <meta name="dct.issued" scheme="ISO8601" content="2014-05-06">
    511511      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    512512      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for distributed, collaborative, hypertext information systems. This document defines the semantics of HTTP/1.1 messages, as expressed by request methods, request header fields, response status codes, and response header fields, along with the payload of messages (metadata and body content) and mechanisms for content negotiation.">
     
    536536            <tr>
    537537               <td class="left">Intended status: Standards Track</td>
    538                <td class="right">May 1, 2014</td>
     538               <td class="right">May 6, 2014</td>
    539539            </tr>
    540540            <tr>
    541                <td class="left">Expires: November 2, 2014</td>
     541               <td class="left">Expires: November 7, 2014</td>
    542542               <td class="right"></td>
    543543            </tr>
     
    568568            in progress”.
    569569         </p>
    570          <p>This Internet-Draft will expire on November 2, 2014.</p>
     570         <p>This Internet-Draft will expire on November 7, 2014.</p>
    571571      </div>
    572572      <div id="rfc.copyrightnotice">
     
    798798            responds to that request with one or more response messages. A client constructs request messages to communicate specific
    799799            intentions, and examines received responses to see if the intentions were carried out and determine how to interpret the results.
    800             This document defines HTTP/1.1 request and response semantics in terms of the architecture defined in <a href="#Part1" id="rfc.xref.Part1.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.
     800            This document defines HTTP/1.1 request and response semantics in terms of the architecture defined in <a href="#RFC7230" id="rfc.xref.RFC7230.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>.
    801801         </p>
    802802         <p id="rfc.section.1.p.2">HTTP provides a uniform interface for interacting with a resource (<a href="#resources" title="Resources">Section&nbsp;2</a>), regardless of its type, nature, or implementation, via the manipulation and transfer of representations (<a href="#representations" title="Representations">Section&nbsp;3</a>).
     
    813813               in this document are to be interpreted as described in <a href="#RFC2119" id="rfc.xref.RFC2119.1"><cite title="Key words for use in RFCs to Indicate Requirement Levels">[RFC2119]</cite></a>.
    814814            </p>
    815             <p id="rfc.section.1.1.p.2">Conformance criteria and considerations regarding error handling are defined in <a href="p1-messaging.html#conformance" title="Conformance and Error Handling">Section 2.5</a> of <a href="#Part1" id="rfc.xref.Part1.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.
     815            <p id="rfc.section.1.1.p.2">Conformance criteria and considerations regarding error handling are defined in <a href="p1-messaging.html#conformance" title="Conformance and Error Handling">Section 2.5</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>.
    816816            </p>
    817817         </div>
    818818         <div id="notation">
    819819            <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a href="#notation">Syntax Notation</a></h2>
    820             <p id="rfc.section.1.2.p.1">This specification uses the Augmented Backus-Naur Form (ABNF) notation of <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with a list extension, defined in <a href="p1-messaging.html#abnf.extension" title="ABNF list extension: #rule">Section 7</a> of <a href="#Part1" id="rfc.xref.Part1.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, that allows for compact definition of comma-separated lists using a '#' operator (similar to how the '*' operator indicates
     820            <p id="rfc.section.1.2.p.1">This specification uses the Augmented Backus-Naur Form (ABNF) notation of <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with a list extension, defined in <a href="p1-messaging.html#abnf.extension" title="ABNF list extension: #rule">Section 7</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, that allows for compact definition of comma-separated lists using a '#' operator (similar to how the '*' operator indicates
    821821               repetition). <a href="#imported.abnf" title="Imported ABNF">Appendix&nbsp;C</a> describes rules imported from other documents. <a href="#collected.abnf" title="Collected ABNF">Appendix&nbsp;D</a> shows the collected grammar with all list operators expanded to standard ABNF notation.
    822822            </p>
     
    830830         <p id="rfc.section.2.p.1">The target of an HTTP request is called a resource. HTTP does not limit the nature of a resource; it merely defines an interface
    831831            that might be used to interact with resources. Each resource is identified by a Uniform Resource Identifier (URI), as described
    832             in <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.7</a> of <a href="#Part1" id="rfc.xref.Part1.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.
    833          </p>
    834          <p id="rfc.section.2.p.2">When a client constructs an HTTP/1.1 request message, it sends the <a href="p1-messaging.html#target-resource" class="smpl">target URI</a> in one of various forms, as defined in (<a href="p1-messaging.html#request-target" title="Request Target">Section 5.3</a> of <a href="#Part1" id="rfc.xref.Part1.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>). When a request is received, the server reconstructs an <a href="p1-messaging.html#effective.request.uri" class="smpl">effective request URI</a> for 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.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>).
     832            in <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.7</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>.
     833         </p>
     834         <p id="rfc.section.2.p.2">When a client constructs an HTTP/1.1 request message, it sends the <a href="p1-messaging.html#target-resource" class="smpl">target URI</a> in one of various forms, as defined in (<a href="p1-messaging.html#request-target" title="Request Target">Section 5.3</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>). When a request is received, the server reconstructs an <a href="p1-messaging.html#effective.request.uri" class="smpl">effective request URI</a> for the target resource (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>).
    835835         </p>
    836836         <p id="rfc.section.2.p.3">One design goal of HTTP is to separate resource identification from request semantics, which is made possible by vesting the
     
    853853         <p id="rfc.section.3.p.3">An origin server might be provided with, or capable of generating, multiple representations that are each intended to reflect
    854854            the current state of a <a href="#resources" class="smpl">target resource</a>. In such cases, some algorithm is used by the origin server to select one of those representations as most applicable to
    855             a given request, usually based on <a href="#content.negotiation" class="smpl">content negotiation</a>. This "<dfn>selected representation</dfn>" is used to provide the data and metadata for evaluating conditional requests <a href="#Part4" id="rfc.xref.Part4.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a> and constructing the payload for <a href="#status.200" class="smpl">200 (OK)</a> and <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a> responses to GET (<a href="#GET" id="rfc.xref.GET.1" title="GET">Section&nbsp;4.3.1</a>).
     855            a given request, usually based on <a href="#content.negotiation" class="smpl">content negotiation</a>. This "<dfn>selected representation</dfn>" is used to provide the data and metadata for evaluating conditional requests <a href="#RFC7232" id="rfc.xref.RFC7232.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[RFC7232]</cite></a> and constructing the payload for <a href="#status.200" class="smpl">200 (OK)</a> and <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a> responses to GET (<a href="#GET" id="rfc.xref.GET.1" title="GET">Section&nbsp;4.3.1</a>).
    856856         </p>
    857857         <div id="representation.metadata">
     
    959959                  <p id="rfc.section.3.1.1.4.p.2">HTTP message framing does not use the multipart boundary as an indicator of message body length, though it might be used by
    960960                     implementations that generate or process the payload. For example, the "multipart/form-data" type is often used for carrying
    961                      form data in a request, as described in <a href="#RFC2388" id="rfc.xref.RFC2388.1"><cite title="Returning Values from Forms: multipart/form-data">[RFC2388]</cite></a>, and the "multipart/byteranges" type is defined by this specification for use in some <a href="p5-range.html#status.206" class="smpl">206 (Partial Content)</a> responses <a href="#Part5" id="rfc.xref.Part5.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a>.
     961                     form data in a request, as described in <a href="#RFC2388" id="rfc.xref.RFC2388.1"><cite title="Returning Values from Forms: multipart/form-data">[RFC2388]</cite></a>, and the "multipart/byteranges" type is defined by this specification for use in some <a href="p5-range.html#status.206" class="smpl">206 (Partial Content)</a> responses <a href="#RFC7233" id="rfc.xref.RFC7233.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[RFC7233]</cite></a>.
    962962                  </p>
    963963               </div>
     
    10061006                  <p id="rfc.section.3.1.2.1.p.4">The following content-coding values are defined by this specification: </p>
    10071007                  <ul class="empty">
    1008                      <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>.
     1008                     <li>compress (and x-compress): See <a href="p1-messaging.html#compress.coding" title="Compress Coding">Section 4.2.1</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>.
    10091009                     </li>
    1010                      <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>.
     1010                     <li>deflate: See <a href="p1-messaging.html#deflate.coding" title="Deflate Coding">Section 4.2.2</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>.
    10111011                     </li>
    1012                      <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>.
     1012                     <li>gzip (and x-gzip): See <a href="p1-messaging.html#gzip.coding" title="Gzip Coding">Section 4.2.3</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.9"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>.
    10131013                     </li>
    10141014                  </ul>
     
    10281028                     information about the encoding parameters can be provided by other header fields not defined by this specification.
    10291029                  </p>
    1030                   <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
     1030                  <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="#RFC7230" id="rfc.xref.RFC7230.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>), the codings listed in Content-Encoding are a characteristic of the representation; the representation is defined in terms
    10311031                     of the coded form, and all other metadata about the representation is about the coded form unless otherwise noted in the metadata
    10321032                     definition. Typically, the representation is only decoded just prior to rendering or analogous usage.
     
    11071107                  <p id="rfc.section.3.1.4.1.p.3">For a response message, the following rules are applied in order until a match is found: </p>
    11081108                  <ol>
    1109                      <li>If the request method 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 is a representation of the resource identified by 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>).
     1109                     <li>If the request method 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 is a representation of the resource identified by the effective request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.11"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>).
    11101110                     </li>
    11111111                     <li>If the request method 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 or enhanced representation of the <a href="#resources" class="smpl">target resource</a> as provided by an intermediary.
     
    11291129                  </p>
    11301130                  <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.12"></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>
    1131 </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
     1131</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="#RFC7230" id="rfc.xref.RFC7230.12"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>). It is representation metadata. It has the same syntax and semantics as the header field of the same name defined for MIME
    11321132                     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.
    11331133                  </p>
     
    12091209                     <tr>
    12101210                        <td class="left">Content-Length</td>
    1211                         <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>
     1211                        <td class="left"><a href="p1-messaging.html#header.content-length" title="Content-Length">Section 3.3.2</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.13"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a></td>
    12121212                     </tr>
    12131213                     <tr>
    12141214                        <td class="left">Content-Range</td>
    1215                         <td class="left"><a href="p5-range.html#header.content-range" title="Content-Range">Section 4.2</a> of <a href="#Part5" id="rfc.xref.Part5.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a></td>
     1215                        <td class="left"><a href="p5-range.html#header.content-range" title="Content-Range">Section 4.2</a> of <a href="#RFC7233" id="rfc.xref.RFC7233.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[RFC7233]</cite></a></td>
    12161216                     </tr>
    12171217                     <tr>
    12181218                        <td class="left">Trailer</td>
    1219                         <td class="left"><a href="p1-messaging.html#header.trailer" title="Trailer">Section 4.4</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>
     1219                        <td class="left"><a href="p1-messaging.html#header.trailer" title="Trailer">Section 4.4</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.14"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a></td>
    12201220                     </tr>
    12211221                     <tr>
    12221222                        <td class="left">Transfer-Encoding</td>
    1223                         <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.15"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a></td>
     1223                        <td class="left"><a href="p1-messaging.html#header.transfer-encoding" title="Transfer-Encoding">Section 3.3.1</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.15"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a></td>
    12241224                     </tr>
    12251225                  </tbody>
     
    13181318            <p id="rfc.section.4.1.p.2">The request method's semantics might be further specialized by the semantics of some header fields when present in a request
    13191319               (<a href="#request.header.fields" title="Request Header Fields">Section&nbsp;5</a>) if those additional semantics do not conflict with the method. For example, a client can send conditional request header
    1320                fields (<a href="#request.conditionals" title="Conditionals">Section&nbsp;5.2</a>) to make the requested action conditional on the current state of the target resource (<a href="#Part4" id="rfc.xref.Part4.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>).
     1320               fields (<a href="#request.conditionals" title="Conditionals">Section&nbsp;5.2</a>) to make the requested action conditional on the current state of the target resource (<a href="#RFC7232" id="rfc.xref.RFC7232.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[RFC7232]</cite></a>).
    13211321            </p>
    13221322            <div id="rfc.figure.u.17"></div><pre class="inline"><span id="rfc.iref.g.13"></span>  <a href="#method.overview" class="smpl">method</a> = <a href="#imported.abnf" class="smpl">token</a>
     
    14481448               <div id="rfc.iref.c.8"></div>
    14491449               <h3 id="rfc.section.4.2.3"><a href="#rfc.section.4.2.3">4.2.3</a>&nbsp;<a href="#cacheable.methods">Cacheable Methods</a></h3>
    1450                <p id="rfc.section.4.2.3.p.1">Request methods can be defined as "<dfn id="cacheable">cacheable</dfn>" to indicate that responses to them are allowed to be stored for future reuse; for specific requirements see <a href="#Part6" id="rfc.xref.Part6.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>. In general, safe methods that do not depend on a current or authoritative response are defined as cacheable; this specification
     1450               <p id="rfc.section.4.2.3.p.1">Request methods can be defined as "<dfn id="cacheable">cacheable</dfn>" to indicate that responses to them are allowed to be stored for future reuse; for specific requirements see <a href="#RFC7234" id="rfc.xref.RFC7234.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[RFC7234]</cite></a>. In general, safe methods that do not depend on a current or authoritative response are defined as cacheable; this specification
    14511451                  defines GET, HEAD and POST as cacheable, although the overwhelming majority of cache implementations only support GET and
    14521452                  HEAD.
     
    14711471               </p>
    14721472               <p id="rfc.section.4.3.1.p.3">A client can alter the semantics of GET to be a "range request", requesting transfer of only some part(s) of the selected
    1473                   representation, by sending a <a href="p5-range.html#header.range" class="smpl">Range</a> header field in the request (<a href="#Part5" id="rfc.xref.Part5.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a>).
     1473                  representation, by sending a <a href="p5-range.html#header.range" class="smpl">Range</a> header field in the request (<a href="#RFC7233" id="rfc.xref.RFC7233.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[RFC7233]</cite></a>).
    14741474               </p>
    14751475               <p id="rfc.section.4.3.1.p.4">A payload within a GET request message has no defined semantics; sending a payload body on a GET request might cause some
    14761476                  existing implementations to reject the request.
    14771477               </p>
    1478                <p id="rfc.section.4.3.1.p.5">The response to a GET request is cacheable; a cache <em class="bcp14">MAY</em> use it to satisfy subsequent GET and HEAD requests unless otherwise indicated by the Cache-Control header field (<a href="p6-cache.html#header.cache-control" title="Cache-Control">Section 5.2</a> of <a href="#Part6" id="rfc.xref.Part6.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
     1478               <p id="rfc.section.4.3.1.p.5">The response to a GET request is cacheable; a cache <em class="bcp14">MAY</em> use it to satisfy subsequent GET and HEAD requests unless otherwise indicated by the Cache-Control header field (<a href="p6-cache.html#header.cache-control" title="Cache-Control">Section 5.2</a> of <a href="#RFC7234" id="rfc.xref.RFC7234.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[RFC7234]</cite></a>).
    14791479               </p>
    14801480            </div>
     
    14891489                  existing implementations to reject the request.
    14901490               </p>
    1491                <p id="rfc.section.4.3.2.p.3">The response to a HEAD request is cacheable; a cache <em class="bcp14">MAY</em> use it to satisfy subsequent HEAD requests unless otherwise indicated by the Cache-Control header field (<a href="p6-cache.html#header.cache-control" title="Cache-Control">Section 5.2</a> of <a href="#Part6" id="rfc.xref.Part6.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>). A HEAD response might also have an effect on previously cached responses to GET; see <a href="p6-cache.html#head.effects" title="Freshening Responses via HEAD">Section 4.3.5</a> of <a href="#Part6" id="rfc.xref.Part6.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>.
     1491               <p id="rfc.section.4.3.2.p.3">The response to a HEAD request is cacheable; a cache <em class="bcp14">MAY</em> use it to satisfy subsequent HEAD requests unless otherwise indicated by the Cache-Control header field (<a href="p6-cache.html#header.cache-control" title="Cache-Control">Section 5.2</a> of <a href="#RFC7234" id="rfc.xref.RFC7234.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[RFC7234]</cite></a>). A HEAD response might also have an effect on previously cached responses to GET; see <a href="p6-cache.html#head.effects" title="Freshening Responses via HEAD">Section 4.3.5</a> of <a href="#RFC7234" id="rfc.xref.RFC7234.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[RFC7234]</cite></a>.
    14921492               </p>
    14931493            </div>
     
    15111511                  origin server <em class="bcp14">SHOULD</em> send a <a href="#status.201" class="smpl">201 (Created)</a> response containing a <a href="#header.location" class="smpl">Location</a> header field that provides an identifier for the primary resource created (<a href="#header.location" id="rfc.xref.header.location.1" title="Location">Section&nbsp;7.1.2</a>) and a representation that describes the status of the request while referring to the new resource(s).
    15121512               </p>
    1513                <p id="rfc.section.4.3.3.p.4">Responses to POST requests are only cacheable when they include explicit freshness information (see <a href="p6-cache.html#calculating.freshness.lifetime" title="Calculating Freshness Lifetime">Section 4.2.1</a> of <a href="#Part6" id="rfc.xref.Part6.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>). However, POST caching is not widely implemented. For cases where an origin server wishes the client to be able to cache
     1513               <p id="rfc.section.4.3.3.p.4">Responses to POST requests are only cacheable when they include explicit freshness information (see <a href="p6-cache.html#calculating.freshness.lifetime" title="Calculating Freshness Lifetime">Section 4.2.1</a> of <a href="#RFC7234" id="rfc.xref.RFC7234.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[RFC7234]</cite></a>). However, POST caching is not widely implemented. For cases where an origin server wishes the client to be able to cache
    15141514                  the result of a POST in a way that can be reused by a later GET, the origin server <em class="bcp14">MAY</em> send a <a href="#status.200" class="smpl">200 (OK)</a> response containing the result and a <a href="#header.content-location" class="smpl">Content-Location</a> header field that has the same value as the POST's effective request URI (<a href="#header.content-location" id="rfc.xref.header.content-location.2" title="Content-Location">Section&nbsp;3.1.4.2</a>).
    15151515               </p>
     
    15811581                  and might also cause links to be added between the related resources.
    15821582               </p>
    1583                <p id="rfc.section.4.3.4.p.11">An origin server that allows PUT on a given target resource <em class="bcp14">MUST</em> send a <a href="#status.400" class="smpl">400 (Bad Request)</a> response to a PUT request that contains a <a href="p5-range.html#header.content-range" class="smpl">Content-Range</a> header field (<a href="p5-range.html#header.content-range" title="Content-Range">Section 4.2</a> of <a href="#Part5" id="rfc.xref.Part5.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a>), since the payload is likely to be partial content that has been mistakenly PUT as a full representation. Partial content
     1583               <p id="rfc.section.4.3.4.p.11">An origin server that allows PUT on a given target resource <em class="bcp14">MUST</em> send a <a href="#status.400" class="smpl">400 (Bad Request)</a> response to a PUT request that contains a <a href="p5-range.html#header.content-range" class="smpl">Content-Range</a> header field (<a href="p5-range.html#header.content-range" title="Content-Range">Section 4.2</a> of <a href="#RFC7233" id="rfc.xref.RFC7233.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[RFC7233]</cite></a>), since the payload is likely to be partial content that has been mistakenly PUT as a full representation. Partial content
    15841584                  updates are possible by targeting a separately identified resource with state that overlaps a portion of the larger resource,
    15851585                  or by using a different method that has been specifically defined for partial updates (for example, the PATCH method defined
     
    15871587               </p>
    15881588               <p id="rfc.section.4.3.4.p.12">Responses to the PUT method are not cacheable. If a successful PUT request passes through a cache that has one or more stored
    1589                   responses for the effective request URI, those stored responses will be invalidated (see <a href="p6-cache.html#invalidation" title="Invalidation">Section 4.4</a> of <a href="#Part6" id="rfc.xref.Part6.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
     1589                  responses for the effective request URI, those stored responses will be invalidated (see <a href="p6-cache.html#invalidation" title="Invalidation">Section 4.4</a> of <a href="#RFC7234" id="rfc.xref.RFC7234.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[RFC7234]</cite></a>).
    15901590               </p>
    15911591            </div>
     
    16151615               </p>
    16161616               <p id="rfc.section.4.3.5.p.6">Responses to the DELETE method are not cacheable. If a DELETE request passes through a cache that has one or more stored responses
    1617                   for the effective request URI, those stored responses will be invalidated (see <a href="p6-cache.html#invalidation" title="Invalidation">Section 4.4</a> of <a href="#Part6" id="rfc.xref.Part6.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
     1617                  for the effective request URI, those stored responses will be invalidated (see <a href="p6-cache.html#invalidation" title="Invalidation">Section 4.4</a> of <a href="#RFC7234" id="rfc.xref.RFC7234.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[RFC7234]</cite></a>).
    16181618               </p>
    16191619            </div>
     
    16281628               <p id="rfc.section.4.3.6.p.2">CONNECT is intended only for use in requests to a proxy. An origin server that receives a CONNECT request for itself <em class="bcp14">MAY</em> respond with a <a href="#status.2xx" class="smpl">2xx</a> status code to indicate that a connection is established. However, most origin servers do not implement CONNECT.
    16291629               </p>
    1630                <p id="rfc.section.4.3.6.p.3">A client sending a CONNECT request <em class="bcp14">MUST</em> send the authority form of 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>); i.e., the request-target consists of only the host name and port number of the tunnel destination, separated by a colon.
     1630               <p id="rfc.section.4.3.6.p.3">A client sending a CONNECT request <em class="bcp14">MUST</em> send the authority form of request-target (<a href="p1-messaging.html#request-target" title="Request Target">Section 5.3</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.16"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>); i.e., the request-target consists of only the host name and port number of the tunnel destination, separated by a colon.
    16311631                  For example,
    16321632               </p>
     
    16671667                  with a resource, or the capabilities of a server, without implying a resource action.
    16681668               </p>
    1669                <p id="rfc.section.4.3.7.p.2">An OPTIONS request with an asterisk ("*") as 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.17"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) applies to the server in general rather than to a specific resource. Since a server's communication options typically depend
     1669               <p id="rfc.section.4.3.7.p.2">An OPTIONS request with an asterisk ("*") as the request-target (<a href="p1-messaging.html#request-target" title="Request Target">Section 5.3</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.17"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>) applies to the server in general rather than to a specific resource. Since a server's communication options typically depend
    16701670                  on the resource, the "*" request is only useful as a "ping" or "no-op" type of method; it does nothing beyond allowing the
    16711671                  client to test the capabilities of the server. For example, this can be used to test a proxy for HTTP/1.1 conformance (or
     
    16901690               <h3 id="rfc.section.4.3.8"><a href="#rfc.section.4.3.8">4.3.8</a>&nbsp;<a href="#TRACE">TRACE</a></h3>
    16911691               <div id="rfc.iref.t.1"></div>
    1692                <p id="rfc.section.4.3.8.p.1">The TRACE method requests a remote, application-level loop-back of the request message. The final recipient of the request <em class="bcp14">SHOULD</em> reflect the message received, excluding some fields described below, back to the client as the message body of a <a href="#status.200" class="smpl">200 (OK)</a> response with a <a href="#header.content-type" class="smpl">Content-Type</a> of "message/http" (<a href="p1-messaging.html#internet.media.type.message.http" title="Internet Media Type message/http">Section 8.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>). The final recipient is either the origin server or the first server to receive a <a href="#header.max-forwards" class="smpl">Max-Forwards</a> value of zero (0) in the request (<a href="#header.max-forwards" id="rfc.xref.header.max-forwards.2" title="Max-Forwards">Section&nbsp;5.1.2</a>).
     1692               <p id="rfc.section.4.3.8.p.1">The TRACE method requests a remote, application-level loop-back of the request message. The final recipient of the request <em class="bcp14">SHOULD</em> reflect the message received, excluding some fields described below, back to the client as the message body of a <a href="#status.200" class="smpl">200 (OK)</a> response with a <a href="#header.content-type" class="smpl">Content-Type</a> of "message/http" (<a href="p1-messaging.html#internet.media.type.message.http" title="Internet Media Type message/http">Section 8.3.1</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.18"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>). The final recipient is either the origin server or the first server to receive a <a href="#header.max-forwards" class="smpl">Max-Forwards</a> value of zero (0) in the request (<a href="#header.max-forwards" id="rfc.xref.header.max-forwards.2" title="Max-Forwards">Section&nbsp;5.1.2</a>).
    16931693               </p>
    16941694               <p id="rfc.section.4.3.8.p.2">A client <em class="bcp14">MUST NOT</em> generate header fields in a TRACE request containing sensitive data that might be disclosed by the response. For example,
    1695                   it would be foolish for a user agent to send stored user credentials <a href="#Part7" id="rfc.xref.Part7.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[Part7]</cite></a> or cookies <a href="#RFC6265" id="rfc.xref.RFC6265.1"><cite title="HTTP State Management Mechanism">[RFC6265]</cite></a> in a TRACE request. The final recipient of the request <em class="bcp14">SHOULD</em> exclude any request header fields that are likely to contain sensitive data when that recipient generates the response body.
     1695                  it would be foolish for a user agent to send stored user credentials <a href="#RFC7235" id="rfc.xref.RFC7235.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[RFC7235]</cite></a> or cookies <a href="#RFC6265" id="rfc.xref.RFC6265.1"><cite title="HTTP State Management Mechanism">[RFC6265]</cite></a> in a TRACE request. The final recipient of the request <em class="bcp14">SHOULD</em> exclude any request header fields that are likely to contain sensitive data when that recipient generates the response body.
    16961696               </p>
    16971697               <p id="rfc.section.4.3.8.p.3">TRACE allows the client to see what is being received at the other end of the request chain and use that data for testing
    1698                   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.1</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>) 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
     1698                  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.1</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.19"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</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
    16991699                  messages in an infinite loop.
    17001700               </p>
     
    17261726                     <tr>
    17271727                        <td class="left">Cache-Control</td>
    1728                         <td class="left"><a href="p6-cache.html#header.cache-control" title="Cache-Control">Section 5.2</a> of <a href="#Part6" id="rfc.xref.Part6.8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a></td>
     1728                        <td class="left"><a href="p6-cache.html#header.cache-control" title="Cache-Control">Section 5.2</a> of <a href="#RFC7234" id="rfc.xref.RFC7234.8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[RFC7234]</cite></a></td>
    17291729                     </tr>
    17301730                     <tr>
     
    17341734                     <tr>
    17351735                        <td class="left">Host</td>
    1736                         <td class="left"><a href="p1-messaging.html#header.host" title="Host">Section 5.4</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>
     1736                        <td class="left"><a href="p1-messaging.html#header.host" title="Host">Section 5.4</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.20"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a></td>
    17371737                     </tr>
    17381738                     <tr>
     
    17421742                     <tr>
    17431743                        <td class="left">Pragma</td>
    1744                         <td class="left"><a href="p6-cache.html#header.pragma" title="Pragma">Section 5.4</a> of <a href="#Part6" id="rfc.xref.Part6.9"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a></td>
     1744                        <td class="left"><a href="p6-cache.html#header.pragma" title="Pragma">Section 5.4</a> of <a href="#RFC7234" id="rfc.xref.RFC7234.9"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[RFC7234]</cite></a></td>
    17451745                     </tr>
    17461746                     <tr>
    17471747                        <td class="left">Range</td>
    1748                         <td class="left"><a href="p5-range.html#header.range" title="Range">Section 3.1</a> of <a href="#Part5" id="rfc.xref.Part5.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a></td>
     1748                        <td class="left"><a href="p5-range.html#header.range" title="Range">Section 3.1</a> of <a href="#RFC7233" id="rfc.xref.RFC7233.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[RFC7233]</cite></a></td>
    17491749                     </tr>
    17501750                     <tr>
    17511751                        <td class="left">TE</td>
    1752                         <td class="left"><a href="p1-messaging.html#header.te" title="TE">Section 4.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></td>
     1752                        <td class="left"><a href="p1-messaging.html#header.te" title="TE">Section 4.3</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.21"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a></td>
    17531753                     </tr>
    17541754                  </tbody>
     
    18031803                  </li>
    18041804                  <li>A server that responds with a final status code before reading the entire message body <em class="bcp14">SHOULD</em> indicate in that response whether it intends to close the connection or continue reading and discarding the request message
    1805                      (see <a href="p1-messaging.html#persistent.tear-down" title="Tear-down">Section 6.6</a> of <a href="#Part1" id="rfc.xref.Part1.22"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>).
     1805                     (see <a href="p1-messaging.html#persistent.tear-down" title="Tear-down">Section 6.6</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.22"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>).
    18061806                  </li>
    18071807               </ul>
     
    18421842            <div id="rfc.iref.c.10"></div>
    18431843            <h2 id="rfc.section.5.2"><a href="#rfc.section.5.2">5.2</a>&nbsp;<a href="#request.conditionals">Conditionals</a></h2>
    1844             <p id="rfc.section.5.2.p.1">The HTTP conditional request header fields <a href="#Part4" id="rfc.xref.Part4.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a> allow a client to place a precondition on the state of the target resource, so that the action corresponding to the method
     1844            <p id="rfc.section.5.2.p.1">The HTTP conditional request header fields <a href="#RFC7232" id="rfc.xref.RFC7232.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[RFC7232]</cite></a> allow a client to place a precondition on the state of the target resource, so that the action corresponding to the method
    18451845               semantics will not be applied if the precondition evaluates to false. Each precondition defined by this specification consists
    18461846               of a comparison between a set of validators obtained from prior representations of the target resource to the current state
    18471847               of validators for the <a href="#representations" class="smpl">selected representation</a> (<a href="#response.validator" title="Validator Header Fields">Section&nbsp;7.2</a>). Hence, these preconditions evaluate whether the state of the target resource has changed since a given state known by the
    1848                client. The effect of such an evaluation depends on the method semantics and choice of conditional, as defined in <a href="p4-conditional.html#evaluation" title="Evaluation">Section 5</a> of <a href="#Part4" id="rfc.xref.Part4.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>.
     1848               client. The effect of such an evaluation depends on the method semantics and choice of conditional, as defined in <a href="p4-conditional.html#evaluation" title="Evaluation">Section 5</a> of <a href="#RFC7232" id="rfc.xref.RFC7232.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[RFC7232]</cite></a>.
    18491849            </p>
    18501850            <div id="rfc.table.u.4">
     
    18591859                     <tr>
    18601860                        <td class="left">If-Match</td>
    1861                         <td class="left"><a href="p4-conditional.html#header.if-match" title="If-Match">Section 3.1</a> of <a href="#Part4" id="rfc.xref.Part4.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a></td>
     1861                        <td class="left"><a href="p4-conditional.html#header.if-match" title="If-Match">Section 3.1</a> of <a href="#RFC7232" id="rfc.xref.RFC7232.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[RFC7232]</cite></a></td>
    18621862                     </tr>
    18631863                     <tr>
    18641864                        <td class="left">If-None-Match</td>
    1865                         <td class="left"><a href="p4-conditional.html#header.if-none-match" title="If-None-Match">Section 3.2</a> of <a href="#Part4" id="rfc.xref.Part4.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a></td>
     1865                        <td class="left"><a href="p4-conditional.html#header.if-none-match" title="If-None-Match">Section 3.2</a> of <a href="#RFC7232" id="rfc.xref.RFC7232.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[RFC7232]</cite></a></td>
    18661866                     </tr>
    18671867                     <tr>
    18681868                        <td class="left">If-Modified-Since</td>
    1869                         <td class="left"><a href="p4-conditional.html#header.if-modified-since" title="If-Modified-Since">Section 3.3</a> of <a href="#Part4" id="rfc.xref.Part4.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a></td>
     1869                        <td class="left"><a href="p4-conditional.html#header.if-modified-since" title="If-Modified-Since">Section 3.3</a> of <a href="#RFC7232" id="rfc.xref.RFC7232.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[RFC7232]</cite></a></td>
    18701870                     </tr>
    18711871                     <tr>
    18721872                        <td class="left">If-Unmodified-Since</td>
    1873                         <td class="left"><a href="p4-conditional.html#header.if-unmodified-since" title="If-Unmodified-Since">Section 3.4</a> of <a href="#Part4" id="rfc.xref.Part4.8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a></td>
     1873                        <td class="left"><a href="p4-conditional.html#header.if-unmodified-since" title="If-Unmodified-Since">Section 3.4</a> of <a href="#RFC7232" id="rfc.xref.RFC7232.8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[RFC7232]</cite></a></td>
    18741874                     </tr>
    18751875                     <tr>
    18761876                        <td class="left">If-Range</td>
    1877                         <td class="left"><a href="p5-range.html#header.if-range" title="If-Range">Section 3.2</a> of <a href="#Part5" id="rfc.xref.Part5.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a></td>
     1877                        <td class="left"><a href="p5-range.html#header.if-range" title="If-Range">Section 3.2</a> of <a href="#RFC7233" id="rfc.xref.RFC7233.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[RFC7233]</cite></a></td>
    18781878                     </tr>
    18791879                  </tbody>
     
    21432143         <div id="request.auth">
    21442144            <h2 id="rfc.section.5.4"><a href="#rfc.section.5.4">5.4</a>&nbsp;<a href="#request.auth">Authentication Credentials</a></h2>
    2145             <p id="rfc.section.5.4.p.1">Two header fields are used for carrying authentication credentials, as defined in <a href="#Part7" id="rfc.xref.Part7.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[Part7]</cite></a>. Note that various custom mechanisms for user authentication use the Cookie header field for this purpose, as defined in <a href="#RFC6265" id="rfc.xref.RFC6265.2"><cite title="HTTP State Management Mechanism">[RFC6265]</cite></a>.
     2145            <p id="rfc.section.5.4.p.1">Two header fields are used for carrying authentication credentials, as defined in <a href="#RFC7235" id="rfc.xref.RFC7235.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[RFC7235]</cite></a>. Note that various custom mechanisms for user authentication use the Cookie header field for this purpose, as defined in <a href="#RFC6265" id="rfc.xref.RFC6265.2"><cite title="HTTP State Management Mechanism">[RFC6265]</cite></a>.
    21462146            </p>
    21472147            <div id="rfc.table.u.7">
     
    21562156                     <tr>
    21572157                        <td class="left">Authorization</td>
    2158                         <td class="left"><a href="p7-auth.html#header.authorization" title="Authorization">Section 4.2</a> of <a href="#Part7" id="rfc.xref.Part7.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[Part7]</cite></a></td>
     2158                        <td class="left"><a href="p7-auth.html#header.authorization" title="Authorization">Section 4.2</a> of <a href="#RFC7235" id="rfc.xref.RFC7235.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[RFC7235]</cite></a></td>
    21592159                     </tr>
    21602160                     <tr>
    21612161                        <td class="left">Proxy-Authorization</td>
    2162                         <td class="left"><a href="p7-auth.html#header.proxy-authorization" title="Proxy-Authorization">Section 4.4</a> of <a href="#Part7" id="rfc.xref.Part7.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[Part7]</cite></a></td>
     2162                        <td class="left"><a href="p7-auth.html#header.proxy-authorization" title="Proxy-Authorization">Section 4.4</a> of <a href="#RFC7235" id="rfc.xref.RFC7235.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[RFC7235]</cite></a></td>
    21632163                     </tr>
    21642164                  </tbody>
     
    22522252               </p>
    22532253               <div id="rfc.figure.u.39"></div><pre class="inline"><span id="rfc.iref.g.30"></span>  <a href="#header.user-agent" class="smpl">User-Agent</a> = <a href="#header.user-agent" class="smpl">product</a> *( <a href="#imported.abnf" class="smpl">RWS</a> ( <a href="#header.user-agent" class="smpl">product</a> / <a href="#imported.abnf" class="smpl">comment</a> ) )
    2254 </pre><p id="rfc.section.5.5.3.p.3">The User-Agent field-value consists of one or more product identifiers, each followed by zero or more comments (<a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</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>), which together identify the user agent software and its significant subproducts. By convention, the product identifiers
     2254</pre><p id="rfc.section.5.5.3.p.3">The User-Agent field-value consists of one or more product identifiers, each followed by zero or more comments (<a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.23"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>), which together identify the user agent software and its significant subproducts. By convention, the product identifiers
    22552255                  are listed in decreasing order of their significance for identifying the user agent software. Each product identifier consists
    22562256                  of a name and optional version.
     
    23022302         <div id="overview.of.status.codes">
    23032303            <h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a>&nbsp;<a href="#overview.of.status.codes">Overview of Status Codes</a></h2>
    2304             <p id="rfc.section.6.1.p.1">The status codes listed below are defined in this specification, <a href="p4-conditional.html#status.code.definitions" title="Status Code Definitions">Section 4</a> of <a href="#Part4" id="rfc.xref.Part4.9"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>, <a href="p5-range.html#range.response" title="Responses to a Range Request">Section 4</a> of <a href="#Part5" id="rfc.xref.Part5.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a>, and <a href="p7-auth.html#status.code.definitions" title="Status Code Definitions">Section 3</a> of <a href="#Part7" id="rfc.xref.Part7.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[Part7]</cite></a>. The reason phrases listed here are only recommendations — they can be replaced by local equivalents without affecting the
     2304            <p id="rfc.section.6.1.p.1">The status codes listed below are defined in this specification, <a href="p4-conditional.html#status.code.definitions" title="Status Code Definitions">Section 4</a> of <a href="#RFC7232" id="rfc.xref.RFC7232.9"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[RFC7232]</cite></a>, <a href="p5-range.html#range.response" title="Responses to a Range Request">Section 4</a> of <a href="#RFC7233" id="rfc.xref.RFC7233.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[RFC7233]</cite></a>, and <a href="p7-auth.html#status.code.definitions" title="Status Code Definitions">Section 3</a> of <a href="#RFC7235" id="rfc.xref.RFC7235.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[RFC7235]</cite></a>. The reason phrases listed here are only recommendations — they can be replaced by local equivalents without affecting the
    23052305               protocol.
    23062306            </p>
    23072307            <p id="rfc.section.6.1.p.2">Responses with status codes that are defined as cacheable by default (e.g., 200, 203, 204, 206, 300, 301, 404, 405, 410, 414,
    23082308               501 in this specification) can be reused by a cache with heuristic expiration unless otherwise indicated by the method definition
    2309                or explicit cache controls <a href="#Part6" id="rfc.xref.Part6.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>; all other status codes are not cacheable by default.
     2309               or explicit cache controls <a href="#RFC7234" id="rfc.xref.RFC7234.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[RFC7234]</cite></a>; all other status codes are not cacheable by default.
    23102310            </p>
    23112311            <div id="rfc.table.u.9">
     
    23622362                        <td class="left">206</td>
    23632363                        <td class="left">Partial Content</td>
    2364                         <td id="status.206" class="left"><a href="p5-range.html#status.206" title="206 Partial Content">Section 4.1</a> of <a href="#Part5" id="rfc.xref.Part5.8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a></td>
     2364                        <td id="status.206" class="left"><a href="p5-range.html#status.206" title="206 Partial Content">Section 4.1</a> of <a href="#RFC7233" id="rfc.xref.RFC7233.8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[RFC7233]</cite></a></td>
    23652365                     </tr>
    23662366                     <tr>
     
    23872387                        <td class="left">304</td>
    23882388                        <td class="left">Not Modified</td>
    2389                         <td id="status.304" class="left"><a href="p4-conditional.html#status.304" title="304 Not Modified">Section 4.1</a> of <a href="#Part4" id="rfc.xref.Part4.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a></td>
     2389                        <td id="status.304" class="left"><a href="p4-conditional.html#status.304" title="304 Not Modified">Section 4.1</a> of <a href="#RFC7232" id="rfc.xref.RFC7232.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[RFC7232]</cite></a></td>
    23902390                     </tr>
    23912391                     <tr>
     
    24072407                        <td class="left">401</td>
    24082408                        <td class="left">Unauthorized</td>
    2409                         <td id="status.401" class="left"><a href="p7-auth.html#status.401" title="401 Unauthorized">Section 3.1</a> of <a href="#Part7" id="rfc.xref.Part7.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[Part7]</cite></a></td>
     2409                        <td id="status.401" class="left"><a href="p7-auth.html#status.401" title="401 Unauthorized">Section 3.1</a> of <a href="#RFC7235" id="rfc.xref.RFC7235.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[RFC7235]</cite></a></td>
    24102410                     </tr>
    24112411                     <tr>
     
    24372437                        <td class="left">407</td>
    24382438                        <td class="left">Proxy Authentication Required</td>
    2439                         <td id="status.407" class="left"><a href="p7-auth.html#status.407" title="407 Proxy Authentication Required">Section 3.2</a> of <a href="#Part7" id="rfc.xref.Part7.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[Part7]</cite></a></td>
     2439                        <td id="status.407" class="left"><a href="p7-auth.html#status.407" title="407 Proxy Authentication Required">Section 3.2</a> of <a href="#RFC7235" id="rfc.xref.RFC7235.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[RFC7235]</cite></a></td>
    24402440                     </tr>
    24412441                     <tr>
     
    24622462                        <td class="left">412</td>
    24632463                        <td class="left">Precondition Failed</td>
    2464                         <td id="status.412" class="left"><a href="p4-conditional.html#status.412" title="412 Precondition Failed">Section 4.2</a> of <a href="#Part4" id="rfc.xref.Part4.11"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a></td>
     2464                        <td id="status.412" class="left"><a href="p4-conditional.html#status.412" title="412 Precondition Failed">Section 4.2</a> of <a href="#RFC7232" id="rfc.xref.RFC7232.11"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[RFC7232]</cite></a></td>
    24652465                     </tr>
    24662466                     <tr>
     
    24822482                        <td class="left">416</td>
    24832483                        <td class="left">Range Not Satisfiable</td>
    2484                         <td id="status.416" class="left"><a href="p5-range.html#status.416" title="416 Range Not Satisfiable">Section 4.4</a> of <a href="#Part5" id="rfc.xref.Part5.9"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a></td>
     2484                        <td id="status.416" class="left"><a href="p5-range.html#status.416" title="416 Range Not Satisfiable">Section 4.4</a> of <a href="#RFC7233" id="rfc.xref.RFC7233.9"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[RFC7233]</cite></a></td>
    24852485                     </tr>
    24862486                     <tr>
     
    25602560               <div id="rfc.iref.66"></div>
    25612561               <h3 id="rfc.section.6.2.2"><a href="#rfc.section.6.2.2">6.2.2</a>&nbsp;<a href="#status.101">101 Switching Protocols</a></h3>
    2562                <p id="rfc.section.6.2.2.p.1">The <dfn>101 (Switching Protocols)</dfn> status code indicates that 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> header field (<a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 6.7</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>), for a change in the application protocol being used on this connection. The server <em class="bcp14">MUST</em> generate an Upgrade header field in the response that indicates which protocol(s) will be switched to immediately after the
     2562               <p id="rfc.section.6.2.2.p.1">The <dfn>101 (Switching Protocols)</dfn> status code indicates that 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> header field (<a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 6.7</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.24"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>), for a change in the application protocol being used on this connection. The server <em class="bcp14">MUST</em> generate an Upgrade header field in the response that indicates which protocol(s) will be switched to immediately after the
    25632563                  empty line that terminates the 101 response.
    25642564               </p>
     
    26002600               </p>
    26012601               <p id="rfc.section.6.3.1.p.3">A 200 response is cacheable by default; i.e., unless otherwise indicated by the method definition or explicit cache controls
    2602                   (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.2.2</a> of <a href="#Part6" id="rfc.xref.Part6.11"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
     2602                  (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.2.2</a> of <a href="#RFC7234" id="rfc.xref.RFC7234.11"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[RFC7234]</cite></a>).
    26032603               </p>
    26042604            </div>
     
    26292629               <div id="rfc.iref.67"></div>
    26302630               <h3 id="rfc.section.6.3.4"><a href="#rfc.section.6.3.4">6.3.4</a>&nbsp;<a href="#status.203">203 Non-Authoritative Information</a></h3>
    2631                <p id="rfc.section.6.3.4.p.1">The <dfn>203 (Non-Authoritative Information)</dfn> status code indicates that the request was successful but the enclosed payload has been modified from that of the origin server's <a href="#status.200" class="smpl">200 (OK)</a> response by a transforming proxy (<a href="p1-messaging.html#message.transformations" title="Transformations">Section 5.7.2</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>). This status code allows the proxy to notify recipients when a transformation has been applied, since that knowledge might
     2631               <p id="rfc.section.6.3.4.p.1">The <dfn>203 (Non-Authoritative Information)</dfn> status code indicates that the request was successful but the enclosed payload has been modified from that of the origin server's <a href="#status.200" class="smpl">200 (OK)</a> response by a transforming proxy (<a href="p1-messaging.html#message.transformations" title="Transformations">Section 5.7.2</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.25"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>). This status code allows the proxy to notify recipients when a transformation has been applied, since that knowledge might
    26322632                  impact later decisions regarding the content. For example, future cache validation requests for the content might only be
    26332633                  applicable along the same request path (through the same proxies).
    26342634               </p>
    2635                <p id="rfc.section.6.3.4.p.2">The 203 response is similar to the Warning code of 214 Transformation Applied (<a href="p6-cache.html#header.warning" title="Warning">Section 5.5</a> of <a href="#Part6" id="rfc.xref.Part6.12"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>), which has the advantage of being applicable to responses with any status code.
     2635               <p id="rfc.section.6.3.4.p.2">The 203 response is similar to the Warning code of 214 Transformation Applied (<a href="p6-cache.html#header.warning" title="Warning">Section 5.5</a> of <a href="#RFC7234" id="rfc.xref.RFC7234.12"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[RFC7234]</cite></a>), which has the advantage of being applicable to responses with any status code.
    26362636               </p>
    26372637               <p id="rfc.section.6.3.4.p.3">A 203 response is cacheable by default; i.e., unless otherwise indicated by the method definition or explicit cache controls
    2638                   (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.2.2</a> of <a href="#Part6" id="rfc.xref.Part6.13"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
     2638                  (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.2.2</a> of <a href="#RFC7234" id="rfc.xref.RFC7234.13"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[RFC7234]</cite></a>).
    26392639               </p>
    26402640            </div>
     
    26592659               <p id="rfc.section.6.3.5.p.5">A 204 response is terminated by the first empty line after the header fields because it cannot contain a message body.</p>
    26602660               <p id="rfc.section.6.3.5.p.6">A 204 response is cacheable by default; i.e., unless otherwise indicated by the method definition or explicit cache controls
    2661                   (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.2.2</a> of <a href="#Part6" id="rfc.xref.Part6.14"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
     2661                  (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.2.2</a> of <a href="#RFC7234" id="rfc.xref.RFC7234.14"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[RFC7234]</cite></a>).
    26622662               </p>
    26632663            </div>
     
    27332733               </p>
    27342734               <p id="rfc.section.6.4.1.p.4">A 300 response is cacheable by default; i.e., unless otherwise indicated by the method definition or explicit cache controls
    2735                   (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.2.2</a> of <a href="#Part6" id="rfc.xref.Part6.15"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
     2735                  (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.2.2</a> of <a href="#RFC7234" id="rfc.xref.RFC7234.15"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[RFC7234]</cite></a>).
    27362736               </p>
    27372737               <div class="note" id="rfc.section.6.4.1.p.5">
     
    27582758               </div>
    27592759               <p id="rfc.section.6.4.2.p.4">A 301 response is cacheable by default; i.e., unless otherwise indicated by the method definition or explicit cache controls
    2760                   (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.2.2</a> of <a href="#Part6" id="rfc.xref.Part6.16"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
     2760                  (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.2.2</a> of <a href="#RFC7234" id="rfc.xref.RFC7234.16"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[RFC7234]</cite></a>).
    27612761               </p>
    27622762            </div>
     
    28632863               </p>
    28642864               <p id="rfc.section.6.5.4.p.2">A 404 response is cacheable by default; i.e., unless otherwise indicated by the method definition or explicit cache controls
    2865                   (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.2.2</a> of <a href="#Part6" id="rfc.xref.Part6.17"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
     2865                  (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.2.2</a> of <a href="#RFC7234" id="rfc.xref.RFC7234.17"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[RFC7234]</cite></a>).
    28662866               </p>
    28672867            </div>
     
    28722872               </p>
    28732873               <p id="rfc.section.6.5.5.p.2">A 405 response is cacheable by default; i.e., unless otherwise indicated by the method definition or explicit cache controls
    2874                   (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.2.2</a> of <a href="#Part6" id="rfc.xref.Part6.18"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
     2874                  (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.2.2</a> of <a href="#RFC7234" id="rfc.xref.RFC7234.18"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[RFC7234]</cite></a>).
    28752875               </p>
    28762876            </div>
     
    28892889               <h3 id="rfc.section.6.5.7"><a href="#rfc.section.6.5.7">6.5.7</a>&nbsp;<a href="#status.408">408 Request Timeout</a></h3>
    28902890               <p id="rfc.section.6.5.7.p.1">The <dfn>408 (Request Timeout)</dfn> status code indicates that the server did not receive a complete request message within the time that it was prepared to wait.
    2891                   A server <em class="bcp14">SHOULD</em> send the <a href="p1-messaging.html#header.connection" class="smpl">close</a> connection option (<a href="p1-messaging.html#header.connection" title="Connection">Section 6.1</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>) in the response, since 408 implies that the server has decided to close the connection rather than continue waiting. If
     2891                  A server <em class="bcp14">SHOULD</em> send the <a href="p1-messaging.html#header.connection" class="smpl">close</a> connection option (<a href="p1-messaging.html#header.connection" title="Connection">Section 6.1</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.26"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>) in the response, since 408 implies that the server has decided to close the connection rather than continue waiting. If
    28922892                  the client has an outstanding request in transit, the client <em class="bcp14">MAY</em> repeat that request on a new connection.
    28932893               </p>
     
    29182918               </p>
    29192919               <p id="rfc.section.6.5.9.p.3">A 410 response is cacheable by default; i.e., unless otherwise indicated by the method definition or explicit cache controls
    2920                   (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.2.2</a> of <a href="#Part6" id="rfc.xref.Part6.19"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
     2920                  (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.2.2</a> of <a href="#RFC7234" id="rfc.xref.RFC7234.19"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[RFC7234]</cite></a>).
    29212921               </p>
    29222922            </div>
     
    29242924               <div id="rfc.iref.69"></div>
    29252925               <h3 id="rfc.section.6.5.10"><a href="#rfc.section.6.5.10">6.5.10</a>&nbsp;<a href="#status.411">411 Length Required</a></h3>
    2926                <p id="rfc.section.6.5.10.p.1">The <dfn>411 (Length Required)</dfn> status code indicates that the server refuses to accept the request without a defined <a href="p1-messaging.html#header.content-length" class="smpl">Content-Length</a> (<a href="p1-messaging.html#header.content-length" title="Content-Length">Section 3.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>). 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
     2926               <p id="rfc.section.6.5.10.p.1">The <dfn>411 (Length Required)</dfn> status code indicates that the server refuses to accept the request without a defined <a href="p1-messaging.html#header.content-length" class="smpl">Content-Length</a> (<a href="p1-messaging.html#header.content-length" title="Content-Length">Section 3.3.2</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.27"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></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
    29272927                  message.
    29282928               </p>
     
    29402940               <div id="rfc.iref.69"></div>
    29412941               <h3 id="rfc.section.6.5.12"><a href="#rfc.section.6.5.12">6.5.12</a>&nbsp;<a href="#status.414">414 URI Too Long</a></h3>
    2942                <p id="rfc.section.6.5.12.p.1">The <dfn>414 (URI Too Long)</dfn> status code indicates that the server is refusing to service the request because 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.28"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) is longer than the server is willing to interpret. This rare condition is only likely to occur when a client has improperly
     2942               <p id="rfc.section.6.5.12.p.1">The <dfn>414 (URI Too Long)</dfn> status code indicates that the server is refusing to service the request because the request-target (<a href="p1-messaging.html#request-target" title="Request Target">Section 5.3</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.28"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>) is longer than the server is willing to interpret. This rare condition is only likely to occur when a client has improperly
    29432943                  converted a POST request to a GET request with long query information, when the client has descended into a "black hole" of
    29442944                  redirection (e.g., a redirected URI prefix that points to a suffix of itself), or when the server is under attack by a client
     
    29462946               </p>
    29472947               <p id="rfc.section.6.5.12.p.2">A 414 response is cacheable by default; i.e., unless otherwise indicated by the method definition or explicit cache controls
    2948                   (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.2.2</a> of <a href="#Part6" id="rfc.xref.Part6.20"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
     2948                  (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.2.2</a> of <a href="#RFC7234" id="rfc.xref.RFC7234.20"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[RFC7234]</cite></a>).
    29492949               </p>
    29502950            </div>
     
    29662966               <h3 id="rfc.section.6.5.15"><a href="#rfc.section.6.5.15">6.5.15</a>&nbsp;<a href="#status.426">426 Upgrade Required</a></h3>
    29672967               <p id="rfc.section.6.5.15.p.1">The <dfn>426 (Upgrade Required)</dfn> status code indicates that the server refuses to perform the request using the current protocol but might be willing to do
    2968                   so after the client upgrades to a different protocol. The server <em class="bcp14">MUST</em> send an <a href="p1-messaging.html#header.upgrade" class="smpl">Upgrade</a> header field in a 426 response to indicate the required protocol(s) (<a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 6.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>).
     2968                  so after the client upgrades to a different protocol. The server <em class="bcp14">MUST</em> send an <a href="p1-messaging.html#header.upgrade" class="smpl">Upgrade</a> header field in a 426 response to indicate the required protocol(s) (<a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 6.7</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.29"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>).
    29692969               </p>
    29702970               <div id="rfc.figure.u.42"></div>
     
    29992999               </p>
    30003000               <p id="rfc.section.6.6.2.p.2">A 501 response is cacheable by default; i.e., unless otherwise indicated by the method definition or explicit cache controls
    3001                   (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.2.2</a> of <a href="#Part6" id="rfc.xref.Part6.21"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
     3001                  (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.2.2</a> of <a href="#RFC7234" id="rfc.xref.RFC7234.21"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[RFC7234]</cite></a>).
    30023002               </p>
    30033003            </div>
     
    30333033               <p id="rfc.section.6.6.6.p.1">The <dfn>505 (HTTP Version Not Supported)</dfn> status code indicates that the server does not support, or refuses to support, the major version of HTTP that was used in
    30343034                  the request message. The server is indicating that it is unable or unwilling to complete the request using the same major
    3035                   version as the client, as described in <a href="p1-messaging.html#http.version" title="Protocol Versioning">Section 2.6</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>, other than with this error message. The server <em class="bcp14">SHOULD</em> generate a representation for the 505 response that describes why that version is not supported and what other protocols are
     3035                  version as the client, as described in <a href="p1-messaging.html#http.version" title="Protocol Versioning">Section 2.6</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.30"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, other than with this error message. The server <em class="bcp14">SHOULD</em> generate a representation for the 505 response that describes why that version is not supported and what other protocols are
    30363036                  supported by that server.
    30373037               </p>
     
    30633063                     <tr>
    30643064                        <td class="left">Age</td>
    3065                         <td class="left"><a href="p6-cache.html#header.age" title="Age">Section 5.1</a> of <a href="#Part6" id="rfc.xref.Part6.22"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a></td>
     3065                        <td class="left"><a href="p6-cache.html#header.age" title="Age">Section 5.1</a> of <a href="#RFC7234" id="rfc.xref.RFC7234.22"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[RFC7234]</cite></a></td>
    30663066                     </tr>
    30673067                     <tr>
    30683068                        <td class="left">Cache-Control</td>
    3069                         <td class="left"><a href="p6-cache.html#header.cache-control" title="Cache-Control">Section 5.2</a> of <a href="#Part6" id="rfc.xref.Part6.23"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a></td>
     3069                        <td class="left"><a href="p6-cache.html#header.cache-control" title="Cache-Control">Section 5.2</a> of <a href="#RFC7234" id="rfc.xref.RFC7234.23"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[RFC7234]</cite></a></td>
    30703070                     </tr>
    30713071                     <tr>
    30723072                        <td class="left">Expires</td>
    3073                         <td class="left"><a href="p6-cache.html#header.expires" title="Expires">Section 5.3</a> of <a href="#Part6" id="rfc.xref.Part6.24"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a></td>
     3073                        <td class="left"><a href="p6-cache.html#header.expires" title="Expires">Section 5.3</a> of <a href="#RFC7234" id="rfc.xref.RFC7234.24"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[RFC7234]</cite></a></td>
    30743074                     </tr>
    30753075                     <tr>
     
    30913091                     <tr>
    30923092                        <td class="left">Warning</td>
    3093                         <td class="left"><a href="p6-cache.html#header.warning" title="Warning">Section 5.5</a> of <a href="#Part6" id="rfc.xref.Part6.25"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a></td>
     3093                        <td class="left"><a href="p6-cache.html#header.warning" title="Warning">Section 5.5</a> of <a href="#RFC7234" id="rfc.xref.RFC7234.25"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[RFC7234]</cite></a></td>
    30943094                     </tr>
    30953095                  </tbody>
     
    32963296                  <li>
    32973297                     <p>To inform cache recipients that they <em class="bcp14">MUST NOT</em> use this response to satisfy a later request unless the later request has the same values for the listed fields as the original
    3298                         request (<a href="p6-cache.html#caching.negotiated.responses" title="Calculating Secondary Keys with Vary">Section 4.1</a> of <a href="#Part6" id="rfc.xref.Part6.26"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>). In other words, Vary expands the cache key required to match a new request to the stored cache entry.
     3298                        request (<a href="p6-cache.html#caching.negotiated.responses" title="Calculating Secondary Keys with Vary">Section 4.1</a> of <a href="#RFC7234" id="rfc.xref.RFC7234.26"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[RFC7234]</cite></a>). In other words, Vary expands the cache key required to match a new request to the stored cache entry.
    32993299                     </p>
    33003300                  </li>
     
    33083308                  other than the method and request target, unless the variance cannot be crossed or the origin server has been deliberately
    33093309                  configured to prevent cache transparency. For example, there is no need to send the Authorization field name in Vary because
    3310                   reuse across users is constrained by the field definition (<a href="p7-auth.html#header.authorization" title="Authorization">Section 4.2</a> of <a href="#Part7" id="rfc.xref.Part7.8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[Part7]</cite></a>). Likewise, an origin server might use Cache-Control directives (<a href="p6-cache.html#header.cache-control" title="Cache-Control">Section 5.2</a> of <a href="#Part6" id="rfc.xref.Part6.27"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>) to supplant Vary if it considers the variance less significant than the performance cost of Vary's impact on caching.
     3310                  reuse across users is constrained by the field definition (<a href="p7-auth.html#header.authorization" title="Authorization">Section 4.2</a> of <a href="#RFC7235" id="rfc.xref.RFC7235.8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[RFC7235]</cite></a>). Likewise, an origin server might use Cache-Control directives (<a href="p6-cache.html#header.cache-control" title="Cache-Control">Section 5.2</a> of <a href="#RFC7234" id="rfc.xref.RFC7234.27"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[RFC7234]</cite></a>) to supplant Vary if it considers the variance less significant than the performance cost of Vary's impact on caching.
    33113311               </p>
    33123312            </div>
     
    33223322            </p>
    33233323            <p id="rfc.section.7.2.p.3">For example, an ETag header field in a 201 response communicates the entity-tag of the newly created resource's representation,
    3324                so that it can be used in later conditional requests to prevent the "lost update" problem <a href="#Part4" id="rfc.xref.Part4.12"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>.
     3324               so that it can be used in later conditional requests to prevent the "lost update" problem <a href="#RFC7232" id="rfc.xref.RFC7232.12"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[RFC7232]</cite></a>.
    33253325            </p>
    33263326            <div id="rfc.table.u.11">
     
    33353335                     <tr>
    33363336                        <td class="left">ETag</td>
    3337                         <td class="left"><a href="p4-conditional.html#header.etag" title="ETag">Section 2.3</a> of <a href="#Part4" id="rfc.xref.Part4.13"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a></td>
     3337                        <td class="left"><a href="p4-conditional.html#header.etag" title="ETag">Section 2.3</a> of <a href="#RFC7232" id="rfc.xref.RFC7232.13"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[RFC7232]</cite></a></td>
    33383338                     </tr>
    33393339                     <tr>
    33403340                        <td class="left">Last-Modified</td>
    3341                         <td class="left"><a href="p4-conditional.html#header.last-modified" title="Last-Modified">Section 2.2</a> of <a href="#Part4" id="rfc.xref.Part4.14"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a></td>
     3341                        <td class="left"><a href="p4-conditional.html#header.last-modified" title="Last-Modified">Section 2.2</a> of <a href="#RFC7232" id="rfc.xref.RFC7232.14"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[RFC7232]</cite></a></td>
    33423342                     </tr>
    33433343                  </tbody>
     
    33613361                     <tr>
    33623362                        <td class="left">WWW-Authenticate</td>
    3363                         <td class="left"><a href="p7-auth.html#header.www-authenticate" title="WWW-Authenticate">Section 4.1</a> of <a href="#Part7" id="rfc.xref.Part7.9"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[Part7]</cite></a></td>
     3363                        <td class="left"><a href="p7-auth.html#header.www-authenticate" title="WWW-Authenticate">Section 4.1</a> of <a href="#RFC7235" id="rfc.xref.RFC7235.9"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[RFC7235]</cite></a></td>
    33643364                     </tr>
    33653365                     <tr>
    33663366                        <td class="left">Proxy-Authenticate</td>
    3367                         <td class="left"><a href="p7-auth.html#header.proxy-authenticate" title="Proxy-Authenticate">Section 4.3</a> of <a href="#Part7" id="rfc.xref.Part7.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[Part7]</cite></a></td>
     3367                        <td class="left"><a href="p7-auth.html#header.proxy-authenticate" title="Proxy-Authenticate">Section 4.3</a> of <a href="#RFC7235" id="rfc.xref.RFC7235.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[RFC7235]</cite></a></td>
    33683368                     </tr>
    33693369                  </tbody>
     
    33863386                     <tr>
    33873387                        <td class="left">Accept-Ranges</td>
    3388                         <td class="left"><a href="p5-range.html#header.accept-ranges" title="Accept-Ranges">Section 2.3</a> of <a href="#Part5" id="rfc.xref.Part5.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a></td>
     3388                        <td class="left"><a href="p5-range.html#header.accept-ranges" title="Accept-Ranges">Section 2.3</a> of <a href="#RFC7233" id="rfc.xref.RFC7233.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[RFC7233]</cite></a></td>
    33893389                     </tr>
    33903390                     <tr>
     
    34223422               </p>
    34233423               <div id="rfc.figure.u.62"></div><pre class="inline"><span id="rfc.iref.g.55"></span>  <a href="#header.server" class="smpl">Server</a> = <a href="#header.user-agent" class="smpl">product</a> *( <a href="#imported.abnf" class="smpl">RWS</a> ( <a href="#header.user-agent" class="smpl">product</a> / <a href="#imported.abnf" class="smpl">comment</a> ) )
    3424 </pre><p id="rfc.section.7.4.2.p.3">The Server field-value consists of one or more product identifiers, each followed by zero or more comments (<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>), which together identify the origin server software and its significant subproducts. By convention, the product identifiers
     3424</pre><p id="rfc.section.7.4.2.p.3">The Server field-value consists of one or more product identifiers, each followed by zero or more comments (<a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.31"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>), which together identify the origin server software and its significant subproducts. By convention, the product identifiers
    34253425                  are listed in decreasing order of their significance for identifying the origin server software. Each product identifier consists
    34263426                  of a name and optional version, as defined in <a href="#header.user-agent" id="rfc.xref.header.user-agent.2" title="User-Agent">Section&nbsp;5.5.3</a>.
     
    34633463                  to a single application or data format, since orthogonal technologies deserve orthogonal specification.
    34643464               </p>
    3465                <p id="rfc.section.8.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.32"><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
     3465               <p id="rfc.section.8.1.2.p.2">Since message parsing (<a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.32"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>) needs to be independent of method semantics (aside from responses to HEAD), definitions of new methods cannot change the
    34663466                  parsing algorithm or prohibit the presence of a message body on either the request or the response message. Definitions of
    34673467                  new methods can specify that only a zero-length message body is allowed by requiring a Content-Length header field with a
     
    34723472                  under what conditions, a cache can store a response and use it to satisfy a subsequent request. The new method ought to describe
    34733473                  whether it can be made conditional (<a href="#request.conditionals" title="Conditionals">Section&nbsp;5.2</a>) and, if so, how a server responds when the condition is false. Likewise, if the new method might have some use for partial
    3474                   response semantics (<a href="#Part5" id="rfc.xref.Part5.11"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a>), it ought to document this too.
     3474                  response semantics (<a href="#RFC7233" id="rfc.xref.RFC7233.11"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[RFC7233]</cite></a>), it ought to document this too.
    34753475               </p>
    34763476               <div class="note" id="rfc.section.8.1.2.p.4">
     
    35963596                  if the response they occur in has explicit freshness information; however, status codes that are defined as being cacheable
    35973597                  are allowed to be cached without explicit freshness information. Likewise, the definition of a status code can place constraints
    3598                   upon cache behavior. See <a href="#Part6" id="rfc.xref.Part6.28"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a> for more information.
     3598                  upon cache behavior. See <a href="#RFC7234" id="rfc.xref.RFC7234.28"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[RFC7234]</cite></a> for more information.
    35993599               </p>
    36003600               <p id="rfc.section.8.2.2.p.6">Finally, the definition of a new status code ought to indicate whether the payload has any implied association with an identified
     
    38443844               <h3 id="rfc.section.8.3.1"><a href="#rfc.section.8.3.1">8.3.1</a>&nbsp;<a href="#considerations.for.new.header.fields">Considerations for New Header Fields</a></h3>
    38453845               <p id="rfc.section.8.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,
    3846                   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.33"><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.
     3846                  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="#RFC7230" id="rfc.xref.RFC7230.33"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a> for a general definition of header field syntax in HTTP messages.
    38473847               </p>
    38483848               <p id="rfc.section.8.3.1.p.2">The requirements for header field names are defined in <a href="#BCP90" id="rfc.xref.BCP90.2"><cite title="Registration Procedures for Message Header Fields">[BCP90]</cite></a>.
     
    38533853                  processing, since the prefix would ensure that private names never collide with a newly registered Internet name; see <a href="#BCP178" id="rfc.xref.BCP178.1"><cite title="Deprecating the &#34;X-&#34; Prefix and Similar Constructs in Application Protocols">[BCP178]</cite></a> for further information)
    38543854               </p>
    3855                <p id="rfc.section.8.3.1.p.4">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">Section 7</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> as necessary, and are usually constrained to the range of ASCII characters. Header fields needing a greater range of characters
     3855               <p id="rfc.section.8.3.1.p.4">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">Section 7</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.34"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a> as necessary, and are usually constrained to the range of ASCII characters. Header fields needing a greater range of characters
    38563856                  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>.
    38573857               </p>
    3858                <p id="rfc.section.8.3.1.p.5">Leading and trailing whitespace in raw field values is removed upon field parsing (<a href="p1-messaging.html#field.parsing" title="Field Parsing">Section 3.2.4</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>). Field definitions where leading or trailing whitespace in values is significant will have to use a container syntax such
    3859                   as quoted-string (<a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.6</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>).
     3858               <p id="rfc.section.8.3.1.p.5">Leading and trailing whitespace in raw field values is removed upon field parsing (<a href="p1-messaging.html#field.parsing" title="Field Parsing">Section 3.2.4</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.35"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>). Field definitions where leading or trailing whitespace in values is significant will have to use a container syntax such
     3859                  as quoted-string (<a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.6</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.36"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>).
    38603860               </p>
    38613861               <p id="rfc.section.8.3.1.p.6">Because commas (",") are used as a generic delimiter between field-values, they need to be treated with care if they are allowed
     
    38793879               <ul>
    38803880                  <li>
    3881                      <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.37"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>).
     3881                     <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="#RFC7230" id="rfc.xref.RFC7230.37"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>).
    38823882                     </p>
    38833883                     <p>If it does not use the list syntax, document how to treat messages where the field occurs multiple times (a sensible default
     
    39023902                  </li>
    39033903                  <li>
    3904                      <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.38"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>).
     3904                     <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="#RFC7230" id="rfc.xref.RFC7230.38"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>).
    39053905                     </p>
    39063906                  </li>
     
    39133913                  </li>
    39143914                  <li>
    3915                      <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.39"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>).
     3915                     <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="#RFC7230" id="rfc.xref.RFC7230.39"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>).
    39163916                     </p>
    39173917                  </li>
     
    40874087         <div id="content.coding.registry">
    40884088            <h2 id="rfc.section.8.4"><a href="#rfc.section.8.4">8.4</a>&nbsp;<a href="#content.coding.registry">Content Coding Registry</a></h2>
    4089             <p id="rfc.section.8.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.40"><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;.
     4089            <p id="rfc.section.8.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="#RFC7230" id="rfc.xref.RFC7230.40"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</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;.
    40904090            </p>
    40914091            <div id="content.coding.procedure">
     
    40984098                  <li>Pointer to specification text</li>
    40994099               </ul>
    4100                <p id="rfc.section.8.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.41"><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.42"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>).
     4100               <p id="rfc.section.8.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="#RFC7230" id="rfc.xref.RFC7230.41"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</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="#RFC7230" id="rfc.xref.RFC7230.42"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>).
    41014101               </p>
    41024102               <p id="rfc.section.8.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.
     
    41344134         <p id="rfc.section.9.p.1">This section is meant to inform developers, information providers, and users of known security concerns relevant to HTTP semantics
    41354135            and its use for transferring information over the Internet. Considerations related to message syntax, parsing, and routing
    4136             are discussed in <a href="p1-messaging.html#security.considerations" title="Security Considerations">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>.
     4136            are discussed in <a href="p1-messaging.html#security.considerations" title="Security Considerations">Section 9</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.43"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>.
    41374137         </p>
    41384138         <p id="rfc.section.9.p.2">The list of considerations below is not exhaustive. Most security concerns related to HTTP semantics are about securing server-side
     
    42134213         <div id="disclosure.product.information">
    42144214            <h2 id="rfc.section.9.6"><a href="#rfc.section.9.6">9.6</a>&nbsp;<a href="#disclosure.product.information">Disclosure of Product Information</a></h2>
    4215             <p id="rfc.section.9.6.p.1">The <a href="#header.user-agent" class="smpl">User-Agent</a> (<a href="#header.user-agent" id="rfc.xref.header.user-agent.4" title="User-Agent">Section&nbsp;5.5.3</a>), <a href="p1-messaging.html#header.via" class="smpl">Via</a> (<a href="p1-messaging.html#header.via" title="Via">Section 5.7.1</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>), and <a href="#header.server" class="smpl">Server</a> (<a href="#header.server" id="rfc.xref.header.server.3" title="Server">Section&nbsp;7.4.2</a>) header fields often reveal information about the respective sender's software systems. In theory, this can make it easier
     4215            <p id="rfc.section.9.6.p.1">The <a href="#header.user-agent" class="smpl">User-Agent</a> (<a href="#header.user-agent" id="rfc.xref.header.user-agent.4" title="User-Agent">Section&nbsp;5.5.3</a>), <a href="p1-messaging.html#header.via" class="smpl">Via</a> (<a href="p1-messaging.html#header.via" title="Via">Section 5.7.1</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.44"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>), and <a href="#header.server" class="smpl">Server</a> (<a href="#header.server" id="rfc.xref.header.server.3" title="Server">Section&nbsp;7.4.2</a>) header fields often reveal information about the respective sender's software systems. In theory, this can make it easier
    42164216               for an attacker to exploit known security holes; in practice, attackers tend to try all potential holes regardless of the
    42174217               apparent software versions being used.
     
    42534253      <div id="acks">
    42544254         <h1 id="rfc.section.10"><a href="#rfc.section.10">10.</a>&nbsp;<a href="#acks">Acknowledgments</a></h1>
    4255          <p id="rfc.section.10.p.1">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 10</a> of <a href="#Part1" id="rfc.xref.Part1.45"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.
     4255         <p id="rfc.section.10.p.1">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 10</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.45"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>.
    42564256         </p>
    42574257      </div>
     
    42614261      </h2>
    42624262      <table>
    4263          <tr>
    4264             <td class="reference"><b id="Part1">[Part1]</b></td>
    4265             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-latest (work in progress), May&nbsp;2014.
    4266             </td>
    4267          </tr>
    4268          <tr>
    4269             <td class="reference"><b id="Part4">[Part4]</b></td>
    4270             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-latest (work in progress), May&nbsp;2014.
    4271             </td>
    4272          </tr>
    4273          <tr>
    4274             <td class="reference"><b id="Part5">[Part5]</b></td>
    4275             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">Hypertext Transfer Protocol (HTTP/1.1): Range Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-latest (work in progress), May&nbsp;2014.
    4276             </td>
    4277          </tr>
    4278          <tr>
    4279             <td class="reference"><b id="Part6">[Part6]</b></td>
    4280             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:mnot@mnot.net" title="Akamai">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">Hypertext Transfer Protocol (HTTP/1.1): Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-latest (work in progress), May&nbsp;2014.
    4281             </td>
    4282          </tr>
    4283          <tr>
    4284             <td class="reference"><b id="Part7">[Part7]</b></td>
    4285             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p7-auth-latest">Hypertext Transfer Protocol (HTTP/1.1): Authentication</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p7-auth-latest (work in progress), May&nbsp;2014.
    4286             </td>
    4287          </tr>
    42884263         <tr>
    42894264            <td class="reference"><b id="RFC2045">[RFC2045]</b></td>
     
    43244299            <td class="reference"><b id="RFC6365">[RFC6365]</b></td>
    43254300            <td class="top">Hoffman, P. and J. Klensin, “<a href="http://tools.ietf.org/html/rfc6365">Terminology Used in Internationalization in the IETF</a>”, BCP&nbsp;166, RFC&nbsp;6365, September&nbsp;2011.
     4301            </td>
     4302         </tr>
     4303         <tr>
     4304            <td class="reference"><b id="RFC7230">[RFC7230]</b></td>
     4305            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-latest (work in progress), May&nbsp;2014.
     4306            </td>
     4307         </tr>
     4308         <tr>
     4309            <td class="reference"><b id="RFC7232">[RFC7232]</b></td>
     4310            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-latest (work in progress), May&nbsp;2014.
     4311            </td>
     4312         </tr>
     4313         <tr>
     4314            <td class="reference"><b id="RFC7233">[RFC7233]</b></td>
     4315            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">Hypertext Transfer Protocol (HTTP/1.1): Range Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-latest (work in progress), May&nbsp;2014.
     4316            </td>
     4317         </tr>
     4318         <tr>
     4319            <td class="reference"><b id="RFC7234">[RFC7234]</b></td>
     4320            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:mnot@mnot.net" title="Akamai">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">Hypertext Transfer Protocol (HTTP/1.1): Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-latest (work in progress), May&nbsp;2014.
     4321            </td>
     4322         </tr>
     4323         <tr>
     4324            <td class="reference"><b id="RFC7235">[RFC7235]</b></td>
     4325            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p7-auth-latest">Hypertext Transfer Protocol (HTTP/1.1): Authentication</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p7-auth-latest (work in progress), May&nbsp;2014.
    43264326            </td>
    43274327         </tr>
     
    45174517               fold long lines. MHTML messages being transported by HTTP follow all conventions of MHTML, including line length limitations
    45184518               and folding, canonicalization, etc., since HTTP transfers message-bodies as payload and, aside from the "multipart/byteranges"
    4519                type (<a href="p5-range.html#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix A</a> of <a href="#Part5" id="rfc.xref.Part5.12"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a>), does not interpret the content or any MIME header lines that might be contained therein.
     4519               type (<a href="p5-range.html#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix A</a> of <a href="#RFC7233" id="rfc.xref.RFC7233.12"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[RFC7233]</cite></a>), does not interpret the content or any MIME header lines that might be contained therein.
    45204520            </p>
    45214521         </div>
     
    45394539            and the undesirable effect of potentially breaking relative links in content-negotiated resources. (<a href="#header.content-location" id="rfc.xref.header.content-location.5" title="Content-Location">Section&nbsp;3.1.4.2</a>)
    45404540         </p>
    4541          <p id="rfc.section.B.p.6">To be consistent with the method-neutral parsing algorithm of <a href="#Part1" id="rfc.xref.Part1.46"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, the definition of GET has been relaxed so that requests can have a body, even though a body has no meaning for GET. (<a href="#GET" id="rfc.xref.GET.6" title="GET">Section&nbsp;4.3.1</a>)
     4541         <p id="rfc.section.B.p.6">To be consistent with the method-neutral parsing algorithm of <a href="#RFC7230" id="rfc.xref.RFC7230.46"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, the definition of GET has been relaxed so that requests can have a body, even though a body has no meaning for GET. (<a href="#GET" id="rfc.xref.GET.6" title="GET">Section&nbsp;4.3.1</a>)
    45424542         </p>
    45434543         <p id="rfc.section.B.p.7">Servers are no longer required to handle all Content-* header fields and use of <a href="p5-range.html#header.content-range" class="smpl">Content-Range</a> has been explicitly banned in PUT requests. (<a href="#PUT" id="rfc.xref.PUT.5" title="PUT">Section&nbsp;4.3.4</a>)
     
    46004600            (any visible US-ASCII character).
    46014601         </p>
    4602          <p id="rfc.section.C.p.2">The rules below are 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>:
    4603          </p>
    4604          <div id="rfc.figure.u.65"></div><pre class="inline">  <a href="#imported.abnf" class="smpl">BWS</a>           = &lt;BWS, 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.3</a>&gt;
    4605   <a href="#imported.abnf" class="smpl">OWS</a>           = &lt;OWS, 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#whitespace" title="Whitespace">Section 3.2.3</a>&gt;
    4606   <a href="#imported.abnf" class="smpl">RWS</a>           = &lt;RWS, 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#whitespace" title="Whitespace">Section 3.2.3</a>&gt;
    4607   <a href="#imported.abnf" class="smpl">URI-reference</a> = &lt;URI-reference, 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#uri" title="Uniform Resource Identifiers">Section 2.7</a>&gt;
    4608   <a href="#imported.abnf" class="smpl">absolute-URI</a>  = &lt;absolute-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;
    4609   <a href="#imported.abnf" class="smpl">comment</a>       = &lt;comment, 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.6</a>&gt;
    4610   <a href="#imported.abnf" class="smpl">field-name</a>    = &lt;comment, 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#header.fields" title="Header Fields">Section 3.2</a>&gt;
    4611   <a href="#imported.abnf" class="smpl">partial-URI</a>   = &lt;partial-URI, 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#uri" title="Uniform Resource Identifiers">Section 2.7</a>&gt;
    4612   <a href="#imported.abnf" class="smpl">quoted-string</a> = &lt;quoted-string, 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.6</a>&gt;
    4613   <a href="#imported.abnf" class="smpl">token</a>         = &lt;token, defined in <a href="#Part1" id="rfc.xref.Part1.57"><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.6</a>&gt;
     4602         <p id="rfc.section.C.p.2">The rules below are defined in <a href="#RFC7230" id="rfc.xref.RFC7230.47"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>:
     4603         </p>
     4604         <div id="rfc.figure.u.65"></div><pre class="inline">  <a href="#imported.abnf" class="smpl">BWS</a>           = &lt;BWS, defined in <a href="#RFC7230" id="rfc.xref.RFC7230.48"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.3</a>&gt;
     4605  <a href="#imported.abnf" class="smpl">OWS</a>           = &lt;OWS, defined in <a href="#RFC7230" id="rfc.xref.RFC7230.49"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.3</a>&gt;
     4606  <a href="#imported.abnf" class="smpl">RWS</a>           = &lt;RWS, defined in <a href="#RFC7230" id="rfc.xref.RFC7230.50"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.3</a>&gt;
     4607  <a href="#imported.abnf" class="smpl">URI-reference</a> = &lt;URI-reference, defined in <a href="#RFC7230" id="rfc.xref.RFC7230.51"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.7</a>&gt;
     4608  <a href="#imported.abnf" class="smpl">absolute-URI</a>  = &lt;absolute-URI, defined in <a href="#RFC7230" id="rfc.xref.RFC7230.52"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.7</a>&gt;
     4609  <a href="#imported.abnf" class="smpl">comment</a>       = &lt;comment, defined in <a href="#RFC7230" id="rfc.xref.RFC7230.53"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.6</a>&gt;
     4610  <a href="#imported.abnf" class="smpl">field-name</a>    = &lt;comment, defined in <a href="#RFC7230" id="rfc.xref.RFC7230.54"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, <a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a>&gt;
     4611  <a href="#imported.abnf" class="smpl">partial-URI</a>   = &lt;partial-URI, defined in <a href="#RFC7230" id="rfc.xref.RFC7230.55"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.7</a>&gt;
     4612  <a href="#imported.abnf" class="smpl">quoted-string</a> = &lt;quoted-string, defined in <a href="#RFC7230" id="rfc.xref.RFC7230.56"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.6</a>&gt;
     4613  <a href="#imported.abnf" class="smpl">token</a>         = &lt;token, defined in <a href="#RFC7230" id="rfc.xref.RFC7230.57"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.6</a>&gt;
    46144614</pre></div>
    46154615      <div id="collected.abnf">
    46164616         <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a>&nbsp;<a href="#collected.abnf">Collected ABNF</a></h1>
    4617          <p id="rfc.section.D.p.1">In the collected ABNF below, list rules are expanded as per <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#Part1" id="rfc.xref.Part1.58"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.
     4617         <p id="rfc.section.D.p.1">In the collected ABNF below, list rules are expanded as per <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.58"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>.
    46184618         </p>
    46194619         <div id="rfc.figure.u.66"></div><pre class="inline"><a href="#header.accept" class="smpl">Accept</a> = [ ( "," / ( media-range [ accept-params ] ) ) *( OWS "," [
     
    46274627<a href="#header.allow" class="smpl">Allow</a> = [ ( "," / method ) *( OWS "," [ OWS method ] ) ]
    46284628
    4629 <a href="#imported.abnf" class="smpl">BWS</a> = &lt;BWS, defined in [Part1], Section 3.2.3&gt;
     4629<a href="#imported.abnf" class="smpl">BWS</a> = &lt;BWS, defined in [RFC7230], Section 3.2.3&gt;
    46304630
    46314631<a href="#header.content-encoding" class="smpl">Content-Encoding</a> = *( "," OWS ) content-coding *( OWS "," [ OWS
     
    46524652<a href="#header.max-forwards" class="smpl">Max-Forwards</a> = 1*DIGIT
    46534653
    4654 <a href="#imported.abnf" class="smpl">OWS</a> = &lt;OWS, defined in [Part1], Section 3.2.3&gt;
    4655 
    4656 <a href="#imported.abnf" class="smpl">RWS</a> = &lt;RWS, defined in [Part1], Section 3.2.3&gt;
     4654<a href="#imported.abnf" class="smpl">OWS</a> = &lt;OWS, defined in [RFC7230], Section 3.2.3&gt;
     4655
     4656<a href="#imported.abnf" class="smpl">RWS</a> = &lt;RWS, defined in [RFC7230], Section 3.2.3&gt;
    46574657<a href="#header.referer" class="smpl">Referer</a> = absolute-URI / partial-URI
    46584658<a href="#header.retry-after" class="smpl">Retry-After</a> = HTTP-date / delay-seconds
     
    46604660<a href="#header.server" class="smpl">Server</a> = product *( RWS ( product / comment ) )
    46614661
    4662 <a href="#imported.abnf" class="smpl">URI-reference</a> = &lt;URI-reference, defined in [Part1], Section 2.7&gt;
     4662<a href="#imported.abnf" class="smpl">URI-reference</a> = &lt;URI-reference, defined in [RFC7230], Section 2.7&gt;
    46634663<a href="#header.user-agent" class="smpl">User-Agent</a> = product *( RWS ( product / comment ) )
    46644664
     
    46664666 ) )
    46674667
    4668 <a href="#imported.abnf" class="smpl">absolute-URI</a> = &lt;absolute-URI, defined in [Part1], Section 2.7&gt;
     4668<a href="#imported.abnf" class="smpl">absolute-URI</a> = &lt;absolute-URI, defined in [RFC7230], Section 2.7&gt;
    46694669<a href="#header.accept" class="smpl">accept-ext</a> = OWS ";" OWS token [ "=" ( token / quoted-string ) ]
    46704670<a href="#header.accept" class="smpl">accept-params</a> = weight *accept-ext
     
    46734673<a href="#charset" class="smpl">charset</a> = token
    46744674<a href="#header.accept-encoding" class="smpl">codings</a> = content-coding / "identity" / "*"
    4675 <a href="#imported.abnf" class="smpl">comment</a> = &lt;comment, defined in [Part1], Section 3.2.6&gt;
     4675<a href="#imported.abnf" class="smpl">comment</a> = &lt;comment, defined in [RFC7230], Section 3.2.6&gt;
    46764676<a href="#content.codings" class="smpl">content-coding</a> = token
    46774677
     
    46964696<a href="#rule.delay-seconds" class="smpl">delay-seconds</a> = 1*DIGIT
    46974697
    4698 <a href="#imported.abnf" class="smpl">field-name</a> = &lt;comment, defined in [Part1], Section 3.2&gt;
     4698<a href="#imported.abnf" class="smpl">field-name</a> = &lt;comment, defined in [RFC7230], Section 3.2&gt;
    46994699
    47004700<a href="#preferred.date.format" class="smpl">hour</a> = 2DIGIT
     
    47254725
    47264726<a href="#rule.parameter" class="smpl">parameter</a> = token "=" ( token / quoted-string )
    4727 <a href="#imported.abnf" class="smpl">partial-URI</a> = &lt;partial-URI, defined in [Part1], Section 2.7&gt;
     4727<a href="#imported.abnf" class="smpl">partial-URI</a> = &lt;partial-URI, defined in [RFC7230], Section 2.7&gt;
    47284728<a href="#header.user-agent" class="smpl">product</a> = token [ "/" product-version ]
    47294729<a href="#header.user-agent" class="smpl">product-version</a> = token
    47304730
    4731 <a href="#imported.abnf" class="smpl">quoted-string</a> = &lt;quoted-string, defined in [Part1], Section 3.2.6&gt;
     4731<a href="#imported.abnf" class="smpl">quoted-string</a> = &lt;quoted-string, defined in [RFC7230], Section 3.2.6&gt;
    47324732<a href="#quality.values" class="smpl">qvalue</a> = ( "0" [ "." *3DIGIT ] ) / ( "1" [ "." *3"0" ] )
    47334733
     
    47384738
    47394739<a href="#preferred.date.format" class="smpl">time-of-day</a> = hour ":" minute ":" second
    4740 <a href="#imported.abnf" class="smpl">token</a> = &lt;token, defined in [Part1], Section 3.2.6&gt;
     4740<a href="#imported.abnf" class="smpl">token</a> = &lt;token, defined in [RFC7230], Section 3.2.6&gt;
    47414741<a href="#media.type" class="smpl">type</a> = token
    47424742
     
    49834983            </li>
    49844984            <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul>
    4985                   <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">3.3</a>, <a href="#rfc.xref.Part1.16">4.3.6</a>, <a href="#rfc.xref.Part1.17">4.3.7</a>, <a href="#rfc.xref.Part1.18">4.3.8</a>, <a href="#rfc.xref.Part1.19">4.3.8</a>, <a href="#rfc.xref.Part1.20">5.1</a>, <a href="#rfc.xref.Part1.21">5.1</a>, <a href="#rfc.xref.Part1.22">5.1.1</a>, <a href="#rfc.xref.Part1.23">5.5.3</a>, <a href="#rfc.xref.Part1.24">6.2.2</a>, <a href="#rfc.xref.Part1.25">6.3.4</a>, <a href="#rfc.xref.Part1.26">6.5.7</a>, <a href="#rfc.xref.Part1.27">6.5.10</a>, <a href="#rfc.xref.Part1.28">6.5.12</a>, <a href="#rfc.xref.Part1.29">6.5.15</a>, <a href="#rfc.xref.Part1.30">6.6.6</a>, <a href="#rfc.xref.Part1.31">7.4.2</a>, <a href="#rfc.xref.Part1.32">8.1.2</a>, <a href="#rfc.xref.Part1.33">8.3.1</a>, <a href="#rfc.xref.Part1.34">8.3.1</a>, <a href="#rfc.xref.Part1.35">8.3.1</a>, <a href="#rfc.xref.Part1.36">8.3.1</a>, <a href="#rfc.xref.Part1.37">8.3.1</a>, <a href="#rfc.xref.Part1.38">8.3.1</a>, <a href="#rfc.xref.Part1.39">8.3.1</a>, <a href="#rfc.xref.Part1.40">8.4</a>, <a href="#rfc.xref.Part1.41">8.4.1</a>, <a href="#rfc.xref.Part1.42">8.4.1</a>, <a href="#rfc.xref.Part1.43">9</a>, <a href="#rfc.xref.Part1.44">9.6</a>, <a href="#rfc.xref.Part1.45">10</a>, <a href="#Part1"><b>11.1</b></a>, <a href="#rfc.xref.Part1.46">B</a>, <a href="#rfc.xref.Part1.47">C</a>, <a href="#rfc.xref.Part1.48">C</a>, <a href="#rfc.xref.Part1.49">C</a>, <a href="#rfc.xref.Part1.50">C</a>, <a href="#rfc.xref.Part1.51">C</a>, <a href="#rfc.xref.Part1.52">C</a>, <a href="#rfc.xref.Part1.53">C</a>, <a href="#rfc.xref.Part1.54">C</a>, <a href="#rfc.xref.Part1.55">C</a>, <a href="#rfc.xref.Part1.56">C</a>, <a href="#rfc.xref.Part1.57">C</a>, <a href="#rfc.xref.Part1.58">D</a><ul>
    4986                         <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.58">D</a></li>
    4987                         <li><em>Section 2.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.2">1.1</a></li>
    4988                         <li><em>Section 2.6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.30">6.6.6</a></li>
    4989                         <li><em>Section 2.7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.4">2</a>, <a href="#rfc.xref.Part1.51">C</a>, <a href="#rfc.xref.Part1.52">C</a>, <a href="#rfc.xref.Part1.55">C</a></li>
    4990                         <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.23">5.5.3</a>, <a href="#rfc.xref.Part1.31">7.4.2</a>, <a href="#rfc.xref.Part1.33">8.3.1</a>, <a href="#rfc.xref.Part1.37">8.3.1</a>, <a href="#rfc.xref.Part1.54">C</a></li>
    4991                         <li><em>Section 3.2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.48">C</a>, <a href="#rfc.xref.Part1.49">C</a>, <a href="#rfc.xref.Part1.50">C</a></li>
    4992                         <li><em>Section 3.2.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.35">8.3.1</a></li>
    4993                         <li><em>Section 3.2.6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.36">8.3.1</a>, <a href="#rfc.xref.Part1.53">C</a>, <a href="#rfc.xref.Part1.56">C</a>, <a href="#rfc.xref.Part1.57">C</a></li>
    4994                         <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.15">3.3</a></li>
    4995                         <li><em>Section 3.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.32">8.1.2</a></li>
    4996                         <li><em>Section 3.3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.13">3.3</a>, <a href="#rfc.xref.Part1.27">6.5.10</a></li>
    4997                         <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.41">8.4.1</a></li>
    4998                         <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.39">8.3.1</a></li>
    4999                         <li><em>Section 4.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.7">3.1.2.1</a></li>
    5000                         <li><em>Section 4.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.40">8.4</a>, <a href="#rfc.xref.Part1.42">8.4.1</a></li>
    5001                         <li><em>Section 4.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.8">3.1.2.1</a></li>
    5002                         <li><em>Section 4.2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.9">3.1.2.1</a></li>
    5003                         <li><em>Section 4.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.21">5.1</a></li>
    5004                         <li><em>Section 4.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.14">3.3</a></li>
    5005                         <li><em>Section 5.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.5">2</a>, <a href="#rfc.xref.Part1.16">4.3.6</a>, <a href="#rfc.xref.Part1.17">4.3.7</a>, <a href="#rfc.xref.Part1.28">6.5.12</a></li>
    5006                         <li><em>Section 5.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.20">5.1</a></li>
    5007                         <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></li>
    5008                         <li><em>Section 5.7.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.19">4.3.8</a>, <a href="#rfc.xref.Part1.44">9.6</a></li>
    5009                         <li><em>Section 5.7.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.25">6.3.4</a></li>
    5010                         <li><em>Section 6.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.26">6.5.7</a>, <a href="#rfc.xref.Part1.38">8.3.1</a></li>
    5011                         <li><em>Section 6.6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.22">5.1.1</a></li>
    5012                         <li><em>Section 6.7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.24">6.2.2</a>, <a href="#rfc.xref.Part1.29">6.5.15</a></li>
    5013                         <li><em>Section 7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.3">1.2</a>, <a href="#rfc.xref.Part1.34">8.3.1</a></li>
    5014                         <li><em>Section 8.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.18">4.3.8</a></li>
    5015                         <li><em>Section 9</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.43">9</a></li>
    5016                         <li><em>Section 10</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.45">10</a></li>
    5017                      </ul>
    5018                   </li>
    5019                   <li><em>Part4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">3</a>, <a href="#rfc.xref.Part4.2">4.1</a>, <a href="#rfc.xref.Part4.3">5.2</a>, <a href="#rfc.xref.Part4.4">5.2</a>, <a href="#rfc.xref.Part4.5">5.2</a>, <a href="#rfc.xref.Part4.6">5.2</a>, <a href="#rfc.xref.Part4.7">5.2</a>, <a href="#rfc.xref.Part4.8">5.2</a>, <a href="#rfc.xref.Part4.9">6.1</a>, <a href="#rfc.xref.Part4.10">6.1</a>, <a href="#rfc.xref.Part4.11">6.1</a>, <a href="#rfc.xref.Part4.12">7.2</a>, <a href="#rfc.xref.Part4.13">7.2</a>, <a href="#rfc.xref.Part4.14">7.2</a>, <a href="#Part4"><b>11.1</b></a><ul>
    5020                         <li><em>Section 2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.14">7.2</a></li>
    5021                         <li><em>Section 2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.13">7.2</a></li>
    5022                         <li><em>Section 3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.5">5.2</a></li>
    5023                         <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.6">5.2</a></li>
    5024                         <li><em>Section 3.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.7">5.2</a></li>
    5025                         <li><em>Section 3.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.8">5.2</a></li>
    5026                         <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.9">6.1</a></li>
    5027                         <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.10">6.1</a></li>
    5028                         <li><em>Section 4.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.11">6.1</a></li>
    5029                         <li><em>Section 5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.4">5.2</a></li>
    5030                      </ul>
    5031                   </li>
    5032                   <li><em>Part5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.1">3.1.1.4</a>, <a href="#rfc.xref.Part5.2">3.3</a>, <a href="#rfc.xref.Part5.3">4.3.1</a>, <a href="#rfc.xref.Part5.4">4.3.4</a>, <a href="#rfc.xref.Part5.5">5.1</a>, <a href="#rfc.xref.Part5.6">5.2</a>, <a href="#rfc.xref.Part5.7">6.1</a>, <a href="#rfc.xref.Part5.8">6.1</a>, <a href="#rfc.xref.Part5.9">6.1</a>, <a href="#rfc.xref.Part5.10">7.4</a>, <a href="#rfc.xref.Part5.11">8.1.2</a>, <a href="#Part5"><b>11.1</b></a>, <a href="#rfc.xref.Part5.12">A.6</a><ul>
    5033                         <li><em>Section 2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.10">7.4</a></li>
    5034                         <li><em>Section 3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.5">5.1</a></li>
    5035                         <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.6">5.2</a></li>
    5036                         <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.7">6.1</a></li>
    5037                         <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.8">6.1</a></li>
    5038                         <li><em>Section 4.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.2">3.3</a>, <a href="#rfc.xref.Part5.4">4.3.4</a></li>
    5039                         <li><em>Section 4.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.9">6.1</a></li>
    5040                         <li><em>Appendix A</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.12">A.6</a></li>
    5041                      </ul>
    5042                   </li>
    5043                   <li><em>Part6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.1">4.2.3</a>, <a href="#rfc.xref.Part6.2">4.3.1</a>, <a href="#rfc.xref.Part6.3">4.3.2</a>, <a href="#rfc.xref.Part6.4">4.3.2</a>, <a href="#rfc.xref.Part6.5">4.3.3</a>, <a href="#rfc.xref.Part6.6">4.3.4</a>, <a href="#rfc.xref.Part6.7">4.3.5</a>, <a href="#rfc.xref.Part6.8">5.1</a>, <a href="#rfc.xref.Part6.9">5.1</a>, <a href="#rfc.xref.Part6.10">6.1</a>, <a href="#rfc.xref.Part6.11">6.3.1</a>, <a href="#rfc.xref.Part6.12">6.3.4</a>, <a href="#rfc.xref.Part6.13">6.3.4</a>, <a href="#rfc.xref.Part6.14">6.3.5</a>, <a href="#rfc.xref.Part6.15">6.4.1</a>, <a href="#rfc.xref.Part6.16">6.4.2</a>, <a href="#rfc.xref.Part6.17">6.5.4</a>, <a href="#rfc.xref.Part6.18">6.5.5</a>, <a href="#rfc.xref.Part6.19">6.5.9</a>, <a href="#rfc.xref.Part6.20">6.5.12</a>, <a href="#rfc.xref.Part6.21">6.6.2</a>, <a href="#rfc.xref.Part6.22">7.1</a>, <a href="#rfc.xref.Part6.23">7.1</a>, <a href="#rfc.xref.Part6.24">7.1</a>, <a href="#rfc.xref.Part6.25">7.1</a>, <a href="#rfc.xref.Part6.26">7.1.4</a>, <a href="#rfc.xref.Part6.27">7.1.4</a>, <a href="#rfc.xref.Part6.28">8.2.2</a>, <a href="#Part6"><b>11.1</b></a><ul>
    5044                         <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.26">7.1.4</a></li>
    5045                         <li><em>Section 4.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.5">4.3.3</a></li>
    5046                         <li><em>Section 4.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.11">6.3.1</a>, <a href="#rfc.xref.Part6.13">6.3.4</a>, <a href="#rfc.xref.Part6.14">6.3.5</a>, <a href="#rfc.xref.Part6.15">6.4.1</a>, <a href="#rfc.xref.Part6.16">6.4.2</a>, <a href="#rfc.xref.Part6.17">6.5.4</a>, <a href="#rfc.xref.Part6.18">6.5.5</a>, <a href="#rfc.xref.Part6.19">6.5.9</a>, <a href="#rfc.xref.Part6.20">6.5.12</a>, <a href="#rfc.xref.Part6.21">6.6.2</a></li>
    5047                         <li><em>Section 4.3.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.4">4.3.2</a></li>
    5048                         <li><em>Section 4.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.6">4.3.4</a>, <a href="#rfc.xref.Part6.7">4.3.5</a></li>
    5049                         <li><em>Section 5.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.22">7.1</a></li>
    5050                         <li><em>Section 5.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.2">4.3.1</a>, <a href="#rfc.xref.Part6.3">4.3.2</a>, <a href="#rfc.xref.Part6.8">5.1</a>, <a href="#rfc.xref.Part6.23">7.1</a>, <a href="#rfc.xref.Part6.27">7.1.4</a></li>
    5051                         <li><em>Section 5.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.24">7.1</a></li>
    5052                         <li><em>Section 5.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.9">5.1</a></li>
    5053                         <li><em>Section 5.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.12">6.3.4</a>, <a href="#rfc.xref.Part6.25">7.1</a></li>
    5054                      </ul>
    5055                   </li>
    5056                   <li><em>Part7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.1">4.3.8</a>, <a href="#rfc.xref.Part7.2">5.4</a>, <a href="#rfc.xref.Part7.3">5.4</a>, <a href="#rfc.xref.Part7.4">5.4</a>, <a href="#rfc.xref.Part7.5">6.1</a>, <a href="#rfc.xref.Part7.6">6.1</a>, <a href="#rfc.xref.Part7.7">6.1</a>, <a href="#rfc.xref.Part7.8">7.1.4</a>, <a href="#rfc.xref.Part7.9">7.3</a>, <a href="#rfc.xref.Part7.10">7.3</a>, <a href="#Part7"><b>11.1</b></a><ul>
    5057                         <li><em>Section 3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.5">6.1</a></li>
    5058                         <li><em>Section 3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.6">6.1</a></li>
    5059                         <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.7">6.1</a></li>
    5060                         <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.9">7.3</a></li>
    5061                         <li><em>Section 4.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.3">5.4</a>, <a href="#rfc.xref.Part7.8">7.1.4</a></li>
    5062                         <li><em>Section 4.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.10">7.3</a></li>
    5063                         <li><em>Section 4.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.4">5.4</a></li>
    5064                      </ul>
    5065                   </li>
    50664985                  <li>payload&nbsp;&nbsp;<a href="#rfc.iref.p.1">3.3</a></li>
    50674986                  <li>POST method&nbsp;&nbsp;<a href="#rfc.xref.POST.1">3.1.4.2</a>, <a href="#rfc.xref.POST.2">3.3</a>, <a href="#rfc.xref.POST.3">4.1</a>, <a href="#rfc.iref.p.2"><b>4.3.3</b></a>, <a href="#rfc.xref.POST.4">8.1.3</a></li>
     
    51475066                  <li><em>RFC6266</em>&nbsp;&nbsp;<a href="#RFC6266"><b>11.2</b></a>, <a href="#rfc.xref.RFC6266.1">B</a></li>
    51485067                  <li><em>RFC6365</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC6365.1">1.2</a>, <a href="#rfc.xref.RFC6365.2">3.1.1.2</a>, <a href="#RFC6365"><b>11.1</b></a></li>
     5068                  <li><em>RFC7230</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.1">1</a>, <a href="#rfc.xref.RFC7230.2">1.1</a>, <a href="#rfc.xref.RFC7230.3">1.2</a>, <a href="#rfc.xref.RFC7230.4">2</a>, <a href="#rfc.xref.RFC7230.5">2</a>, <a href="#rfc.xref.RFC7230.6">2</a>, <a href="#rfc.xref.RFC7230.7">3.1.2.1</a>, <a href="#rfc.xref.RFC7230.8">3.1.2.1</a>, <a href="#rfc.xref.RFC7230.9">3.1.2.1</a>, <a href="#rfc.xref.RFC7230.10">3.1.2.2</a>, <a href="#rfc.xref.RFC7230.11">3.1.4.1</a>, <a href="#rfc.xref.RFC7230.12">3.1.4.2</a>, <a href="#rfc.xref.RFC7230.13">3.3</a>, <a href="#rfc.xref.RFC7230.14">3.3</a>, <a href="#rfc.xref.RFC7230.15">3.3</a>, <a href="#rfc.xref.RFC7230.16">4.3.6</a>, <a href="#rfc.xref.RFC7230.17">4.3.7</a>, <a href="#rfc.xref.RFC7230.18">4.3.8</a>, <a href="#rfc.xref.RFC7230.19">4.3.8</a>, <a href="#rfc.xref.RFC7230.20">5.1</a>, <a href="#rfc.xref.RFC7230.21">5.1</a>, <a href="#rfc.xref.RFC7230.22">5.1.1</a>, <a href="#rfc.xref.RFC7230.23">5.5.3</a>, <a href="#rfc.xref.RFC7230.24">6.2.2</a>, <a href="#rfc.xref.RFC7230.25">6.3.4</a>, <a href="#rfc.xref.RFC7230.26">6.5.7</a>, <a href="#rfc.xref.RFC7230.27">6.5.10</a>, <a href="#rfc.xref.RFC7230.28">6.5.12</a>, <a href="#rfc.xref.RFC7230.29">6.5.15</a>, <a href="#rfc.xref.RFC7230.30">6.6.6</a>, <a href="#rfc.xref.RFC7230.31">7.4.2</a>, <a href="#rfc.xref.RFC7230.32">8.1.2</a>, <a href="#rfc.xref.RFC7230.33">8.3.1</a>, <a href="#rfc.xref.RFC7230.34">8.3.1</a>, <a href="#rfc.xref.RFC7230.35">8.3.1</a>, <a href="#rfc.xref.RFC7230.36">8.3.1</a>, <a href="#rfc.xref.RFC7230.37">8.3.1</a>, <a href="#rfc.xref.RFC7230.38">8.3.1</a>, <a href="#rfc.xref.RFC7230.39">8.3.1</a>, <a href="#rfc.xref.RFC7230.40">8.4</a>, <a href="#rfc.xref.RFC7230.41">8.4.1</a>, <a href="#rfc.xref.RFC7230.42">8.4.1</a>, <a href="#rfc.xref.RFC7230.43">9</a>, <a href="#rfc.xref.RFC7230.44">9.6</a>, <a href="#rfc.xref.RFC7230.45">10</a>, <a href="#RFC7230"><b>11.1</b></a>, <a href="#rfc.xref.RFC7230.46">B</a>, <a href="#rfc.xref.RFC7230.47">C</a>, <a href="#rfc.xref.RFC7230.48">C</a>, <a href="#rfc.xref.RFC7230.49">C</a>, <a href="#rfc.xref.RFC7230.50">C</a>, <a href="#rfc.xref.RFC7230.51">C</a>, <a href="#rfc.xref.RFC7230.52">C</a>, <a href="#rfc.xref.RFC7230.53">C</a>, <a href="#rfc.xref.RFC7230.54">C</a>, <a href="#rfc.xref.RFC7230.55">C</a>, <a href="#rfc.xref.RFC7230.56">C</a>, <a href="#rfc.xref.RFC7230.57">C</a>, <a href="#rfc.xref.RFC7230.58">D</a><ul>
     5069                        <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.58">D</a></li>
     5070                        <li><em>Section 2.5</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.2">1.1</a></li>
     5071                        <li><em>Section 2.6</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.30">6.6.6</a></li>
     5072                        <li><em>Section 2.7</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.4">2</a>, <a href="#rfc.xref.RFC7230.51">C</a>, <a href="#rfc.xref.RFC7230.52">C</a>, <a href="#rfc.xref.RFC7230.55">C</a></li>
     5073                        <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.23">5.5.3</a>, <a href="#rfc.xref.RFC7230.31">7.4.2</a>, <a href="#rfc.xref.RFC7230.33">8.3.1</a>, <a href="#rfc.xref.RFC7230.37">8.3.1</a>, <a href="#rfc.xref.RFC7230.54">C</a></li>
     5074                        <li><em>Section 3.2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.48">C</a>, <a href="#rfc.xref.RFC7230.49">C</a>, <a href="#rfc.xref.RFC7230.50">C</a></li>
     5075                        <li><em>Section 3.2.4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.35">8.3.1</a></li>
     5076                        <li><em>Section 3.2.6</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.36">8.3.1</a>, <a href="#rfc.xref.RFC7230.53">C</a>, <a href="#rfc.xref.RFC7230.56">C</a>, <a href="#rfc.xref.RFC7230.57">C</a></li>
     5077                        <li><em>Section 3.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.10">3.1.2.2</a>, <a href="#rfc.xref.RFC7230.15">3.3</a></li>
     5078                        <li><em>Section 3.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.32">8.1.2</a></li>
     5079                        <li><em>Section 3.3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.13">3.3</a>, <a href="#rfc.xref.RFC7230.27">6.5.10</a></li>
     5080                        <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.41">8.4.1</a></li>
     5081                        <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.39">8.3.1</a></li>
     5082                        <li><em>Section 4.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.7">3.1.2.1</a></li>
     5083                        <li><em>Section 4.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.40">8.4</a>, <a href="#rfc.xref.RFC7230.42">8.4.1</a></li>
     5084                        <li><em>Section 4.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.8">3.1.2.1</a></li>
     5085                        <li><em>Section 4.2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.9">3.1.2.1</a></li>
     5086                        <li><em>Section 4.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.21">5.1</a></li>
     5087                        <li><em>Section 4.4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.14">3.3</a></li>
     5088                        <li><em>Section 5.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.5">2</a>, <a href="#rfc.xref.RFC7230.16">4.3.6</a>, <a href="#rfc.xref.RFC7230.17">4.3.7</a>, <a href="#rfc.xref.RFC7230.28">6.5.12</a></li>
     5089                        <li><em>Section 5.4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.20">5.1</a></li>
     5090                        <li><em>Section 5.5</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.6">2</a>, <a href="#rfc.xref.RFC7230.11">3.1.4.1</a>, <a href="#rfc.xref.RFC7230.12">3.1.4.2</a></li>
     5091                        <li><em>Section 5.7.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.19">4.3.8</a>, <a href="#rfc.xref.RFC7230.44">9.6</a></li>
     5092                        <li><em>Section 5.7.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.25">6.3.4</a></li>
     5093                        <li><em>Section 6.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.26">6.5.7</a>, <a href="#rfc.xref.RFC7230.38">8.3.1</a></li>
     5094                        <li><em>Section 6.6</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.22">5.1.1</a></li>
     5095                        <li><em>Section 6.7</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.24">6.2.2</a>, <a href="#rfc.xref.RFC7230.29">6.5.15</a></li>
     5096                        <li><em>Section 7</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.3">1.2</a>, <a href="#rfc.xref.RFC7230.34">8.3.1</a></li>
     5097                        <li><em>Section 8.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.18">4.3.8</a></li>
     5098                        <li><em>Section 9</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.43">9</a></li>
     5099                        <li><em>Section 10</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.45">10</a></li>
     5100                     </ul>
     5101                  </li>
     5102                  <li><em>RFC7232</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7232.1">3</a>, <a href="#rfc.xref.RFC7232.2">4.1</a>, <a href="#rfc.xref.RFC7232.3">5.2</a>, <a href="#rfc.xref.RFC7232.4">5.2</a>, <a href="#rfc.xref.RFC7232.5">5.2</a>, <a href="#rfc.xref.RFC7232.6">5.2</a>, <a href="#rfc.xref.RFC7232.7">5.2</a>, <a href="#rfc.xref.RFC7232.8">5.2</a>, <a href="#rfc.xref.RFC7232.9">6.1</a>, <a href="#rfc.xref.RFC7232.10">6.1</a>, <a href="#rfc.xref.RFC7232.11">6.1</a>, <a href="#rfc.xref.RFC7232.12">7.2</a>, <a href="#rfc.xref.RFC7232.13">7.2</a>, <a href="#rfc.xref.RFC7232.14">7.2</a>, <a href="#RFC7232"><b>11.1</b></a><ul>
     5103                        <li><em>Section 2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7232.14">7.2</a></li>
     5104                        <li><em>Section 2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7232.13">7.2</a></li>
     5105                        <li><em>Section 3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7232.5">5.2</a></li>
     5106                        <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7232.6">5.2</a></li>
     5107                        <li><em>Section 3.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7232.7">5.2</a></li>
     5108                        <li><em>Section 3.4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7232.8">5.2</a></li>
     5109                        <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7232.9">6.1</a></li>
     5110                        <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7232.10">6.1</a></li>
     5111                        <li><em>Section 4.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7232.11">6.1</a></li>
     5112                        <li><em>Section 5</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7232.4">5.2</a></li>
     5113                     </ul>
     5114                  </li>
     5115                  <li><em>RFC7233</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7233.1">3.1.1.4</a>, <a href="#rfc.xref.RFC7233.2">3.3</a>, <a href="#rfc.xref.RFC7233.3">4.3.1</a>, <a href="#rfc.xref.RFC7233.4">4.3.4</a>, <a href="#rfc.xref.RFC7233.5">5.1</a>, <a href="#rfc.xref.RFC7233.6">5.2</a>, <a href="#rfc.xref.RFC7233.7">6.1</a>, <a href="#rfc.xref.RFC7233.8">6.1</a>, <a href="#rfc.xref.RFC7233.9">6.1</a>, <a href="#rfc.xref.RFC7233.10">7.4</a>, <a href="#rfc.xref.RFC7233.11">8.1.2</a>, <a href="#RFC7233"><b>11.1</b></a>, <a href="#rfc.xref.RFC7233.12">A.6</a><ul>
     5116                        <li><em>Section 2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7233.10">7.4</a></li>
     5117                        <li><em>Section 3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7233.5">5.1</a></li>
     5118                        <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7233.6">5.2</a></li>
     5119                        <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7233.7">6.1</a></li>
     5120                        <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7233.8">6.1</a></li>
     5121                        <li><em>Section 4.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7233.2">3.3</a>, <a href="#rfc.xref.RFC7233.4">4.3.4</a></li>
     5122                        <li><em>Section 4.4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7233.9">6.1</a></li>
     5123                        <li><em>Appendix A</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7233.12">A.6</a></li>
     5124                     </ul>
     5125                  </li>
     5126                  <li><em>RFC7234</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7234.1">4.2.3</a>, <a href="#rfc.xref.RFC7234.2">4.3.1</a>, <a href="#rfc.xref.RFC7234.3">4.3.2</a>, <a href="#rfc.xref.RFC7234.4">4.3.2</a>, <a href="#rfc.xref.RFC7234.5">4.3.3</a>, <a href="#rfc.xref.RFC7234.6">4.3.4</a>, <a href="#rfc.xref.RFC7234.7">4.3.5</a>, <a href="#rfc.xref.RFC7234.8">5.1</a>, <a href="#rfc.xref.RFC7234.9">5.1</a>, <a href="#rfc.xref.RFC7234.10">6.1</a>, <a href="#rfc.xref.RFC7234.11">6.3.1</a>, <a href="#rfc.xref.RFC7234.12">6.3.4</a>, <a href="#rfc.xref.RFC7234.13">6.3.4</a>, <a href="#rfc.xref.RFC7234.14">6.3.5</a>, <a href="#rfc.xref.RFC7234.15">6.4.1</a>, <a href="#rfc.xref.RFC7234.16">6.4.2</a>, <a href="#rfc.xref.RFC7234.17">6.5.4</a>, <a href="#rfc.xref.RFC7234.18">6.5.5</a>, <a href="#rfc.xref.RFC7234.19">6.5.9</a>, <a href="#rfc.xref.RFC7234.20">6.5.12</a>, <a href="#rfc.xref.RFC7234.21">6.6.2</a>, <a href="#rfc.xref.RFC7234.22">7.1</a>, <a href="#rfc.xref.RFC7234.23">7.1</a>, <a href="#rfc.xref.RFC7234.24">7.1</a>, <a href="#rfc.xref.RFC7234.25">7.1</a>, <a href="#rfc.xref.RFC7234.26">7.1.4</a>, <a href="#rfc.xref.RFC7234.27">7.1.4</a>, <a href="#rfc.xref.RFC7234.28">8.2.2</a>, <a href="#RFC7234"><b>11.1</b></a><ul>
     5127                        <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7234.26">7.1.4</a></li>
     5128                        <li><em>Section 4.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7234.5">4.3.3</a></li>
     5129                        <li><em>Section 4.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7234.11">6.3.1</a>, <a href="#rfc.xref.RFC7234.13">6.3.4</a>, <a href="#rfc.xref.RFC7234.14">6.3.5</a>, <a href="#rfc.xref.RFC7234.15">6.4.1</a>, <a href="#rfc.xref.RFC7234.16">6.4.2</a>, <a href="#rfc.xref.RFC7234.17">6.5.4</a>, <a href="#rfc.xref.RFC7234.18">6.5.5</a>, <a href="#rfc.xref.RFC7234.19">6.5.9</a>, <a href="#rfc.xref.RFC7234.20">6.5.12</a>, <a href="#rfc.xref.RFC7234.21">6.6.2</a></li>
     5130                        <li><em>Section 4.3.5</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7234.4">4.3.2</a></li>
     5131                        <li><em>Section 4.4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7234.6">4.3.4</a>, <a href="#rfc.xref.RFC7234.7">4.3.5</a></li>
     5132                        <li><em>Section 5.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7234.22">7.1</a></li>
     5133                        <li><em>Section 5.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7234.2">4.3.1</a>, <a href="#rfc.xref.RFC7234.3">4.3.2</a>, <a href="#rfc.xref.RFC7234.8">5.1</a>, <a href="#rfc.xref.RFC7234.23">7.1</a>, <a href="#rfc.xref.RFC7234.27">7.1.4</a></li>
     5134                        <li><em>Section 5.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7234.24">7.1</a></li>
     5135                        <li><em>Section 5.4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7234.9">5.1</a></li>
     5136                        <li><em>Section 5.5</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7234.12">6.3.4</a>, <a href="#rfc.xref.RFC7234.25">7.1</a></li>
     5137                     </ul>
     5138                  </li>
     5139                  <li><em>RFC7235</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7235.1">4.3.8</a>, <a href="#rfc.xref.RFC7235.2">5.4</a>, <a href="#rfc.xref.RFC7235.3">5.4</a>, <a href="#rfc.xref.RFC7235.4">5.4</a>, <a href="#rfc.xref.RFC7235.5">6.1</a>, <a href="#rfc.xref.RFC7235.6">6.1</a>, <a href="#rfc.xref.RFC7235.7">6.1</a>, <a href="#rfc.xref.RFC7235.8">7.1.4</a>, <a href="#rfc.xref.RFC7235.9">7.3</a>, <a href="#rfc.xref.RFC7235.10">7.3</a>, <a href="#RFC7235"><b>11.1</b></a><ul>
     5140                        <li><em>Section 3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7235.5">6.1</a></li>
     5141                        <li><em>Section 3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7235.6">6.1</a></li>
     5142                        <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7235.7">6.1</a></li>
     5143                        <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7235.9">7.3</a></li>
     5144                        <li><em>Section 4.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7235.3">5.4</a>, <a href="#rfc.xref.RFC7235.8">7.1.4</a></li>
     5145                        <li><em>Section 4.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7235.10">7.3</a></li>
     5146                        <li><em>Section 4.4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7235.4">5.4</a></li>
     5147                     </ul>
     5148                  </li>
    51495149               </ul>
    51505150            </li>
Note: See TracChangeset for help on using the changeset viewer.