Ignore:
Timestamp:
Jul 27, 2009, 9:14:13 AM (11 years ago)
Author:
julian.reschke@…
Message:

re-generate HTML

File:
1 edited

Legend:

Unmodified
Added
Removed

  • draft-ietf-httpbis/latest/p1-messaging.html

    r628 r631  
    529529         </li>
    530530         <li class="tocline0">2.&nbsp;&nbsp;&nbsp;<a href="#architecture">HTTP architecture</a><ul class="toc">
    531                <li class="tocline1">2.1&nbsp;&nbsp;&nbsp;<a href="#intro.overall.operation">Overall Operation</a></li>
    532                <li class="tocline1">2.2&nbsp;&nbsp;&nbsp;<a href="#http.version">HTTP Version</a></li>
    533                <li class="tocline1">2.3&nbsp;&nbsp;&nbsp;<a href="#uri">Uniform Resource Identifiers</a><ul class="toc">
    534                      <li class="tocline1">2.3.1&nbsp;&nbsp;&nbsp;<a href="#http.uri">http URI scheme</a></li>
    535                      <li class="tocline1">2.3.2&nbsp;&nbsp;&nbsp;<a href="#https.uri">https URI scheme</a></li>
    536                      <li class="tocline1">2.3.3&nbsp;&nbsp;&nbsp;<a href="#uri.comparison">http and https URI Normalization and Comparison</a></li>
    537                      <li class="tocline1">2.3.4&nbsp;&nbsp;&nbsp;<a href="#scheme.aliases">Scheme aliases considered harmful</a></li>
     531               <li class="tocline1">2.1&nbsp;&nbsp;&nbsp;<a href="#operation">Client/Server Operation</a></li>
     532               <li class="tocline1">2.2&nbsp;&nbsp;&nbsp;<a href="#intermediaries">Intermediaries</a></li>
     533               <li class="tocline1">2.3&nbsp;&nbsp;&nbsp;<a href="#caches">Caches</a></li>
     534               <li class="tocline1">2.4&nbsp;&nbsp;&nbsp;<a href="#transport-independence">Transport Independence</a></li>
     535               <li class="tocline1">2.5&nbsp;&nbsp;&nbsp;<a href="#http.version">HTTP Version</a></li>
     536               <li class="tocline1">2.6&nbsp;&nbsp;&nbsp;<a href="#uri">Uniform Resource Identifiers</a><ul class="toc">
     537                     <li class="tocline1">2.6.1&nbsp;&nbsp;&nbsp;<a href="#http.uri">http URI scheme</a></li>
     538                     <li class="tocline1">2.6.2&nbsp;&nbsp;&nbsp;<a href="#https.uri">https URI scheme</a></li>
     539                     <li class="tocline1">2.6.3&nbsp;&nbsp;&nbsp;<a href="#uri.comparison">http and https URI Normalization and Comparison</a></li>
     540                     <li class="tocline1">2.6.4&nbsp;&nbsp;&nbsp;<a href="#scheme.aliases">Scheme aliases considered harmful</a></li>
    538541                  </ul>
    539542               </li>
    540                <li class="tocline1">2.4&nbsp;&nbsp;&nbsp;<a href="#http.proxy">Use of HTTP for proxy communication</a></li>
    541                <li class="tocline1">2.5&nbsp;&nbsp;&nbsp;<a href="#http.intercept">Interception of HTTP for access control</a></li>
    542                <li class="tocline1">2.6&nbsp;&nbsp;&nbsp;<a href="#http.others">Use of HTTP by other protocols</a></li>
    543                <li class="tocline1">2.7&nbsp;&nbsp;&nbsp;<a href="#http.media">Use of HTTP by media type specification</a></li>
     543               <li class="tocline1">2.7&nbsp;&nbsp;&nbsp;<a href="#http.proxy">Use of HTTP for proxy communication</a></li>
     544               <li class="tocline1">2.8&nbsp;&nbsp;&nbsp;<a href="#http.intercept">Interception of HTTP for access control</a></li>
     545               <li class="tocline1">2.9&nbsp;&nbsp;&nbsp;<a href="#http.others">Use of HTTP by other protocols</a></li>
     546               <li class="tocline1">2.10&nbsp;&nbsp;&nbsp;<a href="#http.media">Use of HTTP by media type specification</a></li>
    544547            </ul>
    545548         </li>
    … …  
    804807         hypertext system. Much of that architecture is reflected in the terminology and syntax productions used to define HTTP.
    805808      </p>
    806       <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;<a id="intro.overall.operation" href="#intro.overall.operation">Overall Operation</a></h2>
    807       <p id="rfc.section.2.1.p.1">HTTP is a request/response protocol. A client sends a request to the server in the form of a request method, URI, and protocol
    808          version, followed by a MIME-like message containing request modifiers, client information, and possible body content over
    809          a connection with a server. The server responds with a status line, including the message's protocol version and a success
    810          or error code, followed by a MIME-like message containing server information, entity metadata, and possible entity-body content.
    811       </p>
    812       <p id="rfc.section.2.1.p.2">Most HTTP communication is initiated by a user agent and consists of a request to be applied to a resource via the HTTP interface
    813          provided by some origin server. In the simplest case, this may be accomplished via a single connection (v) between the user
    814          agent (UA) and the origin server (O).
     809      <div id="rfc.iref.c.1"></div>
     810      <div id="rfc.iref.s.1"></div>
     811      <div id="rfc.iref.c.2"></div>
     812      <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;<a id="operation" href="#operation">Client/Server Operation</a></h2>
     813      <p id="rfc.section.2.1.p.1">HTTP is a request/response protocol that operates by exchanging messages across a reliable transport or session-layer connection.
     814         An HTTP client is a program that establishes a connection to a server for the purpose of sending one or more HTTP requests.
     815         An HTTP server is a program that accepts connections in order to service HTTP requests by sending HTTP responses.
     816      </p>
     817      <div id="rfc.iref.u.1"></div>
     818      <div id="rfc.iref.o.1"></div>
     819      <p id="rfc.section.2.1.p.2">Note that the terms "client" and "server" refer only to the roles that these programs perform for a particular connection.
     820         The same program may act as a client on some connections and a server on others. We use the term "user agent" to refer to
     821         the program that initiates a request, such as a WWW browser, editor, or spider (web-traversing robot), and the term "origin
     822         server" to refer to the program that can originate authoritative responses to a request.
     823      </p>
     824      <p id="rfc.section.2.1.p.3">Most HTTP communication consists of a retrieval request (GET) for a representation of some resource identified by a URI. In
     825         the simplest case, this may be accomplished via a single connection (v) between the user agent (UA) and the origin server
     826         (O).
    815827      </p>
    816828      <div id="rfc.figure.u.12"></div><pre class="drawing">       request chain ------------------------&gt;
    817829    UA -------------------v------------------- O
    818830       &lt;----------------------- response chain
    819 </pre><p id="rfc.section.2.1.p.4">A more complicated situation occurs when one or more intermediaries are present in the request/response chain. There are three
    820          common forms of intermediary: proxy, gateway, and tunnel. A proxy is a forwarding agent, receiving requests for a URI in its
    821          absolute form, rewriting all or part of the message, and forwarding the reformatted request toward the server identified by
    822          the URI. A gateway is a receiving agent, acting as a layer above some other server(s) and, if necessary, translating the requests
    823          to the underlying server's protocol. A tunnel acts as a relay point between two connections without changing the messages;
    824          tunnels are used when the communication needs to pass through an intermediary (such as a firewall) even when the intermediary
    825          cannot understand the contents of the messages.
    826       </p>
    827       <div id="rfc.figure.u.13"></div><pre class="drawing">       request chain --------------------------------------&gt;
     831</pre><div id="rfc.iref.m.1"></div>
     832      <div id="rfc.iref.r.1"></div>
     833      <div id="rfc.iref.r.2"></div>
     834      <p id="rfc.section.2.1.p.5">A client sends an HTTP request to the server in the form of a request message (<a href="#request" title="Request">Section&nbsp;4</a>), beginning with a method, URI, and protocol version, followed by MIME-like header fields containing request modifiers, client
     835         information, and payload metadata, an empty line, and finally the payload body (if any). The server response (<a href="#response" title="Response">Section&nbsp;5</a>) begins with a status line, including the protocol version, a success or error code, and textual reason phrase, followed
     836         by MIME-like header fields containing server information, resource metadata, payload metadata, an empty line, and finally
     837         the payload body (if any).
     838      </p>
     839      <div id="rfc.figure.u.13"></div>
     840      <p>The following example illustrates a typical message exchange for a GET request on the URI "http://www.example.com/hello.txt":</p><pre class="drawing">client request:
     841
     842  GET /hello.txt HTTP/1.1
     843  User-Agent: curl/7.16.3 libcurl/7.16.3 OpenSSL/0.9.7l zlib/1.2.3
     844  Host: www.example.com
     845  Accept: */*
     846
     847server response:
     848
     849  HTTP/1.1 200 OK
     850  Date: Mon, 27 Jul 2009 12:28:53 GMT
     851  Server: Apache
     852  Last-Modified: Wed, 22 Jul 2009 19:15:56 GMT
     853  ETag: "34aa387-d-1568eb00"
     854  Accept-Ranges: bytes
     855  Content-Length: 13
     856  Vary: Accept-Encoding
     857  Content-Type: text/plain
     858 
     859  Hello World!
     860</pre><h2 id="rfc.section.2.2"><a href="#rfc.section.2.2">2.2</a>&nbsp;<a id="intermediaries" href="#intermediaries">Intermediaries</a></h2>
     861      <p id="rfc.section.2.2.p.1">A more complicated situation occurs when one or more intermediaries are present in the request/response chain. There are three
     862         common forms of intermediary: proxy, gateway, and tunnel. In some cases, a single intermediary may act as an origin server,
     863         proxy, gateway, or tunnel, switching behavior based on the nature of each request.
     864      </p>
     865      <div id="rfc.figure.u.14"></div><pre class="drawing">       request chain --------------------------------------&gt;
    828866    UA -----v----- A -----v----- B -----v----- C -----v----- O
    829867       &lt;------------------------------------- response chain
    830 </pre><p id="rfc.section.2.1.p.6">The figure above shows three intermediaries (A, B, and C) between the user agent and origin server. A request or response
    831          message that travels the whole chain will pass through four separate connections. This distinction is important because some
    832          HTTP communication options may apply only to the connection with the nearest, non-tunnel neighbor, only to the end-points
    833          of the chain, or to all connections along the chain. Although the diagram is linear, each participant may be engaged in multiple,
    834          simultaneous communications. For example, B may be receiving requests from many clients other than A, and/or forwarding requests
    835          to servers other than C, at the same time that it is handling A's request.
    836       </p>
    837       <p id="rfc.section.2.1.p.7">Any party to the communication which is not acting as a tunnel may employ an internal cache for handling requests. The effect
    838          of a cache is that the request/response chain is shortened if one of the participants along the chain has a cached response
    839          applicable to that request. The following illustrates the resulting chain if B has a cached copy of an earlier response from
    840          O (via C) for a request which has not been cached by UA or A.
    841       </p>
    842       <div id="rfc.figure.u.14"></div><pre class="drawing">          request chain ----------&gt;
     868</pre><p id="rfc.section.2.2.p.3">The figure above shows three intermediaries (A, B, and C) between the user agent and origin server. A request or response
     869         message that travels the whole chain will pass through four separate connections. Some HTTP communication options may apply
     870         only to the connection with the nearest, non-tunnel neighbor, only to the end-points of the chain, or to all connections along
     871         the chain. Although the diagram is linear, each participant may be engaged in multiple, simultaneous communications. For example,
     872         B may be receiving requests from many clients other than A, and/or forwarding requests to servers other than C, at the same
     873         time that it is handling A's request.
     874      </p>
     875      <p id="rfc.section.2.2.p.4"> <span id="rfc.iref.u.2"></span><span id="rfc.iref.d.1"></span>  <span id="rfc.iref.i.1"></span><span id="rfc.iref.o.2"></span> We use the terms "upstream" and "downstream" to describe various requirements in relation to the directional flow of a message:
     876         all messages flow from upstream to downstream. Likewise, we use the terms "inbound" and "outbound" to refer to directions
     877         in relation to the request path: "inbound" means toward the origin server and "outbound" means toward the user agent.
     878      </p>
     879      <p id="rfc.section.2.2.p.5"><span id="rfc.iref.p.1"></span> A proxy is a message forwarding agent that is selected by the client, usually via local configuration rules, to receive requests
     880         for some type(s) of absolute URI and attempt to satisfy those requests via translation through the HTTP interface. Some translations
     881         are minimal, such as for proxy requests for "http" URIs, whereas other requests may require translation to and from entirely
     882         different application-layer protocols. Proxies are often used to group an organization's HTTP requests through a common intermediary
     883         for the sake of security, annotation services, or shared caching.
     884      </p>
     885      <p id="rfc.section.2.2.p.6"><span id="rfc.iref.g.23"></span><span id="rfc.iref.r.3"></span> A gateway (a.k.a., reverse proxy) is a receiving agent that acts as a layer above some other server(s) and translates the
     886         received requests to the underlying server's protocol. Gateways are often used for load balancing or partitioning HTTP services
     887         across multiple machines. Unlike a proxy, a gateway receives requests as if it were the origin server for the requested resource;
     888         the requesting client will not be aware that it is communicating with a gateway. A gateway communicates with the client as
     889         if the gateway is the origin server and thus is subject to all of the requirements on origin servers for that connection.
     890         A gateway communicates with inbound servers using any protocol it desires, including private extensions to HTTP that are outside
     891         the scope of this specification.
     892      </p>
     893      <p id="rfc.section.2.2.p.7"><span id="rfc.iref.t.1"></span> A tunnel acts as a blind relay between two connections without changing the messages. Once active, a tunnel is not considered
     894         a party to the HTTP communication, though the tunnel may have been initiated by an HTTP request. A tunnel ceases to exist
     895         when both ends of the relayed connection are closed. Tunnels are used to extend a virtual connection through an intermediary,
     896         such as when transport-layer security is used to establish private communication through a shared firewall proxy.
     897      </p>
     898      <div id="rfc.iref.c.3"></div>
     899      <h2 id="rfc.section.2.3"><a href="#rfc.section.2.3">2.3</a>&nbsp;<a id="caches" href="#caches">Caches</a></h2>
     900      <p id="rfc.section.2.3.p.1">Any party to HTTP communication that is not acting as a tunnel may employ an internal cache for handling requests. A cache
     901         is a local store of previous response messages and the subsystem that controls its message storage, retrieval, and deletion.
     902         A cache stores cacheable responses in order to reduce the response time and network bandwidth consumption on future, equivalent
     903         requests. Any client or server may include a cache, though a cache cannot be used by a server while it is acting as a tunnel.
     904      </p>
     905      <p id="rfc.section.2.3.p.2">The effect of a cache is that the request/response chain is shortened if one of the participants along the chain has a cached
     906         response applicable to that request. The following illustrates the resulting chain if B has a cached copy of an earlier response
     907         from O (via C) for a request which has not been cached by UA or A.
     908      </p>
     909      <div id="rfc.figure.u.15"></div><pre class="drawing">          request chain ----------&gt;
    843910       UA -----v----- A -----v----- B - - - - - - C - - - - - - O
    844911          &lt;--------- response chain
    845 </pre><p id="rfc.section.2.1.p.9">Not all responses are usefully cacheable, and some requests may contain modifiers which place special requirements on cache
    846          behavior. HTTP requirements for cache behavior and cacheable responses are defined in <a href="p6-cache.html#caching" title="Introduction">Section 1</a> of <a href="#Part6" id="rfc.xref.Part6.4"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>.
    847       </p>
    848       <p id="rfc.section.2.1.p.10">In fact, there are a wide variety of architectures and configurations of caches and proxies currently being experimented with
    849          or deployed across the World Wide Web. These systems include national hierarchies of proxy caches to save transoceanic bandwidth,
    850          systems that broadcast or multicast cache entries, organizations that distribute subsets of cached data via CD-ROM, and so
    851          on. HTTP systems are used in corporate intranets over high-bandwidth links, and for access via PDAs with low-power radio links
    852          and intermittent connectivity. The goal of HTTP/1.1 is to support the wide diversity of configurations already deployed while
    853          introducing protocol constructs that meet the needs of those who build web applications that require high reliability and,
    854          failing that, at least reliable indications of failure.
    855       </p>
    856       <p id="rfc.section.2.1.p.11">HTTP communication usually takes place over TCP/IP connections. The default port is TCP 80 (&lt;<a href="http://www.iana.org/assignments/port-numbers">http://www.iana.org/assignments/port-numbers</a>&gt;), but other ports can be used. This does not preclude HTTP from being implemented on top of any other protocol on the Internet,
     912</pre><p id="rfc.section.2.3.p.4"><span id="rfc.iref.c.4"></span> A response is cacheable if a cache is allowed to store a copy of the response message for use in answering subsequent requests.
     913         Even when a response is cacheable, there may be additional constraints placed by the client or by the origin server on when
     914         that cached response can be used for a particular request. HTTP requirements for cache behavior and cacheable responses are
     915         defined in <a href="p6-cache.html#caching" title="Introduction">Section 1</a> of <a href="#Part6" id="rfc.xref.Part6.4"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>.
     916      </p>
     917      <p id="rfc.section.2.3.p.5">There are a wide variety of architectures and configurations of caches and proxies deployed across the World Wide Web and
     918         inside large organizations. These systems include national hierarchies of proxy caches to save transoceanic bandwidth, systems
     919         that broadcast or multicast cache entries, organizations that distribute subsets of cached data via CD-ROM, and so on.
     920      </p>
     921      <h2 id="rfc.section.2.4"><a href="#rfc.section.2.4">2.4</a>&nbsp;<a id="transport-independence" href="#transport-independence">Transport Independence</a></h2>
     922      <p id="rfc.section.2.4.p.1">HTTP systems are used in a wide variety of environments, from corporate intranets with high-bandwidth links to long-distance
     923         communication over low-power radio links and intermittent connectivity.
     924      </p>
     925      <p id="rfc.section.2.4.p.2">HTTP communication usually takes place over TCP/IP connections. The default port is TCP 80 (&lt;<a href="http://www.iana.org/assignments/port-numbers">http://www.iana.org/assignments/port-numbers</a>&gt;), but other ports can be used. This does not preclude HTTP from being implemented on top of any other protocol on the Internet,
    857926         or on other networks. HTTP only presumes a reliable transport; any protocol that provides such guarantees can be used; the
    858927         mapping of the HTTP/1.1 request and response structures onto the transport data units of the protocol in question is outside
    859928         the scope of this specification.
    860929      </p>
    861       <p id="rfc.section.2.1.p.12">In HTTP/1.0, most implementations used a new connection for each request/response exchange. In HTTP/1.1, a connection may
     930      <p id="rfc.section.2.4.p.3">In HTTP/1.0, most implementations used a new connection for each request/response exchange. In HTTP/1.1, a connection may
    862931         be used for one or more request/response exchanges, although connections may be closed for a variety of reasons (see <a href="#persistent.connections" title="Persistent Connections">Section&nbsp;7.1</a>).
    863932      </p>
    864       <h2 id="rfc.section.2.2"><a href="#rfc.section.2.2">2.2</a>&nbsp;<a id="http.version" href="#http.version">HTTP Version</a></h2>
    865       <p id="rfc.section.2.2.p.1">HTTP uses a "&lt;major&gt;.&lt;minor&gt;" numbering scheme to indicate versions of the protocol. The protocol versioning policy is intended
     933      <h2 id="rfc.section.2.5"><a href="#rfc.section.2.5">2.5</a>&nbsp;<a id="http.version" href="#http.version">HTTP Version</a></h2>
     934      <p id="rfc.section.2.5.p.1">HTTP uses a "&lt;major&gt;.&lt;minor&gt;" numbering scheme to indicate versions of the protocol. The protocol versioning policy is intended
    866935         to allow the sender to indicate the format of a message and its capacity for understanding further HTTP communication, rather
    867936         than the features obtained via that communication. No change is made to the version number for the addition of message components
    … …  
    871940         of a message within the protocol is changed. See <a href="#RFC2145" id="rfc.xref.RFC2145.1"><cite title="Use and Interpretation of HTTP Version Numbers">[RFC2145]</cite></a> for a fuller explanation.
    872941      </p>
    873       <p id="rfc.section.2.2.p.2">The version of an HTTP message is indicated by an HTTP-Version field in the first line of the message. HTTP-Version is case-sensitive.</p>
    874       <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.23"></span><span id="rfc.iref.g.24"></span>  <a href="#http.version" class="smpl">HTTP-Version</a>   = <a href="#http.version" class="smpl">HTTP-Prot-Name</a> "/" 1*<a href="#core.rules" class="smpl">DIGIT</a> "." 1*<a href="#core.rules" class="smpl">DIGIT</a>
     942      <p id="rfc.section.2.5.p.2">The version of an HTTP message is indicated by an HTTP-Version field in the first line of the message. HTTP-Version is case-sensitive.</p>
     943      <div id="rfc.figure.u.16"></div><pre class="inline"><span id="rfc.iref.g.24"></span><span id="rfc.iref.g.25"></span>  <a href="#http.version" class="smpl">HTTP-Version</a>   = <a href="#http.version" class="smpl">HTTP-Prot-Name</a> "/" 1*<a href="#core.rules" class="smpl">DIGIT</a> "." 1*<a href="#core.rules" class="smpl">DIGIT</a>
    875944  <a href="#http.version" class="smpl">HTTP-Prot-Name</a> = %x48.54.54.50 ; "HTTP", case-sensitive
    876 </pre><p id="rfc.section.2.2.p.4">Note that the major and minor numbers <em class="bcp14">MUST</em> be treated as separate integers and that each <em class="bcp14">MAY</em> be incremented higher than a single digit. Thus, HTTP/2.4 is a lower version than HTTP/2.13, which in turn is lower than HTTP/12.3.
     945</pre><p id="rfc.section.2.5.p.4">Note that the major and minor numbers <em class="bcp14">MUST</em> be treated as separate integers and that each <em class="bcp14">MAY</em> be incremented higher than a single digit. Thus, HTTP/2.4 is a lower version than HTTP/2.13, which in turn is lower than HTTP/12.3.
    877946         Leading zeros <em class="bcp14">MUST</em> be ignored by recipients and <em class="bcp14">MUST NOT</em> be sent.
    878947      </p>
    879       <p id="rfc.section.2.2.p.5">An application that sends a request or response message that includes HTTP-Version of "HTTP/1.1" <em class="bcp14">MUST</em> be at least conditionally compliant with this specification. Applications that are at least conditionally compliant with this
     948      <p id="rfc.section.2.5.p.5">An application that sends a request or response message that includes HTTP-Version of "HTTP/1.1" <em class="bcp14">MUST</em> be at least conditionally compliant with this specification. Applications that are at least conditionally compliant with this
    880949         specification <em class="bcp14">SHOULD</em> use an HTTP-Version of "HTTP/1.1" in their messages, and <em class="bcp14">MUST</em> do so for any message that is not compatible with HTTP/1.0. For more details on when to send specific HTTP-Version values,
    881950         see <a href="#RFC2145" id="rfc.xref.RFC2145.2"><cite title="Use and Interpretation of HTTP Version Numbers">[RFC2145]</cite></a>.
    882951      </p>
    883       <p id="rfc.section.2.2.p.6">The HTTP version of an application is the highest HTTP version for which the application is at least conditionally compliant.</p>
    884       <p id="rfc.section.2.2.p.7">Proxy and gateway applications need to be careful when forwarding messages in protocol versions different from that of the
     952      <p id="rfc.section.2.5.p.6">The HTTP version of an application is the highest HTTP version for which the application is at least conditionally compliant.</p>
     953      <p id="rfc.section.2.5.p.7">Proxy and gateway applications need to be careful when forwarding messages in protocol versions different from that of the
    885954         application. Since the protocol version indicates the protocol capability of the sender, a proxy/gateway <em class="bcp14">MUST NOT</em> send a message with a version indicator which is greater than its actual version. If a higher version request is received,
    886955         the proxy/gateway <em class="bcp14">MUST</em> either downgrade the request version, or respond with an error, or switch to tunnel behavior.
    887956      </p>
    888       <p id="rfc.section.2.2.p.8">Due to interoperability problems with HTTP/1.0 proxies discovered since the publication of <a href="#RFC2068" id="rfc.xref.RFC2068.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>, caching proxies <em class="bcp14">MUST</em>, gateways <em class="bcp14">MAY</em>, and tunnels <em class="bcp14">MUST NOT</em> upgrade the request to the highest version they support. The proxy/gateway's response to that request <em class="bcp14">MUST</em> be in the same major version as the request.
     957      <p id="rfc.section.2.5.p.8">Due to interoperability problems with HTTP/1.0 proxies discovered since the publication of <a href="#RFC2068" id="rfc.xref.RFC2068.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>, caching proxies <em class="bcp14">MUST</em>, gateways <em class="bcp14">MAY</em>, and tunnels <em class="bcp14">MUST NOT</em> upgrade the request to the highest version they support. The proxy/gateway's response to that request <em class="bcp14">MUST</em> be in the same major version as the request.
    889958      </p>
    890959      <div class="note">
    … …  
    892961         </p>
    893962      </div>
    894       <div id="rfc.iref.r.1"></div>
    895       <h2 id="rfc.section.2.3"><a href="#rfc.section.2.3">2.3</a>&nbsp;<a id="uri" href="#uri">Uniform Resource Identifiers</a></h2>
    896       <p id="rfc.section.2.3.p.1">Uniform Resource Identifiers (URIs) <a href="#RFC3986" id="rfc.xref.RFC3986.2"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a> are used throughout HTTP as the means for identifying resources. URI references are used to target requests, indicate redirects,
     963      <div id="rfc.iref.r.4"></div>
     964      <h2 id="rfc.section.2.6"><a href="#rfc.section.2.6">2.6</a>&nbsp;<a id="uri" href="#uri">Uniform Resource Identifiers</a></h2>
     965      <p id="rfc.section.2.6.p.1">Uniform Resource Identifiers (URIs) <a href="#RFC3986" id="rfc.xref.RFC3986.2"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a> are used throughout HTTP as the means for identifying resources. URI references are used to target requests, indicate redirects,
    897966         and define relationships. HTTP does not limit what a resource may be; it merely defines an interface that can be used to interact
    898967         with a resource via HTTP. More information on the scope of URIs and resources can be found in <a href="#RFC3986" id="rfc.xref.RFC3986.3"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>.
    899968      </p>
    900       <p id="rfc.section.2.3.p.2">This specification adopts the definitions of "URI-reference", "absolute-URI", "relative-part", "fragment", "port", "host",
     969      <p id="rfc.section.2.6.p.2">This specification adopts the definitions of "URI-reference", "absolute-URI", "relative-part", "fragment", "port", "host",
    901970         "path-abempty", "path-absolute", "query", and "authority" from <a href="#RFC3986" id="rfc.xref.RFC3986.4"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>. In addition, we define a partial-URI rule for protocol elements that allow a relative URI without a fragment.
    902971      </p>
    903       <div id="rfc.figure.u.16"></div><pre class="inline"><span id="rfc.iref.g.25"></span><span id="rfc.iref.g.26"></span><span id="rfc.iref.g.27"></span><span id="rfc.iref.g.28"></span><span id="rfc.iref.g.29"></span><span id="rfc.iref.g.30"></span><span id="rfc.iref.g.31"></span>  <a href="#uri" class="smpl">URI</a>           = &lt;URI, defined in <a href="#RFC3986" id="rfc.xref.RFC3986.5"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-3">Section 3</a>&gt;
     972      <div id="rfc.figure.u.17"></div><pre class="inline"><span id="rfc.iref.g.26"></span><span id="rfc.iref.g.27"></span><span id="rfc.iref.g.28"></span><span id="rfc.iref.g.29"></span><span id="rfc.iref.g.30"></span><span id="rfc.iref.g.31"></span><span id="rfc.iref.g.32"></span>  <a href="#uri" class="smpl">URI</a>           = &lt;URI, defined in <a href="#RFC3986" id="rfc.xref.RFC3986.5"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-3">Section 3</a>&gt;
    904973  <a href="#uri" class="smpl">URI-reference</a> = &lt;URI-reference, defined in <a href="#RFC3986" id="rfc.xref.RFC3986.6"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-4.1">Section 4.1</a>&gt;
    905974  <a href="#uri" class="smpl">absolute-URI</a>  = &lt;absolute-URI, defined in <a href="#RFC3986" id="rfc.xref.RFC3986.7"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-4.3">Section 4.3</a>&gt;
    … …  
    914983 
    915984  <a href="#uri" class="smpl">partial-URI</a>   = relative-part [ "?" query ]
    916 </pre><p id="rfc.section.2.3.p.4">Each protocol element in HTTP that allows a URI reference will indicate in its ABNF production whether the element allows
     985</pre><p id="rfc.section.2.6.p.4">Each protocol element in HTTP that allows a URI reference will indicate in its ABNF production whether the element allows
    917986         only a URI in absolute form (absolute-URI), any relative reference (relative-ref), or some other subset of the URI-reference
    918987         grammar. Unless otherwise indicated, URI references are parsed relative to the request target (the default base URI for both
    919988         the request and its corresponding response).
    920989      </p>
    921       <h3 id="rfc.section.2.3.1"><a href="#rfc.section.2.3.1">2.3.1</a>&nbsp;<a id="http.uri" href="#http.uri">http URI scheme</a></h3>
     990      <h3 id="rfc.section.2.6.1"><a href="#rfc.section.2.6.1">2.6.1</a>&nbsp;<a id="http.uri" href="#http.uri">http URI scheme</a></h3>
    922991      <div id="rfc.iref.h.1"></div>
    923       <div id="rfc.iref.u.1"></div>
    924       <p id="rfc.section.2.3.1.p.1">The "http" URI scheme is hereby defined for the purpose of minting identifiers according to their association with the hierarchical
     992      <div id="rfc.iref.u.3"></div>
     993      <p id="rfc.section.2.6.1.p.1">The "http" URI scheme is hereby defined for the purpose of minting identifiers according to their association with the hierarchical
    925994         namespace governed by a potential HTTP origin server listening for TCP connections on a given port. The HTTP server is identified
    926995         via the generic syntax's <a href="#uri" class="smpl">authority</a> component, which includes a host identifier and optional TCP port, and the remainder of the URI is considered to be identifying
    927996         data corresponding to a resource for which that server might provide an HTTP interface.
    928997      </p>
    929       <div id="rfc.figure.u.17"></div><pre class="inline"><span id="rfc.iref.g.32"></span>  <a href="#http.uri" class="smpl">http-URI</a> = "http:" "//" <a href="#uri" class="smpl">authority</a> <a href="#uri" class="smpl">path-abempty</a> [ "?" <a href="#uri" class="smpl">query</a> ]
    930 </pre><p id="rfc.section.2.3.1.p.3">The host identifier within an <a href="#uri" class="smpl">authority</a> component is defined in <a href="#RFC3986" id="rfc.xref.RFC3986.16"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-3.2.2">Section 3.2.2</a>. If host is provided as an IP literal or IPv4 address, then the HTTP server is any listener on the indicated TCP port at
     998      <div id="rfc.figure.u.18"></div><pre class="inline"><span id="rfc.iref.g.33"></span>  <a href="#http.uri" class="smpl">http-URI</a> = "http:" "//" <a href="#uri" class="smpl">authority</a> <a href="#uri" class="smpl">path-abempty</a> [ "?" <a href="#uri" class="smpl">query</a> ]
     999</pre><p id="rfc.section.2.6.1.p.3">The host identifier within an <a href="#uri" class="smpl">authority</a> component is defined in <a href="#RFC3986" id="rfc.xref.RFC3986.16"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-3.2.2">Section 3.2.2</a>. If host is provided as an IP literal or IPv4 address, then the HTTP server is any listener on the indicated TCP port at
    9311000         that IP address. If host is a registered name, then that name is considered an indirect identifier and the recipient might
    9321001         use a name resolution service, such as DNS, to find the address of a listener for that host. The host <em class="bcp14">MUST NOT</em> be empty; if an "http" URI is received with an empty host, then it <em class="bcp14">MUST</em> be rejected as invalid. If the port subcomponent is empty or not given, then TCP port 80 is assumed (the default reserved
    9331002         port for WWW services).
    9341003      </p>
    935       <p id="rfc.section.2.3.1.p.4">Regardless of the form of host identifier, access to that host is not implied by the mere presence of its name or address.
     1004      <p id="rfc.section.2.6.1.p.4">Regardless of the form of host identifier, access to that host is not implied by the mere presence of its name or address.
    9361005         The host may or may not exist and, even when it does exist, may or may not be running an HTTP server or listening to the indicated
    9371006         port. The "http" URI scheme makes use of the delegated nature of Internet names and addresses to establish a naming authority
    … …  
    9391008         which names are valid and how they might be used.
    9401009      </p>
    941       <p id="rfc.section.2.3.1.p.5">When an "http" URI is used within a context that calls for access to the indicated resource, a client <em class="bcp14">MAY</em> attempt access by resolving the host to an IP address, establishing a TCP connection to that address on the indicated port,
     1010      <p id="rfc.section.2.6.1.p.5">When an "http" URI is used within a context that calls for access to the indicated resource, a client <em class="bcp14">MAY</em> attempt access by resolving the host to an IP address, establishing a TCP connection to that address on the indicated port,
    9421011         and sending an HTTP request message to the server containing the URI's identifying data as described in <a href="#request" title="Request">Section&nbsp;4</a>. If the server responds to that request with a non-interim HTTP response message, as described in <a href="#response" title="Response">Section&nbsp;5</a>, then that response is considered an authoritative answer to the client's request.
    9431012      </p>
    944       <p id="rfc.section.2.3.1.p.6">Although HTTP is independent of the transport protocol, the "http" scheme is specific to TCP-based services because the name
     1013      <p id="rfc.section.2.6.1.p.6">Although HTTP is independent of the transport protocol, the "http" scheme is specific to TCP-based services because the name
    9451014         delegation process depends on TCP for establishing authority. An HTTP service based on some other underlying connection protocol
    9461015         would presumably be identified using a different URI scheme, just as the "https" scheme (below) is used for servers that require
    … …  
    9481017         --- it is only the authoritative interface used for mapping the namespace that is specific to TCP.
    9491018      </p>
    950       <h3 id="rfc.section.2.3.2"><a href="#rfc.section.2.3.2">2.3.2</a>&nbsp;<a id="https.uri" href="#https.uri">https URI scheme</a></h3>
     1019      <h3 id="rfc.section.2.6.2"><a href="#rfc.section.2.6.2">2.6.2</a>&nbsp;<a id="https.uri" href="#https.uri">https URI scheme</a></h3>
    9511020      <div id="rfc.iref.h.2"></div>
    952       <div id="rfc.iref.u.2"></div>
    953       <p id="rfc.section.2.3.2.p.1">The "https" URI scheme is hereby defined for the purpose of minting identifiers according to their association with the hierarchical
     1021      <div id="rfc.iref.u.4"></div>
     1022      <p id="rfc.section.2.6.2.p.1">The "https" URI scheme is hereby defined for the purpose of minting identifiers according to their association with the hierarchical
    9541023         namespace governed by a potential HTTP origin server listening for SSL/TLS-secured connections on a given TCP port. The host
    9551024         and port are determined in the same way as for the "http" scheme, except that a default TCP port of 443 is assumed if the
    9561025         port subcomponent is empty or not given.
    9571026      </p>
    958       <div id="rfc.figure.u.18"></div><pre class="inline"><span id="rfc.iref.g.33"></span>  <a href="#https.uri" class="smpl">https-URI</a> = "https:" "//" <a href="#uri" class="smpl">authority</a> <a href="#uri" class="smpl">path-abempty</a> [ "?" <a href="#uri" class="smpl">query</a> ]
    959 </pre><p id="rfc.section.2.3.2.p.3">The primary difference between the "http" and "https" schemes is that interaction with the latter is required to be secured
     1027      <div id="rfc.figure.u.19"></div><pre class="inline"><span id="rfc.iref.g.34"></span>  <a href="#https.uri" class="smpl">https-URI</a> = "https:" "//" <a href="#uri" class="smpl">authority</a> <a href="#uri" class="smpl">path-abempty</a> [ "?" <a href="#uri" class="smpl">query</a> ]
     1028</pre><p id="rfc.section.2.6.2.p.3">The primary difference between the "http" and "https" schemes is that interaction with the latter is required to be secured
    9601029         for privacy through the use of strong encryption. The URI cannot be sent in a request until the connection is secure. Likewise,
    9611030         the default for caching is that each response that would be considered "public" under the "http" scheme is instead treated
    9621031         as "private" and thus not eligible for shared caching.
    9631032      </p>
    964       <p id="rfc.section.2.3.2.p.4">The process for authoritative access to an "https" identified resource is defined in <a href="#RFC2818" id="rfc.xref.RFC2818.1"><cite title="HTTP Over TLS">[RFC2818]</cite></a>.
    965       </p>
    966       <h3 id="rfc.section.2.3.3"><a href="#rfc.section.2.3.3">2.3.3</a>&nbsp;<a id="uri.comparison" href="#uri.comparison">http and https URI Normalization and Comparison</a></h3>
    967       <p id="rfc.section.2.3.3.p.1">Since the "http" and "https" schemes conform to the URI generic syntax, such URIs are normalized and compared according to
     1033      <p id="rfc.section.2.6.2.p.4">The process for authoritative access to an "https" identified resource is defined in <a href="#RFC2818" id="rfc.xref.RFC2818.1"><cite title="HTTP Over TLS">[RFC2818]</cite></a>.
     1034      </p>
     1035      <h3 id="rfc.section.2.6.3"><a href="#rfc.section.2.6.3">2.6.3</a>&nbsp;<a id="uri.comparison" href="#uri.comparison">http and https URI Normalization and Comparison</a></h3>
     1036      <p id="rfc.section.2.6.3.p.1">Since the "http" and "https" schemes conform to the URI generic syntax, such URIs are normalized and compared according to
    9681037         the algorithm defined in <a href="#RFC3986" id="rfc.xref.RFC3986.17"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-6">Section 6</a>, using the defaults described above for each scheme.
    9691038      </p>
    970       <p id="rfc.section.2.3.3.p.2">If the port is equal to the default port for a scheme, the normal form is to elide the port subcomponent. Likewise, an empty
     1039      <p id="rfc.section.2.6.3.p.2">If the port is equal to the default port for a scheme, the normal form is to elide the port subcomponent. Likewise, an empty
    9711040         path component is equivalent to an absolute path of "/", so the normal form is to provide a path of "/" instead. The scheme
    9721041         and host are case-insensitive and normally provided in lowercase; all other components are compared in a case-sensitive manner.
    9731042         Characters other than those in the "reserved" set are equivalent to their percent-encoded octets (see <a href="#RFC3986" id="rfc.xref.RFC3986.18"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-2.1">Section 2.1</a>): the normal form is to not encode them.
    9741043      </p>
    975       <p id="rfc.section.2.3.3.p.3">For example, the following three URIs are equivalent:</p>
    976       <div id="rfc.figure.u.19"></div><pre class="text">   http://example.com:80/~smith/home.html
     1044      <p id="rfc.section.2.6.3.p.3">For example, the following three URIs are equivalent:</p>
     1045      <div id="rfc.figure.u.20"></div><pre class="text">   http://example.com:80/~smith/home.html
    9771046   http://EXAMPLE.com/%7Esmith/home.html
    9781047   http://EXAMPLE.com:/%7esmith/home.html
    979 </pre><p id="rfc.section.2.3.3.p.5"> <span class="comment" id="rfc.comment.1">[<a href="#rfc.comment.1" class="smpl">rfc.comment.1</a>: [[This paragraph does not belong here. --Roy]]]</span> If path-abempty is the empty string (i.e., there is no slash "/" path separator following the authority), then the "http"
     1048</pre><p id="rfc.section.2.6.3.p.5"> <span class="comment" id="rfc.comment.1">[<a href="#rfc.comment.1" class="smpl">rfc.comment.1</a>: [[This paragraph does not belong here. --Roy]]]</span> If path-abempty is the empty string (i.e., there is no slash "/" path separator following the authority), then the "http"
    9801049         URI <em class="bcp14">MUST</em> be given as "/" when used as a request-target (<a href="#request-target" title="request-target">Section&nbsp;4.1.2</a>). If a proxy receives a host name which is not a fully qualified domain name, it <em class="bcp14">MAY</em> add its domain to the host name it received. If a proxy receives a fully qualified domain name, the proxy <em class="bcp14">MUST NOT</em> change the host name.
    9811050      </p>
    982       <h3 id="rfc.section.2.3.4"><a href="#rfc.section.2.3.4">2.3.4</a>&nbsp;<a id="scheme.aliases" href="#scheme.aliases">Scheme aliases considered harmful</a></h3>
    983       <p id="rfc.section.2.3.4.p.1"> <span class="comment" id="rfc.comment.2">[<a href="#rfc.comment.2" class="smpl">rfc.comment.2</a>: TBS: describe why aliases like webcal are harmful.]</span>
    984       </p>
    985       <h2 id="rfc.section.2.4"><a href="#rfc.section.2.4">2.4</a>&nbsp;<a id="http.proxy" href="#http.proxy">Use of HTTP for proxy communication</a></h2>
    986       <p id="rfc.section.2.4.p.1"> <span class="comment" id="rfc.comment.3">[<a href="#rfc.comment.3" class="smpl">rfc.comment.3</a>: TBD: Configured to use HTTP to proxy HTTP or other protocols.]</span>
    987       </p>
    988       <h2 id="rfc.section.2.5"><a href="#rfc.section.2.5">2.5</a>&nbsp;<a id="http.intercept" href="#http.intercept">Interception of HTTP for access control</a></h2>
    989       <p id="rfc.section.2.5.p.1"> <span class="comment" id="rfc.comment.4">[<a href="#rfc.comment.4" class="smpl">rfc.comment.4</a>: TBD: Interception of HTTP traffic for initiating access control.]</span>
    990       </p>
    991       <h2 id="rfc.section.2.6"><a href="#rfc.section.2.6">2.6</a>&nbsp;<a id="http.others" href="#http.others">Use of HTTP by other protocols</a></h2>
    992       <p id="rfc.section.2.6.p.1"> <span class="comment" id="rfc.comment.5">[<a href="#rfc.comment.5" class="smpl">rfc.comment.5</a>: TBD: Profiles of HTTP defined by other protocol. Extensions of HTTP like WebDAV.]</span>
    993       </p>
    994       <h2 id="rfc.section.2.7"><a href="#rfc.section.2.7">2.7</a>&nbsp;<a id="http.media" href="#http.media">Use of HTTP by media type specification</a></h2>
    995       <p id="rfc.section.2.7.p.1"> <span class="comment" id="rfc.comment.6">[<a href="#rfc.comment.6" class="smpl">rfc.comment.6</a>: TBD: Instructions on composing HTTP requests via hypertext formats.]</span>
     1051      <h3 id="rfc.section.2.6.4"><a href="#rfc.section.2.6.4">2.6.4</a>&nbsp;<a id="scheme.aliases" href="#scheme.aliases">Scheme aliases considered harmful</a></h3>
     1052      <p id="rfc.section.2.6.4.p.1"> <span class="comment" id="rfc.comment.2">[<a href="#rfc.comment.2" class="smpl">rfc.comment.2</a>: TBS: describe why aliases like webcal are harmful.]</span>
     1053      </p>
     1054      <h2 id="rfc.section.2.7"><a href="#rfc.section.2.7">2.7</a>&nbsp;<a id="http.proxy" href="#http.proxy">Use of HTTP for proxy communication</a></h2>
     1055      <p id="rfc.section.2.7.p.1"> <span class="comment" id="rfc.comment.3">[<a href="#rfc.comment.3" class="smpl">rfc.comment.3</a>: TBD: Configured to use HTTP to proxy HTTP or other protocols.]</span>
     1056      </p>
     1057      <h2 id="rfc.section.2.8"><a href="#rfc.section.2.8">2.8</a>&nbsp;<a id="http.intercept" href="#http.intercept">Interception of HTTP for access control</a></h2>
     1058      <p id="rfc.section.2.8.p.1"> <span class="comment" id="rfc.comment.4">[<a href="#rfc.comment.4" class="smpl">rfc.comment.4</a>: TBD: Interception of HTTP traffic for initiating access control.]</span>
     1059      </p>
     1060      <h2 id="rfc.section.2.9"><a href="#rfc.section.2.9">2.9</a>&nbsp;<a id="http.others" href="#http.others">Use of HTTP by other protocols</a></h2>
     1061      <p id="rfc.section.2.9.p.1"> <span class="comment" id="rfc.comment.5">[<a href="#rfc.comment.5" class="smpl">rfc.comment.5</a>: TBD: Profiles of HTTP defined by other protocol. Extensions of HTTP like WebDAV.]</span>
     1062      </p>
     1063      <h2 id="rfc.section.2.10"><a href="#rfc.section.2.10">2.10</a>&nbsp;<a id="http.media" href="#http.media">Use of HTTP by media type specification</a></h2>
     1064      <p id="rfc.section.2.10.p.1"> <span class="comment" id="rfc.comment.6">[<a href="#rfc.comment.6" class="smpl">rfc.comment.6</a>: TBD: Instructions on composing HTTP requests via hypertext formats.]</span>
    9961065      </p>
    9971066      <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a id="http.message" href="#http.message">HTTP Message</a></h1>
    9981067      <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a id="message.types" href="#message.types">Message Types</a></h2>
    9991068      <p id="rfc.section.3.1.p.1">HTTP messages consist of requests from client to server and responses from server to client.</p>
    1000       <div id="rfc.figure.u.20"></div><pre class="inline"><span id="rfc.iref.g.34"></span>  <a href="#message.types" class="smpl">HTTP-message</a>   = <a href="#request" class="smpl">Request</a> / <a href="#response" class="smpl">Response</a>     ; HTTP/1.1 messages
     1069      <div id="rfc.figure.u.21"></div><pre class="inline"><span id="rfc.iref.g.35"></span>  <a href="#message.types" class="smpl">HTTP-message</a>   = <a href="#request" class="smpl">Request</a> / <a href="#response" class="smpl">Response</a>     ; HTTP/1.1 messages
    10011070</pre><p id="rfc.section.3.1.p.3">Request (<a href="#request" title="Request">Section&nbsp;4</a>) and Response (<a href="#response" title="Response">Section&nbsp;5</a>) messages use the generic message format of <a href="#RFC5322" id="rfc.xref.RFC5322.2"><cite title="Internet Message Format">[RFC5322]</cite></a> for transferring entities (the payload of the message). Both types of message consist of a start-line, zero or more header
    10021071         fields (also known as "headers"), an empty line (i.e., a line with nothing preceding the CRLF) indicating the end of the header
    10031072         fields, and possibly a message-body.
    10041073      </p>
    1005       <div id="rfc.figure.u.21"></div><pre class="inline"><span id="rfc.iref.g.35"></span><span id="rfc.iref.g.36"></span>  <a href="#message.types" class="smpl">generic-message</a> = <a href="#message.types" class="smpl">start-line</a>
     1074      <div id="rfc.figure.u.22"></div><pre class="inline"><span id="rfc.iref.g.36"></span><span id="rfc.iref.g.37"></span>  <a href="#message.types" class="smpl">generic-message</a> = <a href="#message.types" class="smpl">start-line</a>
    10061075                    *( <a href="#message.headers" class="smpl">message-header</a> <a href="#core.rules" class="smpl">CRLF</a> )
    10071076                    <a href="#core.rules" class="smpl">CRLF</a>
    … …  
    10221091         case-insensitive.
    10231092      </p>
    1024       <div id="rfc.figure.u.22"></div><pre class="inline"><span id="rfc.iref.g.37"></span><span id="rfc.iref.g.38"></span><span id="rfc.iref.g.39"></span><span id="rfc.iref.g.40"></span>  <a href="#message.headers" class="smpl">message-header</a> = <a href="#message.headers" class="smpl">field-name</a> ":" OWS [ <a href="#message.headers" class="smpl">field-value</a> ] OWS
     1093      <div id="rfc.figure.u.23"></div><pre class="inline"><span id="rfc.iref.g.38"></span><span id="rfc.iref.g.39"></span><span id="rfc.iref.g.40"></span><span id="rfc.iref.g.41"></span>  <a href="#message.headers" class="smpl">message-header</a> = <a href="#message.headers" class="smpl">field-name</a> ":" OWS [ <a href="#message.headers" class="smpl">field-value</a> ] OWS
    10251094  <a href="#message.headers" class="smpl">field-name</a>     = <a href="#rule.token.separators" class="smpl">token</a>
    10261095  <a href="#message.headers" class="smpl">field-value</a>    = *( <a href="#message.headers" class="smpl">field-content</a> / <a href="#rule.whitespace" class="smpl">OWS</a> )
    … …  
    10471116         </p>
    10481117      </div>
    1049       <div id="rfc.figure.u.23"></div><pre class="inline"><span id="rfc.iref.g.41"></span><span id="rfc.iref.g.42"></span>  <a href="#rule.comment" class="smpl">comment</a>        = "(" *( <a href="#rule.comment" class="smpl">ctext</a> / <a href="#rule.quoted-pair" class="smpl">quoted-pair</a> / <a href="#rule.comment" class="smpl">comment</a> ) ")"
     1118      <div id="rfc.figure.u.24"></div><pre class="inline"><span id="rfc.iref.g.42"></span><span id="rfc.iref.g.43"></span>  <a href="#rule.comment" class="smpl">comment</a>        = "(" *( <a href="#rule.comment" class="smpl">ctext</a> / <a href="#rule.quoted-pair" class="smpl">quoted-pair</a> / <a href="#rule.comment" class="smpl">comment</a> ) ")"
    10501119  <a href="#rule.comment" class="smpl">ctext</a>          = <a href="#rule.whitespace" class="smpl">OWS</a> / %x21-27 / %x2A-5B / %x5D-7E / <a href="#rule.quoted-string" class="smpl">obs-text</a>
    10511120                 ; <a href="#rule.whitespace" class="smpl">OWS</a> / &lt;<a href="#core.rules" class="smpl">VCHAR</a> except "(", ")", and "\"&gt; / <a href="#rule.quoted-string" class="smpl">obs-text</a>
    … …  
    10701139         header field (<a href="#header.transfer-encoding" id="rfc.xref.header.transfer-encoding.1" title="Transfer-Encoding">Section&nbsp;8.7</a>).
    10711140      </p>
    1072       <div id="rfc.figure.u.24"></div><pre class="inline"><span id="rfc.iref.g.43"></span>  <a href="#message.body" class="smpl">message-body</a> = <a href="#abnf.dependencies" class="smpl">entity-body</a>
     1141      <div id="rfc.figure.u.25"></div><pre class="inline"><span id="rfc.iref.g.44"></span>  <a href="#message.body" class="smpl">message-body</a> = <a href="#abnf.dependencies" class="smpl">entity-body</a>
    10731142               / &lt;entity-body encoded as per <a href="#header.transfer-encoding" class="smpl">Transfer-Encoding</a>&gt;
    10741143</pre><p id="rfc.section.3.3.p.3">Transfer-Encoding <em class="bcp14">MUST</em> be used to indicate any transfer-codings applied by an application to ensure safe and proper transfer of the message. Transfer-Encoding
    … …  
    11371206         to the entity being transferred. These header fields apply only to the message being transmitted.
    11381207      </p>
    1139       <div id="rfc.figure.u.25"></div><pre class="inline"><span id="rfc.iref.g.44"></span>  <a href="#general.header.fields" class="smpl">general-header</a> = <a href="#abnf.dependencies" class="smpl">Cache-Control</a>            ; <a href="#Part6" id="rfc.xref.Part6.5"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.cache-control" title="Cache-Control">Section 3.2</a>
     1208      <div id="rfc.figure.u.26"></div><pre class="inline"><span id="rfc.iref.g.45"></span>  <a href="#general.header.fields" class="smpl">general-header</a> = <a href="#abnf.dependencies" class="smpl">Cache-Control</a>            ; <a href="#Part6" id="rfc.xref.Part6.5"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.cache-control" title="Cache-Control">Section 3.2</a>
    11401209                 / <a href="#header.connection" class="smpl">Connection</a>               ; <a href="#header.connection" id="rfc.xref.header.connection.1" title="Connection">Section&nbsp;8.1</a>
    11411210                 / <a href="#header.date" class="smpl">Date</a>                     ; <a href="#header.date" id="rfc.xref.header.date.1" title="Date">Section&nbsp;8.3</a>
    … …  
    11541223         resource, the identifier of the resource, and the protocol version in use.
    11551224      </p>
    1156       <div id="rfc.figure.u.26"></div><pre class="inline"><span id="rfc.iref.g.45"></span>  <a href="#request" class="smpl">Request</a>       = <a href="#request-line" class="smpl">Request-Line</a>              ; <a href="#request-line" title="Request-Line">Section&nbsp;4.1</a>
     1225      <div id="rfc.figure.u.27"></div><pre class="inline"><span id="rfc.iref.g.46"></span>  <a href="#request" class="smpl">Request</a>       = <a href="#request-line" class="smpl">Request-Line</a>              ; <a href="#request-line" title="Request-Line">Section&nbsp;4.1</a>
    11571226                  *(( <a href="#general.header.fields" class="smpl">general-header</a>        ; <a href="#general.header.fields" title="General Header Fields">Section&nbsp;3.5</a>
    11581227                   / <a href="#abnf.dependencies" class="smpl">request-header</a>         ; <a href="#Part2" id="rfc.xref.Part2.3"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#request.header.fields" title="Request Header Fields">Section 3</a>
    … …  
    11641233         The elements are separated by SP characters. No CR or LF is allowed except in the final CRLF sequence.
    11651234      </p>
    1166       <div id="rfc.figure.u.27"></div><pre class="inline"><span id="rfc.iref.g.46"></span>  <a href="#request-line" class="smpl">Request-Line</a>   = <a href="#method" class="smpl">Method</a> <a href="#core.rules" class="smpl">SP</a> <a href="#request-target" class="smpl">request-target</a> <a href="#core.rules" class="smpl">SP</a> <a href="#http.version" class="smpl">HTTP-Version</a> <a href="#core.rules" class="smpl">CRLF</a>
     1235      <div id="rfc.figure.u.28"></div><pre class="inline"><span id="rfc.iref.g.47"></span>  <a href="#request-line" class="smpl">Request-Line</a>   = <a href="#method" class="smpl">Method</a> <a href="#core.rules" class="smpl">SP</a> <a href="#request-target" class="smpl">request-target</a> <a href="#core.rules" class="smpl">SP</a> <a href="#http.version" class="smpl">HTTP-Version</a> <a href="#core.rules" class="smpl">CRLF</a>
    11671236</pre><h3 id="rfc.section.4.1.1"><a href="#rfc.section.4.1.1">4.1.1</a>&nbsp;<a id="method" href="#method">Method</a></h3>
    11681237      <p id="rfc.section.4.1.1.p.1">The Method token indicates the method to be performed on the resource identified by the request-target. The method is case-sensitive.</p>
    1169       <div id="rfc.figure.u.28"></div><pre class="inline"><span id="rfc.iref.g.47"></span><span id="rfc.iref.g.48"></span>  <a href="#method" class="smpl">Method</a>         = <a href="#rule.token.separators" class="smpl">token</a>
     1238      <div id="rfc.figure.u.29"></div><pre class="inline"><span id="rfc.iref.g.48"></span><span id="rfc.iref.g.49"></span>  <a href="#method" class="smpl">Method</a>         = <a href="#rule.token.separators" class="smpl">token</a>
    11701239</pre><h3 id="rfc.section.4.1.2"><a href="#rfc.section.4.1.2">4.1.2</a>&nbsp;<a id="request-target" href="#request-target">request-target</a></h3>
    11711240      <p id="rfc.section.4.1.2.p.1">The request-target identifies the resource upon which to apply the request.</p>
    1172       <div id="rfc.figure.u.29"></div><pre class="inline"><span id="rfc.iref.g.49"></span>  <a href="#request-target" class="smpl">request-target</a> = "*"
     1241      <div id="rfc.figure.u.30"></div><pre class="inline"><span id="rfc.iref.g.50"></span>  <a href="#request-target" class="smpl">request-target</a> = "*"
    11731242                 / <a href="#uri" class="smpl">absolute-URI</a>
    11741243                 / ( <a href="#uri" class="smpl">path-absolute</a> [ "?" <a href="#uri" class="smpl">query</a> ] )
    … …  
    11781247         apply to a resource. One example would be
    11791248      </p>
    1180       <div id="rfc.figure.u.30"></div><pre class="text">  OPTIONS * HTTP/1.1
     1249      <div id="rfc.figure.u.31"></div><pre class="text">  OPTIONS * HTTP/1.1
    11811250</pre><p id="rfc.section.4.1.2.p.5">The absolute-URI form is <em class="bcp14">REQUIRED</em> when the request is being made to a proxy. The proxy is requested to forward the request or service it from a valid cache,
    11821251         and return the response. Note that the proxy <em class="bcp14">MAY</em> forward the request on to another proxy or directly to the server specified by the absolute-URI. In order to avoid request
    … …  
    11841253         Request-Line would be:
    11851254      </p>
    1186       <div id="rfc.figure.u.31"></div><pre class="text">  GET http://www.example.org/pub/WWW/TheProject.html HTTP/1.1
     1255      <div id="rfc.figure.u.32"></div><pre class="text">  GET http://www.example.org/pub/WWW/TheProject.html HTTP/1.1
    11871256</pre><p id="rfc.section.4.1.2.p.7">To allow for transition to absolute-URIs in all requests in future versions of HTTP, all HTTP/1.1 servers <em class="bcp14">MUST</em> accept the absolute-URI form in requests, even though HTTP/1.1 clients will only generate them in requests to proxies.
    11881257      </p>
    … …  
    11901259      </p>
    11911260      <p id="rfc.section.4.1.2.p.9">The most common form of request-target is that used to identify a resource on an origin server or gateway. In this case the
    1192          absolute path of the URI <em class="bcp14">MUST</em> be transmitted (see <a href="#http.uri" title="http URI scheme">Section&nbsp;2.3.1</a>, path-absolute) as the request-target, and the network location of the URI (authority) <em class="bcp14">MUST</em> be transmitted in a Host header field. For example, a client wishing to retrieve the resource above directly from the origin
     1261         absolute path of the URI <em class="bcp14">MUST</em> be transmitted (see <a href="#http.uri" title="http URI scheme">Section&nbsp;2.6.1</a>, path-absolute) as the request-target, and the network location of the URI (authority) <em class="bcp14">MUST</em> be transmitted in a Host header field. For example, a client wishing to retrieve the resource above directly from the origin
    11931262         server would create a TCP connection to port 80 of the host "www.example.org" and send the lines:
    11941263      </p>
    1195       <div id="rfc.figure.u.32"></div><pre class="text">  GET /pub/WWW/TheProject.html HTTP/1.1
     1264      <div id="rfc.figure.u.33"></div><pre class="text">  GET /pub/WWW/TheProject.html HTTP/1.1
    11961265  Host: www.example.org
    11971266</pre><p id="rfc.section.4.1.2.p.11">followed by the remainder of the Request. Note that the absolute path cannot be empty; if none is present in the original
    … …  
    12011270         asterisk form of request-target, then the last proxy on the request chain <em class="bcp14">MUST</em> forward the request with "*" as the final request-target.
    12021271      </p>
    1203       <div id="rfc.figure.u.33"></div>
     1272      <div id="rfc.figure.u.34"></div>
    12041273      <p>For example, the request</p><pre class="text">  OPTIONS http://www.example.org:8001 HTTP/1.1
    1205 </pre><div id="rfc.figure.u.34"></div>
     1274</pre><div id="rfc.figure.u.35"></div>
    12061275      <p>would be forwarded by the proxy as</p><pre class="text">  OPTIONS * HTTP/1.1
    12071276  Host: www.example.org:8001
    12081277</pre>  <p>after connecting to port 8001 of host "www.example.org".</p>
    1209       <p id="rfc.section.4.1.2.p.15">The request-target is transmitted in the format specified in <a href="#http.uri" title="http URI scheme">Section&nbsp;2.3.1</a>. If the request-target is percent-encoded (<a href="#RFC3986" id="rfc.xref.RFC3986.19"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-2.1">Section 2.1</a>), the origin server <em class="bcp14">MUST</em> decode the request-target in order to properly interpret the request. Servers <em class="bcp14">SHOULD</em> respond to invalid request-targets with an appropriate status code.
     1278      <p id="rfc.section.4.1.2.p.15">The request-target is transmitted in the format specified in <a href="#http.uri" title="http URI scheme">Section&nbsp;2.6.1</a>. If the request-target is percent-encoded (<a href="#RFC3986" id="rfc.xref.RFC3986.19"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-2.1">Section 2.1</a>), the origin server <em class="bcp14">MUST</em> decode the request-target in order to properly interpret the request. Servers <em class="bcp14">SHOULD</em> respond to invalid request-targets with an appropriate status code.
    12101279      </p>
    12111280      <p id="rfc.section.4.1.2.p.16">A transparent proxy <em class="bcp14">MUST NOT</em> rewrite the "path-absolute" part of the received request-target when forwarding it to the next inbound server, except as noted
    … …  
    12461315      <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a id="response" href="#response">Response</a></h1>
    12471316      <p id="rfc.section.5.p.1">After receiving and interpreting a request message, a server responds with an HTTP response message.</p>
    1248       <div id="rfc.figure.u.35"></div><pre class="inline"><span id="rfc.iref.g.50"></span>  <a href="#response" class="smpl">Response</a>      = <a href="#status-line" class="smpl">Status-Line</a>               ; <a href="#status-line" title="Status-Line">Section&nbsp;5.1</a>
     1317      <div id="rfc.figure.u.36"></div><pre class="inline"><span id="rfc.iref.g.51"></span>  <a href="#response" class="smpl">Response</a>      = <a href="#status-line" class="smpl">Status-Line</a>               ; <a href="#status-line" title="Status-Line">Section&nbsp;5.1</a>
    12491318                  *(( <a href="#general.header.fields" class="smpl">general-header</a>        ; <a href="#general.header.fields" title="General Header Fields">Section&nbsp;3.5</a>
    12501319                   / <a href="#abnf.dependencies" class="smpl">response-header</a>        ; <a href="#Part2" id="rfc.xref.Part2.6"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#response.header.fields" title="Response Header Fields">Section 5</a>
    … …  
    12571326         CRLF sequence.
    12581327      </p>
    1259       <div id="rfc.figure.u.36"></div><pre class="inline"><span id="rfc.iref.g.51"></span>  <a href="#status-line" class="smpl">Status-Line</a> = <a href="#http.version" class="smpl">HTTP-Version</a> <a href="#core.rules" class="smpl">SP</a> <a href="#status.code.and.reason.phrase" class="smpl">Status-Code</a> <a href="#core.rules" class="smpl">SP</a> <a href="#status.code.and.reason.phrase" class="smpl">Reason-Phrase</a> <a href="#core.rules" class="smpl">CRLF</a>
     1328      <div id="rfc.figure.u.37"></div><pre class="inline"><span id="rfc.iref.g.52"></span>  <a href="#status-line" class="smpl">Status-Line</a> = <a href="#http.version" class="smpl">HTTP-Version</a> <a href="#core.rules" class="smpl">SP</a> <a href="#status.code.and.reason.phrase" class="smpl">Status-Code</a> <a href="#core.rules" class="smpl">SP</a> <a href="#status.code.and.reason.phrase" class="smpl">Reason-Phrase</a> <a href="#core.rules" class="smpl">CRLF</a>
    12601329</pre><h3 id="rfc.section.5.1.1"><a href="#rfc.section.5.1.1">5.1.1</a>&nbsp;<a id="status.code.and.reason.phrase" href="#status.code.and.reason.phrase">Status Code and Reason Phrase</a></h3>
    12611330      <p id="rfc.section.5.1.1.p.1">The Status-Code element is a 3-digit integer result code of the attempt to understand and satisfy the request. These codes
    … …  
    12741343         <li>5xx: Server Error - The server failed to fulfill an apparently valid request</li>
    12751344      </ul>
    1276       <div id="rfc.figure.u.37"></div><pre class="inline"><span id="rfc.iref.g.52"></span><span id="rfc.iref.g.53"></span><span id="rfc.iref.g.54"></span>  <a href="#status.code.and.reason.phrase" class="smpl">Status-Code</a>    = 3<a href="#core.rules" class="smpl">DIGIT</a>
     1345      <div id="rfc.figure.u.38"></div><pre class="inline"><span id="rfc.iref.g.53"></span><span id="rfc.iref.g.54"></span><span id="rfc.iref.g.55"></span>  <a href="#status.code.and.reason.phrase" class="smpl">Status-Code</a>    = 3<a href="#core.rules" class="smpl">DIGIT</a>
    12771346  <a href="#status.code.and.reason.phrase" class="smpl">Reason-Phrase</a>  = *( <a href="#core.rules" class="smpl">WSP</a> / <a href="#core.rules" class="smpl">VCHAR</a> / <a href="#rule.quoted-string" class="smpl">obs-text</a> )
    12781347</pre><h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="protocol.parameters" href="#protocol.parameters">Protocol Parameters</a></h1>
    12791348      <h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a>&nbsp;<a id="date.time.formats.full.date" href="#date.time.formats.full.date">Date/Time Formats: Full Date</a></h2>
    12801349      <p id="rfc.section.6.1.p.1">HTTP applications have historically allowed three different formats for the representation of date/time stamps:</p>
    1281       <div id="rfc.figure.u.38"></div><pre class="text">  Sun, 06 Nov 1994 08:49:37 GMT  ; RFC 1123
     1350      <div id="rfc.figure.u.39"></div><pre class="text">  Sun, 06 Nov 1994 08:49:37 GMT  ; RFC 1123
    12821351  Sunday, 06-Nov-94 08:49:37 GMT ; obsolete RFC 850 format
    12831352  Sun Nov  6 08:49:37 1994       ; ANSI C's asctime() format
    … …  
    12891358         time zone, and <em class="bcp14">MUST</em> be assumed when reading the asctime format. HTTP-date is case sensitive and <em class="bcp14">MUST NOT</em> include additional whitespace beyond that specifically included as SP in the grammar.
    12901359      </p>
    1291       <div id="rfc.figure.u.39"></div><pre class="inline"><span id="rfc.iref.g.55"></span>  <a href="#date.time.formats.full.date" class="smpl">HTTP-date</a>    = <a href="#preferred.date.format" class="smpl">rfc1123-date</a> / <a href="#obsolete.date.formats" class="smpl">obs-date</a>
     1360      <div id="rfc.figure.u.40"></div><pre class="inline"><span id="rfc.iref.g.56"></span>  <a href="#date.time.formats.full.date" class="smpl">HTTP-date</a>    = <a href="#preferred.date.format" class="smpl">rfc1123-date</a> / <a href="#obsolete.date.formats" class="smpl">obs-date</a>
    12921361</pre><div id="preferred.date.format">
    12931362         <p id="rfc.section.6.1.p.6">                    Preferred format:</p>
    12941363      </div>
    1295       <div id="rfc.figure.u.40"></div><pre class="inline"><span id="rfc.iref.g.56"></span><span id="rfc.iref.g.57"></span><span id="rfc.iref.g.58"></span><span id="rfc.iref.g.59"></span><span id="rfc.iref.g.60"></span><span id="rfc.iref.g.61"></span><span id="rfc.iref.g.62"></span><span id="rfc.iref.g.63"></span><span id="rfc.iref.g.64"></span><span id="rfc.iref.g.65"></span><span id="rfc.iref.g.66"></span><span id="rfc.iref.g.67"></span>  <a href="#preferred.date.format" class="smpl">rfc1123-date</a> = <a href="#preferred.date.format" class="smpl">day-name</a> "," <a href="#core.rules" class="smpl">SP</a> date1 <a href="#core.rules" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">time-of-day</a> <a href="#core.rules" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">GMT</a>
     1364      <div id="rfc.figure.u.41"></div><pre class="inline"><span id="rfc.iref.g.57"></span><span id="rfc.iref.g.58"></span><span id="rfc.iref.g.59"></span><span id="rfc.iref.g.60"></span><span id="rfc.iref.g.61"></span><span id="rfc.iref.g.62"></span><span id="rfc.iref.g.63"></span><span id="rfc.iref.g.64"></span><span id="rfc.iref.g.65"></span><span id="rfc.iref.g.66"></span><span id="rfc.iref.g.67"></span><span id="rfc.iref.g.68"></span>  <a href="#preferred.date.format" class="smpl">rfc1123-date</a> = <a href="#preferred.date.format" class="smpl">day-name</a> "," <a href="#core.rules" class="smpl">SP</a> date1 <a href="#core.rules" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">time-of-day</a> <a href="#core.rules" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">GMT</a>
    12961365
    12971366  <a href="#preferred.date.format" class="smpl">day-name</a>     = %x4D.6F.6E ; "Mon", case-sensitive
    … …  
    13341403         <p id="rfc.section.6.1.p.9">                Obsolete formats:</p>
    13351404      </div>
    1336       <div id="rfc.figure.u.41"></div><pre class="inline"><span id="rfc.iref.g.68"></span>  <a href="#obsolete.date.formats" class="smpl">obs-date</a>     = <a href="#obsolete.date.formats" class="smpl">rfc850-date</a> / <a href="#obsolete.date.formats" class="smpl">asctime-date</a>
    1337 </pre><div id="rfc.figure.u.42"></div><pre class="inline"><span id="rfc.iref.g.69"></span>  <a href="#obsolete.date.formats" class="smpl">rfc850-date</a>  = <a href="#obsolete.date.formats" class="smpl">day-name-l</a> "," <a href="#core.rules" class="smpl">SP</a> <a href="#obsolete.date.formats" class="smpl">date2</a> <a href="#core.rules" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">time-of-day</a> <a href="#core.rules" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">GMT</a>
     1405      <div id="rfc.figure.u.42"></div><pre class="inline"><span id="rfc.iref.g.69"></span>  <a href="#obsolete.date.formats" class="smpl">obs-date</a>     = <a href="#obsolete.date.formats" class="smpl">rfc850-date</a> / <a href="#obsolete.date.formats" class="smpl">asctime-date</a>
     1406</pre><div id="rfc.figure.u.43"></div><pre class="inline"><span id="rfc.iref.g.70"></span>  <a href="#obsolete.date.formats" class="smpl">rfc850-date</a>  = <a href="#obsolete.date.formats" class="smpl">day-name-l</a> "," <a href="#core.rules" class="smpl">SP</a> <a href="#obsolete.date.formats" class="smpl">date2</a> <a href="#core.rules" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">time-of-day</a> <a href="#core.rules" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">GMT</a>
    13381407  <a href="#obsolete.date.formats" class="smpl">date2</a>        = <a href="#preferred.date.format" class="smpl">day</a> "-" <a href="#preferred.date.format" class="smpl">month</a> "-" 2<a href="#core.rules" class="smpl">DIGIT</a>
    13391408                 ; day-month-year (e.g., 02-Jun-82)
    … …  
    13461415         / %x53.61.74.75.72.64.61.79 ; "Saturday", case-sensitive
    13471416         / %x53.75.6E.64.61.79 ; "Sunday", case-sensitive
    1348 </pre><div id="rfc.figure.u.43"></div><pre class="inline"><span id="rfc.iref.g.70"></span>  <a href="#obsolete.date.formats" class="smpl">asctime-date</a> = <a href="#preferred.date.format" class="smpl">day-name</a> <a href="#core.rules" class="smpl">SP</a> <a href="#obsolete.date.formats" class="smpl">date3</a> <a href="#core.rules" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">time-of-day</a> <a href="#core.rules" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">year</a>
     1417</pre><div id="rfc.figure.u.44"></div><pre class="inline"><span id="rfc.iref.g.71"></span>  <a href="#obsolete.date.formats" class="smpl">asctime-date</a> = <a href="#preferred.date.format" class="smpl">day-name</a> <a href="#core.rules" class="smpl">SP</a> <a href="#obsolete.date.formats" class="smpl">date3</a> <a href="#core.rules" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">time-of-day</a> <a href="#core.rules" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">year</a>
    13491418  <a href="#obsolete.date.formats" class="smpl">date3</a>        = <a href="#preferred.date.format" class="smpl">month</a> <a href="#core.rules" class="smpl">SP</a> ( 2<a href="#core.rules" class="smpl">DIGIT</a> / ( <a href="#core.rules" class="smpl">SP</a> 1<a href="#core.rules" class="smpl">DIGIT</a> ))
    13501419                 ; month day (e.g., Jun  2)
    … …  
    13641433         is a property of the message, not of the original entity.
    13651434      </p>
    1366       <div id="rfc.figure.u.44"></div><pre class="inline"><span id="rfc.iref.g.71"></span><span id="rfc.iref.g.72"></span>  <a href="#transfer.codings" class="smpl">transfer-coding</a>         = "chunked" / <a href="#transfer.codings" class="smpl">transfer-extension</a>
     1435      <div id="rfc.figure.u.45"></div><pre class="inline"><span id="rfc.iref.g.72"></span><span id="rfc.iref.g.73"></span>  <a href="#transfer.codings" class="smpl">transfer-coding</a>         = "chunked" / <a href="#transfer.codings" class="smpl">transfer-extension</a>
    13671436  <a href="#transfer.codings" class="smpl">transfer-extension</a>      = <a href="#rule.token.separators" class="smpl">token</a> *( <a href="#rule.whitespace" class="smpl">OWS</a> ";" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#rule.parameter" class="smpl">transfer-parameter</a> )
    13681437</pre><div id="rule.parameter">
    13691438         <p id="rfc.section.6.2.p.3">      Parameters are in the form of attribute/value pairs.</p>
    13701439      </div>
    1371       <div id="rfc.figure.u.45"></div><pre class="inline"><span id="rfc.iref.g.73"></span><span id="rfc.iref.g.74"></span><span id="rfc.iref.g.75"></span><span id="rfc.iref.g.76"></span><span id="rfc.iref.g.77"></span>  <a href="#rule.parameter" class="smpl">transfer-parameter</a>      = <a href="#rule.parameter" class="smpl">attribute</a> <a href="#rule.whitespace" class="smpl">BWS</a> "=" <a href="#rule.whitespace" class="smpl">BWS</a> <a href="#rule.parameter" class="smpl">value</a>
     1440      <div id="rfc.figure.u.46"></div><pre class="inline"><span id="rfc.iref.g.74"></span><span id="rfc.iref.g.75"></span><span id="rfc.iref.g.76"></span><span id="rfc.iref.g.77"></span><span id="rfc.iref.g.78"></span>  <a href="#rule.parameter" class="smpl">transfer-parameter</a>      = <a href="#rule.parameter" class="smpl">attribute</a> <a href="#rule.whitespace" class="smpl">BWS</a> "=" <a href="#rule.whitespace" class="smpl">BWS</a> <a href="#rule.parameter" class="smpl">value</a>
    13721441  <a href="#rule.parameter" class="smpl">attribute</a>               = <a href="#rule.token.separators" class="smpl">token</a>
    13731442  <a href="#rule.parameter" class="smpl">value</a>                   = <a href="#rule.token.separators" class="smpl">token</a> / <a href="#rule.quoted-string" class="smpl">quoted-string</a>
    … …  
    13941463         necessary for the recipient to verify that it has received the full message.
    13951464      </p>
    1396       <div id="rfc.figure.u.46"></div><pre class="inline"><span id="rfc.iref.g.78"></span><span id="rfc.iref.g.79"></span><span id="rfc.iref.g.80"></span><span id="rfc.iref.g.81"></span><span id="rfc.iref.g.82"></span><span id="rfc.iref.g.83"></span><span id="rfc.iref.g.84"></span><span id="rfc.iref.g.85"></span><span id="rfc.iref.g.86"></span>  <a href="#chunked.transfer.encoding" class="smpl">Chunked-Body</a>   = *<a href="#chunked.transfer.encoding" class="smpl">chunk</a>
     1465      <div id="rfc.figure.u.47"></div><pre class="inline"><span id="rfc.iref.g.79"></span><span id="rfc.iref.g.80"></span><span id="rfc.iref.g.81"></span><span id="rfc.iref.g.82"></span><span id="rfc.iref.g.83"></span><span id="rfc.iref.g.84"></span><span id="rfc.iref.g.85"></span><span id="rfc.iref.g.86"></span><span id="rfc.iref.g.87"></span>  <a href="#chunked.transfer.encoding" class="smpl">Chunked-Body</a>   = *<a href="#chunked.transfer.encoding" class="smpl">chunk</a>
    13971466                   <a href="#chunked.transfer.encoding" class="smpl">last-chunk</a>
    13981467                   <a href="#chunked.transfer.encoding" class="smpl">trailer-part</a>
    … …  
    14321501      </p>
    14331502      <p id="rfc.section.6.2.1.p.7">A process for decoding the "chunked" transfer-coding can be represented in pseudo-code as:</p>
    1434       <div id="rfc.figure.u.47"></div><pre class="text">  length := 0
     1503      <div id="rfc.figure.u.48"></div><pre class="text">  length := 0
    14351504  read chunk-size, chunk-ext (if any) and CRLF
    14361505  while (chunk-size &gt; 0) {
    … …  
    14541523         By convention, the products are listed in order of their significance for identifying the application.
    14551524      </p>
    1456       <div id="rfc.figure.u.48"></div><pre class="inline"><span id="rfc.iref.g.87"></span><span id="rfc.iref.g.88"></span>  <a href="#product.tokens" class="smpl">product</a>         = <a href="#rule.token.separators" class="smpl">token</a> ["/" <a href="#product.tokens" class="smpl">product-version</a>]
     1525      <div id="rfc.figure.u.49"></div><pre class="inline"><span id="rfc.iref.g.88"></span><span id="rfc.iref.g.89"></span>  <a href="#product.tokens" class="smpl">product</a>         = <a href="#rule.token.separators" class="smpl">token</a> ["/" <a href="#product.tokens" class="smpl">product-version</a>]
    14571526  <a href="#product.tokens" class="smpl">product-version</a> = <a href="#rule.token.separators" class="smpl">token</a>
    14581527</pre><p id="rfc.section.6.3.p.3">Examples:</p>
    1459       <div id="rfc.figure.u.49"></div><pre class="text">  User-Agent: CERN-LineMode/2.15 libwww/2.17b3
     1528      <div id="rfc.figure.u.50"></div><pre class="text">  User-Agent: CERN-LineMode/2.15 libwww/2.17b3
    14601529  Server: Apache/0.8.4
    14611530</pre><p id="rfc.section.6.3.p.5">Product tokens <em class="bcp14">SHOULD</em> be short and to the point. They <em class="bcp14">MUST NOT</em> be used for advertising or other non-essential information. Although any token character <em class="bcp14">MAY</em> appear in a product-version, this token <em class="bcp14">SHOULD</em> only be used for a version identifier (i.e., successive versions of the same product <em class="bcp14">SHOULD</em> only differ in the product-version portion of the product value).
    … …  
    14661535         a quality value of 0, then content with this parameter is `not acceptable' for the client. HTTP/1.1 applications <em class="bcp14">MUST NOT</em> generate more than three digits after the decimal point. User configuration of these values <em class="bcp14">SHOULD</em> also be limited in this fashion.
    14671536      </p>
    1468       <div id="rfc.figure.u.50"></div><pre class="inline"><span id="rfc.iref.g.89"></span>  <a href="#quality.values" class="smpl">qvalue</a>         = ( "0" [ "." 0*3<a href="#core.rules" class="smpl">DIGIT</a> ] )
     1537      <div id="rfc.figure.u.51"></div><pre class="inline"><span id="rfc.iref.g.90"></span>  <a href="#quality.values" class="smpl">qvalue</a>         = ( "0" [ "." 0*3<a href="#core.rules" class="smpl">DIGIT</a> ] )
    14691538                 / ( "1" [ "." 0*3("0") ] )
    14701539</pre><div class="note">
    … …  
    16551724         receives the entity.
    16561725      </p>
    1657       <div id="rfc.iref.c.1"></div>
     1726      <div id="rfc.iref.c.5"></div>
    16581727      <div id="rfc.iref.h.3"></div>
    16591728      <h2 id="rfc.section.8.1"><a href="#rfc.section.8.1">8.1</a>&nbsp;<a id="header.connection" href="#header.connection">Connection</a></h2>
    … …  
    16621731      </p>
    16631732      <p id="rfc.section.8.1.p.2">The Connection header's value has the following grammar:</p>
    1664       <div id="rfc.figure.u.51"></div><pre class="inline"><span id="rfc.iref.g.90"></span><span id="rfc.iref.g.91"></span><span id="rfc.iref.g.92"></span>  <a href="#header.connection" class="smpl">Connection</a>       = "Connection" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.connection" class="smpl">Connection-v</a>
     1733      <div id="rfc.figure.u.52"></div><pre class="inline"><span id="rfc.iref.g.91"></span><span id="rfc.iref.g.92"></span><span id="rfc.iref.g.93"></span>  <a href="#header.connection" class="smpl">Connection</a>       = "Connection" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.connection" class="smpl">Connection-v</a>
    16651734  <a href="#header.connection" class="smpl">Connection-v</a>     = 1#<a href="#header.connection" class="smpl">connection-token</a>
    16661735  <a href="#header.connection" class="smpl">connection-token</a> = <a href="#rule.token.separators" class="smpl">token</a>
    … …  
    16751744         of the response. For example,
    16761745      </p>
    1677       <div id="rfc.figure.u.52"></div><pre class="text">  Connection: close
     1746      <div id="rfc.figure.u.53"></div><pre class="text">  Connection: close
    16781747</pre><p id="rfc.section.8.1.p.8">in either the request or the response header fields indicates that the connection <em class="bcp14">SHOULD NOT</em> be considered `persistent' (<a href="#persistent.connections" title="Persistent Connections">Section&nbsp;7.1</a>) after the current request/response is complete.
    16791748      </p>
    … …  
    16851754         connection-token. This protects against mistaken forwarding of such header fields by pre-HTTP/1.1 proxies. See <a href="#compatibility.with.http.1.0.persistent.connections" title="Compatibility with HTTP/1.0 Persistent Connections">Appendix&nbsp;B.2</a>.
    16861755      </p>
    1687       <div id="rfc.iref.c.2"></div>
     1756      <div id="rfc.iref.c.6"></div>
    16881757      <div id="rfc.iref.h.4"></div>
    16891758      <h2 id="rfc.section.8.2"><a href="#rfc.section.8.2">8.2</a>&nbsp;<a id="header.content-length" href="#header.content-length">Content-Length</a></h2>
    … …  
    16911760         or, in the case of the HEAD method, the size of the entity-body that would have been sent had the request been a GET.
    16921761      </p>
    1693       <div id="rfc.figure.u.53"></div><pre class="inline"><span id="rfc.iref.g.93"></span><span id="rfc.iref.g.94"></span>  <a href="#header.content-length" class="smpl">Content-Length</a>   = "Content-Length" ":" <a href="#rule.whitespace" class="smpl">OWS</a> 1*<a href="#header.content-length" class="smpl">Content-Length-v</a>
     1762      <div id="rfc.figure.u.54"></div><pre class="inline"><span id="rfc.iref.g.94"></span><span id="rfc.iref.g.95"></span>  <a href="#header.content-length" class="smpl">Content-Length</a>   = "Content-Length" ":" <a href="#rule.whitespace" class="smpl">OWS</a> 1*<a href="#header.content-length" class="smpl">Content-Length-v</a>
    16941763  <a href="#header.content-length" class="smpl">Content-Length-v</a> = 1*<a href="#core.rules" class="smpl">DIGIT</a>
    16951764</pre><p id="rfc.section.8.2.p.3">An example is</p>
    1696       <div id="rfc.figure.u.54"></div><pre class="text">  Content-Length: 3495
     1765      <div id="rfc.figure.u.55"></div><pre class="text">  Content-Length: 3495
    16971766</pre><p id="rfc.section.8.2.p.5">Applications <em class="bcp14">SHOULD</em> use this field to indicate the transfer-length of the message-body, unless this is prohibited by the rules in <a href="#message.length" title="Message Length">Section&nbsp;3.4</a>.
    16981767      </p>
    … …  
    17031772         in <a href="#message.length" title="Message Length">Section&nbsp;3.4</a>.
    17041773      </p>
    1705       <div id="rfc.iref.d.1"></div>
     1774      <div id="rfc.iref.d.2"></div>
    17061775      <div id="rfc.iref.h.5"></div>
    17071776      <h2 id="rfc.section.8.3"><a href="#rfc.section.8.3">8.3</a>&nbsp;<a id="header.date" href="#header.date">Date</a></h2>
    … …  
    17091778         as orig-date in <a href="http://tools.ietf.org/html/rfc5322#section-3.6.1">Section 3.6.1</a> of <a href="#RFC5322" id="rfc.xref.RFC5322.5"><cite title="Internet Message Format">[RFC5322]</cite></a>. The field value is an HTTP-date, as described in <a href="#date.time.formats.full.date" title="Date/Time Formats: Full Date">Section&nbsp;6.1</a>; it <em class="bcp14">MUST</em> be sent in rfc1123-date format.
    17101779      </p>
    1711       <div id="rfc.figure.u.55"></div><pre class="inline"><span id="rfc.iref.g.95"></span><span id="rfc.iref.g.96"></span>  <a href="#header.date" class="smpl">Date</a>   = "Date" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.date" class="smpl">Date-v</a>
     1780      <div id="rfc.figure.u.56"></div><pre class="inline"><span id="rfc.iref.g.96"></span><span id="rfc.iref.g.97"></span>  <a href="#header.date" class="smpl">Date</a>   = "Date" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.date" class="smpl">Date-v</a>
    17121781  <a href="#header.date" class="smpl">Date-v</a> = <a href="#date.time.formats.full.date" class="smpl">HTTP-date</a>
    17131782</pre><p id="rfc.section.8.3.p.3">An example is</p>
    1714       <div id="rfc.figure.u.56"></div><pre class="text">  Date: Tue, 15 Nov 1994 08:12:31 GMT
     1783      <div id="rfc.figure.u.57"></div><pre class="text">  Date: Tue, 15 Nov 1994 08:12:31 GMT
    17151784</pre><p id="rfc.section.8.3.p.5">Origin servers <em class="bcp14">MUST</em> include a Date header field in all responses, except in these cases:
    17161785      </p>
    … …  
    17441813      <h2 id="rfc.section.8.4"><a href="#rfc.section.8.4">8.4</a>&nbsp;<a id="header.host" href="#header.host">Host</a></h2>
    17451814      <p id="rfc.section.8.4.p.1">The request-header field "Host" specifies the Internet host and port number of the resource being requested, as obtained from
    1746          the original URI given by the user or referring resource (generally an http URI, as described in <a href="#http.uri" title="http URI scheme">Section&nbsp;2.3.1</a>). The Host field value <em class="bcp14">MUST</em> represent the naming authority of the origin server or gateway given by the original URL. This allows the origin server or
     1815         the original URI given by the user or referring resource (generally an http URI, as described in <a href="#http.uri" title="http URI scheme">Section&nbsp;2.6.1</a>). The Host field value <em class="bcp14">MUST</em> represent the naming authority of the origin server or gateway given by the original URL. This allows the origin server or
    17471816         gateway to differentiate between internally-ambiguous URLs, such as the root "/" URL of a server for multiple host names on
    17481817         a single IP address.
    17491818      </p>
    1750       <div id="rfc.figure.u.57"></div><pre class="inline"><span id="rfc.iref.g.97"></span><span id="rfc.iref.g.98"></span>  <a href="#header.host" class="smpl">Host</a>   = "Host" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.host" class="smpl">Host-v</a>
    1751   <a href="#header.host" class="smpl">Host-v</a> = <a href="#uri" class="smpl">uri-host</a> [ ":" <a href="#uri" class="smpl">port</a> ] ; <a href="#http.uri" title="http URI scheme">Section&nbsp;2.3.1</a>
     1819      <div id="rfc.figure.u.58"></div><pre class="inline"><span id="rfc.iref.g.98"></span><span id="rfc.iref.g.99"></span>  <a href="#header.host" class="smpl">Host</a>   = "Host" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.host" class="smpl">Host-v</a>
     1820  <a href="#header.host" class="smpl">Host-v</a> = <a href="#uri" class="smpl">uri-host</a> [ ":" <a href="#uri" class="smpl">port</a> ] ; <a href="#http.uri" title="http URI scheme">Section&nbsp;2.6.1</a>
    17521821</pre><p id="rfc.section.8.4.p.3">A "host" without any trailing port information implies the default port for the service requested (e.g., "80" for an HTTP
    17531822         URL). For example, a request on the origin server for &lt;http://www.example.org/pub/WWW/&gt; would properly include:
    17541823      </p>
    1755       <div id="rfc.figure.u.58"></div><pre class="text">  GET /pub/WWW/ HTTP/1.1
     1824      <div id="rfc.figure.u.59"></div><pre class="text">  GET /pub/WWW/ HTTP/1.1
    17561825  Host: www.example.org
    17571826</pre><p id="rfc.section.8.4.p.5">A client <em class="bcp14">MUST</em> include a Host header field in all HTTP/1.1 request messages. If the requested URI does not include an Internet host name
    … …  
    17611830      <p id="rfc.section.8.4.p.6">See Sections <a href="#the.resource.identified.by.a.request" title="The Resource Identified by a Request">4.2</a> and <a href="#changes.to.simplify.multi-homed.web.servers.and.conserve.ip.addresses" title="Changes to Simplify Multi-homed Web Servers and Conserve IP Addresses">B.1.1</a> for other requirements relating to Host.
    17621831      </p>
    1763       <div id="rfc.iref.t.1"></div>
     1832      <div id="rfc.iref.t.2"></div>
    17641833      <div id="rfc.iref.h.8"></div>
    17651834      <h2 id="rfc.section.8.5"><a href="#rfc.section.8.5">8.5</a>&nbsp;<a id="header.te" href="#header.te">TE</a></h2>
    … …  
    17681837         and/or a comma-separated list of extension transfer-coding names with optional accept parameters (as described in <a href="#transfer.codings" title="Transfer Codings">Section&nbsp;6.2</a>).
    17691838      </p>
    1770       <div id="rfc.figure.u.59"></div><pre class="inline"><span id="rfc.iref.g.99"></span><span id="rfc.iref.g.100"></span><span id="rfc.iref.g.101"></span><span id="rfc.iref.g.102"></span><span id="rfc.iref.g.103"></span>  <a href="#header.te" class="smpl">TE</a>        = "TE" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.te" class="smpl">TE-v</a>
     1839      <div id="rfc.figure.u.60"></div><pre class="inline"><span id="rfc.iref.g.100"></span><span id="rfc.iref.g.101"></span><span id="rfc.iref.g.102"></span><span id="rfc.iref.g.103"></span><span id="rfc.iref.g.104"></span>  <a href="#header.te" class="smpl">TE</a>        = "TE" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.te" class="smpl">TE-v</a>
    17711840  <a href="#header.te" class="smpl">TE-v</a>      = #<a href="#header.te" class="smpl">t-codings</a>
    17721841  <a href="#header.te" class="smpl">t-codings</a> = "trailers" / ( <a href="#transfer.codings" class="smpl">transfer-extension</a> [ <a href="#header.te" class="smpl">te-params</a> ] )
    … …  
    17771846      </p>
    17781847      <p id="rfc.section.8.5.p.4">Examples of its use are:</p>
    1779       <div id="rfc.figure.u.60"></div><pre class="text">  TE: deflate
     1848      <div id="rfc.figure.u.61"></div><pre class="text">  TE: deflate
    17801849  TE:
    17811850  TE: trailers, deflate;q=0.5
    … …  
    18081877         is always acceptable.
    18091878      </p>
    1810       <div id="rfc.iref.t.2"></div>
     1879      <div id="rfc.iref.t.3"></div>
    18111880      <div id="rfc.iref.h.9"></div>
    18121881      <h2 id="rfc.section.8.6"><a href="#rfc.section.8.6">8.6</a>&nbsp;<a id="header.trailer" href="#header.trailer">Trailer</a></h2>
    … …  
    18141883         chunked transfer-coding.
    18151884      </p>
    1816       <div id="rfc.figure.u.61"></div><pre class="inline"><span id="rfc.iref.g.104"></span><span id="rfc.iref.g.105"></span>  <a href="#header.trailer" class="smpl">Trailer</a>   = "Trailer" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.trailer" class="smpl">Trailer-v</a>
     1885      <div id="rfc.figure.u.62"></div><pre class="inline"><span id="rfc.iref.g.105"></span><span id="rfc.iref.g.106"></span>  <a href="#header.trailer" class="smpl">Trailer</a>   = "Trailer" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.trailer" class="smpl">Trailer-v</a>
    18171886  <a href="#header.trailer" class="smpl">Trailer-v</a> = 1#<a href="#message.headers" class="smpl">field-name</a>
    18181887</pre><p id="rfc.section.8.6.p.3">An HTTP/1.1 message <em class="bcp14">SHOULD</em> include a Trailer header field in a message using chunked transfer-coding with a non-empty trailer. Doing so allows the recipient
    … …  
    18281897         <li>Trailer</li>
    18291898      </ul>
    1830       <div id="rfc.iref.t.3"></div>
     1899      <div id="rfc.iref.t.4"></div>
    18311900      <div id="rfc.iref.h.10"></div>
    18321901      <h2 id="rfc.section.8.7"><a href="#rfc.section.8.7">8.7</a>&nbsp;<a id="header.transfer-encoding" href="#header.transfer-encoding">Transfer-Encoding</a></h2>
    … …  
    18351904         transfer-coding is a property of the message, not of the entity.
    18361905      </p>
    1837       <div id="rfc.figure.u.62"></div><pre class="inline"><span id="rfc.iref.g.106"></span><span id="rfc.iref.g.107"></span>  <a href="#header.transfer-encoding" class="smpl">Transfer-Encoding</a>   = "Transfer-Encoding" ":" <a href="#rule.whitespace" class="smpl">OWS</a>
     1906      <div id="rfc.figure.u.63"></div><pre class="inline"><span id="rfc.iref.g.107"></span><span id="rfc.iref.g.108"></span>  <a href="#header.transfer-encoding" class="smpl">Transfer-Encoding</a>   = "Transfer-Encoding" ":" <a href="#rule.whitespace" class="smpl">OWS</a>
    18381907                        <a href="#header.transfer-encoding" class="smpl">Transfer-Encoding-v</a>
    18391908  <a href="#header.transfer-encoding" class="smpl">Transfer-Encoding-v</a> = 1#<a href="#transfer.codings" class="smpl">transfer-coding</a>
    18401909</pre><p id="rfc.section.8.7.p.3">Transfer-codings are defined in <a href="#transfer.codings" title="Transfer Codings">Section&nbsp;6.2</a>. An example is:
    18411910      </p>
    1842       <div id="rfc.figure.u.63"></div><pre class="text">  Transfer-Encoding: chunked
     1911      <div id="rfc.figure.u.64"></div><pre class="text">  Transfer-Encoding: chunked
    18431912</pre><p id="rfc.section.8.7.p.5">If multiple encodings have been applied to an entity, the transfer-codings <em class="bcp14">MUST</em> be listed in the order in which they were applied. Additional information about the encoding parameters <em class="bcp14">MAY</em> be provided by other entity-header fields not defined by this specification.
    18441913      </p>
    18451914      <p id="rfc.section.8.7.p.6">Many older HTTP/1.0 applications do not understand the Transfer-Encoding header.</p>
    1846       <div id="rfc.iref.u.3"></div>
     1915      <div id="rfc.iref.u.5"></div>
    18471916      <div id="rfc.iref.h.11"></div>
    18481917      <h2 id="rfc.section.8.8"><a href="#rfc.section.8.8">8.8</a>&nbsp;<a id="header.upgrade" href="#header.upgrade">Upgrade</a></h2>
    … …  
    18501919         to use if the server finds it appropriate to switch protocols. The server <em class="bcp14">MUST</em> use the Upgrade header field within a 101 (Switching Protocols) response to indicate which protocol(s) are being switched.
    18511920      </p>
    1852       <div id="rfc.figure.u.64"></div><pre class="inline"><span id="rfc.iref.g.108"></span><span id="rfc.iref.g.109"></span>  <a href="#header.upgrade" class="smpl">Upgrade</a>   = "Upgrade" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.upgrade" class="smpl">Upgrade-v</a>
     1921      <div id="rfc.figure.u.65"></div><pre class="inline"><span id="rfc.iref.g.109"></span><span id="rfc.iref.g.110"></span>  <a href="#header.upgrade" class="smpl">Upgrade</a>   = "Upgrade" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.upgrade" class="smpl">Upgrade-v</a>
    18531922  <a href="#header.upgrade" class="smpl">Upgrade-v</a> = 1#<a href="#product.tokens" class="smpl">product</a>
    18541923</pre><p id="rfc.section.8.8.p.3">For example,</p>
    1855       <div id="rfc.figure.u.65"></div><pre class="text">  Upgrade: HTTP/2.0, SHTTP/1.3, IRC/6.9, RTA/x11
     1924      <div id="rfc.figure.u.66"></div><pre class="text">  Upgrade: HTTP/2.0, SHTTP/1.3, IRC/6.9, RTA/x11
    18561925</pre><p id="rfc.section.8.8.p.5">The Upgrade header field is intended to provide a simple mechanism for transition from HTTP/1.1 to some other, incompatible
    18571926         protocol. It does so by allowing the client to advertise its desire to use another protocol, such as a later version of HTTP
    … …  
    18721941      </p>
    18731942      <p id="rfc.section.8.8.p.9">This specification only defines the protocol name "HTTP" for use by the family of Hypertext Transfer Protocols, as defined
    1874          by the HTTP version rules of <a href="#http.version" title="HTTP Version">Section&nbsp;2.2</a> and future updates to this specification. Any token can be used as a protocol name; however, it will only be useful if both
     1943         by the HTTP version rules of <a href="#http.version" title="HTTP Version">Section&nbsp;2.5</a> and future updates to this specification. Any token can be used as a protocol name; however, it will only be useful if both
    18751944         the client and server associate the name with the same protocol.
    18761945      </p>
    … …  
    18821951         of all senders along the request/response chain.
    18831952      </p>
    1884       <div id="rfc.figure.u.66"></div><pre class="inline"><span id="rfc.iref.g.110"></span><span id="rfc.iref.g.111"></span><span id="rfc.iref.g.112"></span><span id="rfc.iref.g.113"></span><span id="rfc.iref.g.114"></span><span id="rfc.iref.g.115"></span><span id="rfc.iref.g.116"></span>  <a href="#header.via" class="smpl">Via</a>               = "Via" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.via" class="smpl">Via-v</a>
     1953      <div id="rfc.figure.u.67"></div><pre class="inline"><span id="rfc.iref.g.111"></span><span id="rfc.iref.g.112"></span><span id="rfc.iref.g.113"></span><span id="rfc.iref.g.114"></span><span id="rfc.iref.g.115"></span><span id="rfc.iref.g.116"></span><span id="rfc.iref.g.117"></span>  <a href="#header.via" class="smpl">Via</a>               = "Via" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.via" class="smpl">Via-v</a>
    18851954  <a href="#header.via" class="smpl">Via-v</a>             = 1#( <a href="#header.via" class="smpl">received-protocol</a> <a href="#rule.whitespace" class="smpl">RWS</a> <a href="#header.via" class="smpl">received-by</a>
    18861955                          [ <a href="#rule.whitespace" class="smpl">RWS</a> <a href="#rule.comment" class="smpl">comment</a> ] )
    … …  
    19071976         server at www.example.com. The request received by www.example.com would then have the following Via header field:
    19081977      </p>
    1909       <div id="rfc.figure.u.67"></div><pre class="text">  Via: 1.0 fred, 1.1 p.example.net (Apache/1.1)
     1978      <div id="rfc.figure.u.68"></div><pre class="text">  Via: 1.0 fred, 1.1 p.example.net (Apache/1.1)
    19101979</pre><p id="rfc.section.8.9.p.9">Proxies and gateways used as a portal through a network firewall <em class="bcp14">SHOULD NOT</em>, by default, forward the names and ports of hosts within the firewall region. This information <em class="bcp14">SHOULD</em> only be propagated if explicitly enabled. If not enabled, the received-by host of any host behind the firewall <em class="bcp14">SHOULD</em> be replaced by an appropriate pseudonym for that host.
    19111980      </p>
    … …  
    19131982         For example,
    19141983      </p>
    1915       <div id="rfc.figure.u.68"></div><pre class="text">  Via: 1.0 ricky, 1.1 ethel, 1.1 fred, 1.0 lucy
     1984      <div id="rfc.figure.u.69"></div><pre class="text">  Via: 1.0 ricky, 1.1 ethel, 1.1 fred, 1.0 lucy
    19161985</pre><p id="rfc.section.8.9.p.12">could be collapsed to</p>
    1917       <div id="rfc.figure.u.69"></div><pre class="text">  Via: 1.0 ricky, 1.1 mertz, 1.0 lucy
     1986      <div id="rfc.figure.u.70"></div><pre class="text">  Via: 1.0 ricky, 1.1 mertz, 1.0 lucy
    19181987</pre><p id="rfc.section.8.9.p.14">Applications <em class="bcp14">SHOULD NOT</em> combine multiple entries unless they are all under the same organizational control and the hosts have already been replaced
    19191988         by pseudonyms. Applications <em class="bcp14">MUST NOT</em> combine entries which have different received-protocol values.
    … …  
    20032072      <p id="rfc.section.9.1.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
    20042073      <h2 id="rfc.section.9.2"><a href="#rfc.section.9.2">9.2</a>&nbsp;<a id="uri.scheme.registration" href="#uri.scheme.registration">URI Scheme Registration</a></h2>
    2005       <p id="rfc.section.9.2.p.1">The entry for the "http" URI Scheme in the registry located at &lt;<a href="http://www.iana.org/assignments/uri-schemes.html">http://www.iana.org/assignments/uri-schemes.html</a>&gt; should be updated to point to <a href="#http.uri" title="http URI scheme">Section&nbsp;2.3.1</a> of this document (see <a href="#RFC4395" id="rfc.xref.RFC4395.1"><cite title="Guidelines and Registration Procedures for New URI Schemes">[RFC4395]</cite></a>).
     2074      <p id="rfc.section.9.2.p.1">The entry for the "http" URI Scheme in the registry located at &lt;<a href="http://www.iana.org/assignments/uri-schemes.html">http://www.iana.org/assignments/uri-schemes.html</a>&gt; should be updated to point to <a href="#http.uri" title="http URI scheme">Section&nbsp;2.6.1</a> of this document (see <a href="#RFC4395" id="rfc.xref.RFC4395.1"><cite title="Guidelines and Registration Procedures for New URI Schemes">[RFC4395]</cite></a>).
    20062075      </p>
    20072076      <h2 id="rfc.section.9.3"><a href="#rfc.section.9.3">9.3</a>&nbsp;<a id="internet.media.type.http" href="#internet.media.type.http">Internet Media Type Registrations</a></h2>
    … …  
    20092078         is to be registered with IANA (see <a href="#RFC4288" id="rfc.xref.RFC4288.1"><cite title="Media Type Specifications and Registration Procedures">[RFC4288]</cite></a>).
    20102079      </p>
    2011       <div id="rfc.iref.m.1"></div>
    20122080      <div id="rfc.iref.m.2"></div>
     2081      <div id="rfc.iref.m.3"></div>
    20132082      <h3 id="rfc.section.9.3.1"><a href="#rfc.section.9.3.1">9.3.1</a>&nbsp;<a id="internet.media.type.message.http" href="#internet.media.type.message.http">Internet Media Type message/http</a></h3>
    20142083      <p id="rfc.section.9.3.1.p.1">The message/http type can be used to enclose a single HTTP request or response message, provided that it obeys the MIME restrictions
    … …  
    20642133         <dd>IESG</dd>
    20652134      </dl>
    2066       <div id="rfc.iref.m.3"></div>
     2135      <div id="rfc.iref.m.4"></div>
    20672136      <div id="rfc.iref.a.1"></div>
    20682137      <h3 id="rfc.section.9.3.2"><a href="#rfc.section.9.3.2">9.3.2</a>&nbsp;<a id="internet.media.type.application.http" href="#internet.media.type.application.http">Internet Media Type application/http</a></h3>
    … …  
    24962565      </p>
    24972566      <p id="rfc.section.B.3.p.3">The use and interpretation of HTTP version numbers has been clarified by <a href="#RFC2145" id="rfc.xref.RFC2145.3"><cite title="Use and Interpretation of HTTP Version Numbers">[RFC2145]</cite></a>. Require proxies to upgrade requests to highest protocol version they support to deal with problems discovered in HTTP/1.0
    2498          implementations (<a href="#http.version" title="HTTP Version">Section&nbsp;2.2</a>)
     2567         implementations (<a href="#http.version" title="HTTP Version">Section&nbsp;2.5</a>)
    24992568      </p>
    25002569      <p id="rfc.section.B.3.p.4">Quality Values of zero should indicate that "I don't want something" to allow clients to refuse a representation. (<a href="#quality.values" title="Quality Values">Section&nbsp;6.4</a>)
    … …  
    25142583         (the TEXT rule was removed) (<a href="#basic.rules" title="Basic Rules">Section&nbsp;1.2.2</a>)
    25152584      </p>
    2516       <p id="rfc.section.B.4.p.3">Clarify that HTTP-Version is case sensitive. (<a href="#http.version" title="HTTP Version">Section&nbsp;2.2</a>)
     2585      <p id="rfc.section.B.4.p.3">Clarify that HTTP-Version is case sensitive. (<a href="#http.version" title="HTTP Version">Section&nbsp;2.5</a>)
    25172586      </p>
    25182587      <p id="rfc.section.B.4.p.4">Remove reference to non-existant identity transfer-coding value tokens. (Sections <a href="#transfer.codings" title="Transfer Codings">6.2</a> and <a href="#message.length" title="Message Length">3.4</a>)
    … …  
    25282597      <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="terminology" href="#terminology">Terminology</a></h1>
    25292598      <p id="rfc.section.C.p.1">This specification uses a number of terms to refer to the roles played by participants in, and objects of, the HTTP communication.</p>
    2530       <p id="rfc.section.C.p.2"> <span id="rfc.iref.c.3"></span>  <dfn>cache</dfn> 
    2531       </p>
    2532       <dl class="empty">
    2533          <dd>A program's local store of response messages and the subsystem that controls its message storage, retrieval, and deletion.
    2534             A cache stores cacheable responses in order to reduce the response time and network bandwidth consumption on future, equivalent
    2535             requests. Any client or server may include a cache, though a cache cannot be used by a server that is acting as a tunnel.
    2536          </dd>
    2537       </dl>
    2538       <p id="rfc.section.C.p.3"> <span id="rfc.iref.c.4"></span>  <dfn>cacheable</dfn> 
    2539       </p>
    2540       <dl class="empty">
    2541          <dd>A response is cacheable if a cache is allowed to store a copy of the response message for use in answering subsequent requests.
    2542             The rules for determining the cacheability of HTTP responses are defined in <a href="p6-cache.html#caching" title="Introduction">Section 1</a> of <a href="#Part6" id="rfc.xref.Part6.9"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>. Even if a resource is cacheable, there may be additional constraints on whether a cache can use the cached copy for a particular
    2543             request.
    2544          </dd>
    2545       </dl>
    2546       <p id="rfc.section.C.p.4"> <span id="rfc.iref.c.5"></span>  <dfn>client</dfn> 
    2547       </p>
    2548       <dl class="empty">
    2549          <dd>A program that establishes connections for the purpose of sending requests.</dd>
    2550       </dl>
    2551       <p id="rfc.section.C.p.5"> <span id="rfc.iref.c.6"></span>  <dfn>connection</dfn> 
    2552       </p>
    2553       <dl class="empty">
    2554          <dd>A transport layer virtual circuit established between two programs for the purpose of communication.</dd>
    2555       </dl>
    2556       <p id="rfc.section.C.p.6"> <span id="rfc.iref.c.7"></span>  <dfn>content negotiation</dfn> 
     2599      <p id="rfc.section.C.p.2"> <span id="rfc.iref.c.7"></span>  <dfn>content negotiation</dfn> 
    25572600      </p>
    25582601      <dl class="empty">
    … …  
    25602603         </dd>
    25612604      </dl>
    2562       <p id="rfc.section.C.p.7"> <span id="rfc.iref.e.1"></span>  <dfn>entity</dfn> 
     2605      <p id="rfc.section.C.p.3"> <span id="rfc.iref.e.1"></span>  <dfn>entity</dfn> 
    25632606      </p>
    25642607      <dl class="empty">
    … …  
    25672610         </dd>
    25682611      </dl>
    2569       <p id="rfc.section.C.p.8"> <span id="rfc.iref.g.117"></span>  <dfn>gateway</dfn> 
    2570       </p>
    2571       <dl class="empty">
    2572          <dd>A server which acts as an intermediary for some other server. Unlike a proxy, a gateway receives requests as if it were the
    2573             origin server for the requested resource; the requesting client may not be aware that it is communicating with a gateway.
    2574          </dd>
    2575       </dl>
    2576       <p id="rfc.section.C.p.9"> <span id="rfc.iref.i.1"></span>  <span id="rfc.iref.o.1"></span>  <dfn>inbound</dfn>/<dfn>outbound</dfn> 
    2577       </p>
    2578       <dl class="empty">
    2579          <dd>Inbound and outbound refer to the request and response paths for messages: "inbound" means "traveling toward the origin server",
    2580             and "outbound" means "traveling toward the user agent"
    2581          </dd>
    2582       </dl>
    2583       <p id="rfc.section.C.p.10"> <span id="rfc.iref.m.4"></span>  <dfn>message</dfn> 
    2584       </p>
    2585       <dl class="empty">
    2586          <dd>The basic unit of HTTP communication, consisting of a structured sequence of octets matching the syntax defined in <a href="#http.message" title="HTTP Message">Section&nbsp;3</a> and transmitted via the connection.
    2587          </dd>
    2588       </dl>
    2589       <p id="rfc.section.C.p.11"> <span id="rfc.iref.o.2"></span>  <dfn>origin server</dfn> 
    2590       </p>
    2591       <dl class="empty">
    2592          <dd>The server on which a given resource resides or is to be created.</dd>
    2593       </dl>
    2594       <p id="rfc.section.C.p.12"> <span id="rfc.iref.p.1"></span>  <dfn>proxy</dfn> 
    2595       </p>
    2596       <dl class="empty">
    2597          <dd>An intermediary program which acts as both a server and a client for the purpose of making requests on behalf of other clients.
    2598             Requests are serviced internally or by passing them on, with possible translation, to other servers. A proxy <em class="bcp14">MUST</em> implement both the client and server requirements of this specification. A "transparent proxy" is a proxy that does not modify
    2599             the request or response beyond what is required for proxy authentication and identification. A "non-transparent proxy" is
    2600             a proxy that modifies the request or response in order to provide some added service to the user agent, such as group annotation
    2601             services, media type transformation, protocol reduction, or anonymity filtering. Except where either transparent or non-transparent
    2602             behavior is explicitly stated, the HTTP proxy requirements apply to both types of proxies.
    2603          </dd>
    2604       </dl>
    2605       <p id="rfc.section.C.p.13"> <span id="rfc.iref.r.2"></span>  <dfn>request</dfn> 
    2606       </p>
    2607       <dl class="empty">
    2608          <dd>An HTTP request message, as defined in <a href="#request" title="Request">Section&nbsp;4</a>.
    2609          </dd>
    2610       </dl>
    2611       <p id="rfc.section.C.p.14"> <span id="rfc.iref.r.3"></span>  <dfn>response</dfn> 
    2612       </p>
    2613       <dl class="empty">
    2614          <dd>An HTTP response message, as defined in <a href="#response" title="Response">Section&nbsp;5</a>.
    2615          </dd>
    2616       </dl>
    2617       <p id="rfc.section.C.p.15"> <span id="rfc.iref.r.4"></span>  <dfn>representation</dfn> 
     2612      <p id="rfc.section.C.p.4"> <span id="rfc.iref.r.5"></span>  <dfn>representation</dfn> 
    26182613      </p>
    26192614      <dl class="empty">
    … …  
    26212616         </dd>
    26222617      </dl>
    2623       <p id="rfc.section.C.p.16"> <span id="rfc.iref.s.1"></span>  <dfn>server</dfn> 
    2624       </p>
    2625       <dl class="empty">
    2626          <dd>An application program that accepts connections in order to service requests by sending back responses. Any given program
    2627             may be capable of being both a client and a server; our use of these terms refers only to the role being performed by the
    2628             program for a particular connection, rather than to the program's capabilities in general. Likewise, any server may act as
    2629             an origin server, proxy, gateway, or tunnel, switching behavior based on the nature of each request.
    2630          </dd>
    2631       </dl>
    2632       <p id="rfc.section.C.p.17"> <span id="rfc.iref.t.4"></span>  <dfn>tunnel</dfn> 
    2633       </p>
    2634       <dl class="empty">
    2635          <dd>An intermediary program which is acting as a blind relay between two connections. Once active, a tunnel is not considered
    2636             a party to the HTTP communication, though the tunnel may have been initiated by an HTTP request. The tunnel ceases to exist
    2637             when both ends of the relayed connections are closed.
    2638          </dd>
    2639       </dl>
    2640       <p id="rfc.section.C.p.18"> <span id="rfc.iref.u.4"></span>  <span id="rfc.iref.d.2"></span>  <dfn>upstream</dfn>/<dfn>downstream</dfn> 
    2641       </p>
    2642       <dl class="empty">
    2643          <dd>Upstream and downstream describe the flow of a message: all messages flow from upstream to downstream.</dd>
    2644       </dl>
    2645       <p id="rfc.section.C.p.19"> <span id="rfc.iref.u.5"></span>  <dfn>user agent</dfn> 
    2646       </p>
    2647       <dl class="empty">
    2648          <dd>The client which initiates a request. These are often browsers, editors, spiders (web-traversing robots), or other end user
    2649             tools.
    2650          </dd>
    2651       </dl>
    2652       <p id="rfc.section.C.p.20"> <span id="rfc.iref.v.2"></span>  <dfn>variant</dfn> 
     2618      <p id="rfc.section.C.p.5"> <span id="rfc.iref.v.2"></span>  <dfn>variant</dfn> 
    26532619      </p>
    26542620      <dl class="empty">
    … …  
    26582624      </dl>
    26592625      <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
    2660       <div id="rfc.figure.u.70"></div> <pre class="inline"><a href="#rule.whitespace" class="smpl">BWS</a> = OWS
     2626      <div id="rfc.figure.u.71"></div> <pre class="inline"><a href="#rule.whitespace" class="smpl">BWS</a> = OWS
    26612627
    26622628<a href="#abnf.dependencies" class="smpl">Cache-Control</a> = &lt;Cache-Control, defined in [Part6], Section 3.4&gt;
    … …  
    28432809
    28442810<a href="#preferred.date.format" class="smpl">year</a> = 4DIGIT
    2845 </pre> <div id="rfc.figure.u.71"></div>
     2811</pre> <div id="rfc.figure.u.72"></div>
    28462812      <p>ABNF diagnostics:</p><pre class="inline">; Chunked-Body defined but not used
    28472813; Content-Length defined but not used
    … …  
    30633029            </li>
    30643030            <li class="indline0"><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul class="ind">
    3065                   <li class="indline1">cache&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.3">C</a></li>
    3066                   <li class="indline1">cacheable&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.4">C</a></li>
    3067                   <li class="indline1">client&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.5">C</a></li>
    3068                   <li class="indline1">connection&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.6">C</a></li>
    3069                   <li class="indline1">Connection header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.connection.1">3.5</a>, <a class="iref" href="#rfc.xref.header.connection.2">7.1.2</a>, <a class="iref" href="#rfc.xref.header.connection.3">7.1.3</a>, <a class="iref" href="#rfc.iref.c.1"><b>8.1</b></a>, <a class="iref" href="#rfc.xref.header.connection.4">8.5</a>, <a class="iref" href="#rfc.xref.header.connection.5">8.8</a>, <a class="iref" href="#rfc.xref.header.connection.6">9.1</a>, <a class="iref" href="#rfc.xref.header.connection.7">B.2</a>, <a class="iref" href="#rfc.xref.header.connection.8">B.4</a></li>
     3031                  <li class="indline1">cache&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.3">2.3</a></li>
     3032                  <li class="indline1">cacheable&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.4">2.3</a></li>
     3033                  <li class="indline1">client&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.1">2.1</a></li>
     3034                  <li class="indline1">connection&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.2">2.1</a></li>
     3035                  <li class="indline1">Connection header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.connection.1">3.5</a>, <a class="iref" href="#rfc.xref.header.connection.2">7.1.2</a>, <a class="iref" href="#rfc.xref.header.connection.3">7.1.3</a>, <a class="iref" href="#rfc.iref.c.5"><b>8.1</b></a>, <a class="iref" href="#rfc.xref.header.connection.4">8.5</a>, <a class="iref" href="#rfc.xref.header.connection.5">8.8</a>, <a class="iref" href="#rfc.xref.header.connection.6">9.1</a>, <a class="iref" href="#rfc.xref.header.connection.7">B.2</a>, <a class="iref" href="#rfc.xref.header.connection.8">B.4</a></li>
    30703036                  <li class="indline1">content negotiation&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.7">C</a></li>
    3071                   <li class="indline1">Content-Length header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-length.1">3.4</a>, <a class="iref" href="#rfc.iref.c.2"><b>8.2</b></a>, <a class="iref" href="#rfc.xref.header.content-length.2">9.1</a>, <a class="iref" href="#rfc.xref.header.content-length.3">B.3</a></li>
     3037                  <li class="indline1">Content-Length header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-length.1">3.4</a>, <a class="iref" href="#rfc.iref.c.6"><b>8.2</b></a>, <a class="iref" href="#rfc.xref.header.content-length.2">9.1</a>, <a class="iref" href="#rfc.xref.header.content-length.3">B.3</a></li>
    30723038               </ul>
    30733039            </li>
    30743040            <li class="indline0"><a id="rfc.index.D" href="#rfc.index.D"><b>D</b></a><ul class="ind">
    3075                   <li class="indline1">Date header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.date.1">3.5</a>, <a class="iref" href="#rfc.iref.d.1"><b>8.3</b></a>, <a class="iref" href="#rfc.xref.header.date.2">9.1</a></li>
    3076                   <li class="indline1">downstream&nbsp;&nbsp;<a class="iref" href="#rfc.iref.d.2">C</a></li>
     3041                  <li class="indline1">Date header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.date.1">3.5</a>, <a class="iref" href="#rfc.iref.d.2"><b>8.3</b></a>, <a class="iref" href="#rfc.xref.header.date.2">9.1</a></li>
     3042                  <li class="indline1">downstream&nbsp;&nbsp;<a class="iref" href="#rfc.iref.d.1">2.2</a></li>
    30773043               </ul>
    30783044            </li>
    … …  
    30823048            </li>
    30833049            <li class="indline0"><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul class="ind">
    3084                   <li class="indline1">gateway&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.117">C</a></li>
     3050                  <li class="indline1">gateway&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.23">2.2</a></li>
    30853051                  <li class="indline1"><tt>Grammar</tt>&nbsp;&nbsp;
    30863052                     <ul class="ind">
    3087                         <li class="indline1"><tt>absolute-URI</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.26"><b>2.3</b></a></li>
     3053                        <li class="indline1"><tt>absolute-URI</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.27"><b>2.6</b></a></li>
    30883054                        <li class="indline1">ALPHA&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.1"><b>1.2</b></a></li>
    3089                         <li class="indline1"><tt>asctime-date</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.70"><b>6.1</b></a></li>
    3090                         <li class="indline1"><tt>attribute</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.74"><b>6.2</b></a></li>
    3091                         <li class="indline1"><tt>authority</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.27"><b>2.3</b></a></li>
     3055                        <li class="indline1"><tt>asctime-date</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.71"><b>6.1</b></a></li>
     3056                        <li class="indline1"><tt>attribute</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.75"><b>6.2</b></a></li>
     3057                        <li class="indline1"><tt>authority</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.28"><b>2.6</b></a></li>
    30923058                        <li class="indline1"><tt>BWS</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.15"><b>1.2.2</b></a></li>
    3093                         <li class="indline1"><tt>chunk</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.79"><b>6.2.1</b></a></li>
    3094                         <li class="indline1"><tt>chunk-data</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.85"><b>6.2.1</b></a></li>
    3095                         <li class="indline1"><tt>chunk-ext</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.82"><b>6.2.1</b></a></li>
    3096                         <li class="indline1"><tt>chunk-ext-name</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.83"><b>6.2.1</b></a></li>
    3097                         <li class="indline1"><tt>chunk-ext-val</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.84"><b>6.2.1</b></a></li>
    3098                         <li class="indline1"><tt>chunk-size</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.80"><b>6.2.1</b></a></li>
    3099                         <li class="indline1"><tt>Chunked-Body</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.78"><b>6.2.1</b></a></li>
    3100                         <li class="indline1"><tt>comment</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.41"><b>3.2</b></a></li>
    3101                         <li class="indline1"><tt>Connection</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.90"><b>8.1</b></a></li>
    3102                         <li class="indline1"><tt>connection-token</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.92"><b>8.1</b></a></li>
    3103                         <li class="indline1"><tt>Connection-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.91"><b>8.1</b></a></li>
    3104                         <li class="indline1"><tt>Content-Length</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.93"><b>8.2</b></a></li>
    3105                         <li class="indline1"><tt>Content-Length-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.94"><b>8.2</b></a></li>
     3059                        <li class="indline1"><tt>chunk</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.80"><b>6.2.1</b></a></li>
     3060                        <li class="indline1"><tt>chunk-data</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.86"><b>6.2.1</b></a></li>
     3061                        <li class="indline1"><tt>chunk-ext</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.83"><b>6.2.1</b></a></li>
     3062                        <li class="indline1"><tt>chunk-ext-name</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.84"><b>6.2.1</b></a></li>
     3063                        <li class="indline1"><tt>chunk-ext-val</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.85"><b>6.2.1</b></a></li>
     3064                        <li class="indline1"><tt>chunk-size</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.81"><b>6.2.1</b></a></li>
     3065                        <li class="indline1"><tt>Chunked-Body</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.79"><b>6.2.1</b></a></li>
     3066                        <li class="indline1"><tt>comment</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.42"><b>3.2</b></a></li>
     3067                        <li class="indline1"><tt>Connection</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.91"><b>8.1</b></a></li>
     3068                        <li class="indline1"><tt>connection-token</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.93"><b>8.1</b></a></li>
     3069                        <li class="indline1"><tt>Connection-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.92"><b>8.1</b></a></li>
     3070                        <li class="indline1"><tt>Content-Length</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.94"><b>8.2</b></a></li>
     3071                        <li class="indline1"><tt>Content-Length-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.95"><b>8.2</b></a></li>
    31063072                        <li class="indline1">CR&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.2"><b>1.2</b></a></li>
    31073073                        <li class="indline1">CRLF&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.3"><b>1.2</b></a></li>
    3108                         <li class="indline1"><tt>ctext</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.42"><b>3.2</b></a></li>
     3074                        <li class="indline1"><tt>ctext</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.43"><b>3.2</b></a></li>
    31093075                        <li class="indline1">CTL&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.4"><b>1.2</b></a></li>
    3110                         <li class="indline1"><tt>Date</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.95"><b>8.3</b></a></li>
    3111                         <li class="indline1"><tt>Date-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.96"><b>8.3</b></a></li>
    3112                         <li class="indline1"><tt>date1</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.57"><b>6.1</b></a></li>
    3113                         <li class="indline1"><tt>date2</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.76"><b>6.2</b></a></li>
    3114                         <li class="indline1"><tt>date3</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.77"><b>6.2</b></a></li>
    3115                         <li class="indline1"><tt>day</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.64"><b>6.1</b></a></li>
    3116                         <li class="indline1"><tt>day-name</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.62"><b>6.1</b></a></li>
    3117                         <li class="indline1"><tt>day-name-l</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.63"><b>6.1</b></a></li>
     3076                        <li class="indline1"><tt>Date</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.96"><b>8.3</b></a></li>
     3077                        <li class="indline1"><tt>Date-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.97"><b>8.3</b></a></li>
     3078                        <li class="indline1"><tt>date1</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.58"><b>6.1</b></a></li>
     3079                        <li class="indline1"><tt>date2</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.77"><b>6.2</b></a></li>
     3080                        <li class="indline1"><tt>date3</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.78"><b>6.2</b></a></li>
     3081                        <li class="indline1"><tt>day</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.65"><b>6.1</b></a></li>
     3082                        <li class="indline1"><tt>day-name</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.63"><b>6.1</b></a></li>
     3083                        <li class="indline1"><tt>day-name-l</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.64"><b>6.1</b></a></li>
    31183084                        <li class="indline1">DIGIT&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.5"><b>1.2</b></a></li>
    31193085                        <li class="indline1">DQUOTE&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.6"><b>1.2</b></a></li>
    3120                         <li class="indline1"><tt>extension-code</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.53"><b>5.1.1</b></a></li>
    3121                         <li class="indline1"><tt>extension-method</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.48"><b>4.1.1</b></a></li>
    3122                         <li class="indline1"><tt>field-content</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.40"><b>3.2</b></a></li>
    3123                         <li class="indline1"><tt>field-name</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.38"><b>3.2</b></a></li>
    3124                         <li class="indline1"><tt>field-value</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.39"><b>3.2</b></a></li>
    3125                         <li class="indline1"><tt>general-header</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.44"><b>3.5</b></a></li>
    3126                         <li class="indline1"><tt>generic-message</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.35"><b>3.1</b></a></li>
    3127                         <li class="indline1"><tt>GMT</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.67"><b>6.1</b></a></li>
     3086                        <li class="indline1"><tt>extension-code</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.54"><b>5.1.1</b></a></li>
     3087                        <li class="indline1"><tt>extension-method</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.49"><b>4.1.1</b></a></li>
     3088                        <li class="indline1"><tt>field-content</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.41"><b>3.2</b></a></li>
     3089                        <li class="indline1"><tt>field-name</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.39"><b>3.2</b></a></li>
     3090                        <li class="indline1"><tt>field-value</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.40"><b>3.2</b></a></li>
     3091                        <li class="indline1"><tt>general-header</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.45"><b>3.5</b></a></li>
     3092                        <li class="indline1"><tt>generic-message</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.36"><b>3.1</b></a></li>
     3093                        <li class="indline1"><tt>GMT</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.68"><b>6.1</b></a></li>
    31283094                        <li class="indline1">HEXDIG&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.7"><b>1.2</b></a></li>
    3129                         <li class="indline1"><tt>Host</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.97"><b>8.4</b></a></li>
    3130                         <li class="indline1"><tt>Host-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.98"><b>8.4</b></a></li>
    3131                         <li class="indline1"><tt>hour</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.59"><b>6.1</b></a></li>
    3132                         <li class="indline1"><tt>HTTP-date</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.55"><b>6.1</b></a></li>
    3133                         <li class="indline1"><tt>HTTP-message</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.34"><b>3.1</b></a></li>
    3134                         <li class="indline1"><tt>HTTP-Prot-Name</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.24"><b>2.2</b></a></li>
    3135                         <li class="indline1"><tt>http-URI</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.32"><b>2.3.1</b></a></li>
    3136                         <li class="indline1"><tt>HTTP-Version</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.23"><b>2.2</b></a></li>
    3137                         <li class="indline1"><tt>https-URI</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.33"><b>2.3.2</b></a></li>
    3138                         <li class="indline1"><tt>last-chunk</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.81"><b>6.2.1</b></a></li>
     3095                        <li class="indline1"><tt>Host</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.98"><b>8.4</b></a></li>
     3096                        <li class="indline1"><tt>Host-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.99"><b>8.4</b></a></li>
     3097                        <li class="indline1"><tt>hour</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.60"><b>6.1</b></a></li>
     3098                        <li class="indline1"><tt>HTTP-date</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.56"><b>6.1</b></a></li>
     3099                        <li class="indline1"><tt>HTTP-message</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.35"><b>3.1</b></a></li>
     3100                        <li class="indline1"><tt>HTTP-Prot-Name</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.25"><b>2.5</b></a></li>
     3101                        <li class="indline1"><tt>http-URI</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.33"><b>2.6.1</b></a></li>
     3102                        <li class="indline1"><tt>HTTP-Version</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.24"><b>2.5</b></a></li>
     3103                        <li class="indline1"><tt>https-URI</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.34"><b>2.6.2</b></a></li>
     3104                        <li class="indline1"><tt>last-chunk</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.82"><b>6.2.1</b></a></li>
    31393105                        <li class="indline1">LF&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.8"><b>1.2</b></a></li>
    3140                         <li class="indline1"><tt>message-body</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.43"><b>3.3</b></a></li>
    3141                         <li class="indline1"><tt>message-header</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.37"><b>3.2</b></a></li>
    3142                         <li class="indline1"><tt>Method</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.47"><b>4.1.1</b></a></li>
    3143                         <li class="indline1"><tt>minute</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.60"><b>6.1</b></a></li>
    3144                         <li class="indline1"><tt>month</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.65"><b>6.1</b></a></li>
    3145                         <li class="indline1"><tt>obs-date</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.68"><b>6.1</b></a></li>
     3106                        <li class="indline1"><tt>message-body</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.44"><b>3.3</b></a></li>
     3107                        <li class="indline1"><tt>message-header</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.38"><b>3.2</b></a></li>
     3108                        <li class="indline1"><tt>Method</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.48"><b>4.1.1</b></a></li>
     3109                        <li class="indline1"><tt>minute</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.61"><b>6.1</b></a></li>
     3110                        <li class="indline1"><tt>month</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.66"><b>6.1</b></a></li>
     3111                        <li class="indline1"><tt>obs-date</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.69"><b>6.1</b></a></li>
    31463112                        <li class="indline1"><tt>obs-text</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.20"><b>1.2.2</b></a></li>
    31473113                        <li class="indline1">OCTET&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.9"><b>1.2</b></a></li>
    31483114                        <li class="indline1"><tt>OWS</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.13"><b>1.2.2</b></a></li>
    3149                         <li class="indline1"><tt>path-absolute</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.28"><b>2.3</b></a></li>
    3150                         <li class="indline1"><tt>port</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.29"><b>2.3</b></a></li>
    3151                         <li class="indline1"><tt>product</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.87"><b>6.3</b></a></li>
    3152                         <li class="indline1"><tt>product-version</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.88"><b>6.3</b></a></li>
    3153                         <li class="indline1"><tt>protocol-name</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.113"><b>8.9</b></a></li>
    3154                         <li class="indline1"><tt>protocol-version</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.114"><b>8.9</b></a></li>
    3155                         <li class="indline1"><tt>pseudonym</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.116"><b>8.9</b></a></li>
     3115                        <li class="indline1"><tt>path-absolute</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.29"><b>2.6</b></a></li>
     3116                        <li class="indline1"><tt>port</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.30"><b>2.6</b></a></li>
     3117                        <li class="indline1"><tt>product</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.88"><b>6.3</b></a></li>
     3118                        <li class="indline1"><tt>product-version</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.89"><b>6.3</b></a></li>
     3119                        <li class="indline1"><tt>protocol-name</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.114"><b>8.9</b></a></li>
     3120                        <li class="indline1"><tt>protocol-version</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.115"><b>8.9</b></a></li>
     3121                        <li class="indline1"><tt>pseudonym</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.117"><b>8.9</b></a></li>
    31563122                        <li class="indline1"><tt>qdtext</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.19"><b>1.2.2</b></a></li>
    3157                         <li class="indline1"><tt>query</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.30"><b>2.3</b></a></li>
     3123                        <li class="indline1"><tt>query</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.31"><b>2.6</b></a></li>
    31583124                        <li class="indline1"><tt>quoted-pair</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.22"><b>1.2.2</b></a></li>
    31593125                        <li class="indline1"><tt>quoted-string</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.18"><b>1.2.2</b></a></li>
    31603126                        <li class="indline1"><tt>quoted-text</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.21"><b>1.2.2</b></a></li>
    3161                         <li class="indline1"><tt>qvalue</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.89"><b>6.4</b></a></li>
    3162                         <li class="indline1"><tt>Reason-Phrase</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.54"><b>5.1.1</b></a></li>
    3163                         <li class="indline1"><tt>received-by</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.115"><b>8.9</b></a></li>
    3164                         <li class="indline1"><tt>received-protocol</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.112"><b>8.9</b></a></li>
    3165                         <li class="indline1"><tt>Request</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.45"><b>4</b></a></li>
    3166                         <li class="indline1"><tt>Request-Line</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.46"><b>4.1</b></a></li>
    3167                         <li class="indline1"><tt>request-target</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.49"><b>4.1.2</b></a></li>
    3168                         <li class="indline1"><tt>Response</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.50"><b>5</b></a></li>
    3169                         <li class="indline1"><tt>rfc1123-date</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.56"><b>6.1</b></a></li>
    3170                         <li class="indline1"><tt>rfc850-date</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.69"><b>6.1</b></a></li>
     3127                        <li class="indline1"><tt>qvalue</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.90"><b>6.4</b></a></li>
     3128                        <li class="indline1"><tt>Reason-Phrase</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.55"><b>5.1.1</b></a></li>
     3129                        <li class="indline1"><tt>received-by</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.116"><b>8.9</b></a></li>
     3130                        <li class="indline1"><tt>received-protocol</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.113"><b>8.9</b></a></li>
     3131                        <li class="indline1"><tt>Request</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.46"><b>4</b></a></li>
     3132                        <li class="indline1"><tt>Request-Line</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.47"><b>4.1</b></a></li>
     3133                        <li class="indline1"><tt>request-target</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.50"><b>4.1.2</b></a></li>
     3134                        <li class="indline1"><tt>Response</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.51"><b>5</b></a></li>
     3135                        <li class="indline1"><tt>rfc1123-date</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.57"><b>6.1</b></a></li>
     3136                        <li class="indline1"><tt>rfc850-date</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.70"><b>6.1</b></a></li>
    31713137                        <li class="indline1"><tt>RWS</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.14"><b>1.2.2</b></a></li>
    3172                         <li class="indline1"><tt>second</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.61"><b>6.1</b></a></li>
     3138                        <li class="indline1"><tt>second</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.62"><b>6.1</b></a></li>
    31733139                        <li class="indline1">SP&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.10"><b>1.2</b></a></li>
    3174                         <li class="indline1"><tt>start-line</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.36"><b>3.1</b></a></li>
    3175                         <li class="indline1"><tt>Status-Code</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.52"><b>5.1.1</b></a></li>
    3176                         <li class="indline1"><tt>Status-Line</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.51"><b>5.1</b></a></li>
    3177                         <li class="indline1"><tt>t-codings</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.101"><b>8.5</b></a></li>
     3140                        <li class="indline1"><tt>start-line</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.37"><b>3.1</b></a></li>
     3141                        <li class="indline1"><tt>Status-Code</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.53"><b>5.1.1</b></a></li>
     3142                        <li class="indline1"><tt>Status-Line</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.52"><b>5.1</b></a></li>
     3143                        <li class="indline1"><tt>t-codings</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.102"><b>8.5</b></a></li>
    31783144                        <li class="indline1"><tt>tchar</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.17"><b>1.2.2</b></a></li>
    3179                         <li class="indline1"><tt>TE</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.99"><b>8.5</b></a></li>
    3180                         <li class="indline1"><tt>te-ext</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.103"><b>8.5</b></a></li>
    3181                         <li class="indline1"><tt>te-params</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.102"><b>8.5</b></a></li>
    3182                         <li class="indline1"><tt>TE-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.100"><b>8.5</b></a></li>
    3183                         <li class="indline1"><tt>time-of-day</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.58"><b>6.1</b></a></li>
     3145                        <li class="indline1"><tt>TE</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.100"><b>8.5</b></a></li>
     3146                        <li class="indline1"><tt>te-ext</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.104"><b>8.5</b></a></li>
     3147                        <li class="indline1"><tt>te-params</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.103"><b>8.5</b></a></li>
     3148                        <li class="indline1"><tt>TE-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.101"><b>8.5</b></a></li>
     3149                        <li class="indline1"><tt>time-of-day</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.59"><b>6.1</b></a></li>
    31843150                        <li class="indline1"><tt>token</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.16"><b>1.2.2</b></a></li>
    3185                         <li class="indline1"><tt>Trailer</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.104"><b>8.6</b></a></li>
    3186                         <li class="indline1"><tt>trailer-part</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.86"><b>6.2.1</b></a></li>
    3187                         <li class="indline1"><tt>Trailer-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.105"><b>8.6</b></a></li>
    3188                         <li class="indline1"><tt>transfer-coding</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.71"><b>6.2</b></a></li>
    3189                         <li class="indline1"><tt>Transfer-Encoding</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.106"><b>8.7</b></a></li>
    3190                         <li class="indline1"><tt>Transfer-Encoding-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.107"><b>8.7</b></a></li>
    3191                         <li class="indline1"><tt>transfer-extension</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.72"><b>6.2</b></a></li>
    3192                         <li class="indline1"><tt>transfer-parameter</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.73"><b>6.2</b></a></li>
    3193                         <li class="indline1"><tt>Upgrade</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.108"><b>8.8</b></a></li>
    3194                         <li class="indline1"><tt>Upgrade-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.109"><b>8.8</b></a></li>
    3195                         <li class="indline1"><tt>uri-host</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.31"><b>2.3</b></a></li>
    3196                         <li class="indline1"><tt>URI-reference</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.25"><b>2.3</b></a></li>
    3197                         <li class="indline1"><tt>value</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.75"><b>6.2</b></a></li>
     3151                        <li class="indline1"><tt>Trailer</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.105"><b>8.6</b></a></li>
     3152                        <li class="indline1"><tt>trailer-part</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.87"><b>6.2.1</b></a></li>
     3153                        <li class="indline1"><tt>Trailer-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.106"><b>8.6</b></a></li>
     3154                        <li class="indline1"><tt>transfer-coding</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.72"><b>6.2</b></a></li>
     3155                        <li class="indline1"><tt>Transfer-Encoding</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.107"><b>8.7</b></a></li>
     3156                        <li class="indline1"><tt>Transfer-Encoding-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.108"><b>8.7</b></a></li>
     3157                        <li class="indline1"><tt>transfer-extension</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.73"><b>6.2</b></a></li>
     3158                        <li class="indline1"><tt>transfer-parameter</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.74"><b>6.2</b></a></li>
     3159                        <li class="indline1"><tt>Upgrade</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.109"><b>8.8</b></a></li>
     3160                        <li class="indline1"><tt>Upgrade-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.110"><b>8.8</b></a></li>
     3161                        <li class="indline1"><tt>uri-host</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.32"><b>2.6</b></a></li>
     3162                        <li class="indline1"><tt>URI-reference</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.26"><b>2.6</b></a></li>
     3163                        <li class="indline1"><tt>value</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.76"><b>6.2</b></a></li>
    31983164                        <li class="indline1">VCHAR&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.11"><b>1.2</b></a></li>
    3199                         <li class="indline1"><tt>Via</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.110"><b>8.9</b></a></li>
    3200                         <li class="indline1"><tt>Via-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.111"><b>8.9</b></a></li>
     3165                        <li class="indline1"><tt>Via</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.111"><b>8.9</b></a></li>
     3166                        <li class="indline1"><tt>Via-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.112"><b>8.9</b></a></li>
    32013167                        <li class="indline1">WSP&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.12"><b>1.2</b></a></li>
    3202                         <li class="indline1"><tt>year</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.66"><b>6.1</b></a></li>
     3168                        <li class="indline1"><tt>year</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.67"><b>6.1</b></a></li>
    32033169                     </ul>
    32043170                  </li>
    … …  
    32203186                  </li>
    32213187                  <li class="indline1">Host header&nbsp;&nbsp;<a class="iref" href="#rfc.iref.h.6"><b>8.4</b></a>, <a class="iref" href="#rfc.xref.header.host.1">9.1</a>, <a class="iref" href="#rfc.xref.header.host.2">B.1.1</a></li>
    3222                   <li class="indline1">http URI scheme&nbsp;&nbsp;<a class="iref" href="#rfc.iref.h.1"><b>2.3.1</b></a></li>
    3223                   <li class="indline1">https URI scheme&nbsp;&nbsp;<a class="iref" href="#rfc.iref.h.2">2.3.2</a></li>
     3188                  <li class="indline1">http URI scheme&nbsp;&nbsp;<a class="iref" href="#rfc.iref.h.1"><b>2.6.1</b></a></li>
     3189                  <li class="indline1">https URI scheme&nbsp;&nbsp;<a class="iref" href="#rfc.iref.h.2">2.6.2</a></li>
    32243190               </ul>
    32253191            </li>
    32263192            <li class="indline0"><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul class="ind">
    3227                   <li class="indline1">inbound&nbsp;&nbsp;<a class="iref" href="#rfc.iref.i.1">C</a></li>
     3193                  <li class="indline1">inbound&nbsp;&nbsp;<a class="iref" href="#rfc.iref.i.1">2.2</a></li>
    32283194                  <li class="indline1"><em>ISO-8859-1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.ISO-8859-1.1">3.2</a>, <a class="iref" href="#ISO-8859-1"><b>12.1</b></a></li>
    32293195               </ul>
    … …  
    32363202                  <li class="indline1">Media Type&nbsp;&nbsp;
    32373203                     <ul class="ind">
    3238                         <li class="indline1">application/http&nbsp;&nbsp;<a class="iref" href="#rfc.iref.m.3"><b>9.3.2</b></a></li>
    3239                         <li class="indline1">message/http&nbsp;&nbsp;<a class="iref" href="#rfc.iref.m.1"><b>9.3.1</b></a></li>
     3204                        <li class="indline1">application/http&nbsp;&nbsp;<a class="iref" href="#rfc.iref.m.4"><b>9.3.2</b></a></li>
     3205                        <li class="indline1">message/http&nbsp;&nbsp;<a class="iref" href="#rfc.iref.m.2"><b>9.3.1</b></a></li>
    32403206                     </ul>
    32413207                  </li>
    3242                   <li class="indline1">message&nbsp;&nbsp;<a class="iref" href="#rfc.iref.m.4">C</a></li>
    3243                   <li class="indline1">message/http Media Type&nbsp;&nbsp;<a class="iref" href="#rfc.iref.m.2"><b>9.3.1</b></a></li>
     3208                  <li class="indline1">message&nbsp;&nbsp;<a class="iref" href="#rfc.iref.m.1">2.1</a></li>
     3209                  <li class="indline1">message/http Media Type&nbsp;&nbsp;<a class="iref" href="#rfc.iref.m.3"><b>9.3.1</b></a></li>
    32443210               </ul>
    32453211            </li>
    … …  
    32493215            </li>
    32503216            <li class="indline0"><a id="rfc.index.O" href="#rfc.index.O"><b>O</b></a><ul class="ind">
    3251                   <li class="indline1">origin server&nbsp;&nbsp;<a class="iref" href="#rfc.iref.o.2">C</a></li>
    3252                   <li class="indline1">outbound&nbsp;&nbsp;<a class="iref" href="#rfc.iref.o.1">C</a></li>
     3217                  <li class="indline1">origin server&nbsp;&nbsp;<a class="iref" href="#rfc.iref.o.1">2.1</a></li>
     3218                  <li class="indline1">outbound&nbsp;&nbsp;<a class="iref" href="#rfc.iref.o.2">2.2</a></li>
    32533219               </ul>
    32543220            </li>
    … …  
    32783244                  </li>
    32793245                  <li class="indline1"><em>Part5</em>&nbsp;&nbsp;<a class="iref" href="#Part5"><b>12.1</b></a>, <a class="iref" href="#rfc.xref.Part5.1">B.3</a></li>
    3280                   <li class="indline1"><em>Part6</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.1">1.2.3</a>, <a class="iref" href="#rfc.xref.Part6.2">1.2.3</a>, <a class="iref" href="#rfc.xref.Part6.3">1.2.3</a>, <a class="iref" href="#rfc.xref.Part6.4">2.1</a>, <a class="iref" href="#rfc.xref.Part6.5">3.5</a>, <a class="iref" href="#rfc.xref.Part6.6">3.5</a>, <a class="iref" href="#rfc.xref.Part6.7">3.5</a>, <a class="iref" href="#Part6"><b>12.1</b></a>, <a class="iref" href="#rfc.xref.Part6.8">B.3</a>, <a class="iref" href="#rfc.xref.Part6.9">C</a><ul class="ind">
    3281                         <li class="indline1"><em>Section 1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.4">2.1</a>, <a class="iref" href="#rfc.xref.Part6.9">C</a></li>
     3246                  <li class="indline1"><em>Part6</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.1">1.2.3</a>, <a class="iref" href="#rfc.xref.Part6.2">1.2.3</a>, <a class="iref" href="#rfc.xref.Part6.3">1.2.3</a>, <a class="iref" href="#rfc.xref.Part6.4">2.3</a>, <a class="iref" href="#rfc.xref.Part6.5">3.5</a>, <a class="iref" href="#rfc.xref.Part6.6">3.5</a>, <a class="iref" href="#rfc.xref.Part6.7">3.5</a>, <a class="iref" href="#Part6"><b>12.1</b></a>, <a class="iref" href="#rfc.xref.Part6.8">B.3</a><ul class="ind">
     3247                        <li class="indline1"><em>Section 1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.4">2.3</a></li>
    32823248                        <li class="indline1"><em>Section 3.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.5">3.5</a></li>
    32833249                        <li class="indline1"><em>Section 3.4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.1">1.2.3</a>, <a class="iref" href="#rfc.xref.Part6.2">1.2.3</a>, <a class="iref" href="#rfc.xref.Part6.6">3.5</a></li>
    … …  
    32853251                     </ul>
    32863252                  </li>
    3287                   <li class="indline1">proxy&nbsp;&nbsp;<a class="iref" href="#rfc.iref.p.1">C</a></li>
     3253                  <li class="indline1">proxy&nbsp;&nbsp;<a class="iref" href="#rfc.iref.p.1">2.2</a></li>
    32883254               </ul>
    32893255            </li>
    32903256            <li class="indline0"><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul class="ind">
    3291                   <li class="indline1">representation&nbsp;&nbsp;<a class="iref" href="#rfc.iref.r.4">C</a></li>
    3292                   <li class="indline1">request&nbsp;&nbsp;<a class="iref" href="#rfc.iref.r.2">C</a></li>
    3293                   <li class="indline1">resource&nbsp;&nbsp;<a class="iref" href="#rfc.iref.r.1"><b>2.3</b></a></li>
    3294                   <li class="indline1">response&nbsp;&nbsp;<a class="iref" href="#rfc.iref.r.3">C</a></li>
     3257                  <li class="indline1">representation&nbsp;&nbsp;<a class="iref" href="#rfc.iref.r.5">C</a></li>
     3258                  <li class="indline1">request&nbsp;&nbsp;<a class="iref" href="#rfc.iref.r.1">2.1</a></li>
     3259                  <li class="indline1">resource&nbsp;&nbsp;<a class="iref" href="#rfc.iref.r.4"><b>2.6</b></a></li>
     3260                  <li class="indline1">response&nbsp;&nbsp;<a class="iref" href="#rfc.iref.r.2">2.1</a></li>
     3261                  <li class="indline1">reverse proxy&nbsp;&nbsp;<a class="iref" href="#rfc.iref.r.3">2.2</a></li>
    32953262                  <li class="indline1"><em>RFC1123</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1123.1">6.1</a>, <a class="iref" href="#RFC1123"><b>12.2</b></a></li>
    32963263                  <li class="indline1"><em>RFC1305</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1305.1">8.3</a>, <a class="iref" href="#RFC1305"><b>12.2</b></a></li>
    … …  
    32993266                  <li class="indline1"><em>RFC2045</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2045.1">1</a>, <a class="iref" href="#rfc.xref.RFC2045.2">6.2</a>, <a class="iref" href="#rfc.xref.RFC2045.3">11</a>, <a class="iref" href="#RFC2045"><b>12.2</b></a></li>
    33003267                  <li class="indline1"><em>RFC2047</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2047.1">3.2</a>, <a class="iref" href="#RFC2047"><b>12.2</b></a></li>
    3301                   <li class="indline1"><em>RFC2068</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2068.1">2.2</a>, <a class="iref" href="#rfc.xref.RFC2068.2">7.1.3</a>, <a class="iref" href="#rfc.xref.RFC2068.3">7.2.3</a>, <a class="iref" href="#rfc.xref.RFC2068.4">11</a>, <a class="iref" href="#RFC2068"><b>12.2</b></a>, <a class="iref" href="#rfc.xref.RFC2068.5">B</a>, <a class="iref" href="#rfc.xref.RFC2068.6">B.2</a><ul class="ind">
     3268                  <li class="indline1"><em>RFC2068</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2068.1">2.5</a>, <a class="iref" href="#rfc.xref.RFC2068.2">7.1.3</a>, <a class="iref" href="#rfc.xref.RFC2068.3">7.2.3</a>, <a class="iref" href="#rfc.xref.RFC2068.4">11</a>, <a class="iref" href="#RFC2068"><b>12.2</b></a>, <a class="iref" href="#rfc.xref.RFC2068.5">B</a>, <a class="iref" href="#rfc.xref.RFC2068.6">B.2</a><ul class="ind">
    33023269                        <li class="indline1"><em>Section 19.7.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2068.2">7.1.3</a>, <a class="iref" href="#rfc.xref.RFC2068.5">B</a>, <a class="iref" href="#rfc.xref.RFC2068.6">B.2</a></li>
    33033270                     </ul>
    … …  
    33053272                  <li class="indline1"><em>RFC2109</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2109.1">3.2</a>, <a class="iref" href="#RFC2109"><b>12.2</b></a></li>
    33063273                  <li class="indline1"><em>RFC2119</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2119.1">1.1</a>, <a class="iref" href="#RFC2119"><b>12.1</b></a>, <a class="iref" href="#rfc.xref.RFC2119.2">B.3</a></li>
    3307                   <li class="indline1"><em>RFC2145</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2145.1">2.2</a>, <a class="iref" href="#rfc.xref.RFC2145.2">2.2</a>, <a class="iref" href="#RFC2145"><b>12.2</b></a>, <a class="iref" href="#rfc.xref.RFC2145.3">B.3</a></li>
     3274                  <li class="indline1"><em>RFC2145</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2145.1">2.5</a>, <a class="iref" href="#rfc.xref.RFC2145.2">2.5</a>, <a class="iref" href="#RFC2145"><b>12.2</b></a>, <a class="iref" href="#rfc.xref.RFC2145.3">B.3</a></li>
    33083275                  <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2616.1">1</a>, <a class="iref" href="#rfc.xref.RFC2616.2">11</a>, <a class="iref" href="#RFC2616"><b>12.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.3">E.1</a></li>
    3309                   <li class="indline1"><em>RFC2818</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2818.1">2.3.2</a>, <a class="iref" href="#RFC2818"><b>12.2</b></a></li>
     3276                  <li class="indline1"><em>RFC2818</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2818.1">2.6.2</a>, <a class="iref" href="#RFC2818"><b>12.2</b></a></li>
    33103277                  <li class="indline1"><em>RFC2965</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2965.1">3.2</a>, <a class="iref" href="#RFC2965"><b>12.2</b></a></li>
    33113278                  <li class="indline1"><em>RFC3864</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3864.1">9.1</a>, <a class="iref" href="#RFC3864"><b>12.2</b></a></li>
    3312                   <li class="indline1"><em>RFC3986</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3986.1">1</a>, <a class="iref" href="#rfc.xref.RFC3986.2">2.3</a>, <a class="iref" href="#rfc.xref.RFC3986.3">2.3</a>, <a class="iref" href="#rfc.xref.RFC3986.4">2.3</a>, <a class="iref" href="#rfc.xref.RFC3986.5">2.3</a>, <a class="iref" href="#rfc.xref.RFC3986.6">2.3</a>, <a class="iref" href="#rfc.xref.RFC3986.7">2.3</a>, <a class="iref" href="#rfc.xref.RFC3986.8">2.3</a>, <a class="iref" href="#rfc.xref.RFC3986.9">2.3</a>, <a class="iref" href="#rfc.xref.RFC3986.10">2.3</a>, <a class="iref" href="#rfc.xref.RFC3986.11">2.3</a>, <a class="iref" href="#rfc.xref.RFC3986.12">2.3</a>, <a class="iref" href="#rfc.xref.RFC3986.13">2.3</a>, <a class="iref" href="#rfc.xref.RFC3986.14">2.3</a>, <a class="iref" href="#rfc.xref.RFC3986.15">2.3</a>, <a class="iref" href="#rfc.xref.RFC3986.16">2.3.1</a>, <a class="iref" href="#rfc.xref.RFC3986.17">2.3.3</a>, <a class="iref" href="#rfc.xref.RFC3986.18">2.3.3</a>, <a class="iref" href="#rfc.xref.RFC3986.19">4.1.2</a>, <a class="iref" href="#RFC3986"><b>12.1</b></a><ul class="ind">
    3313                         <li class="indline1"><em>Section 2.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3986.18">2.3.3</a>, <a class="iref" href="#rfc.xref.RFC3986.19">4.1.2</a></li>
    3314                         <li class="indline1"><em>Section 3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3986.5">2.3</a></li>
    3315                         <li class="indline1"><em>Section 3.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3986.9">2.3</a></li>
    3316                         <li class="indline1"><em>Section 3.2.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3986.15">2.3</a>, <a class="iref" href="#rfc.xref.RFC3986.16">2.3.1</a></li>
    3317                         <li class="indline1"><em>Section 3.2.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3986.13">2.3</a></li>
    3318                         <li class="indline1"><em>Section 3.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3986.11">2.3</a>, <a class="iref" href="#rfc.xref.RFC3986.12">2.3</a></li>
    3319                         <li class="indline1"><em>Section 3.4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3986.14">2.3</a></li>
    3320                         <li class="indline1"><em>Section 3.5</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3986.10">2.3</a></li>
    3321                         <li class="indline1"><em>Section 4.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3986.6">2.3</a></li>
    3322                         <li class="indline1"><em>Section 4.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3986.8">2.3</a></li>
    3323                         <li class="indline1"><em>Section 4.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3986.7">2.3</a></li>
    3324                         <li class="indline1"><em>Section 6</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3986.17">2.3.3</a></li>
     3279                  <li class="indline1"><em>RFC3986</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3986.1">1</a>, <a class="iref" href="#rfc.xref.RFC3986.2">2.6</a>, <a class="iref" href="#rfc.xref.RFC3986.3">2.6</a>, <a class="iref" href="#rfc.xref.RFC3986.4">2.6</a>, <a class="iref" href="#rfc.xref.RFC3986.5">2.6</a>, <a class="iref" href="#rfc.xref.RFC3986.6">2.6</a>, <a class="iref" href="#rfc.xref.RFC3986.7">2.6</a>, <a class="iref" href="#rfc.xref.RFC3986.8">2.6</a>, <a class="iref" href="#rfc.xref.RFC3986.9">2.6</a>, <a class="iref" href="#rfc.xref.RFC3986.10">2.6</a>, <a class="iref" href="#rfc.xref.RFC3986.11">2.6</a>, <a class="iref" href="#rfc.xref.RFC3986.12">2.6</a>, <a class="iref" href="#rfc.xref.RFC3986.13">2.6</a>, <a class="iref" href="#rfc.xref.RFC3986.14">2.6</a>, <a class="iref" href="#rfc.xref.RFC3986.15">2.6</a>, <a class="iref" href="#rfc.xref.RFC3986.16">2.6.1</a>, <a class="iref" href="#rfc.xref.RFC3986.17">2.6.3</a>, <a class="iref" href="#rfc.xref.RFC3986.18">2.6.3</a>, <a class="iref" href="#rfc.xref.RFC3986.19">4.1.2</a>, <a class="iref" href="#RFC3986"><b>12.1</b></a><ul class="ind">
     3280                        <li class="indline1"><em>Section 2.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3986.18">2.6.3</a>, <a class="iref" href="#rfc.xref.RFC3986.19">4.1.2</a></li>
     3281                        <li class="indline1"><em>Section 3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3986.5">2.6</a></li>
     3282                        <li class="indline1"><em>Section 3.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3986.9">2.6</a></li>
     3283                        <li class="indline1"><em>Section 3.2.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3986.15">2.6</a>, <a class="iref" href="#rfc.xref.RFC3986.16">2.6.1</a></li>
     3284                        <li class="indline1"><em>Section 3.2.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3986.13">2.6</a></li>
     3285                        <li class="indline1"><em>Section 3.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3986.11">2.6</a>, <a class="iref" href="#rfc.xref.RFC3986.12">2.6</a></li>
     3286                        <li class="indline1"><em>Section 3.4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3986.14">2.6</a></li>
     3287                        <li class="indline1"><em>Section 3.5</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3986.10">2.6</a></li>
     3288                        <li class="indline1"><em>Section 4.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3986.6">2.6</a></li>
     3289                        <li class="indline1"><em>Section 4.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3986.8">2.6</a></li>
     3290                        <li class="indline1"><em>Section 4.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3986.7">2.6</a></li>
     3291                        <li class="indline1"><em>Section 6</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3986.17">2.6.3</a></li>
    33253292                     </ul>
    33263293                  </li>
    … …  
    33413308            </li>
    33423309            <li class="indline0"><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul class="ind">
    3343                   <li class="indline1">server&nbsp;&nbsp;<a class="iref" href="#rfc.iref.s.1">C</a></li>
     3310                  <li class="indline1">server&nbsp;&nbsp;<a class="iref" href="#rfc.iref.s.1">2.1</a></li>
    33443311                  <li class="indline1"><em>Spe</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Spe.1">7.1.1</a>, <a class="iref" href="#Spe"><b>12.2</b></a></li>
    33453312               </ul>
    33463313            </li>
    33473314            <li class="indline0"><a id="rfc.index.T" href="#rfc.index.T"><b>T</b></a><ul class="ind">
    3348                   <li class="indline1">TE header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.te.1">6.2</a>, <a class="iref" href="#rfc.xref.header.te.2">6.2.1</a>, <a class="iref" href="#rfc.xref.header.te.3">6.4</a>, <a class="iref" href="#rfc.iref.t.1"><b>8.5</b></a>, <a class="iref" href="#rfc.xref.header.te.4">9.1</a>, <a class="iref" href="#rfc.xref.header.te.5">B.3</a></li>
     3315                  <li class="indline1">TE header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.te.1">6.2</a>, <a class="iref" href="#rfc.xref.header.te.2">6.2.1</a>, <a class="iref" href="#rfc.xref.header.te.3">6.4</a>, <a class="iref" href="#rfc.iref.t.2"><b>8.5</b></a>, <a class="iref" href="#rfc.xref.header.te.4">9.1</a>, <a class="iref" href="#rfc.xref.header.te.5">B.3</a></li>
    33493316                  <li class="indline1"><em>Tou1998</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Tou1998.1">7.1.1</a>, <a class="iref" href="#Tou1998"><b>12.2</b></a></li>
    3350                   <li class="indline1">Trailer header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.trailer.1">3.5</a>, <a class="iref" href="#rfc.xref.header.trailer.2">6.2.1</a>, <a class="iref" href="#rfc.iref.t.2"><b>8.6</b></a>, <a class="iref" href="#rfc.xref.header.trailer.3">9.1</a></li>
    3351                   <li class="indline1">Transfer-Encoding header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.transfer-encoding.1">3.3</a>, <a class="iref" href="#rfc.xref.header.transfer-encoding.2">3.4</a>, <a class="iref" href="#rfc.xref.header.transfer-encoding.3">3.5</a>, <a class="iref" href="#rfc.xref.header.transfer-encoding.4">6.2</a>, <a class="iref" href="#rfc.iref.t.3"><b>8.7</b></a>, <a class="iref" href="#rfc.xref.header.transfer-encoding.5">9.1</a></li>
    3352                   <li class="indline1">tunnel&nbsp;&nbsp;<a class="iref" href="#rfc.iref.t.4">C</a></li>
     3317                  <li class="indline1">Trailer header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.trailer.1">3.5</a>, <a class="iref" href="#rfc.xref.header.trailer.2">6.2.1</a>, <a class="iref" href="#rfc.iref.t.3"><b>8.6</b></a>, <a class="iref" href="#rfc.xref.header.trailer.3">9.1</a></li>
     3318                  <li class="indline1">Transfer-Encoding header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.transfer-encoding.1">3.3</a>, <a class="iref" href="#rfc.xref.header.transfer-encoding.2">3.4</a>, <a class="iref" href="#rfc.xref.header.transfer-encoding.3">3.5</a>, <a class="iref" href="#rfc.xref.header.transfer-encoding.4">6.2</a>, <a class="iref" href="#rfc.iref.t.4"><b>8.7</b></a>, <a class="iref" href="#rfc.xref.header.transfer-encoding.5">9.1</a></li>
     3319                  <li class="indline1">tunnel&nbsp;&nbsp;<a class="iref" href="#rfc.iref.t.1">2.2</a></li>
    33533320               </ul>
    33543321            </li>
    33553322            <li class="indline0"><a id="rfc.index.U" href="#rfc.index.U"><b>U</b></a><ul class="ind">
    3356                   <li class="indline1">Upgrade header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.upgrade.1">3.5</a>, <a class="iref" href="#rfc.iref.u.3"><b>8.8</b></a>, <a class="iref" href="#rfc.xref.header.upgrade.2">9.1</a></li>
    3357                   <li class="indline1">upstream&nbsp;&nbsp;<a class="iref" href="#rfc.iref.u.4">C</a></li>
     3323                  <li class="indline1">Upgrade header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.upgrade.1">3.5</a>, <a class="iref" href="#rfc.iref.u.5"><b>8.8</b></a>, <a class="iref" href="#rfc.xref.header.upgrade.2">9.1</a></li>
     3324                  <li class="indline1">upstream&nbsp;&nbsp;<a class="iref" href="#rfc.iref.u.2">2.2</a></li>
    33583325                  <li class="indline1">URI scheme&nbsp;&nbsp;
    33593326                     <ul class="ind">
    3360                         <li class="indline1">http&nbsp;&nbsp;<a class="iref" href="#rfc.iref.u.1"><b>2.3.1</b></a></li>
    3361                         <li class="indline1">https&nbsp;&nbsp;<a class="iref" href="#rfc.iref.u.2">2.3.2</a></li>
     3327                        <li class="indline1">http&nbsp;&nbsp;<a class="iref" href="#rfc.iref.u.3"><b>2.6.1</b></a></li>
     3328                        <li class="indline1">https&nbsp;&nbsp;<a class="iref" href="#rfc.iref.u.4">2.6.2</a></li>
    33623329                     </ul>
    33633330                  </li>
    33643331                  <li class="indline1"><em>USASCII</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.USASCII.1">1.2</a>, <a class="iref" href="#rfc.xref.USASCII.2">3.2</a>, <a class="iref" href="#USASCII"><b>12.1</b></a></li>
    3365                   <li class="indline1">user agent&nbsp;&nbsp;<a class="iref" href="#rfc.iref.u.5">C</a></li>
     3332                  <li class="indline1">user agent&nbsp;&nbsp;<a class="iref" href="#rfc.iref.u.1">2.1</a></li>
    33663333               </ul>
    33673334            </li>
Note: See TracChangeset for help on using the changeset viewer.