Changeset 2629


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

insert RFC numbers (#553)

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

Legend:

Unmodified
Added
Removed

  • draft-ietf-httpbis/latest/abnf2xml2rfc.xslt

    r2206 r2629  
    2020    <xsl:text>&#10;</xsl:text>
    2121      <xsl:if test="not(starts-with($abnf,'p1-'))"><t>
    22   In the collected ABNF below, list rules are expanded as per <xref target='Part1' x:rel='#notation'/>.
     22  In the collected ABNF below, list rules are expanded as per <xref target='RFC7230' x:rel='#notation'/>.
    2323</t></xsl:if>
    2424      <figure>

  • draft-ietf-httpbis/latest/common-abnf.sh

    r1216 r2629  
    1616done | \
    1717        fgrep -v ", defined in [Part" | \
     18        fgrep -v ", defined in [RFC723" | \
    1819        sort | uniq | \
    1920        $bap/bap -k -i $bap/core.abnf

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

    r2628 r2629  
    463463  }
    464464  @bottom-center {
    465        content: "Expires November 2, 2014";
     465       content: "Expires November 7, 2014";
    466466  }
    467467  @bottom-right {
    … …  
    505505      <meta name="dct.creator" content="Reschke, J. F.">
    506506      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest">
    507       <meta name="dct.issued" scheme="ISO8601" content="2014-05-01">
     507      <meta name="dct.issued" scheme="ISO8601" content="2014-05-06">
    508508      <meta name="dct.replaces" content="urn:ietf:rfc:2145">
    509509      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    … …  
    534534            <tr>
    535535               <td class="left">Intended status: Standards Track</td>
    536                <td class="right">May 1, 2014</td>
     536               <td class="right">May 6, 2014</td>
    537537            </tr>
    538538            <tr>
    539                <td class="left">Expires: November 2, 2014</td>
     539               <td class="left">Expires: November 7, 2014</td>
    540540               <td class="right"></td>
    541541            </tr>
    … …  
    566566            in progress”.
    567567         </p>
    568          <p>This Internet-Draft will expire on November 2, 2014.</p>
     568         <p>This Internet-Draft will expire on November 7, 2014.</p>
    569569      </div>
    570570      <div id="rfc.copyrightnotice">
    … …  
    750750         </p>
    751751         <ul class="empty">
    752             <li>RFC xxx1: Message Syntax and Routing</li>
    753             <li><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content" id="rfc.xref.Part2.1">RFC xxx2</cite>: Semantics and Content
     752            <li>RFC 7230: Message Syntax and Routing</li>
     753            <li><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content" id="rfc.xref.RFC7231.1">RFC 7231</cite>: Semantics and Content
    754754            </li>
    755             <li><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests" id="rfc.xref.Part4.1">RFC xxx3</cite>: Conditional Requests
     755            <li><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests" id="rfc.xref.RFC7232.1">RFC 7232</cite>: Conditional Requests
    756756            </li>
    757             <li><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests" id="rfc.xref.Part5.1">RFC xxx4</cite>: Range Requests
     757            <li><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests" id="rfc.xref.RFC7233.1">RFC 7233</cite>: Range Requests
    758758            </li>
    759             <li><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching" id="rfc.xref.Part6.1">RFC xxx5</cite>: Caching
     759            <li><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching" id="rfc.xref.RFC7234.1">RFC 7234</cite>: Caching
    760760            </li>
    761             <li><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication" id="rfc.xref.Part7.1">RFC xxx6</cite>: Authentication
     761            <li><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching" id="rfc.xref.RFC7234.2">RFC 7235</cite>: Authentication
    762762            </li>
    763763         </ul>
    … …  
    842842               robots), command-line tools, custom applications, and mobile apps. The term "<dfn>origin server</dfn>" refers to the program that can originate authoritative responses for a given target resource. The terms "<dfn>sender</dfn>" and "<dfn>recipient</dfn>" refer to any implementation that sends or receives a given message, respectively.
    843843            </p>
    844             <p id="rfc.section.2.1.p.3">HTTP relies upon the Uniform Resource Identifier (URI) standard <a href="#RFC3986" id="rfc.xref.RFC3986.1"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a> to indicate the target resource (<a href="#target-resource" title="Identifying a Target Resource">Section&nbsp;5.1</a>) and relationships between resources. Messages are passed in a format similar to that used by Internet mail <a href="#RFC5322" id="rfc.xref.RFC5322.1"><cite title="Internet Message Format">[RFC5322]</cite></a> and the Multipurpose Internet Mail Extensions (MIME) <a href="#RFC2045" id="rfc.xref.RFC2045.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies">[RFC2045]</cite></a> (see <a href="p2-semantics.html#differences.between.http.and.mime" title="Differences between HTTP and MIME">Appendix A</a> of <a href="#Part2" id="rfc.xref.Part2.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a> for the differences between HTTP and MIME messages).
     844            <p id="rfc.section.2.1.p.3">HTTP relies upon the Uniform Resource Identifier (URI) standard <a href="#RFC3986" id="rfc.xref.RFC3986.1"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a> to indicate the target resource (<a href="#target-resource" title="Identifying a Target Resource">Section&nbsp;5.1</a>) and relationships between resources. Messages are passed in a format similar to that used by Internet mail <a href="#RFC5322" id="rfc.xref.RFC5322.1"><cite title="Internet Message Format">[RFC5322]</cite></a> and the Multipurpose Internet Mail Extensions (MIME) <a href="#RFC2045" id="rfc.xref.RFC2045.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies">[RFC2045]</cite></a> (see <a href="p2-semantics.html#differences.between.http.and.mime" title="Differences between HTTP and MIME">Appendix A</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a> for the differences between HTTP and MIME messages).
    845845            </p>
    846846            <p id="rfc.section.2.1.p.4">Most HTTP communication consists of a retrieval request (GET) for a representation of some resource identified by a URI. In
    … …  
    861861            <p id="rfc.section.2.1.p.8">A connection might be used for multiple request/response exchanges, as defined in <a href="#persistent.connections" title="Persistence">Section&nbsp;6.3</a>.
    862862            </p>
    863             <p id="rfc.section.2.1.p.9">The following example illustrates a typical message exchange for a GET request (<a href="p2-semantics.html#GET" title="GET">Section 4.3.1</a> of <a href="#Part2" id="rfc.xref.Part2.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>) on the URI "http://www.example.com/hello.txt":
     863            <p id="rfc.section.2.1.p.9">The following example illustrates a typical message exchange for a GET request (<a href="p2-semantics.html#GET" title="GET">Section 4.3.1</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>) on the URI "http://www.example.com/hello.txt":
    864864            </p>
    865865            <div id="rfc.figure.u.2"></div>
    … …  
    977977</pre><p id="rfc.section.2.4.p.4"><span id="rfc.iref.c.5"></span> A response is "<dfn>cacheable</dfn>" if a cache is allowed to store a copy of the response message for use in answering subsequent requests. Even when a response
    978978               is cacheable, there might be additional constraints placed by the client or by the origin server on when that cached response
    979                can be used for a particular request. HTTP requirements for cache behavior and cacheable responses are defined in <a href="p6-cache.html#caching.overview" title="Overview of Cache Operation">Section 2</a> of <a href="#Part6" id="rfc.xref.Part6.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>.
     979               can be used for a particular request. HTTP requirements for cache behavior and cacheable responses are defined in <a href="p6-cache.html#caching.overview" title="Overview of Cache Operation">Section 2</a> of <a href="#RFC7234" id="rfc.xref.RFC7234.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[RFC7234]</cite></a>.
    980980            </p>
    981981            <p id="rfc.section.2.4.p.5">There are a wide variety of architectures and configurations of caches deployed across the World Wide Web and inside large
    … …  
    10901090            <div id="rfc.iref.r.5"></div>
    10911091            <h2 id="rfc.section.2.7"><a href="#rfc.section.2.7">2.7</a>&nbsp;<a href="#uri">Uniform Resource Identifiers</a></h2>
    1092             <p id="rfc.section.2.7.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 (<a href="p2-semantics.html#resources" title="Resources">Section 2</a> of <a href="#Part2" id="rfc.xref.Part2.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>). URI references are used to target requests, indicate redirects, and define relationships.
     1092            <p id="rfc.section.2.7.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 (<a href="p2-semantics.html#resources" title="Resources">Section 2</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>). URI references are used to target requests, indicate redirects, and define relationships.
    10931093            </p>
    10941094            <p id="rfc.section.2.7.p.2">The definitions of "URI-reference", "absolute-URI", "relative-part", "scheme", "authority", "port", "host", "path-abempty",
    … …  
    11441144               </p>
    11451145               <p id="rfc.section.2.7.1.p.7">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,
    1146                   and sending an HTTP request message (<a href="#http.message" title="Message Format">Section&nbsp;3</a>) containing the URI's identifying data (<a href="#message.routing" title="Message Routing">Section&nbsp;5</a>) to the server. If the server responds to that request with a non-interim HTTP response message, as described in <a href="p2-semantics.html#status.codes" title="Response Status Codes">Section 6</a> of <a href="#Part2" id="rfc.xref.Part2.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>, then that response is considered an authoritative answer to the client's request.
     1146                  and sending an HTTP request message (<a href="#http.message" title="Message Format">Section&nbsp;3</a>) containing the URI's identifying data (<a href="#message.routing" title="Message Routing">Section&nbsp;5</a>) to the server. If the server responds to that request with a non-interim HTTP response message, as described in <a href="p2-semantics.html#status.codes" title="Response Status Codes">Section 6</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>, then that response is considered an authoritative answer to the client's request.
    11471147               </p>
    11481148               <p id="rfc.section.2.7.1.p.8">Although HTTP is independent of the transport protocol, the "http" scheme is specific to TCP-based services because the name
    … …  
    12571257               </div>
    12581258               <div id="rfc.figure.u.14"></div><pre class="inline"><span id="rfc.iref.g.32"></span>  <a href="#method" class="smpl">method</a>         = <a href="#rule.token.separators" class="smpl">token</a>
    1259 </pre><p id="rfc.section.3.1.1.p.5">The request methods defined by this specification can be found in <a href="p2-semantics.html#methods" title="Request Methods">Section 4</a> of <a href="#Part2" id="rfc.xref.Part2.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>, along with information regarding the HTTP method registry and considerations for defining new methods.
     1259</pre><p id="rfc.section.3.1.1.p.5">The request methods defined by this specification can be found in <a href="p2-semantics.html#methods" title="Request Methods">Section 4</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>, along with information regarding the HTTP method registry and considerations for defining new methods.
    12601260               </p>
    12611261               <div id="rfc.iref.r.6"></div>
    … …  
    12681268                  crafted to bypass security filters along the request chain.
    12691269               </p>
    1270                <p id="rfc.section.3.1.1.p.9">HTTP does not place a pre-defined limit on the length of a request-line, as described in <a href="#conformance" title="Conformance and Error Handling">Section&nbsp;2.5</a>. A server that receives a method longer than any that it implements <em class="bcp14">SHOULD</em> respond with a <a href="p2-semantics.html#status.501" class="smpl">501 (Not Implemented)</a> status code. A server that receives a request-target longer than any URI it wishes to parse <em class="bcp14">MUST</em> respond with a <a href="p2-semantics.html#status.414" class="smpl">414 (URI Too Long)</a> status code (see <a href="p2-semantics.html#status.414" title="414 URI Too Long">Section 6.5.12</a> of <a href="#Part2" id="rfc.xref.Part2.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>).
     1270               <p id="rfc.section.3.1.1.p.9">HTTP does not place a pre-defined limit on the length of a request-line, as described in <a href="#conformance" title="Conformance and Error Handling">Section&nbsp;2.5</a>. A server that receives a method longer than any that it implements <em class="bcp14">SHOULD</em> respond with a <a href="p2-semantics.html#status.501" class="smpl">501 (Not Implemented)</a> status code. A server that receives a request-target longer than any URI it wishes to parse <em class="bcp14">MUST</em> respond with a <a href="p2-semantics.html#status.414" class="smpl">414 (URI Too Long)</a> status code (see <a href="p2-semantics.html#status.414" title="414 URI Too Long">Section 6.5.12</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>).
    12711271               </p>
    12721272               <p id="rfc.section.3.1.1.p.10">Various ad-hoc limitations on request-line length are found in practice. It is <em class="bcp14">RECOMMENDED</em> that all HTTP senders and recipients support, at a minimum, request-line lengths of 8000 octets.
    … …  
    12811281</pre><p id="rfc.section.3.1.2.p.3">The status-code element is a 3-digit integer code describing the result of the server's attempt to understand and satisfy
    12821282                  the client's corresponding request. The rest of the response message is to be interpreted in light of the semantics defined
    1283                   for that status code. See <a href="p2-semantics.html#status.codes" title="Response Status Codes">Section 6</a> of <a href="#Part2" id="rfc.xref.Part2.8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a> for information about the semantics of status codes, including the classes of status code (indicated by the first digit),
     1283                  for that status code. See <a href="p2-semantics.html#status.codes" title="Response Status Codes">Section 6</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a> for information about the semantics of status codes, including the classes of status code (indicated by the first digit),
    12841284                  the status codes defined by this specification, considerations for the definition of new status codes, and the IANA registry.
    12851285               </p>
    … …  
    13081308                 ; see <a href="#field.parsing" title="Field Parsing">Section&nbsp;3.2.4</a>
    13091309</pre><p id="rfc.section.3.2.p.3">The field-name token labels the corresponding field-value as having the semantics defined by that header field. For example,
    1310                the <a href="p2-semantics.html#header.date" class="smpl">Date</a> header field is defined in <a href="p2-semantics.html#header.date" title="Date">Section 7.1.1.2</a> of <a href="#Part2" id="rfc.xref.Part2.9"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a> as containing the origination timestamp for the message in which it appears.
     1310               the <a href="p2-semantics.html#header.date" class="smpl">Date</a> header field is defined in <a href="p2-semantics.html#header.date" title="Date">Section 7.1.1.2</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.9"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a> as containing the origination timestamp for the message in which it appears.
    13111311            </p>
    13121312            <div id="field.extensibility">
    … …  
    13221322                  of deployed intermediaries.
    13231323               </p>
    1324                <p id="rfc.section.3.2.1.p.4">All defined header fields ought to be registered with IANA in the Message Header Field Registry, as described in <a href="p2-semantics.html#header.field.registry" title="Header Field Registry">Section 8.3</a> of <a href="#Part2" id="rfc.xref.Part2.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>.
     1324               <p id="rfc.section.3.2.1.p.4">All defined header fields ought to be registered with IANA in the Message Header Field Registry, as described in <a href="p2-semantics.html#header.field.registry" title="Header Field Registry">Section 8.3</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>.
    13251325               </p>
    13261326            </div>
    … …  
    14691469            </p>
    14701470            <p id="rfc.section.3.3.p.5">The presence of a message body in a response depends on both the request method to which it is responding and the response
    1471                status code (<a href="#status.line" title="Status Line">Section&nbsp;3.1.2</a>). Responses to the HEAD request method (<a href="p2-semantics.html#HEAD" title="HEAD">Section 4.3.2</a> of <a href="#Part2" id="rfc.xref.Part2.11"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>) never include a message body because the associated response header fields (e.g., <a href="#header.transfer-encoding" class="smpl">Transfer-Encoding</a>, <a href="#header.content-length" class="smpl">Content-Length</a>, etc.), if present, indicate only what their values would have been if the request method had been GET (<a href="p2-semantics.html#GET" title="GET">Section 4.3.1</a> of <a href="#Part2" id="rfc.xref.Part2.12"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>). <a href="p2-semantics.html#status.2xx" class="smpl">2xx (Successful)</a> responses to a CONNECT request method (<a href="p2-semantics.html#CONNECT" title="CONNECT">Section 4.3.6</a> of <a href="#Part2" id="rfc.xref.Part2.13"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>) switch to tunnel mode instead of having a message body. All <a href="p2-semantics.html#status.1xx" class="smpl">1xx (Informational)</a>, <a href="p2-semantics.html#status.204" class="smpl">204 (No Content)</a>, and <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a> responses do not include a message body. All other responses do include a message body, although the body might be of zero
     1471               status code (<a href="#status.line" title="Status Line">Section&nbsp;3.1.2</a>). Responses to the HEAD request method (<a href="p2-semantics.html#HEAD" title="HEAD">Section 4.3.2</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.11"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>) never include a message body because the associated response header fields (e.g., <a href="#header.transfer-encoding" class="smpl">Transfer-Encoding</a>, <a href="#header.content-length" class="smpl">Content-Length</a>, etc.), if present, indicate only what their values would have been if the request method had been GET (<a href="p2-semantics.html#GET" title="GET">Section 4.3.1</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.12"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>). <a href="p2-semantics.html#status.2xx" class="smpl">2xx (Successful)</a> responses to a CONNECT request method (<a href="p2-semantics.html#CONNECT" title="CONNECT">Section 4.3.6</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.13"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>) switch to tunnel mode instead of having a message body. All <a href="p2-semantics.html#status.1xx" class="smpl">1xx (Informational)</a>, <a href="p2-semantics.html#status.204" class="smpl">204 (No Content)</a>, and <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a> responses do not include a message body. All other responses do include a message body, although the body might be of zero
    14721472               length.
    14731473            </p>
    … …  
    14941494                  forming the message body.
    14951495               </p>
    1496                <p id="rfc.section.3.3.1.p.6">Unlike <a href="p2-semantics.html#header.content-encoding" class="smpl">Content-Encoding</a> (<a href="p2-semantics.html#content.codings" title="Content Codings">Section 3.1.2.1</a> of <a href="#Part2" id="rfc.xref.Part2.14"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>), Transfer-Encoding is a property of the message, not of the representation, and any recipient along the request/response
     1496               <p id="rfc.section.3.3.1.p.6">Unlike <a href="p2-semantics.html#header.content-encoding" class="smpl">Content-Encoding</a> (<a href="p2-semantics.html#content.codings" title="Content Codings">Section 3.1.2.1</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.14"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>), Transfer-Encoding is a property of the message, not of the representation, and any recipient along the request/response
    14971497                  chain <em class="bcp14">MAY</em> decode the received transfer coding(s) or apply additional transfer coding(s) to the message body, assuming that corresponding
    14981498                  changes are made to the Transfer-Encoding field-value. Additional information about the encoding parameters can be provided
    14991499                  by other header fields not defined by this specification.
    15001500               </p>
    1501                <p id="rfc.section.3.3.1.p.7">Transfer-Encoding <em class="bcp14">MAY</em> be sent in a response to a HEAD request or in a <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a> response (<a href="p4-conditional.html#status.304" title="304 Not Modified">Section 4.1</a> of <a href="#Part4" id="rfc.xref.Part4.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>) to a GET request, neither of which includes a message body, to indicate that the origin server would have applied a transfer
     1501               <p id="rfc.section.3.3.1.p.7">Transfer-Encoding <em class="bcp14">MAY</em> be sent in a response to a HEAD request or in a <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a> response (<a href="p4-conditional.html#status.304" title="304 Not Modified">Section 4.1</a> of <a href="#RFC7232" id="rfc.xref.RFC7232.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[RFC7232]</cite></a>) to a GET request, neither of which includes a message body, to indicate that the origin server would have applied a transfer
    15021502                  coding to the message body if the request had been an unconditional GET. This indication is not required, however, because
    15031503                  any recipient on the response chain (including the origin server) can remove transfer codings when they are not needed.
    15041504               </p>
    1505                <p id="rfc.section.3.3.1.p.8">A server <em class="bcp14">MUST NOT</em> send a Transfer-Encoding header field in any response with a status code of <a href="p2-semantics.html#status.1xx" class="smpl">1xx (Informational)</a> or <a href="p2-semantics.html#status.204" class="smpl">204 (No Content)</a>. A server <em class="bcp14">MUST NOT</em> send a Transfer-Encoding header field in any <a href="p2-semantics.html#status.2xx" class="smpl">2xx (Successful)</a> response to a CONNECT request (<a href="p2-semantics.html#CONNECT" title="CONNECT">Section 4.3.6</a> of <a href="#Part2" id="rfc.xref.Part2.15"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>).
     1505               <p id="rfc.section.3.3.1.p.8">A server <em class="bcp14">MUST NOT</em> send a Transfer-Encoding header field in any response with a status code of <a href="p2-semantics.html#status.1xx" class="smpl">1xx (Informational)</a> or <a href="p2-semantics.html#status.204" class="smpl">204 (No Content)</a>. A server <em class="bcp14">MUST NOT</em> send a Transfer-Encoding header field in any <a href="p2-semantics.html#status.2xx" class="smpl">2xx (Successful)</a> response to a CONNECT request (<a href="p2-semantics.html#CONNECT" title="CONNECT">Section 4.3.6</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.15"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>).
    15061506               </p>
    15071507               <p id="rfc.section.3.3.1.p.9">Transfer-Encoding was added in HTTP/1.1. It is generally assumed that implementations advertising only HTTP/1.0 support will
    … …  
    15181518                  payload body. For messages that do include a payload body, the Content-Length field-value provides the framing information
    15191519                  necessary for determining where the body (and message) ends. For messages that do not include a payload body, the Content-Length
    1520                   indicates the size of the selected representation (<a href="p2-semantics.html#representations" title="Representations">Section 3</a> of <a href="#Part2" id="rfc.xref.Part2.16"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>).
     1520                  indicates the size of the selected representation (<a href="p2-semantics.html#representations" title="Representations">Section 3</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.16"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>).
    15211521               </p>
    15221522               <div id="rfc.figure.u.27"></div><pre class="inline"><span id="rfc.iref.g.55"></span>  <a href="#header.content-length" class="smpl">Content-Length</a> = 1*<a href="#core.rules" class="smpl">DIGIT</a>
    … …  
    15291529                  anticipate such a body.
    15301530               </p>
    1531                <p id="rfc.section.3.3.2.p.7">A server <em class="bcp14">MAY</em> send a Content-Length header field in a response to a HEAD request (<a href="p2-semantics.html#HEAD" title="HEAD">Section 4.3.2</a> of <a href="#Part2" id="rfc.xref.Part2.17"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>); a server <em class="bcp14">MUST NOT</em> send Content-Length in such a response unless its field-value equals the decimal number of octets that would have been sent
     1531               <p id="rfc.section.3.3.2.p.7">A server <em class="bcp14">MAY</em> send a Content-Length header field in a response to a HEAD request (<a href="p2-semantics.html#HEAD" title="HEAD">Section 4.3.2</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.17"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>); a server <em class="bcp14">MUST NOT</em> send Content-Length in such a response unless its field-value equals the decimal number of octets that would have been sent
    15321532                  in the payload body of a response if the same request had used the GET method.
    15331533               </p>
    1534                <p id="rfc.section.3.3.2.p.8">A server <em class="bcp14">MAY</em> send a Content-Length header field in a <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a> response to a conditional GET request (<a href="p4-conditional.html#status.304" title="304 Not Modified">Section 4.1</a> of <a href="#Part4" id="rfc.xref.Part4.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>); a server <em class="bcp14">MUST NOT</em> send Content-Length in such a response unless its field-value equals the decimal number of octets that would have been sent
     1534               <p id="rfc.section.3.3.2.p.8">A server <em class="bcp14">MAY</em> send a Content-Length header field in a <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a> response to a conditional GET request (<a href="p4-conditional.html#status.304" title="304 Not Modified">Section 4.1</a> of <a href="#RFC7232" id="rfc.xref.RFC7232.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[RFC7232]</cite></a>); a server <em class="bcp14">MUST NOT</em> send Content-Length in such a response unless its field-value equals the decimal number of octets that would have been sent
    15351535                  in the payload body of a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response to the same request.
    15361536               </p>
    1537                <p id="rfc.section.3.3.2.p.9">A server <em class="bcp14">MUST NOT</em> send a Content-Length header field in any response with a status code of <a href="p2-semantics.html#status.1xx" class="smpl">1xx (Informational)</a> or <a href="p2-semantics.html#status.204" class="smpl">204 (No Content)</a>. A server <em class="bcp14">MUST NOT</em> send a Content-Length header field in any <a href="p2-semantics.html#status.2xx" class="smpl">2xx (Successful)</a> response to a CONNECT request (<a href="p2-semantics.html#CONNECT" title="CONNECT">Section 4.3.6</a> of <a href="#Part2" id="rfc.xref.Part2.18"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>).
     1537               <p id="rfc.section.3.3.2.p.9">A server <em class="bcp14">MUST NOT</em> send a Content-Length header field in any response with a status code of <a href="p2-semantics.html#status.1xx" class="smpl">1xx (Informational)</a> or <a href="p2-semantics.html#status.204" class="smpl">204 (No Content)</a>. A server <em class="bcp14">MUST NOT</em> send a Content-Length header field in any <a href="p2-semantics.html#status.2xx" class="smpl">2xx (Successful)</a> response to a CONNECT request (<a href="p2-semantics.html#CONNECT" title="CONNECT">Section 4.3.6</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.18"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>).
    15381538               </p>
    15391539               <p id="rfc.section.3.3.2.p.10">Aside from the cases defined above, in the absence of Transfer-Encoding, an origin server <em class="bcp14">SHOULD</em> send a Content-Length header field when the payload body size is known prior to sending the complete header section. This
    … …  
    16281628            </p>
    16291629            <p id="rfc.section.3.4.p.2">A client that receives an incomplete response message, which can occur when a connection is closed prematurely or when decoding
    1630                a supposedly chunked transfer coding fails, <em class="bcp14">MUST</em> record the message as incomplete. Cache requirements for incomplete responses are defined in <a href="p6-cache.html#response.cacheability" title="Storing Responses in Caches">Section 3</a> of <a href="#Part6" id="rfc.xref.Part6.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>.
     1630               a supposedly chunked transfer coding fails, <em class="bcp14">MUST</em> record the message as incomplete. Cache requirements for incomplete responses are defined in <a href="p6-cache.html#response.cacheability" title="Storing Responses in Caches">Section 3</a> of <a href="#RFC7234" id="rfc.xref.RFC7234.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[RFC7234]</cite></a>.
    16311631            </p>
    16321632            <p id="rfc.section.3.4.p.3">If a response terminates in the middle of the header section (before the empty line is received) and the status code might
    … …  
    17331733               </p>
    17341734               <div id="rfc.figure.u.33"></div><pre class="inline"><span id="rfc.iref.g.70"></span><span id="rfc.iref.g.71"></span>  <a href="#chunked.trailer.part" class="smpl">trailer-part</a>   = *( <a href="#header.fields" class="smpl">header-field</a> <a href="#core.rules" class="smpl">CRLF</a> )
    1735 </pre><p id="rfc.section.4.1.2.p.3">A sender <em class="bcp14">MUST NOT</em> generate a trailer that contains a field necessary for message framing (e.g., <a href="#header.transfer-encoding" class="smpl">Transfer-Encoding</a> and <a href="#header.content-length" class="smpl">Content-Length</a>), routing (e.g., <a href="#header.host" class="smpl">Host</a>), request modifiers (e.g., controls and conditionals in <a href="p2-semantics.html#request.header.fields" title="Request Header Fields">Section 5</a> of <a href="#Part2" id="rfc.xref.Part2.19"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>), authentication (e.g., see <a href="#Part7" id="rfc.xref.Part7.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[Part7]</cite></a> and <a href="#RFC6265" id="rfc.xref.RFC6265.3"><cite title="HTTP State Management Mechanism">[RFC6265]</cite></a>), response control data (e.g., see <a href="p2-semantics.html#response.control.data" title="Control Data">Section 7.1</a> of <a href="#Part2" id="rfc.xref.Part2.20"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>), or determining how to process the payload (e.g., <a href="p2-semantics.html#header.content-encoding" class="smpl">Content-Encoding</a>, <a href="p2-semantics.html#header.content-type" class="smpl">Content-Type</a>, <a href="p5-range.html#header.content-range" class="smpl">Content-Range</a>, and <a href="#header.trailer" class="smpl">Trailer</a>).
     1735</pre><p id="rfc.section.4.1.2.p.3">A sender <em class="bcp14">MUST NOT</em> generate a trailer that contains a field necessary for message framing (e.g., <a href="#header.transfer-encoding" class="smpl">Transfer-Encoding</a> and <a href="#header.content-length" class="smpl">Content-Length</a>), routing (e.g., <a href="#header.host" class="smpl">Host</a>), request modifiers (e.g., controls and conditionals in <a href="p2-semantics.html#request.header.fields" title="Request Header Fields">Section 5</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.19"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>), authentication (e.g., see <a href="#RFC7235" id="rfc.xref.RFC7235.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[RFC7235]</cite></a> and <a href="#RFC6265" id="rfc.xref.RFC6265.3"><cite title="HTTP State Management Mechanism">[RFC6265]</cite></a>), response control data (e.g., see <a href="p2-semantics.html#response.control.data" title="Control Data">Section 7.1</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.20"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>), or determining how to process the payload (e.g., <a href="p2-semantics.html#header.content-encoding" class="smpl">Content-Encoding</a>, <a href="p2-semantics.html#header.content-type" class="smpl">Content-Type</a>, <a href="p5-range.html#header.content-range" class="smpl">Content-Range</a>, and <a href="#header.trailer" class="smpl">Trailer</a>).
    17361736               </p>
    17371737               <p id="rfc.section.4.1.2.p.4">When a chunked message containing a non-empty trailer is received, the recipient <em class="bcp14">MAY</em> process the fields (aside from those forbidden above) as if they were appended to the message's header section. A recipient <em class="bcp14">MUST</em> ignore (or consider as an error) any fields that are forbidden to be sent in a trailer, since processing them as if they were
    … …  
    18171817            </p>
    18181818            <p id="rfc.section.4.3.p.7">When multiple transfer codings are acceptable, the client <em class="bcp14">MAY</em> rank the codings by preference using a case-insensitive "q" parameter (similar to the qvalues used in content negotiation
    1819                fields, <a href="p2-semantics.html#quality.values" title="Quality Values">Section 5.3.1</a> of <a href="#Part2" id="rfc.xref.Part2.21"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>). The rank value is a real number in the range 0 through 1, where 0.001 is the least preferred and 1 is the most preferred;
     1819               fields, <a href="p2-semantics.html#quality.values" title="Quality Values">Section 5.3.1</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.21"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>). The rank value is a real number in the range 0 through 1, where 0.001 is the least preferred and 1 is the most preferred;
    18201820               a value of 0 means "not acceptable".
    18211821            </p>
    … …  
    18521852            </p>
    18531853            <p id="rfc.section.5.1.p.2">HTTP communication is initiated by a user agent for some purpose. The purpose is a combination of request semantics, which
    1854                are defined in <a href="#Part2" id="rfc.xref.Part2.22"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>, and a target resource upon which to apply those semantics. A URI reference (<a href="#uri" title="Uniform Resource Identifiers">Section&nbsp;2.7</a>) is typically used as an identifier for the "<dfn>target resource</dfn>", which a user agent would resolve to its absolute form in order to obtain the "<dfn>target URI</dfn>". The target URI excludes the reference's fragment component, if any, since fragment identifiers are reserved for client-side
     1854               are defined in <a href="#RFC7231" id="rfc.xref.RFC7231.22"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>, and a target resource upon which to apply those semantics. A URI reference (<a href="#uri" title="Uniform Resource Identifiers">Section&nbsp;2.7</a>) is typically used as an identifier for the "<dfn>target resource</dfn>", which a user agent would resolve to its absolute form in order to obtain the "<dfn>target URI</dfn>". The target URI excludes the reference's fragment component, if any, since fragment identifiers are reserved for client-side
    18551855               processing (<a href="#RFC3986" id="rfc.xref.RFC3986.21"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-3.5">Section 3.5</a>).
    18561856            </p>
    … …  
    18611861               semantics and, if so, where that request is to be directed.
    18621862            </p>
    1863             <p id="rfc.section.5.2.p.2">If the client has a cache <a href="#Part6" id="rfc.xref.Part6.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a> and the request can be satisfied by it, then the request is usually directed there first.
     1863            <p id="rfc.section.5.2.p.2">If the client has a cache <a href="#RFC7234" id="rfc.xref.RFC7234.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[RFC7234]</cite></a> and the request can be satisfied by it, then the request is usually directed there first.
    18641864            </p>
    18651865            <p id="rfc.section.5.2.p.3">If the request is not satisfied by a cache, then a typical client will check its configuration to determine whether a proxy
    … …  
    19221922               <div id="rfc.iref.a.3"></div>
    19231923               <h3 id="rfc.section.5.3.3"><a href="#rfc.section.5.3.3">5.3.3</a>&nbsp;<a href="#authority-form">authority-form</a></h3>
    1924                <p id="rfc.section.5.3.3.p.1">The <dfn>authority-form</dfn> of request-target is only used for CONNECT requests (<a href="p2-semantics.html#CONNECT" title="CONNECT">Section 4.3.6</a> of <a href="#Part2" id="rfc.xref.Part2.23"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>).
     1924               <p id="rfc.section.5.3.3.p.1">The <dfn>authority-form</dfn> of request-target is only used for CONNECT requests (<a href="p2-semantics.html#CONNECT" title="CONNECT">Section 4.3.6</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.23"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>).
    19251925               </p>
    19261926               <div id="rfc.figure.u.44"></div><pre class="inline"><span id="rfc.iref.g.86"></span>  <a href="#authority-form" class="smpl">authority-form</a> = <a href="#uri" class="smpl">authority</a>
    … …  
    19321932               <div id="rfc.iref.a.4"></div>
    19331933               <h3 id="rfc.section.5.3.4"><a href="#rfc.section.5.3.4">5.3.4</a>&nbsp;<a href="#asterisk-form">asterisk-form</a></h3>
    1934                <p id="rfc.section.5.3.4.p.1">The <dfn>asterisk-form</dfn> of request-target is only used for a server-wide OPTIONS request (<a href="p2-semantics.html#OPTIONS" title="OPTIONS">Section 4.3.7</a> of <a href="#Part2" id="rfc.xref.Part2.24"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>).
     1934               <p id="rfc.section.5.3.4.p.1">The <dfn>asterisk-form</dfn> of request-target is only used for a server-wide OPTIONS request (<a href="p2-semantics.html#OPTIONS" title="OPTIONS">Section 4.3.7</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.24"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>).
    19351935               </p>
    19361936               <div id="rfc.figure.u.46"></div><pre class="inline"><span id="rfc.iref.g.87"></span>  <a href="#asterisk-form" class="smpl">asterisk-form</a>  = "*"
    … …  
    20282028            <p id="rfc.section.5.6.p.1">HTTP does not include a request identifier for associating a given request message with its corresponding one or more response
    20292029               messages. Hence, it relies on the order of response arrival to correspond exactly to the order in which requests are made
    2030                on the same connection. More than one response message per request only occurs when one or more informational responses (<a href="p2-semantics.html#status.1xx" class="smpl">1xx</a>, see <a href="p2-semantics.html#status.1xx" title="Informational 1xx">Section 6.2</a> of <a href="#Part2" id="rfc.xref.Part2.25"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>) precede a final response to the same request.
     2030               on the same connection. More than one response message per request only occurs when one or more informational responses (<a href="p2-semantics.html#status.1xx" class="smpl">1xx</a>, see <a href="p2-semantics.html#status.1xx" title="Informational 1xx">Section 6.2</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.25"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>) precede a final response to the same request.
    20312031            </p>
    20322032            <p id="rfc.section.5.6.p.2">A client that has more than one outstanding request on a connection <em class="bcp14">MUST</em> maintain a list of outstanding requests in the order sent and <em class="bcp14">MUST</em> associate each received response message on that connection to the highest ordered request that has not yet received a final
    … …  
    21172117               <p id="rfc.section.5.7.2.p.5">A proxy <em class="bcp14">MAY</em> modify the message body through application or removal of a transfer coding (<a href="#transfer.codings" title="Transfer Codings">Section&nbsp;4</a>).
    21182118               </p>
    2119                <p id="rfc.section.5.7.2.p.6">A proxy <em class="bcp14">MUST NOT</em> transform the payload (<a href="p2-semantics.html#payload" title="Payload Semantics">Section 3.3</a> of <a href="#Part2" id="rfc.xref.Part2.26"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>) of a message that contains a no-transform cache-control directive (<a href="p6-cache.html#header.cache-control" title="Cache-Control">Section 5.2</a> of <a href="#Part6" id="rfc.xref.Part6.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
     2119               <p id="rfc.section.5.7.2.p.6">A proxy <em class="bcp14">MUST NOT</em> transform the payload (<a href="p2-semantics.html#payload" title="Payload Semantics">Section 3.3</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.26"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>) of a message that contains a no-transform cache-control directive (<a href="p6-cache.html#header.cache-control" title="Cache-Control">Section 5.2</a> of <a href="#RFC7234" id="rfc.xref.RFC7234.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[RFC7234]</cite></a>).
    21202120               </p>
    21212121               <p id="rfc.section.5.7.2.p.7">A proxy <em class="bcp14">MAY</em> transform the payload of a message that does not contain a no-transform cache-control directive. A proxy that transforms a
    2122                   payload <em class="bcp14">MUST</em> add a <a href="p6-cache.html#header.warning" class="smpl">Warning</a> header field with the warn-code of 214 ("Transformation Applied") if one is not already in the message (see <a href="p6-cache.html#header.warning" title="Warning">Section 5.5</a> of <a href="#Part6" id="rfc.xref.Part6.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>). A proxy that transforms the payload of a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response can further inform downstream recipients that a transformation has been applied by changing the response status code
    2123                   to <a href="p2-semantics.html#status.203" class="smpl">203 (Non-Authoritative Information)</a> (<a href="p2-semantics.html#status.203" title="203 Non-Authoritative Information">Section 6.3.4</a> of <a href="#Part2" id="rfc.xref.Part2.27"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>).
     2122                  payload <em class="bcp14">MUST</em> add a <a href="p6-cache.html#header.warning" class="smpl">Warning</a> header field with the warn-code of 214 ("Transformation Applied") if one is not already in the message (see <a href="p6-cache.html#header.warning" title="Warning">Section 5.5</a> of <a href="#RFC7234" id="rfc.xref.RFC7234.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[RFC7234]</cite></a>). A proxy that transforms the payload of a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response can further inform downstream recipients that a transformation has been applied by changing the response status code
     2123                  to <a href="p2-semantics.html#status.203" class="smpl">203 (Non-Authoritative Information)</a> (<a href="p2-semantics.html#status.203" title="203 Non-Authoritative Information">Section 6.3.4</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.27"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>).
    21242124               </p>
    21252125               <p id="rfc.section.5.7.2.p.8">A proxy <em class="bcp14">SHOULD NOT</em> modify header fields that provide information about the end points of the communication chain, the resource state, or the
    … …  
    21652165  <a href="#header.connection" class="smpl">connection-option</a> = <a href="#rule.token.separators" class="smpl">token</a>
    21662166</pre><p id="rfc.section.6.1.p.6">Connection options are case-insensitive.</p>
    2167             <p id="rfc.section.6.1.p.7">A sender <em class="bcp14">MUST NOT</em> send a connection option corresponding to a header field that is intended for all recipients of the payload. For example, <a href="p6-cache.html#header.cache-control" class="smpl">Cache-Control</a> is never appropriate as a connection option (<a href="p6-cache.html#header.cache-control" title="Cache-Control">Section 5.2</a> of <a href="#Part6" id="rfc.xref.Part6.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
     2167            <p id="rfc.section.6.1.p.7">A sender <em class="bcp14">MUST NOT</em> send a connection option corresponding to a header field that is intended for all recipients of the payload. For example, <a href="p6-cache.html#header.cache-control" class="smpl">Cache-Control</a> is never appropriate as a connection option (<a href="p6-cache.html#header.cache-control" title="Cache-Control">Section 5.2</a> of <a href="#RFC7234" id="rfc.xref.RFC7234.8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[RFC7234]</cite></a>).
    21682168            </p>
    21692169            <p id="rfc.section.6.1.p.8">The connection options do not always correspond to a header field present in the message, since a connection-specific header
    … …  
    22272227               </p>
    22282228               <p id="rfc.section.6.3.1.p.2">When an inbound connection is closed prematurely, a client <em class="bcp14">MAY</em> open a new connection and automatically retransmit an aborted sequence of requests if all of those requests have idempotent
    2229                   methods (<a href="p2-semantics.html#idempotent.methods" title="Idempotent Methods">Section 4.2.2</a> of <a href="#Part2" id="rfc.xref.Part2.28"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>). A proxy <em class="bcp14">MUST NOT</em> automatically retry non-idempotent requests.
     2229                  methods (<a href="p2-semantics.html#idempotent.methods" title="Idempotent Methods">Section 4.2.2</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.28"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>). A proxy <em class="bcp14">MUST NOT</em> automatically retry non-idempotent requests.
    22302230               </p>
    22312231               <p id="rfc.section.6.3.1.p.3">A user agent <em class="bcp14">MUST NOT</em> automatically retry a request with a non-idempotent method unless it has some means to know that the request semantics are
    … …  
    22412241            <div id="pipelining">
    22422242               <h3 id="rfc.section.6.3.2"><a href="#rfc.section.6.3.2">6.3.2</a>&nbsp;<a href="#pipelining">Pipelining</a></h3>
    2243                <p id="rfc.section.6.3.2.p.1">A client that supports persistent connections <em class="bcp14">MAY</em> "<dfn>pipeline</dfn>" its requests (i.e., send multiple requests without waiting for each response). A server <em class="bcp14">MAY</em> process a sequence of pipelined requests in parallel if they all have safe methods (<a href="p2-semantics.html#safe.methods" title="Safe Methods">Section 4.2.1</a> of <a href="#Part2" id="rfc.xref.Part2.29"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>), but <em class="bcp14">MUST</em> send the corresponding responses in the same order that the requests were received.
     2243               <p id="rfc.section.6.3.2.p.1">A client that supports persistent connections <em class="bcp14">MAY</em> "<dfn>pipeline</dfn>" its requests (i.e., send multiple requests without waiting for each response). A server <em class="bcp14">MAY</em> process a sequence of pipelined requests in parallel if they all have safe methods (<a href="p2-semantics.html#safe.methods" title="Safe Methods">Section 4.2.1</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.29"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>), but <em class="bcp14">MUST</em> send the corresponding responses in the same order that the requests were received.
    22442244               </p>
    22452245               <p id="rfc.section.6.3.2.p.2">A client that pipelines requests <em class="bcp14">SHOULD</em> retry unanswered requests if the connection closes before it receives all of the corresponding responses. When retrying pipelined
    … …  
    22482248                  problem described in <a href="#persistent.tear-down" id="rfc.xref.persistent.tear-down.2" title="Tear-down">Section&nbsp;6.6</a>).
    22492249               </p>
    2250                <p id="rfc.section.6.3.2.p.3">Idempotent methods (<a href="p2-semantics.html#idempotent.methods" title="Idempotent Methods">Section 4.2.2</a> of <a href="#Part2" id="rfc.xref.Part2.30"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>) are significant to pipelining because they can be automatically retried after a connection failure. A user agent <em class="bcp14">SHOULD NOT</em> pipeline requests after a non-idempotent method, until the final response status code for that method has been received, unless
     2250               <p id="rfc.section.6.3.2.p.3">Idempotent methods (<a href="p2-semantics.html#idempotent.methods" title="Idempotent Methods">Section 4.2.2</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.30"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>) are significant to pipelining because they can be automatically retried after a connection failure. A user agent <em class="bcp14">SHOULD NOT</em> pipeline requests after a non-idempotent method, until the final response status code for that method has been received, unless
    22512251                  the user agent has a means to detect and recover from partial failure conditions involving the pipelined sequence.
    22522252               </p>
    … …  
    23732373            </p>
    23742374            <p id="rfc.section.6.7.p.11">A client cannot begin using an upgraded protocol on the connection until it has completely sent the request message (i.e.,
    2375                the client can't change the protocol it is sending in the middle of a message). If a server receives both Upgrade and an <a href="p2-semantics.html#header.expect" class="smpl">Expect</a> header field with the "100-continue" expectation (<a href="p2-semantics.html#header.expect" title="Expect">Section 5.1.1</a> of <a href="#Part2" id="rfc.xref.Part2.31"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>), the server <em class="bcp14">MUST</em> send a <a href="p2-semantics.html#status.100" class="smpl">100 (Continue)</a> response before sending a <a href="p2-semantics.html#status.101" class="smpl">101 (Switching Protocols)</a> response.
     2375               the client can't change the protocol it is sending in the middle of a message). If a server receives both Upgrade and an <a href="p2-semantics.html#header.expect" class="smpl">Expect</a> header field with the "100-continue" expectation (<a href="p2-semantics.html#header.expect" title="Expect">Section 5.1.1</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.31"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>), the server <em class="bcp14">MUST</em> send a <a href="p2-semantics.html#status.100" class="smpl">100 (Continue)</a> response before sending a <a href="p2-semantics.html#status.101" class="smpl">101 (Switching Protocols)</a> response.
    23762376            </p>
    23772377            <p id="rfc.section.6.7.p.12">The Upgrade header field only applies to switching protocols on top of the existing connection; it cannot be used to switch
    23782378               the underlying connection (transport) protocol, nor to switch the existing communication to a different connection. For those
    2379                purposes, it is more appropriate to use a <a href="p2-semantics.html#status.3xx" class="smpl">3xx (Redirection)</a> response (<a href="p2-semantics.html#status.3xx" title="Redirection 3xx">Section 6.4</a> of <a href="#Part2" id="rfc.xref.Part2.32"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>).
     2379               purposes, it is more appropriate to use a <a href="p2-semantics.html#status.3xx" class="smpl">3xx (Redirection)</a> response (<a href="p2-semantics.html#status.3xx" title="Redirection 3xx">Section 6.4</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.32"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>).
    23802380            </p>
    23812381            <p id="rfc.section.6.7.p.13">This specification only defines the protocol name "HTTP" for use by the family of Hypertext Transfer Protocols, as defined
    … …  
    27092709                  <li>Pointer to specification text</li>
    27102710               </ul>
    2711                <p id="rfc.section.8.4.1.p.2">Names of transfer codings <em class="bcp14">MUST NOT</em> overlap with names of content codings (<a href="p2-semantics.html#content.codings" title="Content Codings">Section 3.1.2.1</a> of <a href="#Part2" id="rfc.xref.Part2.33"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>) unless the encoding transformation is identical, as is the case for the compression codings defined in <a href="#compression.codings" title="Compression Codings">Section&nbsp;4.2</a>.
     2711               <p id="rfc.section.8.4.1.p.2">Names of transfer codings <em class="bcp14">MUST NOT</em> overlap with names of content codings (<a href="p2-semantics.html#content.codings" title="Content Codings">Section 3.1.2.1</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.33"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>) unless the encoding transformation is identical, as is the case for the compression codings defined in <a href="#compression.codings" title="Compression Codings">Section&nbsp;4.2</a>.
    27122712               </p>
    27132713               <p id="rfc.section.8.4.1.p.3">Values to be added to this name space require IETF Review (see <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a> of <a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>), and <em class="bcp14">MUST</em> conform to the purpose of transfer coding defined in this specification.
    … …  
    28822882         <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a>&nbsp;<a href="#security.considerations">Security Considerations</a></h1>
    28832883         <p id="rfc.section.9.p.1">This section is meant to inform developers, information providers, and users of known security considerations relevant to
    2884             HTTP message syntax, parsing, and routing. Security considerations about HTTP semantics and payloads are addressed in <a href="#Part2" id="rfc.xref.Part2.34"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>.
     2884            HTTP message syntax, parsing, and routing. Security considerations about HTTP semantics and payloads are addressed in <a href="#RFC7231" id="rfc.xref.RFC7231.34"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>.
    28852885         </p>
    28862886         <div id="establishing.authority">
    … …  
    29192919               without regard to security and privacy considerations, might be used in the commission of a wide range of potential attacks.
    29202920            </p>
    2921             <p id="rfc.section.9.2.p.2">Intermediaries that contain a shared cache are especially vulnerable to cache poisoning attacks, as described in <a href="p6-cache.html#security.considerations" title="Security Considerations">Section 8</a> of <a href="#Part6" id="rfc.xref.Part6.8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>.
     2921            <p id="rfc.section.9.2.p.2">Intermediaries that contain a shared cache are especially vulnerable to cache poisoning attacks, as described in <a href="p6-cache.html#security.considerations" title="Security Considerations">Section 8</a> of <a href="#RFC7234" id="rfc.xref.RFC7234.9"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[RFC7234]</cite></a>.
    29222922            </p>
    29232923            <p id="rfc.section.9.2.p.3">Implementers need to consider the privacy and security implications of their design and coding decisions, and of the configuration
    … …  
    29372937               that most implementations will choose substantially higher limits.
    29382938            </p>
    2939             <p id="rfc.section.9.3.p.3">A server can reject a message that has a request-target that is too long (<a href="p2-semantics.html#status.414" title="414 URI Too Long">Section 6.5.12</a> of <a href="#Part2" id="rfc.xref.Part2.35"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>) or a request payload that is too large (<a href="p2-semantics.html#status.413" title="413 Payload Too Large">Section 6.5.11</a> of <a href="#Part2" id="rfc.xref.Part2.36"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>). Additional status codes related to capacity limits have been defined by extensions to HTTP <a href="#RFC6585" id="rfc.xref.RFC6585.1"><cite title="Additional HTTP Status Codes">[RFC6585]</cite></a>.
     2939            <p id="rfc.section.9.3.p.3">A server can reject a message that has a request-target that is too long (<a href="p2-semantics.html#status.414" title="414 URI Too Long">Section 6.5.12</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.35"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>) or a request payload that is too large (<a href="p2-semantics.html#status.413" title="413 Payload Too Large">Section 6.5.11</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.36"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>). Additional status codes related to capacity limits have been defined by extensions to HTTP <a href="#RFC6585" id="rfc.xref.RFC6585.1"><cite title="Additional HTTP Status Codes">[RFC6585]</cite></a>.
    29402940            </p>
    29412941            <p id="rfc.section.9.3.p.4">Recipients ought to carefully limit the extent to which they process other protocol elements, including (but not limited to)
    … …  
    30793079      <table>
    30803080         <tr>
    3081             <td class="reference"><b id="Part2">[Part2]</b></td>
    3082             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p2-semantics-latest (work in progress), May&nbsp;2014.
    3083             </td>
    3084          </tr>
    3085          <tr>
    3086             <td class="reference"><b id="Part4">[Part4]</b></td>
    3087             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-latest (work in progress), May&nbsp;2014.
    3088             </td>
    3089          </tr>
    3090          <tr>
    3091             <td class="reference"><b id="Part5">[Part5]</b></td>
    3092             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">Hypertext Transfer Protocol (HTTP/1.1): Range Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-latest (work in progress), May&nbsp;2014.
    3093             </td>
    3094          </tr>
    3095          <tr>
    3096             <td class="reference"><b id="Part6">[Part6]</b></td>
    3097             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:mnot@mnot.net" title="Akamai">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">Hypertext Transfer Protocol (HTTP/1.1): Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-latest (work in progress), May&nbsp;2014.
    3098             </td>
    3099          </tr>
    3100          <tr>
    3101             <td class="reference"><b id="Part7">[Part7]</b></td>
    3102             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p7-auth-latest">Hypertext Transfer Protocol (HTTP/1.1): Authentication</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p7-auth-latest (work in progress), May&nbsp;2014.
    3103             </td>
    3104          </tr>
    3105          <tr>
    31063081            <td class="reference"><b id="RFC0793">[RFC0793]</b></td>
    31073082            <td class="top">Postel, J., “<a href="http://tools.ietf.org/html/rfc793">Transmission Control Protocol</a>”, STD&nbsp;7, RFC&nbsp;793, September&nbsp;1981.
    … …  
    31363111            <td class="reference"><b id="RFC5234">[RFC5234]</b></td>
    31373112            <td class="top"><a href="mailto:dcrocker@bbiw.net" title="Brandenburg InternetWorking">Crocker, D., Ed.</a> and <a href="mailto:paul.overell@thus.net" title="THUS plc.">P. Overell</a>, “<a href="http://tools.ietf.org/html/rfc5234">Augmented BNF for Syntax Specifications: ABNF</a>”, STD&nbsp;68, RFC&nbsp;5234, January&nbsp;2008.
     3113            </td>
     3114         </tr>
     3115         <tr>
     3116            <td class="reference"><b id="RFC7231">[RFC7231]</b></td>
     3117            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p2-semantics-latest (work in progress), May&nbsp;2014.
     3118            </td>
     3119         </tr>
     3120         <tr>
     3121            <td class="reference"><b id="RFC7232">[RFC7232]</b></td>
     3122            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-latest (work in progress), May&nbsp;2014.
     3123            </td>
     3124         </tr>
     3125         <tr>
     3126            <td class="reference"><b id="RFC7233">[RFC7233]</b></td>
     3127            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">Hypertext Transfer Protocol (HTTP/1.1): Range Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-latest (work in progress), May&nbsp;2014.
     3128            </td>
     3129         </tr>
     3130         <tr>
     3131            <td class="reference"><b id="RFC7234">[RFC7234]</b></td>
     3132            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:mnot@mnot.net" title="Akamai">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">Hypertext Transfer Protocol (HTTP/1.1): Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-latest (work in progress), May&nbsp;2014.
     3133            </td>
     3134         </tr>
     3135         <tr>
     3136            <td class="reference"><b id="RFC7235">[RFC7235]</b></td>
     3137            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p7-auth-latest">Hypertext Transfer Protocol (HTTP/1.1): Authentication</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p7-auth-latest (work in progress), May&nbsp;2014.
    31383138            </td>
    31393139         </tr>
    … …  
    37663766            </li>
    37673767            <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul>
    3768                   <li><em>Part2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.1">1</a>, <a href="#rfc.xref.Part2.2">2.1</a>, <a href="#rfc.xref.Part2.3">2.1</a>, <a href="#rfc.xref.Part2.4">2.7</a>, <a href="#rfc.xref.Part2.5">2.7.1</a>, <a href="#rfc.xref.Part2.6">3.1.1</a>, <a href="#rfc.xref.Part2.7">3.1.1</a>, <a href="#rfc.xref.Part2.8">3.1.2</a>, <a href="#rfc.xref.Part2.9">3.2</a>, <a href="#rfc.xref.Part2.10">3.2.1</a>, <a href="#rfc.xref.Part2.11">3.3</a>, <a href="#rfc.xref.Part2.12">3.3</a>, <a href="#rfc.xref.Part2.13">3.3</a>, <a href="#rfc.xref.Part2.14">3.3.1</a>, <a href="#rfc.xref.Part2.15">3.3.1</a>, <a href="#rfc.xref.Part2.16">3.3.2</a>, <a href="#rfc.xref.Part2.17">3.3.2</a>, <a href="#rfc.xref.Part2.18">3.3.2</a>, <a href="#rfc.xref.Part2.19">4.1.2</a>, <a href="#rfc.xref.Part2.20">4.1.2</a>, <a href="#rfc.xref.Part2.21">4.3</a>, <a href="#rfc.xref.Part2.22">5.1</a>, <a href="#rfc.xref.Part2.23">5.3.3</a>, <a href="#rfc.xref.Part2.24">5.3.4</a>, <a href="#rfc.xref.Part2.25">5.6</a>, <a href="#rfc.xref.Part2.26">5.7.2</a>, <a href="#rfc.xref.Part2.27">5.7.2</a>, <a href="#rfc.xref.Part2.28">6.3.1</a>, <a href="#rfc.xref.Part2.29">6.3.2</a>, <a href="#rfc.xref.Part2.30">6.3.2</a>, <a href="#rfc.xref.Part2.31">6.7</a>, <a href="#rfc.xref.Part2.32">6.7</a>, <a href="#rfc.xref.Part2.33">8.4.1</a>, <a href="#rfc.xref.Part2.34">9</a>, <a href="#rfc.xref.Part2.35">9.3</a>, <a href="#rfc.xref.Part2.36">9.3</a>, <a href="#Part2"><b>11.1</b></a><ul>
    3769                         <li><em>Section 2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.4">2.7</a></li>
    3770                         <li><em>Section 3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.16">3.3.2</a></li>
    3771                         <li><em>Section 3.1.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.14">3.3.1</a>, <a href="#rfc.xref.Part2.33">8.4.1</a></li>
    3772                         <li><em>Section 3.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.26">5.7.2</a></li>
    3773                         <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.6">3.1.1</a></li>
    3774                         <li><em>Section 4.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.29">6.3.2</a></li>
    3775                         <li><em>Section 4.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.28">6.3.1</a>, <a href="#rfc.xref.Part2.30">6.3.2</a></li>
    3776                         <li><em>Section 4.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.3">2.1</a>, <a href="#rfc.xref.Part2.12">3.3</a></li>
    3777                         <li><em>Section 4.3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.11">3.3</a>, <a href="#rfc.xref.Part2.17">3.3.2</a></li>
    3778                         <li><em>Section 4.3.6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.13">3.3</a>, <a href="#rfc.xref.Part2.15">3.3.1</a>, <a href="#rfc.xref.Part2.18">3.3.2</a>, <a href="#rfc.xref.Part2.23">5.3.3</a></li>
    3779                         <li><em>Section 4.3.7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.24">5.3.4</a></li>
    3780                         <li><em>Section 5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.19">4.1.2</a></li>
    3781                         <li><em>Section 5.1.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.31">6.7</a></li>
    3782                         <li><em>Section 5.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.21">4.3</a></li>
    3783                         <li><em>Section 6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.5">2.7.1</a>, <a href="#rfc.xref.Part2.8">3.1.2</a></li>
    3784                         <li><em>Section 6.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.25">5.6</a></li>
    3785                         <li><em>Section 6.3.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.27">5.7.2</a></li>
    3786                         <li><em>Section 6.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.32">6.7</a></li>
    3787                         <li><em>Section 6.5.11</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.36">9.3</a></li>
    3788                         <li><em>Section 6.5.12</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.7">3.1.1</a>, <a href="#rfc.xref.Part2.35">9.3</a></li>
    3789                         <li><em>Section 7.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.20">4.1.2</a></li>
    3790                         <li><em>Section 7.1.1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.9">3.2</a></li>
    3791                         <li><em>Section 8.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.10">3.2.1</a></li>
    3792                         <li><em>Appendix A</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.2">2.1</a></li>
    3793                      </ul>
    3794                   </li>
    3795                   <li><em>Part4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">1</a>, <a href="#rfc.xref.Part4.2">3.3.1</a>, <a href="#rfc.xref.Part4.3">3.3.2</a>, <a href="#Part4"><b>11.1</b></a><ul>
    3796                         <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.2">3.3.1</a>, <a href="#rfc.xref.Part4.3">3.3.2</a></li>
    3797                      </ul>
    3798                   </li>
    3799                   <li><em>Part5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.1">1</a>, <a href="#Part5"><b>11.1</b></a></li>
    3800                   <li><em>Part6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.1">1</a>, <a href="#rfc.xref.Part6.2">2.4</a>, <a href="#rfc.xref.Part6.3">3.4</a>, <a href="#rfc.xref.Part6.4">5.2</a>, <a href="#rfc.xref.Part6.5">5.7.2</a>, <a href="#rfc.xref.Part6.6">5.7.2</a>, <a href="#rfc.xref.Part6.7">6.1</a>, <a href="#rfc.xref.Part6.8">9.2</a>, <a href="#Part6"><b>11.1</b></a><ul>
    3801                         <li><em>Section 2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.2">2.4</a></li>
    3802                         <li><em>Section 3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.3">3.4</a></li>
    3803                         <li><em>Section 5.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.5">5.7.2</a>, <a href="#rfc.xref.Part6.7">6.1</a></li>
    3804                         <li><em>Section 5.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.6">5.7.2</a></li>
    3805                         <li><em>Section 8</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.8">9.2</a></li>
    3806                      </ul>
    3807                   </li>
    3808                   <li><em>Part7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.1">1</a>, <a href="#rfc.xref.Part7.2">4.1.2</a>, <a href="#Part7"><b>11.1</b></a></li>
    38093768                  <li>phishing&nbsp;&nbsp;<a href="#rfc.iref.p.2"><b>9.1</b></a></li>
    38103769                  <li>proxy&nbsp;&nbsp;<a href="#rfc.iref.p.1"><b>2.3</b></a></li>
    … …  
    38823841                  <li><em>RFC6265</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC6265.1">2.7.2</a>, <a href="#rfc.xref.RFC6265.2">3.2.2</a>, <a href="#rfc.xref.RFC6265.3">4.1.2</a>, <a href="#RFC6265"><b>11.2</b></a></li>
    38833842                  <li><em>RFC6585</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC6585.1">9.3</a>, <a href="#RFC6585"><b>11.2</b></a></li>
     3843                  <li><em>RFC7231</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7231.1">1</a>, <a href="#rfc.xref.RFC7231.2">2.1</a>, <a href="#rfc.xref.RFC7231.3">2.1</a>, <a href="#rfc.xref.RFC7231.4">2.7</a>, <a href="#rfc.xref.RFC7231.5">2.7.1</a>, <a href="#rfc.xref.RFC7231.6">3.1.1</a>, <a href="#rfc.xref.RFC7231.7">3.1.1</a>, <a href="#rfc.xref.RFC7231.8">3.1.2</a>, <a href="#rfc.xref.RFC7231.9">3.2</a>, <a href="#rfc.xref.RFC7231.10">3.2.1</a>, <a href="#rfc.xref.RFC7231.11">3.3</a>, <a href="#rfc.xref.RFC7231.12">3.3</a>, <a href="#rfc.xref.RFC7231.13">3.3</a>, <a href="#rfc.xref.RFC7231.14">3.3.1</a>, <a href="#rfc.xref.RFC7231.15">3.3.1</a>, <a href="#rfc.xref.RFC7231.16">3.3.2</a>, <a href="#rfc.xref.RFC7231.17">3.3.2</a>, <a href="#rfc.xref.RFC7231.18">3.3.2</a>, <a href="#rfc.xref.RFC7231.19">4.1.2</a>, <a href="#rfc.xref.RFC7231.20">4.1.2</a>, <a href="#rfc.xref.RFC7231.21">4.3</a>, <a href="#rfc.xref.RFC7231.22">5.1</a>, <a href="#rfc.xref.RFC7231.23">5.3.3</a>, <a href="#rfc.xref.RFC7231.24">5.3.4</a>, <a href="#rfc.xref.RFC7231.25">5.6</a>, <a href="#rfc.xref.RFC7231.26">5.7.2</a>, <a href="#rfc.xref.RFC7231.27">5.7.2</a>, <a href="#rfc.xref.RFC7231.28">6.3.1</a>, <a href="#rfc.xref.RFC7231.29">6.3.2</a>, <a href="#rfc.xref.RFC7231.30">6.3.2</a>, <a href="#rfc.xref.RFC7231.31">6.7</a>, <a href="#rfc.xref.RFC7231.32">6.7</a>, <a href="#rfc.xref.RFC7231.33">8.4.1</a>, <a href="#rfc.xref.RFC7231.34">9</a>, <a href="#rfc.xref.RFC7231.35">9.3</a>, <a href="#rfc.xref.RFC7231.36">9.3</a>, <a href="#RFC7231"><b>11.1</b></a><ul>
     3844                        <li><em>Section 2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7231.4">2.7</a></li>
     3845                        <li><em>Section 3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7231.16">3.3.2</a></li>
     3846                        <li><em>Section 3.1.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7231.14">3.3.1</a>, <a href="#rfc.xref.RFC7231.33">8.4.1</a></li>
     3847                        <li><em>Section 3.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7231.26">5.7.2</a></li>
     3848                        <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7231.6">3.1.1</a></li>
     3849                        <li><em>Section 4.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7231.29">6.3.2</a></li>
     3850                        <li><em>Section 4.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7231.28">6.3.1</a>, <a href="#rfc.xref.RFC7231.30">6.3.2</a></li>
     3851                        <li><em>Section 4.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7231.3">2.1</a>, <a href="#rfc.xref.RFC7231.12">3.3</a></li>
     3852                        <li><em>Section 4.3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7231.11">3.3</a>, <a href="#rfc.xref.RFC7231.17">3.3.2</a></li>
     3853                        <li><em>Section 4.3.6</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7231.13">3.3</a>, <a href="#rfc.xref.RFC7231.15">3.3.1</a>, <a href="#rfc.xref.RFC7231.18">3.3.2</a>, <a href="#rfc.xref.RFC7231.23">5.3.3</a></li>
     3854                        <li><em>Section 4.3.7</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7231.24">5.3.4</a></li>
     3855                        <li><em>Section 5</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7231.19">4.1.2</a></li>
     3856                        <li><em>Section 5.1.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7231.31">6.7</a></li>
     3857                        <li><em>Section 5.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7231.21">4.3</a></li>
     3858                        <li><em>Section 6</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7231.5">2.7.1</a>, <a href="#rfc.xref.RFC7231.8">3.1.2</a></li>
     3859                        <li><em>Section 6.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7231.25">5.6</a></li>
     3860                        <li><em>Section 6.3.4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7231.27">5.7.2</a></li>
     3861                        <li><em>Section 6.4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7231.32">6.7</a></li>
     3862                        <li><em>Section 6.5.11</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7231.36">9.3</a></li>
     3863                        <li><em>Section 6.5.12</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7231.7">3.1.1</a>, <a href="#rfc.xref.RFC7231.35">9.3</a></li>
     3864                        <li><em>Section 7.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7231.20">4.1.2</a></li>
     3865                        <li><em>Section 7.1.1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7231.9">3.2</a></li>
     3866                        <li><em>Section 8.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7231.10">3.2.1</a></li>
     3867                        <li><em>Appendix A</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7231.2">2.1</a></li>
     3868                     </ul>
     3869                  </li>
     3870                  <li><em>RFC7232</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7232.1">1</a>, <a href="#rfc.xref.RFC7232.2">3.3.1</a>, <a href="#rfc.xref.RFC7232.3">3.3.2</a>, <a href="#RFC7232"><b>11.1</b></a><ul>
     3871                        <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7232.2">3.3.1</a>, <a href="#rfc.xref.RFC7232.3">3.3.2</a></li>
     3872                     </ul>
     3873                  </li>
     3874                  <li><em>RFC7233</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7233.1">1</a>, <a href="#RFC7233"><b>11.1</b></a></li>
     3875                  <li><em>RFC7234</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7234.1">1</a>, <a href="#rfc.xref.RFC7234.2">1</a>, <a href="#rfc.xref.RFC7234.3">2.4</a>, <a href="#rfc.xref.RFC7234.4">3.4</a>, <a href="#rfc.xref.RFC7234.5">5.2</a>, <a href="#rfc.xref.RFC7234.6">5.7.2</a>, <a href="#rfc.xref.RFC7234.7">5.7.2</a>, <a href="#rfc.xref.RFC7234.8">6.1</a>, <a href="#rfc.xref.RFC7234.9">9.2</a>, <a href="#RFC7234"><b>11.1</b></a><ul>
     3876                        <li><em>Section 2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7234.3">2.4</a></li>
     3877                        <li><em>Section 3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7234.4">3.4</a></li>
     3878                        <li><em>Section 5.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7234.6">5.7.2</a>, <a href="#rfc.xref.RFC7234.8">6.1</a></li>
     3879                        <li><em>Section 5.5</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7234.7">5.7.2</a></li>
     3880                        <li><em>Section 8</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7234.9">9.2</a></li>
     3881                     </ul>
     3882                  </li>
     3883                  <li><em>RFC7235</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7235.1">4.1.2</a>, <a href="#RFC7235"><b>11.1</b></a></li>
    38843884               </ul>
    38853885            </li>

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

    r2628 r2629  
    1717  <!ENTITY mdash "&#8212;">
    1818  <!ENTITY Note "<x:h xmlns:x='http://purl.org/net/xml2rfc/ext'>Note:</x:h>">
    19   <!ENTITY caching-overview       "<xref target='Part6' x:rel='#caching.overview' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    20   <!ENTITY cache-incomplete       "<xref target='Part6' x:rel='#response.cacheability' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    21   <!ENTITY cache-poisoning        "<xref target='Part6' x:rel='#security.considerations' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    22   <!ENTITY payload                "<xref target='Part2' x:rel='#payload' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    23   <!ENTITY media-type             "<xref target='Part2' x:rel='#media.type' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    24   <!ENTITY content-codings        "<xref target='Part2' x:rel='#content.codings' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    25   <!ENTITY CONNECT                "<xref target='Part2' x:rel='#CONNECT' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    26   <!ENTITY content.negotiation    "<xref target='Part2' x:rel='#content.negotiation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    27   <!ENTITY diff-mime              "<xref target='Part2' x:rel='#differences.between.http.and.mime' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    28   <!ENTITY representation         "<xref target='Part2' x:rel='#representations' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    29   <!ENTITY GET                    "<xref target='Part2' x:rel='#GET' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    30   <!ENTITY HEAD                   "<xref target='Part2' x:rel='#HEAD' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    31   <!ENTITY header-allow           "<xref target='Part2' x:rel='#header.allow' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    32   <!ENTITY header-cache-control   "<xref target='Part6' x:rel='#header.cache-control' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    33   <!ENTITY header-content-encoding    "<xref target='Part2' x:rel='#header.content-encoding' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    34   <!ENTITY header-content-location    "<xref target='Part2' x:rel='#header.content-location' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    35   <!ENTITY header-content-range   "<xref target='Part5' x:rel='#header.content-range' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    36   <!ENTITY header-content-type    "<xref target='Part2' x:rel='#header.content-type' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    37   <!ENTITY header-date            "<xref target='Part2' x:rel='#header.date' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    38   <!ENTITY header-etag            "<xref target='Part4' x:rel='#header.etag' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    39   <!ENTITY header-expect          "<xref target='Part2' x:rel='#header.expect' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    40   <!ENTITY header-expires         "<xref target='Part6' x:rel='#header.expires' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    41   <!ENTITY header-last-modified   "<xref target='Part4' x:rel='#header.last-modified' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    42   <!ENTITY header-mime-version    "<xref target='Part2' x:rel='#mime-version' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    43   <!ENTITY header-pragma          "<xref target='Part6' x:rel='#header.pragma' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    44   <!ENTITY header-proxy-authenticate  "<xref target='Part7' x:rel='#header.proxy-authenticate' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    45   <!ENTITY header-proxy-authorization "<xref target='Part7' x:rel='#header.proxy-authorization' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    46   <!ENTITY header-server          "<xref target='Part2' x:rel='#header.server' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    47   <!ENTITY header-warning         "<xref target='Part6' x:rel='#header.warning' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    48   <!ENTITY idempotent-methods     "<xref target='Part2' x:rel='#idempotent.methods' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    49   <!ENTITY safe-methods           "<xref target='Part2' x:rel='#safe.methods' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    50   <!ENTITY methods                "<xref target='Part2' x:rel='#methods' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    51   <!ENTITY OPTIONS                "<xref target='Part2' x:rel='#OPTIONS' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    52   <!ENTITY qvalue                 "<xref target='Part2' x:rel='#quality.values' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    53   <!ENTITY request-header-fields  "<xref target='Part2' x:rel='#request.header.fields' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    54   <!ENTITY response-control-data  "<xref target='Part2' x:rel='#response.control.data' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    55   <!ENTITY resource               "<xref target='Part2' x:rel='#resources' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    56   <!ENTITY semantics              "<xref target='Part2' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    57   <!ENTITY status-codes           "<xref target='Part2' x:rel='#status.codes' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    58   <!ENTITY status-1xx             "<xref target='Part2' x:rel='#status.1xx' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    59   <!ENTITY status-203             "<xref target='Part2' x:rel='#status.203' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    60   <!ENTITY status-3xx             "<xref target='Part2' x:rel='#status.3xx' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    61   <!ENTITY status-304             "<xref target='Part4' x:rel='#status.304' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    62   <!ENTITY status-4xx             "<xref target='Part2' x:rel='#status.4xx' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    63   <!ENTITY status-413             "<xref target='Part2' x:rel='#status.413' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    64   <!ENTITY status-414             "<xref target='Part2' x:rel='#status.414' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    65   <!ENTITY iana-header-registry   "<xref target='Part2' x:rel='#header.field.registry' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     19  <!ENTITY caching-overview       "<xref target='RFC7234' x:rel='#caching.overview' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     20  <!ENTITY cache-incomplete       "<xref target='RFC7234' x:rel='#response.cacheability' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     21  <!ENTITY cache-poisoning        "<xref target='RFC7234' x:rel='#security.considerations' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     22  <!ENTITY payload                "<xref target='RFC7231' x:rel='#payload' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     23  <!ENTITY media-type             "<xref target='RFC7231' x:rel='#media.type' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     24  <!ENTITY content-codings        "<xref target='RFC7231' x:rel='#content.codings' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     25  <!ENTITY CONNECT                "<xref target='RFC7231' x:rel='#CONNECT' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     26  <!ENTITY content.negotiation    "<xref target='RFC7231' x:rel='#content.negotiation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     27  <!ENTITY diff-mime              "<xref target='RFC7231' x:rel='#differences.between.http.and.mime' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     28  <!ENTITY representation         "<xref target='RFC7231' x:rel='#representations' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     29  <!ENTITY GET                    "<xref target='RFC7231' x:rel='#GET' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     30  <!ENTITY HEAD                   "<xref target='RFC7231' x:rel='#HEAD' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     31  <!ENTITY header-allow           "<xref target='RFC7231' x:rel='#header.allow' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     32  <!ENTITY header-cache-control   "<xref target='RFC7234' x:rel='#header.cache-control' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     33  <!ENTITY header-content-encoding    "<xref target='RFC7231' x:rel='#header.content-encoding' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     34  <!ENTITY header-content-location    "<xref target='RFC7231' x:rel='#header.content-location' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     35  <!ENTITY header-content-range   "<xref target='RFC7233' x:rel='#header.content-range' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     36  <!ENTITY header-content-type    "<xref target='RFC7231' x:rel='#header.content-type' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     37  <!ENTITY header-date            "<xref target='RFC7231' x:rel='#header.date' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     38  <!ENTITY header-etag            "<xref target='RFC7232' x:rel='#header.etag' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     39  <!ENTITY header-expect          "<xref target='RFC7231' x:rel='#header.expect' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     40  <!ENTITY header-expires         "<xref target='RFC7234' x:rel='#header.expires' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     41  <!ENTITY header-last-modified   "<xref target='RFC7232' x:rel='#header.last-modified' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     42  <!ENTITY header-mime-version    "<xref target='RFC7231' x:rel='#mime-version' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     43  <!ENTITY header-pragma          "<xref target='RFC7234' x:rel='#header.pragma' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     44  <!ENTITY header-proxy-authenticate  "<xref target='RFC7235' x:rel='#header.proxy-authenticate' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     45  <!ENTITY header-proxy-authorization "<xref target='RFC7235' x:rel='#header.proxy-authorization' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     46  <!ENTITY header-server          "<xref target='RFC7231' x:rel='#header.server' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     47  <!ENTITY header-warning         "<xref target='RFC7234' x:rel='#header.warning' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     48  <!ENTITY idempotent-methods     "<xref target='RFC7231' x:rel='#idempotent.methods' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     49  <!ENTITY safe-methods           "<xref target='RFC7231' x:rel='#safe.methods' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     50  <!ENTITY methods                "<xref target='RFC7231' x:rel='#methods' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     51  <!ENTITY OPTIONS                "<xref target='RFC7231' x:rel='#OPTIONS' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     52  <!ENTITY qvalue                 "<xref target='RFC7231' x:rel='#quality.values' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     53  <!ENTITY request-header-fields  "<xref target='RFC7231' x:rel='#request.header.fields' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     54  <!ENTITY response-control-data  "<xref target='RFC7231' x:rel='#response.control.data' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     55  <!ENTITY resource               "<xref target='RFC7231' x:rel='#resources' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     56  <!ENTITY semantics              "<xref target='RFC7231' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     57  <!ENTITY status-codes           "<xref target='RFC7231' x:rel='#status.codes' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     58  <!ENTITY status-1xx             "<xref target='RFC7231' x:rel='#status.1xx' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     59  <!ENTITY status-203             "<xref target='RFC7231' x:rel='#status.203' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     60  <!ENTITY status-3xx             "<xref target='RFC7231' x:rel='#status.3xx' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     61  <!ENTITY status-304             "<xref target='RFC7232' x:rel='#status.304' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     62  <!ENTITY status-4xx             "<xref target='RFC7231' x:rel='#status.4xx' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     63  <!ENTITY status-413             "<xref target='RFC7231' x:rel='#status.413' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     64  <!ENTITY status-414             "<xref target='RFC7231' x:rel='#status.414' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     65  <!ENTITY iana-header-registry   "<xref target='RFC7231' x:rel='#header.field.registry' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    6666]>
    6767<?rfc toc="yes" ?>
    … …  
    156156   a series of documents that collectively form the HTTP/1.1 specification:
    157157   <list style="empty">
    158     <t>RFC xxx1: Message Syntax and Routing</t>
    159     <t><xref target="Part2" x:fmt="none">RFC xxx2</xref>: Semantics and Content</t>
    160     <t><xref target="Part4" x:fmt="none">RFC xxx3</xref>: Conditional Requests</t>
    161     <t><xref target="Part5" x:fmt="none">RFC xxx4</xref>: Range Requests</t>
    162     <t><xref target="Part6" x:fmt="none">RFC xxx5</xref>: Caching</t>
    163     <t><xref target="Part7" x:fmt="none">RFC xxx6</xref>: Authentication</t>
     158    <t>RFC 7230: Message Syntax and Routing</t>
     159    <t><xref target="RFC7231" x:fmt="none">RFC 7231</xref>: Semantics and Content</t>
     160    <t><xref target="RFC7232" x:fmt="none">RFC 7232</xref>: Conditional Requests</t>
     161    <t><xref target="RFC7233" x:fmt="none">RFC 7233</xref>: Range Requests</t>
     162    <t><xref target="RFC7234" x:fmt="none">RFC 7234</xref>: Caching</t>
     163    <t><xref target="RFC7234" x:fmt="none">RFC 7235</xref>: Authentication</t>
    164164   </list>
    165165</t>
    … …  
    20632063   <x:ref>Content-Length</x:ref>), routing (e.g., <x:ref>Host</x:ref>),
    20642064   request modifiers (e.g., controls and conditionals in
    2065    &request-header-fields;), authentication (e.g., see <xref target="Part7"/>
     2065   &request-header-fields;), authentication (e.g., see <xref target="RFC7235"/>
    20662066   and <xref target="RFC6265"/>), response control data (e.g., see
    20672067   &response-control-data;), or determining how to process the payload
    … …  
    22702270   HTTP communication is initiated by a user agent for some purpose.
    22712271   The purpose is a combination of request semantics, which are defined in
    2272    <xref target="Part2"/>, and a target resource upon which to apply those
     2272   <xref target="RFC7231"/>, and a target resource upon which to apply those
    22732273   semantics.  A URI reference (<xref target="uri"/>) is typically used as
    22742274   an identifier for the "<x:dfn>target resource</x:dfn>", which a user agent
    … …  
    22882288</t>
    22892289<t>
    2290    If the client has a cache <xref target="Part6"/> and the request can be
     2290   If the client has a cache <xref target="RFC7234"/> and the request can be
    22912291   satisfied by it, then the request is
    22922292   usually directed there first.
    … …  
    44744474<references title="Normative References">
    44754475
    4476 <reference anchor="Part2">
     4476<reference anchor="RFC7231">
    44774477  <front>
    44784478    <title>Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</title>
    … …  
    45244524</reference>
    45254525
    4526 <reference anchor="Part4">
     4526<reference anchor="RFC7232">
    45274527  <front>
    45284528    <title>Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</title>
    … …  
    45454545</reference>
    45464546
    4547 <reference anchor="Part5">
     4547<reference anchor="RFC7233">
    45484548  <front>
    45494549    <title>Hypertext Transfer Protocol (HTTP/1.1): Range Requests</title>
    … …  
    45684568</reference>
    45694569
    4570 <reference anchor="Part6">
     4570<reference anchor="RFC7234">
    45714571  <front>
    45724572    <title>Hypertext Transfer Protocol (HTTP/1.1): Caching</title>
    … …  
    45934593</reference>
    45944594
    4595 <reference anchor="Part7">
     4595<reference anchor="RFC7235">
    45964596  <front>
    45974597    <title>Hypertext Transfer Protocol (HTTP/1.1): Authentication</title>

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

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

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

    r2628 r2629  
    1717  <!ENTITY mdash "&#8212;">
    1818  <!ENTITY Note "<x:h xmlns:x='http://purl.org/net/xml2rfc/ext'>Note:</x:h>">
    19   <!ENTITY architecture               "<xref target='Part1' x:rel='#architecture' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    20   <!ENTITY conformance                "<xref target='Part1' x:rel='#conformance' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    21   <!ENTITY notation                   "<xref target='Part1' x:rel='#notation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    22   <!ENTITY acks                       "<xref target='Part1' x:rel='#acks' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    23   <!ENTITY messaging                  "<xref target='Part1' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    24   <!ENTITY conditional                "<xref target='Part4' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    25   <!ENTITY range                      "<xref target='Part5' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    26   <!ENTITY caching                    "<xref target='Part6' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    27   <!ENTITY auth                       "<xref target='Part7' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     19  <!ENTITY architecture               "<xref target='RFC7230' x:rel='#architecture' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     20  <!ENTITY conformance                "<xref target='RFC7230' x:rel='#conformance' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     21  <!ENTITY notation                   "<xref target='RFC7230' x:rel='#notation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     22  <!ENTITY acks                       "<xref target='RFC7230' x:rel='#acks' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     23  <!ENTITY messaging                  "<xref target='RFC7230' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     24  <!ENTITY conditional                "<xref target='RFC7232' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     25  <!ENTITY range                      "<xref target='RFC7233' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     26  <!ENTITY caching                    "<xref target='RFC7234' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     27  <!ENTITY auth                       "<xref target='RFC7235' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    2828  <!ENTITY content-negotiation        "<xref target='content.negotiation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    2929  <!ENTITY reactive-negotiation       "<xref target='reactive.negotiation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    30   <!ENTITY abnf-extension             "<xref target='Part1' x:rel='#abnf.extension' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    31   <!ENTITY whitespace                 "<xref target='Part1' x:rel='#whitespace' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    32   <!ENTITY field-components           "<xref target='Part1' x:rel='#field.components' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    33   <!ENTITY field-parsing              "<xref target='Part1' x:rel='#field.parsing' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    34   <!ENTITY uri                        "<xref target='Part1' x:rel='#uri' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    35   <!ENTITY effective-request-uri      "<xref target='Part1' x:rel='#effective.request.uri' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    36   <!ENTITY intermediaries             "<xref target='Part1' x:rel='#intermediaries' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    37   <!ENTITY transformations            "<xref target='Part1' x:rel='#message.transformations' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    38   <!ENTITY chunked-encoding           "<xref target='Part1' x:rel='#chunked.encoding' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    39   <!ENTITY http-url                   "<xref target='Part1' x:rel='#http-url' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    40   <!ENTITY http-version               "<xref target='Part1' x:rel='#http.version' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    41   <!ENTITY request-target             "<xref target='Part1' x:rel='#request-target' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     30  <!ENTITY abnf-extension             "<xref target='RFC7230' x:rel='#abnf.extension' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     31  <!ENTITY whitespace                 "<xref target='RFC7230' x:rel='#whitespace' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     32  <!ENTITY field-components           "<xref target='RFC7230' x:rel='#field.components' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     33  <!ENTITY field-parsing              "<xref target='RFC7230' x:rel='#field.parsing' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     34  <!ENTITY uri                        "<xref target='RFC7230' x:rel='#uri' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     35  <!ENTITY effective-request-uri      "<xref target='RFC7230' x:rel='#effective.request.uri' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     36  <!ENTITY intermediaries             "<xref target='RFC7230' x:rel='#intermediaries' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     37  <!ENTITY transformations            "<xref target='RFC7230' x:rel='#message.transformations' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     38  <!ENTITY chunked-encoding           "<xref target='RFC7230' x:rel='#chunked.encoding' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     39  <!ENTITY http-url                   "<xref target='RFC7230' x:rel='#http-url' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     40  <!ENTITY http-version               "<xref target='RFC7230' x:rel='#http.version' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     41  <!ENTITY request-target             "<xref target='RFC7230' x:rel='#request-target' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    4242  <!ENTITY header-accept              "<xref target='header.accept' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    4343  <!ENTITY header-accept-charset      "<xref target='header.accept-charset' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    4444  <!ENTITY header-accept-encoding     "<xref target='header.accept-encoding' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    4545  <!ENTITY header-accept-language     "<xref target='header.accept-language' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    46   <!ENTITY header-accept-ranges       "<xref target='Part5' x:rel='#header.accept-ranges' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    47   <!ENTITY header-age                 "<xref target='Part6' x:rel='#header.age' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    48   <!ENTITY header-authorization       "<xref target='Part7' x:rel='#header.authorization' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    49   <!ENTITY header-cache-control       "<xref target='Part6' x:rel='#header.cache-control' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    50   <!ENTITY header-connection          "<xref target='Part1' x:rel='#header.connection' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    51   <!ENTITY header-content-length      "<xref target='Part1' x:rel='#header.content-length' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     46  <!ENTITY header-accept-ranges       "<xref target='RFC7233' x:rel='#header.accept-ranges' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     47  <!ENTITY header-age                 "<xref target='RFC7234' x:rel='#header.age' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     48  <!ENTITY header-authorization       "<xref target='RFC7235' x:rel='#header.authorization' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     49  <!ENTITY header-cache-control       "<xref target='RFC7234' x:rel='#header.cache-control' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     50  <!ENTITY header-connection          "<xref target='RFC7230' x:rel='#header.connection' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     51  <!ENTITY header-content-length      "<xref target='RFC7230' x:rel='#header.content-length' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    5252  <!ENTITY header-content-location    "<xref target='header.content-location' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    53   <!ENTITY header-content-range       "<xref target='Part5' x:rel='#header.content-range' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     53  <!ENTITY header-content-range       "<xref target='RFC7233' x:rel='#header.content-range' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    5454  <!ENTITY header-content-type        "<xref target='header.content-type' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    55   <!ENTITY header-etag                "<xref target='Part4' x:rel='#header.etag' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    56   <!ENTITY header-expires             "<xref target='Part6' x:rel='#header.expires' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    57   <!ENTITY header-fields              "<xref target='Part1' x:rel='#header.fields' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    58   <!ENTITY header-host                "<xref target='Part1' x:rel='#header.host' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    59   <!ENTITY header-if-match            "<xref target='Part4' x:rel='#header.if-match' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    60   <!ENTITY header-if-modified-since   "<xref target='Part4' x:rel='#header.if-modified-since' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    61   <!ENTITY header-if-none-match       "<xref target='Part4' x:rel='#header.if-none-match' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    62   <!ENTITY header-if-range            "<xref target='Part5' x:rel='#header.if-range' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    63   <!ENTITY header-if-unmodified-since "<xref target='Part4' x:rel='#header.if-unmodified-since' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    64   <!ENTITY header-last-modified       "<xref target='Part4' x:rel='#header.last-modified' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    65   <!ENTITY header-pragma              "<xref target='Part6' x:rel='#header.pragma' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    66   <!ENTITY header-proxy-authenticate  "<xref target='Part7' x:rel='#header.proxy-authenticate' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    67   <!ENTITY header-proxy-authorization "<xref target='Part7' x:rel='#header.proxy-authorization' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    68   <!ENTITY header-range               "<xref target='Part5' x:rel='#header.range' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    69   <!ENTITY header-te                  "<xref target='Part1' x:rel='#header.te' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    70   <!ENTITY header-trailer                  "<xref target='Part1' x:rel='#header.trailer' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    71   <!ENTITY header-transfer-encoding   "<xref target='Part1' x:rel='#header.transfer-encoding' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    72   <!ENTITY header-upgrade             "<xref target='Part1' x:rel='#header.upgrade' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     55  <!ENTITY header-etag                "<xref target='RFC7232' x:rel='#header.etag' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     56  <!ENTITY header-expires             "<xref target='RFC7234' x:rel='#header.expires' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     57  <!ENTITY header-fields              "<xref target='RFC7230' x:rel='#header.fields' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     58  <!ENTITY header-host                "<xref target='RFC7230' x:rel='#header.host' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     59  <!ENTITY header-if-match            "<xref target='RFC7232' x:rel='#header.if-match' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     60  <!ENTITY header-if-modified-since   "<xref target='RFC7232' x:rel='#header.if-modified-since' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     61  <!ENTITY header-if-none-match       "<xref target='RFC7232' x:rel='#header.if-none-match' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     62  <!ENTITY header-if-range            "<xref target='RFC7233' x:rel='#header.if-range' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     63  <!ENTITY header-if-unmodified-since "<xref target='RFC7232' x:rel='#header.if-unmodified-since' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     64  <!ENTITY header-last-modified       "<xref target='RFC7232' x:rel='#header.last-modified' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     65  <!ENTITY header-pragma              "<xref target='RFC7234' x:rel='#header.pragma' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     66  <!ENTITY header-proxy-authenticate  "<xref target='RFC7235' x:rel='#header.proxy-authenticate' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     67  <!ENTITY header-proxy-authorization "<xref target='RFC7235' x:rel='#header.proxy-authorization' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     68  <!ENTITY header-range               "<xref target='RFC7233' x:rel='#header.range' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     69  <!ENTITY header-te                  "<xref target='RFC7230' x:rel='#header.te' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     70  <!ENTITY header-trailer                  "<xref target='RFC7230' x:rel='#header.trailer' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     71  <!ENTITY header-transfer-encoding   "<xref target='RFC7230' x:rel='#header.transfer-encoding' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     72  <!ENTITY header-upgrade             "<xref target='RFC7230' x:rel='#header.upgrade' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    7373  <!ENTITY header-user-agent          "<xref target='header.user-agent' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    74   <!ENTITY header-via                 "<xref target='Part1' x:rel='#header.via' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    75   <!ENTITY header-warning             "<xref target='Part6' x:rel='#header.warning' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    76   <!ENTITY header-www-authenticate    "<xref target='Part7' x:rel='#header.www-authenticate' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     74  <!ENTITY header-via                 "<xref target='RFC7230' x:rel='#header.via' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     75  <!ENTITY header-warning             "<xref target='RFC7234' x:rel='#header.warning' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     76  <!ENTITY header-www-authenticate    "<xref target='RFC7235' x:rel='#header.www-authenticate' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    7777  <!ENTITY media-type                "<xref target='media.type' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    78   <!ENTITY message-body               "<xref target='Part1' x:rel='#message.body' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    79   <!ENTITY media-type-message-http    "<xref target='Part1' x:rel='#internet.media.type.message.http' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    80   <!ENTITY persistent-tear-down       "<xref target='Part1' x:rel='#persistent.tear-down' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    81   <!ENTITY status-206                 "<xref target='Part5' x:rel='#status.206' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    82   <!ENTITY status-304                 "<xref target='Part4' x:rel='#status.304' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    83   <!ENTITY status-401                 "<xref target='Part7' x:rel='#status.401' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    84   <!ENTITY status-407                 "<xref target='Part7' x:rel='#status.407' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    85   <!ENTITY status-412                 "<xref target='Part4' x:rel='#status.412' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    86   <!ENTITY status-416                 "<xref target='Part5' x:rel='#status.416' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    87   <!ENTITY p1-security-considerations "<xref target='Part1' x:rel='#security.considerations' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    88   <!ENTITY p4-status-codes            "<xref target='Part4' x:rel='#status.code.definitions' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    89   <!ENTITY p5-status-codes            "<xref target='Part5' x:rel='#range.response' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    90   <!ENTITY p7-status-codes            "<xref target='Part7' x:rel='#status.code.definitions' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    91   <!ENTITY p6-heuristic               "<xref target='Part6' x:rel='#heuristic.freshness' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    92   <!ENTITY p6-explicit                "<xref target='Part6' x:rel='#calculating.freshness.lifetime' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    93   <!ENTITY p6-invalid                 "<xref target='Part6' x:rel='#invalidation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    94   <!ENTITY p6-head                    "<xref target='Part6' x:rel='#head.effects' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     78  <!ENTITY message-body               "<xref target='RFC7230' x:rel='#message.body' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     79  <!ENTITY media-type-message-http    "<xref target='RFC7230' x:rel='#internet.media.type.message.http' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     80  <!ENTITY persistent-tear-down       "<xref target='RFC7230' x:rel='#persistent.tear-down' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     81  <!ENTITY status-206                 "<xref target='RFC7233' x:rel='#status.206' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     82  <!ENTITY status-304                 "<xref target='RFC7232' x:rel='#status.304' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     83  <!ENTITY status-401                 "<xref target='RFC7235' x:rel='#status.401' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     84  <!ENTITY status-407                 "<xref target='RFC7235' x:rel='#status.407' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     85  <!ENTITY status-412                 "<xref target='RFC7232' x:rel='#status.412' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     86  <!ENTITY status-416                 "<xref target='RFC7233' x:rel='#status.416' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     87  <!ENTITY p1-security-considerations "<xref target='RFC7230' x:rel='#security.considerations' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     88  <!ENTITY p4-status-codes            "<xref target='RFC7232' x:rel='#status.code.definitions' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     89  <!ENTITY p5-status-codes            "<xref target='RFC7233' x:rel='#range.response' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     90  <!ENTITY p7-status-codes            "<xref target='RFC7235' x:rel='#status.code.definitions' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     91  <!ENTITY p6-heuristic               "<xref target='RFC7234' x:rel='#heuristic.freshness' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     92  <!ENTITY p6-explicit                "<xref target='RFC7234' x:rel='#calculating.freshness.lifetime' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     93  <!ENTITY p6-invalid                 "<xref target='RFC7234' x:rel='#invalidation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     94  <!ENTITY p6-head                    "<xref target='RFC7234' x:rel='#head.effects' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    9595  <!ENTITY qvalue                     "<xref target='quality.values'/>">
    96   <!ENTITY architecture               "<xref target='Part1' x:rel='#architecture' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    97   <!ENTITY notation                   "<xref target='Part1' x:rel='#notation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    98   <!ENTITY abnf-extension             "<xref target='Part1' x:rel='#abnf.extension' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    99   <!ENTITY acks                       "<xref target='Part1' x:rel='#acks' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    100   <!ENTITY whitespace                 "<xref target='Part1' x:rel='#whitespace' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    101   <!ENTITY field-components           "<xref target='Part1' x:rel='#field.components' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    102   <!ENTITY caching-neg-resp           "<xref target='Part6' x:rel='#caching.negotiated.responses' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    103   <!ENTITY message-body               "<xref target='Part1' x:rel='#message.body' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    104   <!ENTITY multipart-byteranges       "<xref target='Part5' x:rel='#internet.media.type.multipart.byteranges' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    105   <!ENTITY evaluate-conditional       "<xref target='Part4' x:rel='#evaluation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     96  <!ENTITY architecture               "<xref target='RFC7230' x:rel='#architecture' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     97  <!ENTITY notation                   "<xref target='RFC7230' x:rel='#notation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     98  <!ENTITY abnf-extension             "<xref target='RFC7230' x:rel='#abnf.extension' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     99  <!ENTITY acks                       "<xref target='RFC7230' x:rel='#acks' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     100  <!ENTITY whitespace                 "<xref target='RFC7230' x:rel='#whitespace' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     101  <!ENTITY field-components           "<xref target='RFC7230' x:rel='#field.components' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     102  <!ENTITY caching-neg-resp           "<xref target='RFC7234' x:rel='#caching.negotiated.responses' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     103  <!ENTITY message-body               "<xref target='RFC7230' x:rel='#message.body' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     104  <!ENTITY multipart-byteranges       "<xref target='RFC7233' x:rel='#internet.media.type.multipart.byteranges' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     105  <!ENTITY evaluate-conditional       "<xref target='RFC7232' x:rel='#evaluation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    106106  <!ENTITY http-date                  "<xref target='http.date' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    107   <!ENTITY uri                        "<xref target='Part1' x:rel='#uri' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    108   <!ENTITY effective-request-uri      "<xref target='Part1' x:rel='#effective.request.uri' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    109   <!ENTITY compression-codings        "<xref target='Part1' x:rel='#compression.codings' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    110   <!ENTITY transfer-codings           "<xref target='Part1' x:rel='#transfer.codings' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    111   <!ENTITY compress-coding            "<xref target='Part1' x:rel='#compress.coding' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    112   <!ENTITY deflate-coding             "<xref target='Part1' x:rel='#deflate.coding' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    113   <!ENTITY gzip-coding                "<xref target='Part1' x:rel='#gzip.coding' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     107  <!ENTITY uri                        "<xref target='RFC7230' x:rel='#uri' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     108  <!ENTITY effective-request-uri      "<xref target='RFC7230' x:rel='#effective.request.uri' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     109  <!ENTITY compression-codings        "<xref target='RFC7230' x:rel='#compression.codings' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     110  <!ENTITY transfer-codings           "<xref target='RFC7230' x:rel='#transfer.codings' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     111  <!ENTITY compress-coding            "<xref target='RFC7230' x:rel='#compress.coding' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     112  <!ENTITY deflate-coding             "<xref target='RFC7230' x:rel='#deflate.coding' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     113  <!ENTITY gzip-coding                "<xref target='RFC7230' x:rel='#gzip.coding' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    114114]>
    115115<?rfc toc="yes" ?>
    … …  
    209209   intentions were carried out and determine how to interpret the results.
    210210   This document defines HTTP/1.1 request and response semantics in terms of
    211    the architecture defined in <xref target="Part1"/>.
     211   the architecture defined in <xref target="RFC7230"/>.
    212212</t>
    213213<t>
    … …  
    323323   to a given request, usually based on <x:ref>content negotiation</x:ref>.
    324324   This "<x:dfn>selected representation</x:dfn>" is used to provide the data
    325    and metadata for evaluating conditional requests <xref target="Part4"/> and
     325   and metadata for evaluating conditional requests <xref target="RFC7232"/> and
    326326   constructing the payload for <x:ref>200 (OK)</x:ref> and
    327327   <x:ref>304 (Not Modified)</x:ref> responses to GET (<xref target="GET"/>).
    … …  
    479479   <xref target="RFC2388"/>, and the "multipart/byteranges" type is defined
    480480   by this specification for use in some <x:ref>206 (Partial Content)</x:ref>
    481    responses <xref target="Part5"/>.
     481   responses <xref target="RFC7233"/>.
    482482</t>
    483483</section>
    … …  
    11001100   (<xref target="request.conditionals"/>) to make the requested
    11011101   action conditional on the current state of the target resource
    1102    (<xref target="Part4"/>).
     1102   (<xref target="RFC7232"/>).
    11031103</t>
    11041104<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="method"/>
    … …  
    13141314   A client can alter the semantics of GET to be a "range request", requesting
    13151315   transfer of only some part(s) of the selected representation, by sending a
    1316    <x:ref>Range</x:ref> header field in the request (<xref target="Part5"/>).
     1316   <x:ref>Range</x:ref> header field in the request (<xref target="RFC7233"/>).
    13171317</t>
    13181318<t>
    … …  
    17701770   sensitive data that might be disclosed by the response. For example, it
    17711771   would be foolish for a user agent to send stored user credentials
    1772    <xref target="Part7"/> or cookies <xref target="RFC6265"/> in a TRACE
     1772   <xref target="RFC7235"/> or cookies <xref target="RFC6265"/> in a TRACE
    17731773   request. The final recipient of the request &SHOULD; exclude any request
    17741774   header fields that are likely to contain sensitive data when that recipient
    … …  
    20052005  <iref item="conditional request" primary="true"/>
    20062006<t>
    2007    The HTTP conditional request header fields <xref target="Part4"/> allow a
     2007   The HTTP conditional request header fields <xref target="RFC7232"/> allow a
    20082008   client to place a precondition on the state of the target resource, so that
    20092009   the action corresponding to the method semantics will not be applied if the
    … …  
    24082408<t>
    24092409   Two header fields are used for carrying authentication credentials, as
    2410    defined in <xref target="Part7"/>. Note that various custom mechanisms for
     2410   defined in <xref target="RFC7235"/>. Note that various custom mechanisms for
    24112411   user authentication use the Cookie header field for this purpose, as
    24122412   defined in <xref target="RFC6265"/>.
    … …  
    40894089   entity-tag of the newly created resource's representation, so that it can
    40904090   be used in later conditional requests to prevent the "lost update"
    4091    problem <xref target="Part4"/>.
     4091   problem <xref target="RFC7232"/>.
    40924092</t>
    40934093<texttable align="left">
    … …  
    42574257   when the condition is false.
    42584258   Likewise, if the new method might have some use for partial response
    4259    semantics (<xref target="Part5"/>), it ought to document this too.
     4259   semantics (<xref target="RFC7233"/>), it ought to document this too.
    42604260</t>
    42614261<x:note>
    … …  
    51215121<references title="Normative References">
    51225122
    5123 <reference anchor="Part1">
     5123<reference anchor="RFC7230">
    51245124  <front>
    51255125    <title>Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</title>
    … …  
    51485148</reference>
    51495149
    5150 <reference anchor="Part4">
     5150<reference anchor="RFC7232">
    51515151  <front>
    51525152    <title>Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</title>
    … …  
    51745174</reference>
    51755175
    5176 <reference anchor="Part5">
     5176<reference anchor="RFC7233">
    51775177  <front>
    51785178    <title>Hypertext Transfer Protocol (HTTP/1.1): Range Requests</title>
    … …  
    52015201</reference>
    52025202
    5203 <reference anchor="Part6">
     5203<reference anchor="RFC7234">
    52045204  <front>
    52055205    <title>Hypertext Transfer Protocol (HTTP/1.1): Caching</title>
    … …  
    52225222</reference>
    52235223
    5224 <reference anchor="Part7">
     5224<reference anchor="RFC7235">
    52255225  <front>
    52265226    <title>Hypertext Transfer Protocol (HTTP/1.1): Authentication</title>
    … …  
    59575957<t>
    59585958   To be consistent with the method-neutral parsing algorithm of
    5959    <xref target="Part1"/>, the definition of GET has been relaxed so that
     5959   <xref target="RFC7230"/>, the definition of GET has been relaxed so that
    59605960   requests can have a body, even though a body has no meaning for GET.
    59615961   (<xref target="GET"/>)
    … …  
    61196119</t>
    61206120<t>
    6121   The rules below are defined in <xref target="Part1"/>:
     6121  The rules below are defined in <xref target="RFC7230"/>:
    61226122</t>
    61236123<figure><artwork type="abnf2616">
    … …  
    61386138<section xmlns:x="http://purl.org/net/xml2rfc/ext" title="Collected ABNF" anchor="collected.abnf">
    61396139<t>
    6140   In the collected ABNF below, list rules are expanded as per <xref target="Part1" x:rel="#notation"/>.
     6140  In the collected ABNF below, list rules are expanded as per <xref target="RFC7230" x:rel="#notation"/>.
    61416141</t><figure>
    61426142<artwork type="abnf" name="p2-semantics.parsed-abnf">
    … …  
    61516151<x:ref>Allow</x:ref> = [ ( "," / method ) *( OWS "," [ OWS method ] ) ]
    61526152
    6153 <x:ref>BWS</x:ref> = &lt;BWS, defined in [Part1], Section 3.2.3&gt;
     6153<x:ref>BWS</x:ref> = &lt;BWS, defined in [RFC7230], Section 3.2.3&gt;
    61546154
    61556155<x:ref>Content-Encoding</x:ref> = *( "," OWS ) content-coding *( OWS "," [ OWS
    … …  
    61766176<x:ref>Max-Forwards</x:ref> = 1*DIGIT
    61776177
    6178 <x:ref>OWS</x:ref> = &lt;OWS, defined in [Part1], Section 3.2.3&gt;
    6179 
    6180 <x:ref>RWS</x:ref> = &lt;RWS, defined in [Part1], Section 3.2.3&gt;
     6178<x:ref>OWS</x:ref> = &lt;OWS, defined in [RFC7230], Section 3.2.3&gt;
     6179
     6180<x:ref>RWS</x:ref> = &lt;RWS, defined in [RFC7230], Section 3.2.3&gt;
    61816181<x:ref>Referer</x:ref> = absolute-URI / partial-URI
    61826182<x:ref>Retry-After</x:ref> = HTTP-date / delay-seconds
    … …  
    61846184<x:ref>Server</x:ref> = product *( RWS ( product / comment ) )
    61856185
    6186 <x:ref>URI-reference</x:ref> = &lt;URI-reference, defined in [Part1], Section 2.7&gt;
     6186<x:ref>URI-reference</x:ref> = &lt;URI-reference, defined in [RFC7230], Section 2.7&gt;
    61876187<x:ref>User-Agent</x:ref> = product *( RWS ( product / comment ) )
    61886188
    … …  
    61906190 ) )
    61916191
    6192 <x:ref>absolute-URI</x:ref> = &lt;absolute-URI, defined in [Part1], Section 2.7&gt;
     6192<x:ref>absolute-URI</x:ref> = &lt;absolute-URI, defined in [RFC7230], Section 2.7&gt;
    61936193<x:ref>accept-ext</x:ref> = OWS ";" OWS token [ "=" ( token / quoted-string ) ]
    61946194<x:ref>accept-params</x:ref> = weight *accept-ext
    … …  
    61976197<x:ref>charset</x:ref> = token
    61986198<x:ref>codings</x:ref> = content-coding / "identity" / "*"
    6199 <x:ref>comment</x:ref> = &lt;comment, defined in [Part1], Section 3.2.6&gt;
     6199<x:ref>comment</x:ref> = &lt;comment, defined in [RFC7230], Section 3.2.6&gt;
    62006200<x:ref>content-coding</x:ref> = token
    62016201
    … …  
    62206220<x:ref>delay-seconds</x:ref> = 1*DIGIT
    62216221
    6222 <x:ref>field-name</x:ref> = &lt;comment, defined in [Part1], Section 3.2&gt;
     6222<x:ref>field-name</x:ref> = &lt;comment, defined in [RFC7230], Section 3.2&gt;
    62236223
    62246224<x:ref>hour</x:ref> = 2DIGIT
    … …  
    62496249
    62506250<x:ref>parameter</x:ref> = token "=" ( token / quoted-string )
    6251 <x:ref>partial-URI</x:ref> = &lt;partial-URI, defined in [Part1], Section 2.7&gt;
     6251<x:ref>partial-URI</x:ref> = &lt;partial-URI, defined in [RFC7230], Section 2.7&gt;
    62526252<x:ref>product</x:ref> = token [ "/" product-version ]
    62536253<x:ref>product-version</x:ref> = token
    62546254
    6255 <x:ref>quoted-string</x:ref> = &lt;quoted-string, defined in [Part1], Section 3.2.6&gt;
     6255<x:ref>quoted-string</x:ref> = &lt;quoted-string, defined in [RFC7230], Section 3.2.6&gt;
    62566256<x:ref>qvalue</x:ref> = ( "0" [ "." *3DIGIT ] ) / ( "1" [ "." *3"0" ] )
    62576257
    … …  
    62626262
    62636263<x:ref>time-of-day</x:ref> = hour ":" minute ":" second
    6264 <x:ref>token</x:ref> = &lt;token, defined in [Part1], Section 3.2.6&gt;
     6264<x:ref>token</x:ref> = &lt;token, defined in [RFC7230], Section 3.2.6&gt;
    62656265<x:ref>type</x:ref> = token
    62666266

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

    r2628 r2629  
    463463  }
    464464  @bottom-center {
    465        content: "Expires November 2, 2014";
     465       content: "Expires November 7, 2014";
    466466  }
    467467  @bottom-right {
    … …  
    506506      <meta name="dct.creator" content="Reschke, J. F.">
    507507      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p4-conditional-latest">
    508       <meta name="dct.issued" scheme="ISO8601" content="2014-05-01">
     508      <meta name="dct.issued" scheme="ISO8601" content="2014-05-06">
    509509      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    510510      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for distributed, collaborative, hypertext information systems. This document defines HTTP/1.1 conditional requests, including metadata header fields for indicating state changes, request header fields for making preconditions on such state, and rules for constructing the responses to a conditional request when one or more preconditions evaluate to false.">
    … …  
    532532            </tr>
    533533            <tr>
    534                <td class="left">Expires: November 2, 2014</td>
    535                <td class="right">May 1, 2014</td>
     534               <td class="left">Expires: November 7, 2014</td>
     535               <td class="right">May 6, 2014</td>
    536536            </tr>
    537537         </tbody>
    … …  
    561561            in progress”.
    562562         </p>
    563          <p>This Internet-Draft will expire on November 2, 2014.</p>
     563         <p>This Internet-Draft will expire on November 7, 2014.</p>
    564564      </div>
    565565      <div id="rfc.copyrightnotice">
    … …  
    644644      <div id="introduction">
    645645         <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a href="#introduction">Introduction</a></h1>
    646          <p id="rfc.section.1.p.1">Conditional requests are HTTP requests <a href="#Part2" id="rfc.xref.Part2.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a> that include one or more header fields indicating a precondition to be tested before applying the method semantics to the
     646         <p id="rfc.section.1.p.1">Conditional requests are HTTP requests <a href="#RFC7231" id="rfc.xref.RFC7231.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a> that include one or more header fields indicating a precondition to be tested before applying the method semantics to the
    647647            target resource. This document defines the HTTP/1.1 conditional request mechanisms in terms of the architecture, syntax notation,
    648             and conformance criteria defined in <a href="#Part1" id="rfc.xref.Part1.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.
    649          </p>
    650          <p id="rfc.section.1.p.2">Conditional GET requests are the most efficient mechanism for HTTP cache updates <a href="#Part6" id="rfc.xref.Part6.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>. Conditionals can also be applied to state-changing methods, such as PUT and DELETE, to prevent the "lost update" problem:
     648            and conformance criteria defined in <a href="#RFC7230" id="rfc.xref.RFC7230.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>.
     649         </p>
     650         <p id="rfc.section.1.p.2">Conditional GET requests are the most efficient mechanism for HTTP cache updates <a href="#RFC7234" id="rfc.xref.RFC7234.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[RFC7234]</cite></a>. Conditionals can also be applied to state-changing methods, such as PUT and DELETE, to prevent the "lost update" problem:
    651651            one client accidentally overwriting the work of another client that has been acting in parallel.
    652652         </p>
    … …  
    654654            state as observed in a previously obtained representation (one value in that set). A resource might have multiple current
    655655            representations, each with its own observable state. The conditional request mechanisms assume that the mapping of requests
    656             to a "selected representation" (<a href="p2-semantics.html#representations" title="Representations">Section 3</a> of <a href="#Part2" id="rfc.xref.Part2.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>) will be consistent over time if the server intends to take advantage of conditionals. Regardless, if the mapping is inconsistent
     656            to a "selected representation" (<a href="p2-semantics.html#representations" title="Representations">Section 3</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>) will be consistent over time if the server intends to take advantage of conditionals. Regardless, if the mapping is inconsistent
    657657            and the server is unable to select the appropriate representation, then no harm will result when the precondition evaluates
    658658            to false.
    … …  
    665665               in this document are to be interpreted as described in <a href="#RFC2119" id="rfc.xref.RFC2119.1"><cite title="Key words for use in RFCs to Indicate Requirement Levels">[RFC2119]</cite></a>.
    666666            </p>
    667             <p id="rfc.section.1.1.p.2">Conformance criteria and considerations regarding error handling are defined in <a href="p1-messaging.html#conformance" title="Conformance and Error Handling">Section 2.5</a> of <a href="#Part1" id="rfc.xref.Part1.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.
     667            <p id="rfc.section.1.1.p.2">Conformance criteria and considerations regarding error handling are defined in <a href="p1-messaging.html#conformance" title="Conformance and Error Handling">Section 2.5</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>.
    668668            </p>
    669669         </div>
    670670         <div id="notation">
    671671            <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a href="#notation">Syntax Notation</a></h2>
    672             <p id="rfc.section.1.2.p.1">This specification uses the Augmented Backus-Naur Form (ABNF) notation of <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with a list extension, defined in <a href="p1-messaging.html#abnf.extension" title="ABNF list extension: #rule">Section 7</a> of <a href="#Part1" id="rfc.xref.Part1.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, that allows for compact definition of comma-separated lists using a '#' operator (similar to how the '*' operator indicates
     672            <p id="rfc.section.1.2.p.1">This specification uses the Augmented Backus-Naur Form (ABNF) notation of <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with a list extension, defined in <a href="p1-messaging.html#abnf.extension" title="ABNF list extension: #rule">Section 7</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, that allows for compact definition of comma-separated lists using a '#' operator (similar to how the '*' operator indicates
    673673               repetition). <a href="#imported.abnf" title="Imported ABNF">Appendix&nbsp;B</a> describes rules imported from other documents. <a href="#collected.abnf" title="Collected ABNF">Appendix&nbsp;C</a> shows the collected grammar with all list operators expanded to standard ABNF notation.
    674674            </p>
    … …  
    748748               <h3 id="rfc.section.2.2.1"><a href="#rfc.section.2.2.1">2.2.1</a>&nbsp;<a href="#lastmod.generation">Generation</a></h3>
    749749               <p id="rfc.section.2.2.1.p.1">An origin server <em class="bcp14">SHOULD</em> send Last-Modified for any selected representation for which a last modification date can be reasonably and consistently determined,
    750                   since its use in conditional requests and evaluating cache freshness (<a href="#Part6" id="rfc.xref.Part6.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>) results in a substantial reduction of HTTP traffic on the Internet and can be a significant factor in improving service
     750                  since its use in conditional requests and evaluating cache freshness (<a href="#RFC7234" id="rfc.xref.RFC7234.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[RFC7234]</cite></a>) results in a substantial reduction of HTTP traffic on the Internet and can be a significant factor in improving service
    751751                  scalability and reliability.
    752752               </p>
    … …  
    847847               </p>
    848848               <p id="rfc.section.2.3.1.p.3">An origin server <em class="bcp14">SHOULD</em> send ETag for any selected representation for which detection of changes can be reasonably and consistently determined, since
    849                   the entity-tag's use in conditional requests and evaluating cache freshness (<a href="#Part6" id="rfc.xref.Part6.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>) can result in a substantial reduction of HTTP network traffic and can be a significant factor in improving service scalability
     849                  the entity-tag's use in conditional requests and evaluating cache freshness (<a href="#RFC7234" id="rfc.xref.RFC7234.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[RFC7234]</cite></a>) can result in a substantial reduction of HTTP network traffic and can be a significant factor in improving service scalability
    850850                  and reliability.
    851851               </p>
    … …  
    905905            <div id="example.entity.tag.vs.conneg">
    906906               <h3 id="rfc.section.2.3.3"><a href="#rfc.section.2.3.3">2.3.3</a>&nbsp;<a href="#example.entity.tag.vs.conneg">Example: Entity-tags Varying on Content-Negotiated Resources</a></h3>
    907                <p id="rfc.section.2.3.3.p.1">Consider a resource that is subject to content negotiation (<a href="p2-semantics.html#content.negotiation" title="Content Negotiation">Section 3.4</a> of <a href="#Part2" id="rfc.xref.Part2.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>), and where the representations sent in response to a GET request vary based on the <a href="p2-semantics.html#header.accept-encoding" class="smpl">Accept-Encoding</a> request header field (<a href="p2-semantics.html#header.accept-encoding" title="Accept-Encoding">Section 5.3.4</a> of <a href="#Part2" id="rfc.xref.Part2.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>):
     907               <p id="rfc.section.2.3.3.p.1">Consider a resource that is subject to content negotiation (<a href="p2-semantics.html#content.negotiation" title="Content Negotiation">Section 3.4</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>), and where the representations sent in response to a GET request vary based on the <a href="p2-semantics.html#header.accept-encoding" class="smpl">Accept-Encoding</a> request header field (<a href="p2-semantics.html#header.accept-encoding" title="Accept-Encoding">Section 5.3.4</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>):
    908908               </p>
    909909               <div id="rfc.figure.u.5"></div>
    … …  
    939939                  <p><b>Note:</b> Content codings are a property of the representation data, so a strong entity-tag for a content-encoded representation has
    940940                     to be distinct from the entity tag of an unencoded representation to prevent potential conflicts during cache updates and
    941                      range requests. In contrast, transfer codings (<a href="p1-messaging.html#transfer.codings" title="Transfer Codings">Section 4</a> of <a href="#Part1" id="rfc.xref.Part1.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) apply only during message transfer and do not result in distinct entity-tags.
     941                     range requests. In contrast, transfer codings (<a href="p1-messaging.html#transfer.codings" title="Transfer Codings">Section 4</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>) apply only during message transfer and do not result in distinct entity-tags.
    942942                  </p>
    943943               </div>
    … …  
    10291029            <p id="rfc.section.3.2.p.7">If-None-Match can also be used with a value of "*" to prevent an unsafe request method (e.g., PUT) from inadvertently modifying
    10301030               an existing representation of the target resource when the client believes that the resource does not have a current representation
    1031                (<a href="p2-semantics.html#safe.methods" title="Safe Methods">Section 4.2.1</a> of <a href="#Part2" id="rfc.xref.Part2.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>). This is a variation on the "lost update" problem that might arise if more than one client attempts to create an initial
     1031               (<a href="p2-semantics.html#safe.methods" title="Safe Methods">Section 4.2.1</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>). This is a variation on the "lost update" problem that might arise if more than one client attempts to create an initial
    10321032               representation for the target resource.
    10331033            </p>
    … …  
    10381038            <p id="rfc.section.3.2.p.9">An origin server <em class="bcp14">MUST NOT</em> perform the requested method if the condition evaluates to false; instead, the origin server <em class="bcp14">MUST</em> respond with either a) the <a href="#status.304" class="smpl">304 (Not Modified)</a> status code if the request method is GET or HEAD; or, b) the <a href="#status.412" class="smpl">412 (Precondition Failed)</a> status code for all other request methods.
    10391039            </p>
    1040             <p id="rfc.section.3.2.p.10">Requirements on cache handling of a received If-None-Match header field are defined in <a href="p6-cache.html#validation.received" title="Handling a Received Validation Request">Section 4.3.2</a> of <a href="#Part6" id="rfc.xref.Part6.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>.
     1040            <p id="rfc.section.3.2.p.10">Requirements on cache handling of a received If-None-Match header field are defined in <a href="p6-cache.html#validation.received" title="Handling a Received Validation Request">Section 4.3.2</a> of <a href="#RFC7234" id="rfc.xref.RFC7234.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[RFC7234]</cite></a>.
    10411041            </p>
    10421042         </div>
    … …  
    10751075               provided in the field-value; instead, the origin server <em class="bcp14">SHOULD</em> generate a <a href="#status.304" class="smpl">304 (Not Modified)</a> response, including only those metadata that are useful for identifying or updating a previously cached response.
    10761076            </p>
    1077             <p id="rfc.section.3.3.p.12">Requirements on cache handling of a received If-Modified-Since header field are defined in <a href="p6-cache.html#validation.received" title="Handling a Received Validation Request">Section 4.3.2</a> of <a href="#Part6" id="rfc.xref.Part6.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>.
     1077            <p id="rfc.section.3.3.p.12">Requirements on cache handling of a received If-Modified-Since header field are defined in <a href="p6-cache.html#validation.received" title="Handling a Received Validation Request">Section 4.3.2</a> of <a href="#RFC7234" id="rfc.xref.RFC7234.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[RFC7234]</cite></a>.
    10781078            </p>
    10791079         </div>
    … …  
    11121112            <h2 id="rfc.section.3.5"><a href="#rfc.section.3.5">3.5</a>&nbsp;<a href="#header.if-range">If-Range</a></h2>
    11131113            <p id="rfc.section.3.5.p.1">The "If-Range" header field provides a special conditional request mechanism that is similar to the <a href="#header.if-match" class="smpl">If-Match</a> and <a href="#header.if-unmodified-since" class="smpl">If-Unmodified-Since</a> header fields but instructs the recipient to ignore the <a href="p5-range.html#header.range" class="smpl">Range</a> header field if the validator doesn't match, resulting in transfer of the new selected representation instead of a 412 response.
    1114                If-Range is defined in <a href="p5-range.html#header.if-range" title="If-Range">Section 3.2</a> of <a href="#Part5" id="rfc.xref.Part5.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a>.
     1114               If-Range is defined in <a href="p5-range.html#header.if-range" title="If-Range">Section 3.2</a> of <a href="#RFC7233" id="rfc.xref.RFC7233.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[RFC7233]</cite></a>.
    11151115            </p>
    11161116         </div>
    … …  
    11321132               cache updates (e.g., <a href="#header.last-modified" class="smpl">Last-Modified</a> might be useful if the response does not have an <a href="#header.etag" class="smpl">ETag</a> field).
    11331133            </p>
    1134             <p id="rfc.section.4.1.p.4">Requirements on a cache that receives a 304 response are defined in <a href="p6-cache.html#freshening.responses" title="Freshening Stored Responses upon Validation">Section 4.3.4</a> of <a href="#Part6" id="rfc.xref.Part6.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>. If the conditional request originated with an outbound client, such as a user agent with its own cache sending a conditional
     1134            <p id="rfc.section.4.1.p.4">Requirements on a cache that receives a 304 response are defined in <a href="p6-cache.html#freshening.responses" title="Freshening Stored Responses upon Validation">Section 4.3.4</a> of <a href="#RFC7234" id="rfc.xref.RFC7234.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[RFC7234]</cite></a>. If the conditional request originated with an outbound client, such as a user agent with its own cache sending a conditional
    11351135               GET to a shared proxy, then the proxy <em class="bcp14">SHOULD</em> forward the 304 response to that client.
    11361136            </p>
    … …  
    12051205            <li id="precedence5">When the method is GET and both <a href="p5-range.html#header.range" class="smpl">Range</a> and <a href="p5-range.html#header.if-range" class="smpl">If-Range</a> are present, evaluate the <a href="p5-range.html#header.if-range" class="smpl">If-Range</a> precondition:
    12061206               <ul>
    1207                   <li>if the validator matches and the Range specification is applicable to the selected representation, respond <a href="p5-range.html#status.206" class="smpl">206 (Partial Content)</a> <a href="#Part5" id="rfc.xref.Part5.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a></li>
     1207                  <li>if the validator matches and the Range specification is applicable to the selected representation, respond <a href="p5-range.html#status.206" class="smpl">206 (Partial Content)</a> <a href="#RFC7233" id="rfc.xref.RFC7233.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[RFC7233]</cite></a></li>
    12081208               </ul>
    12091209            </li>
    … …  
    13221322         <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a href="#security.considerations">Security Considerations</a></h1>
    13231323         <p id="rfc.section.8.p.1">This section is meant to inform developers, information providers, and users of known security concerns specific to the HTTP
    1324             conditional request mechanisms. More general security considerations are addressed in HTTP messaging <a href="#Part1" id="rfc.xref.Part1.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a> and semantics <a href="#Part2" id="rfc.xref.Part2.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>.
     1324            conditional request mechanisms. More general security considerations are addressed in HTTP messaging <a href="#RFC7230" id="rfc.xref.RFC7230.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a> and semantics <a href="#RFC7231" id="rfc.xref.RFC7231.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>.
    13251325         </p>
    13261326         <p id="rfc.section.8.p.2">The validators defined by this specification are not intended to ensure the validity of a representation, guard against malicious
    … …  
    13391339      <div id="acks">
    13401340         <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a>&nbsp;<a href="#acks">Acknowledgments</a></h1>
    1341          <p id="rfc.section.9.p.1">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 10</a> of <a href="#Part1" id="rfc.xref.Part1.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.
     1341         <p id="rfc.section.9.p.1">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 10</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>.
    13421342         </p>
    13431343      </div>
    … …  
    13471347      </h2>
    13481348      <table>
    1349          <tr>
    1350             <td class="reference"><b id="Part1">[Part1]</b></td>
    1351             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-latest (work in progress), May&nbsp;2014.
    1352             </td>
    1353          </tr>
    1354          <tr>
    1355             <td class="reference"><b id="Part2">[Part2]</b></td>
    1356             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p2-semantics-latest (work in progress), May&nbsp;2014.
    1357             </td>
    1358          </tr>
    1359          <tr>
    1360             <td class="reference"><b id="Part5">[Part5]</b></td>
    1361             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">Hypertext Transfer Protocol (HTTP/1.1): Range Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-latest (work in progress), May&nbsp;2014.
    1362             </td>
    1363          </tr>
    1364          <tr>
    1365             <td class="reference"><b id="Part6">[Part6]</b></td>
    1366             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:mnot@mnot.net" title="Akamai">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">Hypertext Transfer Protocol (HTTP/1.1): Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-latest (work in progress), May&nbsp;2014.
    1367             </td>
    1368          </tr>
    13691349         <tr>
    13701350            <td class="reference"><b id="RFC2119">[RFC2119]</b></td>
    … …  
    13751355            <td class="reference"><b id="RFC5234">[RFC5234]</b></td>
    13761356            <td class="top"><a href="mailto:dcrocker@bbiw.net" title="Brandenburg InternetWorking">Crocker, D., Ed.</a> and <a href="mailto:paul.overell@thus.net" title="THUS plc.">P. Overell</a>, “<a href="http://tools.ietf.org/html/rfc5234">Augmented BNF for Syntax Specifications: ABNF</a>”, STD&nbsp;68, RFC&nbsp;5234, January&nbsp;2008.
     1357            </td>
     1358         </tr>
     1359         <tr>
     1360            <td class="reference"><b id="RFC7230">[RFC7230]</b></td>
     1361            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-latest (work in progress), May&nbsp;2014.
     1362            </td>
     1363         </tr>
     1364         <tr>
     1365            <td class="reference"><b id="RFC7231">[RFC7231]</b></td>
     1366            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p2-semantics-latest (work in progress), May&nbsp;2014.
     1367            </td>
     1368         </tr>
     1369         <tr>
     1370            <td class="reference"><b id="RFC7233">[RFC7233]</b></td>
     1371            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">Hypertext Transfer Protocol (HTTP/1.1): Range Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-latest (work in progress), May&nbsp;2014.
     1372            </td>
     1373         </tr>
     1374         <tr>
     1375            <td class="reference"><b id="RFC7234">[RFC7234]</b></td>
     1376            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:mnot@mnot.net" title="Akamai">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">Hypertext Transfer Protocol (HTTP/1.1): Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-latest (work in progress), May&nbsp;2014.
    13771377            </td>
    13781378         </tr>
    … …  
    14171417            character).
    14181418         </p>
    1419          <p id="rfc.section.B.p.2">The rules below are defined in <a href="#Part1" id="rfc.xref.Part1.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>:
    1420          </p>
    1421          <div id="rfc.figure.u.16"></div><pre class="inline">  <a href="#imported.abnf" class="smpl">OWS</a>           = &lt;OWS, defined in <a href="#Part1" id="rfc.xref.Part1.8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.3</a>&gt;
    1422   <a href="#imported.abnf" class="smpl">obs-text</a>      = &lt;obs-text, defined in <a href="#Part1" id="rfc.xref.Part1.9"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.6</a>&gt;
     1419         <p id="rfc.section.B.p.2">The rules below are defined in <a href="#RFC7230" id="rfc.xref.RFC7230.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>:
     1420         </p>
     1421         <div id="rfc.figure.u.16"></div><pre class="inline">  <a href="#imported.abnf" class="smpl">OWS</a>           = &lt;OWS, defined in <a href="#RFC7230" id="rfc.xref.RFC7230.8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.3</a>&gt;
     1422  <a href="#imported.abnf" class="smpl">obs-text</a>      = &lt;obs-text, defined in <a href="#RFC7230" id="rfc.xref.RFC7230.9"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.6</a>&gt;
    14231423</pre><p id="rfc.section.B.p.4">The rules below are defined in other parts:</p>
    1424          <div id="rfc.figure.u.17"></div><pre class="inline">  <a href="#imported.abnf" class="smpl">HTTP-date</a>     = &lt;HTTP-date, defined in <a href="#Part2" id="rfc.xref.Part2.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>, <a href="p2-semantics.html#http.date" title="Date/Time Formats">Section 7.1.1.1</a>&gt;
     1424         <div id="rfc.figure.u.17"></div><pre class="inline">  <a href="#imported.abnf" class="smpl">HTTP-date</a>     = &lt;HTTP-date, defined in <a href="#RFC7231" id="rfc.xref.RFC7231.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>, <a href="p2-semantics.html#http.date" title="Date/Time Formats">Section 7.1.1.1</a>&gt;
    14251425</pre></div>
    14261426      <div id="collected.abnf">
    14271427         <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a href="#collected.abnf">Collected ABNF</a></h1>
    1428          <p id="rfc.section.C.p.1">In the collected ABNF below, list rules are expanded as per <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#Part1" id="rfc.xref.Part1.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.
     1428         <p id="rfc.section.C.p.1">In the collected ABNF below, list rules are expanded as per <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>.
    14291429         </p>
    14301430         <div id="rfc.figure.u.18"></div><pre class="inline"><a href="#header.etag" class="smpl">ETag</a> = entity-tag
    14311431
    1432 <a href="#imported.abnf" class="smpl">HTTP-date</a> = &lt;HTTP-date, defined in [Part2], Section 7.1.1.1&gt;
     1432<a href="#imported.abnf" class="smpl">HTTP-date</a> = &lt;HTTP-date, defined in [RFC7231], Section 7.1.1.1&gt;
    14331433
    14341434<a href="#header.if-match" class="smpl">If-Match</a> = "*" / ( *( "," OWS ) entity-tag *( OWS "," [ OWS
    … …  
    14411441<a href="#header.last-modified" class="smpl">Last-Modified</a> = HTTP-date
    14421442
    1443 <a href="#imported.abnf" class="smpl">OWS</a> = &lt;OWS, defined in [Part1], Section 3.2.3&gt;
     1443<a href="#imported.abnf" class="smpl">OWS</a> = &lt;OWS, defined in [RFC7230], Section 3.2.3&gt;
    14441444
    14451445<a href="#header.etag" class="smpl">entity-tag</a> = [ weak ] opaque-tag
    … …  
    14471447 / obs-text
    14481448
    1449 <a href="#imported.abnf" class="smpl">obs-text</a> = &lt;obs-text, defined in [Part1], Section 3.2.6&gt;
     1449<a href="#imported.abnf" class="smpl">obs-text</a> = &lt;obs-text, defined in [RFC7230], Section 3.2.6&gt;
    14501450<a href="#header.etag" class="smpl">opaque-tag</a> = DQUOTE *etagc DQUOTE
    14511451
    … …  
    14821482      </div>
    14831483      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
    1484       <p class="noprint"><a href="#rfc.index.3">3</a> <a href="#rfc.index.4">4</a> <a href="#rfc.index.B">B</a> <a href="#rfc.index.E">E</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.L">L</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> <a href="#rfc.index.V">V</a>
     1484      <p class="noprint"><a href="#rfc.index.3">3</a> <a href="#rfc.index.4">4</a> <a href="#rfc.index.B">B</a> <a href="#rfc.index.E">E</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.L">L</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> <a href="#rfc.index.V">V</a>
    14851485      </p>
    14861486      <div class="print2col">
    … …  
    15341534               </ul>
    15351535            </li>
    1536             <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul>
    1537                   <li><em>Part1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1</a>, <a href="#rfc.xref.Part1.2">1.1</a>, <a href="#rfc.xref.Part1.3">1.2</a>, <a href="#rfc.xref.Part1.4">2.3.3</a>, <a href="#rfc.xref.Part1.5">8</a>, <a href="#rfc.xref.Part1.6">9</a>, <a href="#Part1"><b>10.1</b></a>, <a href="#rfc.xref.Part1.7">B</a>, <a href="#rfc.xref.Part1.8">B</a>, <a href="#rfc.xref.Part1.9">B</a>, <a href="#rfc.xref.Part1.10">C</a><ul>
    1538                         <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.10">C</a></li>
    1539                         <li><em>Section 2.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.2">1.1</a></li>
    1540                         <li><em>Section 3.2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.8">B</a></li>
    1541                         <li><em>Section 3.2.6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.9">B</a></li>
    1542                         <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.4">2.3.3</a></li>
    1543                         <li><em>Section 7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.3">1.2</a></li>
    1544                         <li><em>Section 10</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.6">9</a></li>
    1545                      </ul>
    1546                   </li>
    1547                   <li><em>Part2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.1">1</a>, <a href="#rfc.xref.Part2.2">1</a>, <a href="#rfc.xref.Part2.3">2.3.3</a>, <a href="#rfc.xref.Part2.4">2.3.3</a>, <a href="#rfc.xref.Part2.5">3.2</a>, <a href="#rfc.xref.Part2.6">8</a>, <a href="#Part2"><b>10.1</b></a>, <a href="#rfc.xref.Part2.7">B</a><ul>
    1548                         <li><em>Section 3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.2">1</a></li>
    1549                         <li><em>Section 3.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.3">2.3.3</a></li>
    1550                         <li><em>Section 4.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.5">3.2</a></li>
    1551                         <li><em>Section 5.3.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.4">2.3.3</a></li>
    1552                         <li><em>Section 7.1.1.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.7">B</a></li>
    1553                      </ul>
    1554                   </li>
    1555                   <li><em>Part5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.1">3.5</a>, <a href="#rfc.xref.Part5.2">6</a>, <a href="#Part5"><b>10.1</b></a><ul>
    1556                         <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.1">3.5</a></li>
    1557                      </ul>
    1558                   </li>
    1559                   <li><em>Part6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.1">1</a>, <a href="#rfc.xref.Part6.2">2.2.1</a>, <a href="#rfc.xref.Part6.3">2.3.1</a>, <a href="#rfc.xref.Part6.4">3.2</a>, <a href="#rfc.xref.Part6.5">3.3</a>, <a href="#rfc.xref.Part6.6">4.1</a>, <a href="#Part6"><b>10.1</b></a><ul>
    1560                         <li><em>Section 4.3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.4">3.2</a>, <a href="#rfc.xref.Part6.5">3.3</a></li>
    1561                         <li><em>Section 4.3.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.6">4.1</a></li>
    1562                      </ul>
    1563                   </li>
    1564                </ul>
    1565             </li>
    15661536            <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul>
    15671537                  <li><em>RFC2119</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2119.1">1.1</a>, <a href="#RFC2119"><b>10.1</b></a></li>
    … …  
    15761546                  <li><em>RFC5234</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.1">1.2</a>, <a href="#RFC5234"><b>10.1</b></a>, <a href="#rfc.xref.RFC5234.2">B</a><ul>
    15771547                        <li><em>Appendix B.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.2">B</a></li>
     1548                     </ul>
     1549                  </li>
     1550                  <li><em>RFC7230</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.1">1</a>, <a href="#rfc.xref.RFC7230.2">1.1</a>, <a href="#rfc.xref.RFC7230.3">1.2</a>, <a href="#rfc.xref.RFC7230.4">2.3.3</a>, <a href="#rfc.xref.RFC7230.5">8</a>, <a href="#rfc.xref.RFC7230.6">9</a>, <a href="#RFC7230"><b>10.1</b></a>, <a href="#rfc.xref.RFC7230.7">B</a>, <a href="#rfc.xref.RFC7230.8">B</a>, <a href="#rfc.xref.RFC7230.9">B</a>, <a href="#rfc.xref.RFC7230.10">C</a><ul>
     1551                        <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.10">C</a></li>
     1552                        <li><em>Section 2.5</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.2">1.1</a></li>
     1553                        <li><em>Section 3.2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.8">B</a></li>
     1554                        <li><em>Section 3.2.6</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.9">B</a></li>
     1555                        <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.4">2.3.3</a></li>
     1556                        <li><em>Section 7</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.3">1.2</a></li>
     1557                        <li><em>Section 10</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.6">9</a></li>
     1558                     </ul>
     1559                  </li>
     1560                  <li><em>RFC7231</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7231.1">1</a>, <a href="#rfc.xref.RFC7231.2">1</a>, <a href="#rfc.xref.RFC7231.3">2.3.3</a>, <a href="#rfc.xref.RFC7231.4">2.3.3</a>, <a href="#rfc.xref.RFC7231.5">3.2</a>, <a href="#rfc.xref.RFC7231.6">8</a>, <a href="#RFC7231"><b>10.1</b></a>, <a href="#rfc.xref.RFC7231.7">B</a><ul>
     1561                        <li><em>Section 3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7231.2">1</a></li>
     1562                        <li><em>Section 3.4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7231.3">2.3.3</a></li>
     1563                        <li><em>Section 4.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7231.5">3.2</a></li>
     1564                        <li><em>Section 5.3.4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7231.4">2.3.3</a></li>
     1565                        <li><em>Section 7.1.1.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7231.7">B</a></li>
     1566                     </ul>
     1567                  </li>
     1568                  <li><em>RFC7233</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7233.1">3.5</a>, <a href="#rfc.xref.RFC7233.2">6</a>, <a href="#RFC7233"><b>10.1</b></a><ul>
     1569                        <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7233.1">3.5</a></li>
     1570                     </ul>
     1571                  </li>
     1572                  <li><em>RFC7234</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7234.1">1</a>, <a href="#rfc.xref.RFC7234.2">2.2.1</a>, <a href="#rfc.xref.RFC7234.3">2.3.1</a>, <a href="#rfc.xref.RFC7234.4">3.2</a>, <a href="#rfc.xref.RFC7234.5">3.3</a>, <a href="#rfc.xref.RFC7234.6">4.1</a>, <a href="#RFC7234"><b>10.1</b></a><ul>
     1573                        <li><em>Section 4.3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7234.4">3.2</a>, <a href="#rfc.xref.RFC7234.5">3.3</a></li>
     1574                        <li><em>Section 4.3.4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7234.6">4.1</a></li>
    15781575                     </ul>
    15791576                  </li>

  • draft-ietf-httpbis/latest/p4-conditional.xml

    r2628 r2629  
    1717  <!ENTITY mdash "&#8212;">
    1818  <!ENTITY Note "<x:h xmlns:x='http://purl.org/net/xml2rfc/ext'>Note:</x:h>">
    19   <!ENTITY architecture               "<xref target='Part1' x:rel='#architecture' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    20   <!ENTITY conformance                "<xref target='Part1' x:rel='#conformance' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    21   <!ENTITY notation                   "<xref target='Part1' x:rel='#notation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    22   <!ENTITY abnf-extension             "<xref target='Part1' x:rel='#abnf.extension' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    23   <!ENTITY acks                       "<xref target='Part1' x:rel='#acks' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    24   <!ENTITY whitespace                 "<xref target='Part1' x:rel='#whitespace' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    25   <!ENTITY field-components           "<xref target='Part1' x:rel='#field.components' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    26   <!ENTITY header-date                "<xref target='Part2' x:rel='#header.date' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    27   <!ENTITY safe-methods               "<xref target='Part2' x:rel='#safe.methods' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    28   <!ENTITY representation             "<xref target='Part2' x:rel='#representations' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    29   <!ENTITY messaging                  "<xref target='Part1' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    30   <!ENTITY semantics                  "<xref target='Part2' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    31   <!ENTITY caching                    "<xref target='Part6' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    32   <!ENTITY cache-key                  "<xref target='Part6' x:rel='#constructing.responses.from.caches' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    33   <!ENTITY cache-validation-received  "<xref target='Part6' x:rel='#validation.received' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    34   <!ENTITY freshening-responses       "<xref target='Part6' x:rel='#freshening.responses' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    35   <!ENTITY header-accept-encoding     "<xref target='Part2' x:rel='#header.accept-encoding' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    36   <!ENTITY header-if-range            "<xref target='Part5' x:rel='#header.if-range' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    37   <!ENTITY header-range               "<xref target='Part5' x:rel='#header.range' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    38   <!ENTITY header-vary                "<xref target='Part2' x:rel='#header.vary' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    39   <!ENTITY http-date                  "<xref target='Part2' x:rel='#http.date' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    40   <!ENTITY transfer-codings           "<xref target='Part1' x:rel='#transfer.codings' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    41   <!ENTITY content-negotiation        "<xref target='Part2' x:rel='#content.negotiation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     19  <!ENTITY architecture               "<xref target='RFC7230' x:rel='#architecture' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     20  <!ENTITY conformance                "<xref target='RFC7230' x:rel='#conformance' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     21  <!ENTITY notation                   "<xref target='RFC7230' x:rel='#notation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     22  <!ENTITY abnf-extension             "<xref target='RFC7230' x:rel='#abnf.extension' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     23  <!ENTITY acks                       "<xref target='RFC7230' x:rel='#acks' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     24  <!ENTITY whitespace                 "<xref target='RFC7230' x:rel='#whitespace' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     25  <!ENTITY field-components           "<xref target='RFC7230' x:rel='#field.components' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     26  <!ENTITY header-date                "<xref target='RFC7231' x:rel='#header.date' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     27  <!ENTITY safe-methods               "<xref target='RFC7231' x:rel='#safe.methods' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     28  <!ENTITY representation             "<xref target='RFC7231' x:rel='#representations' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     29  <!ENTITY messaging                  "<xref target='RFC7230' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     30  <!ENTITY semantics                  "<xref target='RFC7231' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     31  <!ENTITY caching                    "<xref target='RFC7234' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     32  <!ENTITY cache-key                  "<xref target='RFC7234' x:rel='#constructing.responses.from.caches' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     33  <!ENTITY cache-validation-received  "<xref target='RFC7234' x:rel='#validation.received' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     34  <!ENTITY freshening-responses       "<xref target='RFC7234' x:rel='#freshening.responses' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     35  <!ENTITY header-accept-encoding     "<xref target='RFC7231' x:rel='#header.accept-encoding' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     36  <!ENTITY header-if-range            "<xref target='RFC7233' x:rel='#header.if-range' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     37  <!ENTITY header-range               "<xref target='RFC7233' x:rel='#header.range' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     38  <!ENTITY header-vary                "<xref target='RFC7231' x:rel='#header.vary' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     39  <!ENTITY http-date                  "<xref target='RFC7231' x:rel='#http.date' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     40  <!ENTITY transfer-codings           "<xref target='RFC7230' x:rel='#transfer.codings' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     41  <!ENTITY content-negotiation        "<xref target='RFC7231' x:rel='#content.negotiation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    4242]>
    4343<?rfc toc="yes" ?>
    … …  
    128128<section title="Introduction" anchor="introduction">
    129129<t>
    130    Conditional requests are HTTP requests <xref target="Part2"/> that include
     130   Conditional requests are HTTP requests <xref target="RFC7231"/> that include
    131131   one or more header fields indicating a precondition to be tested before
    132132   applying the method semantics to the target resource.
    133133   This document defines the HTTP/1.1 conditional request mechanisms in terms
    134134   of the architecture, syntax notation, and conformance criteria defined in
    135    <xref target="Part1"/>.
     135   <xref target="RFC7230"/>.
    136136</t>
    137137<t>
    … …  
    11181118         <t>if the validator matches and the Range specification is
    11191119            applicable to the selected representation, respond
    1120             <x:ref>206 (Partial Content)</x:ref> <xref target="Part5"/></t>
     1120            <x:ref>206 (Partial Content)</x:ref> <xref target="RFC7233"/></t>
    11211121       </list>
    11221122     </t>
    … …  
    12691269<references title="Normative References">
    12701270
    1271 <reference anchor="Part1">
     1271<reference anchor="RFC7230">
    12721272  <front>
    12731273    <title>Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</title>
    … …  
    12861286</reference>
    12871287
    1288 <reference anchor="Part2">
     1288<reference anchor="RFC7231">
    12891289  <front>
    12901290    <title>Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</title>
    … …  
    13151315</reference>
    13161316
    1317 <reference anchor="Part5">
     1317<reference anchor="RFC7233">
    13181318  <front>
    13191319    <title>Hypertext Transfer Protocol (HTTP/1.1): Range Requests</title>
    … …  
    13401340</reference>
    13411341
    1342 <reference anchor="Part6">
     1342<reference anchor="RFC7234">
    13431343  <front>
    13441344    <title>Hypertext Transfer Protocol (HTTP/1.1): Caching</title>
    … …  
    15211521</t>
    15221522<t>
    1523   The rules below are defined in <xref target="Part1"/>:
     1523  The rules below are defined in <xref target="RFC7230"/>:
    15241524</t>
    15251525<figure><artwork type="abnf2616">
    … …  
    15381538<section xmlns:x="http://purl.org/net/xml2rfc/ext" title="Collected ABNF" anchor="collected.abnf">
    15391539<t>
    1540   In the collected ABNF below, list rules are expanded as per <xref target="Part1" x:rel="#notation"/>.
     1540  In the collected ABNF below, list rules are expanded as per <xref target="RFC7230" x:rel="#notation"/>.
    15411541</t><figure>
    15421542<artwork type="abnf" name="p4-conditional.parsed-abnf">
    15431543<x:ref>ETag</x:ref> = entity-tag
    15441544
    1545 <x:ref>HTTP-date</x:ref> = &lt;HTTP-date, defined in [Part2], Section 7.1.1.1&gt;
     1545<x:ref>HTTP-date</x:ref> = &lt;HTTP-date, defined in [RFC7231], Section 7.1.1.1&gt;
    15461546
    15471547<x:ref>If-Match</x:ref> = "*" / ( *( "," OWS ) entity-tag *( OWS "," [ OWS
    … …  
    15541554<x:ref>Last-Modified</x:ref> = HTTP-date
    15551555
    1556 <x:ref>OWS</x:ref> = &lt;OWS, defined in [Part1], Section 3.2.3&gt;
     1556<x:ref>OWS</x:ref> = &lt;OWS, defined in [RFC7230], Section 3.2.3&gt;
    15571557
    15581558<x:ref>entity-tag</x:ref> = [ weak ] opaque-tag
    … …  
    15601560 / obs-text
    15611561
    1562 <x:ref>obs-text</x:ref> = &lt;obs-text, defined in [Part1], Section 3.2.6&gt;
     1562<x:ref>obs-text</x:ref> = &lt;obs-text, defined in [RFC7230], Section 3.2.6&gt;
    15631563<x:ref>opaque-tag</x:ref> = DQUOTE *etagc DQUOTE
    15641564

  • draft-ietf-httpbis/latest/p5-range.html

    r2628 r2629  
    463463  }
    464464  @bottom-center {
    465        content: "Expires November 2, 2014";
     465       content: "Expires November 7, 2014";
    466466  }
    467467  @bottom-right {
    … …  
    506506      <meta name="dct.creator" content="Reschke, J. F.">
    507507      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest">
    508       <meta name="dct.issued" scheme="ISO8601" content="2014-05-01">
     508      <meta name="dct.issued" scheme="ISO8601" content="2014-05-06">
    509509      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    510510      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for distributed, collaborative, hypertext information systems. This document defines range requests and the rules for constructing and combining responses to those requests.">
    … …  
    532532            </tr>
    533533            <tr>
    534                <td class="left">Expires: November 2, 2014</td>
     534               <td class="left">Expires: November 7, 2014</td>
    535535               <td class="right">J. Reschke, Editor</td>
    536536            </tr>
    … …  
    541541            <tr>
    542542               <td class="left"></td>
    543                <td class="right">May 1, 2014</td>
     543               <td class="right">May 6, 2014</td>
    544544            </tr>
    545545         </tbody>
    … …  
    568568            in progress”.
    569569         </p>
    570          <p>This Internet-Draft will expire on November 2, 2014.</p>
     570         <p>This Internet-Draft will expire on November 7, 2014.</p>
    571571      </div>
    572572      <div id="rfc.copyrightnotice">
    … …  
    670670               in this document are to be interpreted as described in <a href="#RFC2119" id="rfc.xref.RFC2119.1"><cite title="Key words for use in RFCs to Indicate Requirement Levels">[RFC2119]</cite></a>.
    671671            </p>
    672             <p id="rfc.section.1.1.p.2">Conformance criteria and considerations regarding error handling are defined in <a href="p1-messaging.html#conformance" title="Conformance and Error Handling">Section 2.5</a> of <a href="#Part1" id="rfc.xref.Part1.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.
     672            <p id="rfc.section.1.1.p.2">Conformance criteria and considerations regarding error handling are defined in <a href="p1-messaging.html#conformance" title="Conformance and Error Handling">Section 2.5</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>.
    673673            </p>
    674674         </div>
    675675         <div id="notation">
    676676            <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a href="#notation">Syntax Notation</a></h2>
    677             <p id="rfc.section.1.2.p.1">This specification uses the Augmented Backus-Naur Form (ABNF) notation of <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with a list extension, defined in <a href="p1-messaging.html#abnf.extension" title="ABNF list extension: #rule">Section 7</a> of <a href="#Part1" id="rfc.xref.Part1.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, that allows for compact definition of comma-separated lists using a '#' operator (similar to how the '*' operator indicates
     677            <p id="rfc.section.1.2.p.1">This specification uses the Augmented Backus-Naur Form (ABNF) notation of <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with a list extension, defined in <a href="p1-messaging.html#abnf.extension" title="ABNF list extension: #rule">Section 7</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, that allows for compact definition of comma-separated lists using a '#' operator (similar to how the '*' operator indicates
    678678               repetition). <a href="#imported.abnf" title="Imported ABNF">Appendix&nbsp;C</a> describes rules imported from other documents. <a href="#collected.abnf" title="Collected ABNF">Appendix&nbsp;D</a> shows the collected grammar with all list operators expanded to standard ABNF notation.
    679679            </p>
    … …  
    689689            <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;<a href="#byte.ranges">Byte Ranges</a></h2>
    690690            <p id="rfc.section.2.1.p.1">Since representation data is transferred in payloads as a sequence of octets, a byte range is a meaningful substructure for
    691                any representation transferable over HTTP (<a href="p2-semantics.html#representations" title="Representations">Section 3</a> of <a href="#Part2" id="rfc.xref.Part2.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>). The "bytes" range unit is defined for expressing subranges of the data's octet sequence.
     691               any representation transferable over HTTP (<a href="p2-semantics.html#representations" title="Representations">Section 3</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>). The "bytes" range unit is defined for expressing subranges of the data's octet sequence.
    692692            </p>
    693693            <div id="rfc.figure.u.2"></div><pre class="inline"><span id="rfc.iref.g.4"></span>  <a href="#byte.ranges" class="smpl">bytes-unit</a>       = "bytes"
    … …  
    792792               stored in reverse order and the user agent wishes to transfer one page at a time.
    793793            </p>
    794             <p id="rfc.section.3.1.p.7">The Range header field is evaluated after evaluating the precondition header fields defined in <a href="#Part4" id="rfc.xref.Part4.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>, and only if the result in absence of the Range header field would be a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response. In other words, Range is ignored when a conditional GET would result in a <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a> response.
     794            <p id="rfc.section.3.1.p.7">The Range header field is evaluated after evaluating the precondition header fields defined in <a href="#RFC7232" id="rfc.xref.RFC7232.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[RFC7232]</cite></a>, and only if the result in absence of the Range header field would be a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response. In other words, Range is ignored when a conditional GET would result in a <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a> response.
    795795            </p>
    796796            <p id="rfc.section.3.1.p.8">The If-Range header field (<a href="#header.if-range" id="rfc.xref.header.if-range.1" title="If-Range">Section&nbsp;3.2</a>) can be used as a precondition to applying the Range header field.
    … …  
    818818            </p>
    819819            <p id="rfc.section.3.2.p.5">A client <em class="bcp14">MUST NOT</em> generate an If-Range header field containing an entity-tag that is marked as weak. A client <em class="bcp14">MUST NOT</em> generate an If-Range header field containing an <a href="#imported.abnf" class="smpl">HTTP-date</a> unless the client has no entity-tag for the corresponding representation and the date is a strong validator in the sense defined
    820                by <a href="p4-conditional.html#lastmod.comparison" title="Comparison">Section 2.2.2</a> of <a href="#Part4" id="rfc.xref.Part4.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>.
    821             </p>
    822             <p id="rfc.section.3.2.p.6">A server that evaluates an If-Range precondition <em class="bcp14">MUST</em> use the strong comparison function when comparing entity-tags (<a href="p4-conditional.html#entity.tag.comparison" title="Comparison">Section 2.3.2</a> of <a href="#Part4" id="rfc.xref.Part4.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>) and <em class="bcp14">MUST</em> evaluate the condition as false if an <a href="#imported.abnf" class="smpl">HTTP-date</a> validator is provided that is not a strong validator in the sense defined by <a href="p4-conditional.html#lastmod.comparison" title="Comparison">Section 2.2.2</a> of <a href="#Part4" id="rfc.xref.Part4.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>. A valid <a href="#imported.abnf" class="smpl">entity-tag</a> can be distinguished from a valid <a href="#imported.abnf" class="smpl">HTTP-date</a> by examining the first two characters for a DQUOTE.
     820               by <a href="p4-conditional.html#lastmod.comparison" title="Comparison">Section 2.2.2</a> of <a href="#RFC7232" id="rfc.xref.RFC7232.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[RFC7232]</cite></a>.
     821            </p>
     822            <p id="rfc.section.3.2.p.6">A server that evaluates an If-Range precondition <em class="bcp14">MUST</em> use the strong comparison function when comparing entity-tags (<a href="p4-conditional.html#entity.tag.comparison" title="Comparison">Section 2.3.2</a> of <a href="#RFC7232" id="rfc.xref.RFC7232.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[RFC7232]</cite></a>) and <em class="bcp14">MUST</em> evaluate the condition as false if an <a href="#imported.abnf" class="smpl">HTTP-date</a> validator is provided that is not a strong validator in the sense defined by <a href="p4-conditional.html#lastmod.comparison" title="Comparison">Section 2.2.2</a> of <a href="#RFC7232" id="rfc.xref.RFC7232.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[RFC7232]</cite></a>. A valid <a href="#imported.abnf" class="smpl">entity-tag</a> can be distinguished from a valid <a href="#imported.abnf" class="smpl">HTTP-date</a> by examining the first two characters for a DQUOTE.
    823823            </p>
    824824            <p id="rfc.section.3.2.p.7">If the validator given in the If-Range header field matches the current validator for the selected representation of the target
    … …  
    887887               a prior response containing those header fields. Otherwise, the sender <em class="bcp14">MUST</em> generate all of the representation header fields that would have been sent in a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response to the same request.
    888888            </p>
    889             <p id="rfc.section.4.1.p.12">A 206 response is cacheable by default; i.e., unless otherwise indicated by explicit cache controls (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.2.2</a> of <a href="#Part6" id="rfc.xref.Part6.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
     889            <p id="rfc.section.4.1.p.12">A 206 response is cacheable by default; i.e., unless otherwise indicated by explicit cache controls (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.2.2</a> of <a href="#RFC7234" id="rfc.xref.RFC7234.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[RFC7234]</cite></a>).
    890890            </p>
    891891         </div>
    … …  
    951951            <p id="rfc.section.4.3.p.1">A response might transfer only a subrange of a representation if the connection closed prematurely or if the request used
    952952               one or more Range specifications. After several such transfers, a client might have received several ranges of the same representation.
    953                These ranges can only be safely combined if they all have in common the same strong validator (<a href="p4-conditional.html#weak.and.strong.validators" title="Weak versus Strong">Section 2.1</a> of <a href="#Part4" id="rfc.xref.Part4.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>).
     953               These ranges can only be safely combined if they all have in common the same strong validator (<a href="p4-conditional.html#weak.and.strong.validators" title="Weak versus Strong">Section 2.1</a> of <a href="#RFC7232" id="rfc.xref.RFC7232.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[RFC7232]</cite></a>).
    954954            </p>
    955955            <p id="rfc.section.4.3.p.2">A client that has received multiple partial responses to GET requests on a target resource <em class="bcp14">MAY</em> combine those responses into a larger continuous range if they share the same strong validator.
    … …  
    11831183         <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a href="#security.considerations">Security Considerations</a></h1>
    11841184         <p id="rfc.section.6.p.1">This section is meant to inform developers, information providers, and users of known security concerns specific to the HTTP
    1185             range request mechanisms. More general security considerations are addressed in HTTP messaging <a href="#Part1" id="rfc.xref.Part1.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a> and semantics <a href="#Part2" id="rfc.xref.Part2.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>.
     1185            range request mechanisms. More general security considerations are addressed in HTTP messaging <a href="#RFC7230" id="rfc.xref.RFC7230.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a> and semantics <a href="#RFC7231" id="rfc.xref.RFC7231.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>.
    11861186         </p>
    11871187         <div id="overlapping.ranges">
    … …  
    11971197      <div id="acks">
    11981198         <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a href="#acks">Acknowledgments</a></h1>
    1199          <p id="rfc.section.7.p.1">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 10</a> of <a href="#Part1" id="rfc.xref.Part1.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.
     1199         <p id="rfc.section.7.p.1">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 10</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>.
    12001200         </p>
    12011201      </div>
    … …  
    12051205      </h2>
    12061206      <table>
    1207          <tr>
    1208             <td class="reference"><b id="Part1">[Part1]</b></td>
    1209             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-latest (work in progress), May&nbsp;2014.
    1210             </td>
    1211          </tr>
    1212          <tr>
    1213             <td class="reference"><b id="Part2">[Part2]</b></td>
    1214             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p2-semantics-latest (work in progress), May&nbsp;2014.
    1215             </td>
    1216          </tr>
    1217          <tr>
    1218             <td class="reference"><b id="Part4">[Part4]</b></td>
    1219             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-latest (work in progress), May&nbsp;2014.
    1220             </td>
    1221          </tr>
    1222          <tr>
    1223             <td class="reference"><b id="Part6">[Part6]</b></td>
    1224             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:mnot@mnot.net" title="Akamai">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">Hypertext Transfer Protocol (HTTP/1.1): Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-latest (work in progress), May&nbsp;2014.
    1225             </td>
    1226          </tr>
    12271207         <tr>
    12281208            <td class="reference"><b id="RFC2046">[RFC2046]</b></td>
    … …  
    12381218            <td class="reference"><b id="RFC5234">[RFC5234]</b></td>
    12391219            <td class="top"><a href="mailto:dcrocker@bbiw.net" title="Brandenburg InternetWorking">Crocker, D., Ed.</a> and <a href="mailto:paul.overell@thus.net" title="THUS plc.">P. Overell</a>, “<a href="http://tools.ietf.org/html/rfc5234">Augmented BNF for Syntax Specifications: ABNF</a>”, STD&nbsp;68, RFC&nbsp;5234, January&nbsp;2008.
     1220            </td>
     1221         </tr>
     1222         <tr>
     1223            <td class="reference"><b id="RFC7230">[RFC7230]</b></td>
     1224            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-latest (work in progress), May&nbsp;2014.
     1225            </td>
     1226         </tr>
     1227         <tr>
     1228            <td class="reference"><b id="RFC7231">[RFC7231]</b></td>
     1229            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p2-semantics-latest (work in progress), May&nbsp;2014.
     1230            </td>
     1231         </tr>
     1232         <tr>
     1233            <td class="reference"><b id="RFC7232">[RFC7232]</b></td>
     1234            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-latest (work in progress), May&nbsp;2014.
     1235            </td>
     1236         </tr>
     1237         <tr>
     1238            <td class="reference"><b id="RFC7234">[RFC7234]</b></td>
     1239            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:mnot@mnot.net" title="Akamai">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">Hypertext Transfer Protocol (HTTP/1.1): Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-latest (work in progress), May&nbsp;2014.
    12401240            </td>
    12411241         </tr>
    … …  
    13241324         <p id="rfc.section.C.p.2">Note that all rules derived from <a href="#imported.abnf" class="smpl">token</a> are to be compared case-insensitively, like <a href="#range.units" class="smpl">range-unit</a> and <a href="#header.accept-ranges" class="smpl">acceptable-ranges</a>.
    13251325         </p>
    1326          <p id="rfc.section.C.p.3">The rules below are defined in <a href="#Part1" id="rfc.xref.Part1.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>:
    1327          </p>
    1328          <div id="rfc.figure.u.29"></div><pre class="inline">  <a href="#imported.abnf" class="smpl">OWS</a>        = &lt;OWS, defined in <a href="#Part1" id="rfc.xref.Part1.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.3</a>&gt;
    1329   <a href="#imported.abnf" class="smpl">token</a>      = &lt;token, defined in <a href="#Part1" id="rfc.xref.Part1.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.6</a>&gt;
     1326         <p id="rfc.section.C.p.3">The rules below are defined in <a href="#RFC7230" id="rfc.xref.RFC7230.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>:
     1327         </p>
     1328         <div id="rfc.figure.u.29"></div><pre class="inline">  <a href="#imported.abnf" class="smpl">OWS</a>        = &lt;OWS, defined in <a href="#RFC7230" id="rfc.xref.RFC7230.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.3</a>&gt;
     1329  <a href="#imported.abnf" class="smpl">token</a>      = &lt;token, defined in <a href="#RFC7230" id="rfc.xref.RFC7230.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.6</a>&gt;
    13301330</pre><p id="rfc.section.C.p.5">The rules below are defined in other parts:</p>
    1331          <div id="rfc.figure.u.30"></div><pre class="inline">  <a href="#imported.abnf" class="smpl">HTTP-date</a>  = &lt;HTTP-date, defined in <a href="#Part2" id="rfc.xref.Part2.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>, <a href="p2-semantics.html#http.date" title="Date/Time Formats">Section 7.1.1.1</a>&gt;
    1332   <a href="#imported.abnf" class="smpl">entity-tag</a> = &lt;entity-tag, defined in <a href="#Part4" id="rfc.xref.Part4.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.etag" title="ETag">Section 2.3</a>&gt;
     1331         <div id="rfc.figure.u.30"></div><pre class="inline">  <a href="#imported.abnf" class="smpl">HTTP-date</a>  = &lt;HTTP-date, defined in <a href="#RFC7231" id="rfc.xref.RFC7231.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>, <a href="p2-semantics.html#http.date" title="Date/Time Formats">Section 7.1.1.1</a>&gt;
     1332  <a href="#imported.abnf" class="smpl">entity-tag</a> = &lt;entity-tag, defined in <a href="#RFC7232" id="rfc.xref.RFC7232.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[RFC7232]</cite></a>, <a href="p4-conditional.html#header.etag" title="ETag">Section 2.3</a>&gt;
    13331333</pre></div>
    13341334      <div id="collected.abnf">
    13351335         <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a>&nbsp;<a href="#collected.abnf">Collected ABNF</a></h1>
    1336          <p id="rfc.section.D.p.1">In the collected ABNF below, list rules are expanded as per <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#Part1" id="rfc.xref.Part1.8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.
     1336         <p id="rfc.section.D.p.1">In the collected ABNF below, list rules are expanded as per <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>.
    13371337         </p>
    13381338         <div id="rfc.figure.u.31"></div><pre class="inline"><a href="#header.accept-ranges" class="smpl">Accept-Ranges</a> = acceptable-ranges
    … …  
    13401340<a href="#header.content-range" class="smpl">Content-Range</a> = byte-content-range / other-content-range
    13411341
    1342 <a href="#imported.abnf" class="smpl">HTTP-date</a> = &lt;HTTP-date, defined in [Part2], Section 7.1.1.1&gt;
     1342<a href="#imported.abnf" class="smpl">HTTP-date</a> = &lt;HTTP-date, defined in [RFC7231], Section 7.1.1.1&gt;
    13431343
    13441344<a href="#header.if-range" class="smpl">If-Range</a> = entity-tag / HTTP-date
    13451345
    1346 <a href="#imported.abnf" class="smpl">OWS</a> = &lt;OWS, defined in [Part1], Section 3.2.3&gt;
     1346<a href="#imported.abnf" class="smpl">OWS</a> = &lt;OWS, defined in [RFC7230], Section 3.2.3&gt;
    13471347
    13481348<a href="#header.range" class="smpl">Range</a> = byte-ranges-specifier / other-ranges-specifier
    … …  
    13641364<a href="#header.content-range" class="smpl">complete-length</a> = 1*DIGIT
    13651365
    1366 <a href="#imported.abnf" class="smpl">entity-tag</a> = &lt;entity-tag, defined in [Part4], Section 2.3&gt;
     1366<a href="#imported.abnf" class="smpl">entity-tag</a> = &lt;entity-tag, defined in [RFC7232], Section 2.3&gt;
    13671367
    13681368<a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> = 1*DIGIT
    … …  
    13811381<a href="#rule.ranges-specifier" class="smpl">suffix-length</a> = 1*DIGIT
    13821382
    1383 <a href="#imported.abnf" class="smpl">token</a> = &lt;token, defined in [Part1], Section 3.2.6&gt;
     1383<a href="#imported.abnf" class="smpl">token</a> = &lt;token, defined in [RFC7230], Section 3.2.6&gt;
    13841384
    13851385<a href="#header.content-range" class="smpl">unsatisfied-range</a> = "*/" complete-length
    … …  
    14231423      </div>
    14241424      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
    1425       <p class="noprint"><a href="#rfc.index.2">2</a> <a href="#rfc.index.4">4</a> <a href="#rfc.index.A">A</a> <a href="#rfc.index.B">B</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a>
     1425      <p class="noprint"><a href="#rfc.index.2">2</a> <a href="#rfc.index.4">4</a> <a href="#rfc.index.A">A</a> <a href="#rfc.index.B">B</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.R">R</a>
    14261426      </p>
    14271427      <div class="print2col">
    … …  
    14931493               </ul>
    14941494            </li>
    1495             <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul>
    1496                   <li><em>Part1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1.1</a>, <a href="#rfc.xref.Part1.2">1.2</a>, <a href="#rfc.xref.Part1.3">6</a>, <a href="#rfc.xref.Part1.4">7</a>, <a href="#Part1"><b>8.1</b></a>, <a href="#rfc.xref.Part1.5">C</a>, <a href="#rfc.xref.Part1.6">C</a>, <a href="#rfc.xref.Part1.7">C</a>, <a href="#rfc.xref.Part1.8">D</a><ul>
    1497                         <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.8">D</a></li>
    1498                         <li><em>Section 2.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1.1</a></li>
    1499                         <li><em>Section 3.2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.6">C</a></li>
    1500                         <li><em>Section 3.2.6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.7">C</a></li>
    1501                         <li><em>Section 7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.2">1.2</a></li>
    1502                         <li><em>Section 10</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.4">7</a></li>
    1503                      </ul>
    1504                   </li>
    1505                   <li><em>Part2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.1">2.1</a>, <a href="#rfc.xref.Part2.2">6</a>, <a href="#Part2"><b>8.1</b></a>, <a href="#rfc.xref.Part2.3">C</a><ul>
    1506                         <li><em>Section 3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.1">2.1</a></li>
    1507                         <li><em>Section 7.1.1.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.3">C</a></li>
    1508                      </ul>
    1509                   </li>
    1510                   <li><em>Part4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">3.1</a>, <a href="#rfc.xref.Part4.2">3.2</a>, <a href="#rfc.xref.Part4.3">3.2</a>, <a href="#rfc.xref.Part4.4">3.2</a>, <a href="#rfc.xref.Part4.5">4.3</a>, <a href="#Part4"><b>8.1</b></a>, <a href="#rfc.xref.Part4.6">C</a><ul>
    1511                         <li><em>Section 2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.5">4.3</a></li>
    1512                         <li><em>Section 2.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.2">3.2</a>, <a href="#rfc.xref.Part4.4">3.2</a></li>
    1513                         <li><em>Section 2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.6">C</a></li>
    1514                         <li><em>Section 2.3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.3">3.2</a></li>
    1515                      </ul>
    1516                   </li>
    1517                   <li><em>Part6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.1">4.1</a>, <a href="#Part6"><b>8.1</b></a><ul>
    1518                         <li><em>Section 4.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.1">4.1</a></li>
    1519                      </ul>
    1520                   </li>
    1521                </ul>
    1522             </li>
    15231495            <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul>
    15241496                  <li>Range header field&nbsp;&nbsp;<a href="#rfc.xref.header.range.1">2</a>, <a href="#rfc.iref.r.1"><b>3.1</b></a>, <a href="#rfc.xref.header.range.2">4.1</a>, <a href="#rfc.xref.header.range.3">4.4</a>, <a href="#rfc.xref.header.range.4">5.3</a>, <a href="#rfc.xref.header.range.5">B</a></li>
    … …  
    15351507                  <li><em>RFC5234</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.1">1.2</a>, <a href="#RFC5234"><b>8.1</b></a>, <a href="#rfc.xref.RFC5234.2">C</a><ul>
    15361508                        <li><em>Appendix B.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.2">C</a></li>
     1509                     </ul>
     1510                  </li>
     1511                  <li><em>RFC7230</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.1">1.1</a>, <a href="#rfc.xref.RFC7230.2">1.2</a>, <a href="#rfc.xref.RFC7230.3">6</a>, <a href="#rfc.xref.RFC7230.4">7</a>, <a href="#RFC7230"><b>8.1</b></a>, <a href="#rfc.xref.RFC7230.5">C</a>, <a href="#rfc.xref.RFC7230.6">C</a>, <a href="#rfc.xref.RFC7230.7">C</a>, <a href="#rfc.xref.RFC7230.8">D</a><ul>
     1512                        <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.8">D</a></li>
     1513                        <li><em>Section 2.5</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.1">1.1</a></li>
     1514                        <li><em>Section 3.2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.6">C</a></li>
     1515                        <li><em>Section 3.2.6</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.7">C</a></li>
     1516                        <li><em>Section 7</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.2">1.2</a></li>
     1517                        <li><em>Section 10</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.4">7</a></li>
     1518                     </ul>
     1519                  </li>
     1520                  <li><em>RFC7231</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7231.1">2.1</a>, <a href="#rfc.xref.RFC7231.2">6</a>, <a href="#RFC7231"><b>8.1</b></a>, <a href="#rfc.xref.RFC7231.3">C</a><ul>
     1521                        <li><em>Section 3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7231.1">2.1</a></li>
     1522                        <li><em>Section 7.1.1.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7231.3">C</a></li>
     1523                     </ul>
     1524                  </li>
     1525                  <li><em>RFC7232</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7232.1">3.1</a>, <a href="#rfc.xref.RFC7232.2">3.2</a>, <a href="#rfc.xref.RFC7232.3">3.2</a>, <a href="#rfc.xref.RFC7232.4">3.2</a>, <a href="#rfc.xref.RFC7232.5">4.3</a>, <a href="#RFC7232"><b>8.1</b></a>, <a href="#rfc.xref.RFC7232.6">C</a><ul>
     1526                        <li><em>Section 2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7232.5">4.3</a></li>
     1527                        <li><em>Section 2.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7232.2">3.2</a>, <a href="#rfc.xref.RFC7232.4">3.2</a></li>
     1528                        <li><em>Section 2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7232.6">C</a></li>
     1529                        <li><em>Section 2.3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7232.3">3.2</a></li>
     1530                     </ul>
     1531                  </li>
     1532                  <li><em>RFC7234</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7234.1">4.1</a>, <a href="#RFC7234"><b>8.1</b></a><ul>
     1533                        <li><em>Section 4.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7234.1">4.1</a></li>
    15371534                     </ul>
    15381535                  </li>

  • draft-ietf-httpbis/latest/p5-range.xml

    r2628 r2629  
    1717  <!ENTITY mdash "&#8212;">
    1818  <!ENTITY Note "<x:h xmlns:x='http://purl.org/net/xml2rfc/ext'>Note:</x:h>">
    19   <!ENTITY architecture               "<xref target='Part1' x:rel='#architecture' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    20   <!ENTITY conformance                "<xref target='Part1' x:rel='#conformance' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    21   <!ENTITY notation                   "<xref target='Part1' x:rel='#notation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    22   <!ENTITY abnf-extension             "<xref target='Part1' x:rel='#abnf.extension' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    23   <!ENTITY acks                       "<xref target='Part1' x:rel='#acks' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    24   <!ENTITY whitespace                 "<xref target='Part1' x:rel='#whitespace' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    25   <!ENTITY field-components           "<xref target='Part1' x:rel='#field.components' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    26   <!ENTITY messaging                  "<xref target='Part1' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    27   <!ENTITY semantics                  "<xref target='Part2' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    28   <!ENTITY http-date                  "<xref target='Part2' x:rel='#http.date' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    29   <!ENTITY representation             "<xref target='Part2' x:rel='#representations' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    30   <!ENTITY entity-tags                "<xref target='Part4' x:rel='#header.etag' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    31   <!ENTITY weak-and-strong-validators "<xref target='Part4' x:rel='#weak.and.strong.validators' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    32   <!ENTITY entity-tag-comparison      "<xref target='Part4' x:rel='#entity.tag.comparison' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    33   <!ENTITY lastmod-comparison         "<xref target='Part4' x:rel='#lastmod.comparison' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    34   <!ENTITY p6-heuristic               "<xref target='Part6' x:rel='#heuristic.freshness' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     19  <!ENTITY architecture               "<xref target='RFC7230' x:rel='#architecture' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     20  <!ENTITY conformance                "<xref target='RFC7230' x:rel='#conformance' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     21  <!ENTITY notation                   "<xref target='RFC7230' x:rel='#notation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     22  <!ENTITY abnf-extension             "<xref target='RFC7230' x:rel='#abnf.extension' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     23  <!ENTITY acks                       "<xref target='RFC7230' x:rel='#acks' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     24  <!ENTITY whitespace                 "<xref target='RFC7230' x:rel='#whitespace' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     25  <!ENTITY field-components           "<xref target='RFC7230' x:rel='#field.components' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     26  <!ENTITY messaging                  "<xref target='RFC7230' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     27  <!ENTITY semantics                  "<xref target='RFC7231' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     28  <!ENTITY http-date                  "<xref target='RFC7231' x:rel='#http.date' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     29  <!ENTITY representation             "<xref target='RFC7231' x:rel='#representations' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     30  <!ENTITY entity-tags                "<xref target='RFC7232' x:rel='#header.etag' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     31  <!ENTITY weak-and-strong-validators "<xref target='RFC7232' x:rel='#weak.and.strong.validators' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     32  <!ENTITY entity-tag-comparison      "<xref target='RFC7232' x:rel='#entity.tag.comparison' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     33  <!ENTITY lastmod-comparison         "<xref target='RFC7232' x:rel='#lastmod.comparison' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     34  <!ENTITY p6-heuristic               "<xref target='RFC7234' x:rel='#heuristic.freshness' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    3535]>
    3636<?rfc toc="yes" ?>
    … …  
    425425<t>
    426426   The Range header field is evaluated after evaluating the precondition header
    427    fields defined in <xref target="Part4"/>, and only if the result in absence
     427   fields defined in <xref target="RFC7232"/>, and only if the result in absence
    428428   of the Range header field would be a <x:ref>200 (OK)</x:ref> response. In
    429429   other words, Range is ignored when a conditional GET would result in a
    … …  
    10811081<references title="Normative References">
    10821082
    1083 <reference anchor="Part1">
     1083<reference anchor="RFC7230">
    10841084  <front>
    10851085    <title>Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</title>
    … …  
    11001100</reference>
    11011101
    1102 <reference anchor="Part2">
     1102<reference anchor="RFC7231">
    11031103  <front>
    11041104    <title>Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</title>
    … …  
    11251125</reference>
    11261126
    1127 <reference anchor="Part4">
     1127<reference anchor="RFC7232">
    11281128  <front>
    11291129    <title>Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</title>
    … …  
    11501150</reference>
    11511151
    1152 <reference anchor="Part6">
     1152<reference anchor="RFC7234">
    11531153  <front>
    11541154    <title>Hypertext Transfer Protocol (HTTP/1.1): Caching</title>
    … …  
    14391439</t>
    14401440<t>
    1441   The rules below are defined in <xref target="Part1"/>:
     1441  The rules below are defined in <xref target="RFC7230"/>:
    14421442</t>
    14431443<figure><artwork type="abnf2616">
    … …  
    14571457<section xmlns:x="http://purl.org/net/xml2rfc/ext" title="Collected ABNF" anchor="collected.abnf">
    14581458<t>
    1459   In the collected ABNF below, list rules are expanded as per <xref target="Part1" x:rel="#notation"/>.
     1459  In the collected ABNF below, list rules are expanded as per <xref target="RFC7230" x:rel="#notation"/>.
    14601460</t><figure>
    14611461<artwork type="abnf" name="p5-range.parsed-abnf">
    … …  
    14641464<x:ref>Content-Range</x:ref> = byte-content-range / other-content-range
    14651465
    1466 <x:ref>HTTP-date</x:ref> = &lt;HTTP-date, defined in [Part2], Section 7.1.1.1&gt;
     1466<x:ref>HTTP-date</x:ref> = &lt;HTTP-date, defined in [RFC7231], Section 7.1.1.1&gt;
    14671467
    14681468<x:ref>If-Range</x:ref> = entity-tag / HTTP-date
    14691469
    1470 <x:ref>OWS</x:ref> = &lt;OWS, defined in [Part1], Section 3.2.3&gt;
     1470<x:ref>OWS</x:ref> = &lt;OWS, defined in [RFC7230], Section 3.2.3&gt;
    14711471
    14721472<x:ref>Range</x:ref> = byte-ranges-specifier / other-ranges-specifier
    … …  
    14881488<x:ref>complete-length</x:ref> = 1*DIGIT
    14891489
    1490 <x:ref>entity-tag</x:ref> = &lt;entity-tag, defined in [Part4], Section 2.3&gt;
     1490<x:ref>entity-tag</x:ref> = &lt;entity-tag, defined in [RFC7232], Section 2.3&gt;
    14911491
    14921492<x:ref>first-byte-pos</x:ref> = 1*DIGIT
    … …  
    15051505<x:ref>suffix-length</x:ref> = 1*DIGIT
    15061506
    1507 <x:ref>token</x:ref> = &lt;token, defined in [Part1], Section 3.2.6&gt;
     1507<x:ref>token</x:ref> = &lt;token, defined in [RFC7230], Section 3.2.6&gt;
    15081508
    15091509<x:ref>unsatisfied-range</x:ref> = "*/" complete-length

  • draft-ietf-httpbis/latest/p6-cache.html

    r2628 r2629  
    466466  }
    467467  @bottom-center {
    468        content: "Expires November 2, 2014";
     468       content: "Expires November 7, 2014";
    469469  }
    470470  @bottom-right {
    … …  
    510510      <meta name="dct.creator" content="Reschke, J. F.">
    511511      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest">
    512       <meta name="dct.issued" scheme="ISO8601" content="2014-05-01">
     512      <meta name="dct.issued" scheme="ISO8601" content="2014-05-06">
    513513      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    514514      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for distributed, collaborative, hypertext information systems. This document defines HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages.">
    … …  
    536536            </tr>
    537537            <tr>
    538                <td class="left">Expires: November 2, 2014</td>
     538               <td class="left">Expires: November 7, 2014</td>
    539539               <td class="right">J. Reschke, Editor</td>
    540540            </tr>
    … …  
    545545            <tr>
    546546               <td class="left"></td>
    547                <td class="right">May 1, 2014</td>
     547               <td class="right">May 6, 2014</td>
    548548            </tr>
    549549         </tbody>
    … …  
    572572            in progress”.
    573573         </p>
    574          <p>This Internet-Draft will expire on November 2, 2014.</p>
     574         <p>This Internet-Draft will expire on November 7, 2014.</p>
    575575      </div>
    576576      <div id="rfc.copyrightnotice">
    … …  
    712712               in this document are to be interpreted as described in <a href="#RFC2119" id="rfc.xref.RFC2119.1"><cite title="Key words for use in RFCs to Indicate Requirement Levels">[RFC2119]</cite></a>.
    713713            </p>
    714             <p id="rfc.section.1.1.p.2">Conformance criteria and considerations regarding error handling are defined in <a href="p1-messaging.html#conformance" title="Conformance and Error Handling">Section 2.5</a> of <a href="#Part1" id="rfc.xref.Part1.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.
     714            <p id="rfc.section.1.1.p.2">Conformance criteria and considerations regarding error handling are defined in <a href="p1-messaging.html#conformance" title="Conformance and Error Handling">Section 2.5</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>.
    715715            </p>
    716716         </div>
    717717         <div id="notation">
    718718            <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a href="#notation">Syntax Notation</a></h2>
    719             <p id="rfc.section.1.2.p.1">This specification uses the Augmented Backus-Naur Form (ABNF) notation of <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with a list extension, defined in <a href="p1-messaging.html#abnf.extension" title="ABNF list extension: #rule">Section 7</a> of <a href="#Part1" id="rfc.xref.Part1.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, that allows for compact definition of comma-separated lists using a '#' operator (similar to how the '*' operator indicates
     719            <p id="rfc.section.1.2.p.1">This specification uses the Augmented Backus-Naur Form (ABNF) notation of <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with a list extension, defined in <a href="p1-messaging.html#abnf.extension" title="ABNF list extension: #rule">Section 7</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, that allows for compact definition of comma-separated lists using a '#' operator (similar to how the '*' operator indicates
    720720               repetition). <a href="#imported.abnf" title="Imported ABNF">Appendix&nbsp;B</a> describes rules imported from other documents. <a href="#collected.abnf" title="Collected ABNF">Appendix&nbsp;C</a> shows the collected grammar with all list operators expanded to standard ABNF notation.
    721721            </p>
    … …  
    742742         <div id="rfc.iref.c.3"></div>
    743743         <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a href="#caching.overview">Overview of Cache Operation</a></h1>
    744          <p id="rfc.section.2.p.1">Proper cache operation preserves the semantics of HTTP transfers (<a href="#Part2" id="rfc.xref.Part2.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>) while eliminating the transfer of information already held in the cache. Although caching is an entirely <em class="bcp14">OPTIONAL</em> feature of HTTP, it can be assumed that reusing a cached response is desirable and that such reuse is the default behavior
     744         <p id="rfc.section.2.p.1">Proper cache operation preserves the semantics of HTTP transfers (<a href="#RFC7231" id="rfc.xref.RFC7231.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>) while eliminating the transfer of information already held in the cache. Although caching is an entirely <em class="bcp14">OPTIONAL</em> feature of HTTP, it can be assumed that reusing a cached response is desirable and that such reuse is the default behavior
    745745            when no requirement or local configuration prevents it. Therefore, HTTP cache requirements are focused on preventing a cache
    746746            from either storing a non-reusable response or reusing a stored response inappropriately, rather than mandating that caches
    … …  
    748748         </p>
    749749         <p id="rfc.section.2.p.2">Each <dfn>cache entry</dfn> consists of a cache key and one or more HTTP responses corresponding to prior requests that used the same key. The most common
    750             form of cache entry is a successful result of a retrieval request: i.e., a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response to a GET request, which contains a representation of the resource identified by the request target (<a href="p2-semantics.html#GET" title="GET">Section 4.3.1</a> of <a href="#Part2" id="rfc.xref.Part2.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>). However, it is also possible to cache permanent redirects, negative results (e.g., <a href="p2-semantics.html#status.404" class="smpl">404 (Not Found)</a>), incomplete results (e.g., <a href="p5-range.html#status.206" class="smpl">206 (Partial Content)</a>), and responses to methods other than GET if the method's definition allows such caching and defines something suitable for
     750            form of cache entry is a successful result of a retrieval request: i.e., a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response to a GET request, which contains a representation of the resource identified by the request target (<a href="p2-semantics.html#GET" title="GET">Section 4.3.1</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>). However, it is also possible to cache permanent redirects, negative results (e.g., <a href="p2-semantics.html#status.404" class="smpl">404 (Not Found)</a>), incomplete results (e.g., <a href="p5-range.html#status.206" class="smpl">206 (Partial Content)</a>), and responses to methods other than GET if the method's definition allows such caching and defines something suitable for
    751751            use as a cache key.
    752752         </p>
    … …  
    770770            <li>the "private" response directive (see <a href="#cache-response-directive.private" title="private">Section&nbsp;5.2.2.6</a>) does not appear in the response, if the cache is shared, and
    771771            </li>
    772             <li>the <a href="p7-auth.html#header.authorization" class="smpl">Authorization</a> header field (see <a href="p7-auth.html#header.authorization" title="Authorization">Section 4.2</a> of <a href="#Part7" id="rfc.xref.Part7.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[Part7]</cite></a>) does not appear in the request, if the cache is shared, unless the response explicitly allows it (see <a href="#caching.authenticated.responses" title="Storing Responses to Authenticated Requests">Section&nbsp;3.2</a>), and
     772            <li>the <a href="p7-auth.html#header.authorization" class="smpl">Authorization</a> header field (see <a href="p7-auth.html#header.authorization" title="Authorization">Section 4.2</a> of <a href="#RFC7235" id="rfc.xref.RFC7235.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[RFC7235]</cite></a>) does not appear in the request, if the cache is shared, unless the response explicitly allows it (see <a href="#caching.authenticated.responses" title="Storing Responses to Authenticated Requests">Section&nbsp;3.2</a>), and
    773773            </li>
    774774            <li>the response either:
    … …  
    799799         <div id="incomplete.responses">
    800800            <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a href="#incomplete.responses">Storing Incomplete Responses</a></h2>
    801             <p id="rfc.section.3.1.p.1">A response message is considered complete when all of the octets indicated by the message framing (<a href="#Part1" id="rfc.xref.Part1.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) are received prior to the connection being closed. If the request method is GET, the response status code is <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a>, and the entire response header section has been received, a cache <em class="bcp14">MAY</em> store an incomplete response message body if the cache entry is recorded as incomplete. Likewise, a <a href="p5-range.html#status.206" class="smpl">206 (Partial Content)</a> response <em class="bcp14">MAY</em> be stored as if it were an incomplete <a href="p2-semantics.html#status.200" class="smpl">200
     801            <p id="rfc.section.3.1.p.1">A response message is considered complete when all of the octets indicated by the message framing (<a href="#RFC7230" id="rfc.xref.RFC7230.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>) are received prior to the connection being closed. If the request method is GET, the response status code is <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a>, and the entire response header section has been received, a cache <em class="bcp14">MAY</em> store an incomplete response message body if the cache entry is recorded as incomplete. Likewise, a <a href="p5-range.html#status.206" class="smpl">206 (Partial Content)</a> response <em class="bcp14">MAY</em> be stored as if it were an incomplete <a href="p2-semantics.html#status.200" class="smpl">200
    802802                  (OK)</a> cache entry. However, a cache <em class="bcp14">MUST NOT</em> store incomplete or partial content responses if it does not support the <a href="p5-range.html#header.range" class="smpl">Range</a> and <a href="p5-range.html#header.content-range" class="smpl">Content-Range</a> header fields or if it does not understand the range units used in those fields.
    803803            </p>
    804             <p id="rfc.section.3.1.p.2">A cache <em class="bcp14">MAY</em> complete a stored incomplete response by making a subsequent range request (<a href="#Part5" id="rfc.xref.Part5.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a>) and combining the successful response with the stored entry, as defined in <a href="#combining.responses" title="Combining Partial Content">Section&nbsp;3.3</a>. A cache <em class="bcp14">MUST NOT</em> use an incomplete response to answer requests unless the response has been made complete or the request is partial and specifies
     804            <p id="rfc.section.3.1.p.2">A cache <em class="bcp14">MAY</em> complete a stored incomplete response by making a subsequent range request (<a href="#RFC7233" id="rfc.xref.RFC7233.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[RFC7233]</cite></a>) and combining the successful response with the stored entry, as defined in <a href="#combining.responses" title="Combining Partial Content">Section&nbsp;3.3</a>. A cache <em class="bcp14">MUST NOT</em> use an incomplete response to answer requests unless the response has been made complete or the request is partial and specifies
    805805               a range that is wholly within the incomplete response. A cache <em class="bcp14">MUST NOT</em> send a partial response to a client without explicitly marking it as such using the <a href="p5-range.html#status.206" class="smpl">206 (Partial Content)</a> status code.
    806806            </p>
    … …  
    808808         <div id="caching.authenticated.responses">
    809809            <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a href="#caching.authenticated.responses">Storing Responses to Authenticated Requests</a></h2>
    810             <p id="rfc.section.3.2.p.1">A shared cache <em class="bcp14">MUST NOT</em> use a cached response to a request with an <a href="p7-auth.html#header.authorization" class="smpl">Authorization</a> header field (<a href="p7-auth.html#header.authorization" title="Authorization">Section 4.2</a> of <a href="#Part7" id="rfc.xref.Part7.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[Part7]</cite></a>) to satisfy any subsequent request unless a cache directive that allows such responses to be stored is present in the response.
     810            <p id="rfc.section.3.2.p.1">A shared cache <em class="bcp14">MUST NOT</em> use a cached response to a request with an <a href="p7-auth.html#header.authorization" class="smpl">Authorization</a> header field (<a href="p7-auth.html#header.authorization" title="Authorization">Section 4.2</a> of <a href="#RFC7235" id="rfc.xref.RFC7235.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[RFC7235]</cite></a>) to satisfy any subsequent request unless a cache directive that allows such responses to be stored is present in the response.
    811811            </p>
    812812            <p id="rfc.section.3.2.p.2">In this specification, the following <a href="#header.cache-control" class="smpl">Cache-Control</a> response directives (<a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;5.2.2</a>) have such an effect: must-revalidate, public, s-maxage.
    … …  
    820820            <h2 id="rfc.section.3.3"><a href="#rfc.section.3.3">3.3</a>&nbsp;<a href="#combining.responses">Combining Partial Content</a></h2>
    821821            <p id="rfc.section.3.3.p.1">A response might transfer only a partial representation if the connection closed prematurely or if the request used one or
    822                more Range specifiers (<a href="#Part5" id="rfc.xref.Part5.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a>). After several such transfers, a cache might have received several ranges of the same representation. A cache <em class="bcp14">MAY</em> combine these ranges into a single stored response, and reuse that response to satisfy later requests, if they all share the
    823                same strong validator and the cache complies with the client requirements in <a href="p5-range.html#combining.byte.ranges" title="Combining Ranges">Section 4.3</a> of <a href="#Part5" id="rfc.xref.Part5.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a>.
     822               more Range specifiers (<a href="#RFC7233" id="rfc.xref.RFC7233.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[RFC7233]</cite></a>). After several such transfers, a cache might have received several ranges of the same representation. A cache <em class="bcp14">MAY</em> combine these ranges into a single stored response, and reuse that response to satisfy later requests, if they all share the
     823               same strong validator and the cache complies with the client requirements in <a href="p5-range.html#combining.byte.ranges" title="Combining Ranges">Section 4.3</a> of <a href="#RFC7233" id="rfc.xref.RFC7233.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[RFC7233]</cite></a>.
    824824            </p>
    825825            <p id="rfc.section.3.3.p.2">When combining the new response with one or more stored responses, a cache <em class="bcp14">MUST</em>:
    … …  
    840840         </p>
    841841         <ul>
    842             <li>The presented effective request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) and that of the stored response match, and
     842