Changeset 2590


Ignore:
Timestamp:
Jan 27, 2014, 3:20:33 PM (6 years ago)
Author:
fielding@…
Message:

(editorial) import scheme from URI spec and add links within constructing effective request URI; related to [2587]; see #531

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

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/httpbis.abnf

    r2585 r2590  
    196196request-target = origin-form / absolute-form / authority-form / asterisk-form
    197197rfc850-date = day-name-l "," SP date2 SP time-of-day SP GMT
     198scheme = <scheme, defined in [RFC3986], Section 3.1>
    198199second = 2DIGIT
    199200segment = <segment, defined in [RFC3986], Section 3.3>
     
    276277; http-URI defined but not used
    277278; https-URI defined but not used
     279; scheme defined but not used
  • draft-ietf-httpbis/latest/p1-messaging.html

    r2587 r2590  
    448448  }
    449449  @bottom-center {
    450        content: "Expires July 30, 2014";
     450       content: "Expires July 31, 2014";
    451451  }
    452452  @bottom-right {
     
    490490      <meta name="dct.creator" content="Reschke, J. F.">
    491491      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest">
    492       <meta name="dct.issued" scheme="ISO8601" content="2014-01-26">
     492      <meta name="dct.issued" scheme="ISO8601" content="2014-01-27">
    493493      <meta name="dct.replaces" content="urn:ietf:rfc:2145">
    494494      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
     
    519519            <tr>
    520520               <td class="left">Intended status: Standards Track</td>
    521                <td class="right">January 26, 2014</td>
     521               <td class="right">January 27, 2014</td>
    522522            </tr>
    523523            <tr>
    524                <td class="left">Expires: July 30, 2014</td>
     524               <td class="left">Expires: July 31, 2014</td>
    525525               <td class="right"></td>
    526526            </tr>
     
    551551            in progress”.
    552552         </p>
    553          <p>This Internet-Draft will expire on July 30, 2014.</p>
     553         <p>This Internet-Draft will expire on July 31, 2014.</p>
    554554      </div>
    555555      <div id="rfc.copyrightnotice">
     
    10651065            <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.
    10661066            </p>
    1067             <p id="rfc.section.2.7.p.2">The definitions of "URI-reference", "absolute-URI", "relative-part", "authority", "port", "host", "path-abempty", "segment",
    1068                "query", and "fragment" are adopted from the URI generic syntax. An "absolute-path" rule is defined, differing slightly from
    1069                RFC 3986's "path-absolute" in that it allows a leading "//". A "partial-URI" rule is defined for protocol elements that allow
    1070                a relative URI but not a fragment.
    1071             </p>
    1072             <div id="rfc.figure.u.7"></div><pre class="inline"><span id="rfc.iref.g.16"></span><span id="rfc.iref.g.17"></span><span id="rfc.iref.g.18"></span><span id="rfc.iref.g.19"></span><span id="rfc.iref.g.20"></span><span id="rfc.iref.g.21"></span><span id="rfc.iref.g.22"></span><span id="rfc.iref.g.23"></span><span id="rfc.iref.g.24"></span><span id="rfc.iref.g.25"></span>  <a href="#uri" class="smpl">URI-reference</a> = &lt;URI-reference, defined in <a href="#RFC3986" id="rfc.xref.RFC3986.3"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-4.1">Section 4.1</a>&gt;
     1067            <p id="rfc.section.2.7.p.2">The definitions of "URI-reference", "absolute-URI", "relative-part", "scheme", "authority", "port", "host", "path-abempty",
     1068               "segment", "query", and "fragment" are adopted from the URI generic syntax. An "absolute-path" rule is defined, differing
     1069               slightly from RFC 3986's "path-absolute" in that it allows a leading "//". A "partial-URI" rule is defined for protocol elements
     1070               that allow a relative URI but not a fragment.
     1071            </p>
     1072            <div id="rfc.figure.u.7"></div><pre class="inline"><span id="rfc.iref.g.16"></span><span id="rfc.iref.g.17"></span><span id="rfc.iref.g.18"></span><span id="rfc.iref.g.19"></span><span id="rfc.iref.g.20"></span><span id="rfc.iref.g.21"></span><span id="rfc.iref.g.22"></span><span id="rfc.iref.g.23"></span><span id="rfc.iref.g.24"></span><span id="rfc.iref.g.25"></span><span id="rfc.iref.g.26"></span>  <a href="#uri" class="smpl">URI-reference</a> = &lt;URI-reference, defined in <a href="#RFC3986" id="rfc.xref.RFC3986.3"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-4.1">Section 4.1</a>&gt;
    10731073  <a href="#uri" class="smpl">absolute-URI</a>  = &lt;absolute-URI, defined in <a href="#RFC3986" id="rfc.xref.RFC3986.4"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-4.3">Section 4.3</a>&gt;
    10741074  <a href="#uri" class="smpl">relative-part</a> = &lt;relative-part, defined in <a href="#RFC3986" id="rfc.xref.RFC3986.5"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-4.2">Section 4.2</a>&gt;
    1075   <a href="#uri" class="smpl">authority</a>     = &lt;authority, defined in <a href="#RFC3986" id="rfc.xref.RFC3986.6"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-3.2">Section 3.2</a>&gt;
    1076   <a href="#uri" class="smpl">uri-host</a>      = &lt;host, defined in <a href="#RFC3986" id="rfc.xref.RFC3986.7"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-3.2.2">Section 3.2.2</a>&gt;
    1077   <a href="#uri" class="smpl">port</a>          = &lt;port, defined in <a href="#RFC3986" id="rfc.xref.RFC3986.8"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-3.2.3">Section 3.2.3</a>&gt;
    1078   <a href="#uri" class="smpl">path-abempty</a>  = &lt;path-abempty, defined in <a href="#RFC3986" id="rfc.xref.RFC3986.9"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-3.3">Section 3.3</a>&gt;
    1079   <a href="#uri" class="smpl">segment</a>       = &lt;segment, defined in <a href="#RFC3986" id="rfc.xref.RFC3986.10"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-3.3">Section 3.3</a>&gt;
    1080   <a href="#uri" class="smpl">query</a>         = &lt;query, defined in <a href="#RFC3986" id="rfc.xref.RFC3986.11"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-3.4">Section 3.4</a>&gt;
    1081   <a href="#uri" class="smpl">fragment</a>      = &lt;fragment, defined in <a href="#RFC3986" id="rfc.xref.RFC3986.12"><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>&gt;
     1075  <a href="#uri" class="smpl">scheme</a>        = &lt;scheme, defined in <a href="#RFC3986" id="rfc.xref.RFC3986.6"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-3.1">Section 3.1</a>&gt;
     1076  <a href="#uri" class="smpl">authority</a>     = &lt;authority, defined in <a href="#RFC3986" id="rfc.xref.RFC3986.7"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-3.2">Section 3.2</a>&gt;
     1077  <a href="#uri" class="smpl">uri-host</a>      = &lt;host, defined in <a href="#RFC3986" id="rfc.xref.RFC3986.8"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-3.2.2">Section 3.2.2</a>&gt;
     1078  <a href="#uri" class="smpl">port</a>          = &lt;port, defined in <a href="#RFC3986" id="rfc.xref.RFC3986.9"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-3.2.3">Section 3.2.3</a>&gt;
     1079  <a href="#uri" class="smpl">path-abempty</a>  = &lt;path-abempty, defined in <a href="#RFC3986" id="rfc.xref.RFC3986.10"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-3.3">Section 3.3</a>&gt;
     1080  <a href="#uri" class="smpl">segment</a>       = &lt;segment, defined in <a href="#RFC3986" id="rfc.xref.RFC3986.11"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-3.3">Section 3.3</a>&gt;
     1081  <a href="#uri" class="smpl">query</a>         = &lt;query, defined in <a href="#RFC3986" id="rfc.xref.RFC3986.12"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-3.4">Section 3.4</a>&gt;
     1082  <a href="#uri" class="smpl">fragment</a>      = &lt;fragment, defined in <a href="#RFC3986" id="rfc.xref.RFC3986.13"><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>&gt;
    10821083 
    10831084  <a href="#uri" class="smpl">absolute-path</a> = 1*( "/" segment )
     
    10951096                  namespace governed by a potential HTTP origin server listening for TCP (<a href="#RFC0793" id="rfc.xref.RFC0793.1"><cite title="Transmission Control Protocol">[RFC0793]</cite></a>) connections on a given port.
    10961097               </p>
    1097                <div id="rfc.figure.u.8"></div><pre class="inline"><span id="rfc.iref.g.26"></span>  <a href="#http.uri" class="smpl">http-URI</a> = "http:" "//" <a href="#uri" class="smpl">authority</a> <a href="#uri" class="smpl">path-abempty</a> [ "?" <a href="#uri" class="smpl">query</a> ]
     1098               <div id="rfc.figure.u.8"></div><pre class="inline"><span id="rfc.iref.g.27"></span>  <a href="#http.uri" class="smpl">http-URI</a> = "http:" "//" <a href="#uri" class="smpl">authority</a> <a href="#uri" class="smpl">path-abempty</a> [ "?" <a href="#uri" class="smpl">query</a> ]
    10981099             [ "#" <a href="#uri" class="smpl">fragment</a> ]
    1099 </pre><p id="rfc.section.2.7.1.p.3">The HTTP origin server is identified by the generic syntax's <a href="#uri" class="smpl">authority</a> component, which includes a host identifier and optional TCP port (<a href="#RFC3986" id="rfc.xref.RFC3986.13"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-3.2.2">Section 3.2.2</a>). The remainder of the URI, consisting of both the hierarchical path component and optional query component, serves as an
     1100</pre><p id="rfc.section.2.7.1.p.3">The HTTP origin server is identified by the generic syntax's <a href="#uri" class="smpl">authority</a> component, which includes a host identifier and optional TCP port (<a href="#RFC3986" id="rfc.xref.RFC3986.14"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-3.2.2">Section 3.2.2</a>). The remainder of the URI, consisting of both the hierarchical path component and optional query component, serves as an
    11001101                  identifier for a potential resource within that origin server's name space.
    11011102               </p>
     
    11221123                  — it is only the authoritative interface that is specific to TCP.
    11231124               </p>
    1124                <p id="rfc.section.2.7.1.p.9">The URI generic syntax for authority also includes a deprecated userinfo subcomponent (<a href="#RFC3986" id="rfc.xref.RFC3986.14"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-3.2.1">Section 3.2.1</a>) for including user authentication information in the URI. Some implementations make use of the userinfo component for internal
     1125               <p id="rfc.section.2.7.1.p.9">The URI generic syntax for authority also includes a deprecated userinfo subcomponent (<a href="#RFC3986" id="rfc.xref.RFC3986.15"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-3.2.1">Section 3.2.1</a>) for including user authentication information in the URI. Some implementations make use of the userinfo component for internal
    11251126                  configuration of authentication information, such as within command invocation options, configuration files, or bookmark lists,
    11261127                  even though such usage might expose a user identifier or password. A sender <em class="bcp14">MUST NOT</em> generate the userinfo subcomponent (and its "@" delimiter) when an "http" URI reference is generated within a message as a
     
    11401141                  the first HTTP request.
    11411142               </p>
    1142                <div id="rfc.figure.u.9"></div><pre class="inline"><span id="rfc.iref.g.27"></span>  <a href="#https.uri" class="smpl">https-URI</a> = "https:" "//" <a href="#uri" class="smpl">authority</a> <a href="#uri" class="smpl">path-abempty</a> [ "?" <a href="#uri" class="smpl">query</a> ]
     1143               <div id="rfc.figure.u.9"></div><pre class="inline"><span id="rfc.iref.g.28"></span>  <a href="#https.uri" class="smpl">https-URI</a> = "https:" "//" <a href="#uri" class="smpl">authority</a> <a href="#uri" class="smpl">path-abempty</a> [ "?" <a href="#uri" class="smpl">query</a> ]
    11431144              [ "#" <a href="#uri" class="smpl">fragment</a> ]
    11441145</pre><p id="rfc.section.2.7.2.p.4">Note that the "https" URI scheme depends on both TLS and TCP for establishing authority. Resources made available via the
     
    11531154               <h3 id="rfc.section.2.7.3"><a href="#rfc.section.2.7.3">2.7.3</a>&nbsp;<a href="#uri.comparison">http and https URI Normalization and Comparison</a></h3>
    11541155               <p id="rfc.section.2.7.3.p.1">Since the "http" and "https" schemes conform to the URI generic syntax, such URIs are normalized and compared according to
    1155                   the algorithm defined in <a href="http://tools.ietf.org/html/rfc3986#section-6">Section 6</a> of <a href="#RFC3986" id="rfc.xref.RFC3986.15"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, using the defaults described above for each scheme.
     1156                  the algorithm defined in <a href="http://tools.ietf.org/html/rfc3986#section-6">Section 6</a> of <a href="#RFC3986" id="rfc.xref.RFC3986.16"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, using the defaults described above for each scheme.
    11561157               </p>
    11571158               <p id="rfc.section.2.7.3.p.2">If the port is equal to the default port for a scheme, the normal form is to omit the port subcomponent. When not being used
     
    11591160                  "/", so the normal form is to provide a path of "/" instead. The scheme and host are case-insensitive and normally provided
    11601161                  in lowercase; all other components are compared in a case-sensitive manner. Characters other than those in the "reserved"
    1161                   set are equivalent to their percent-encoded octets: the normal form is to not encode them (see Sections <a href="http://tools.ietf.org/html/rfc3986#section-2.1" id="rfc.xref.RFC3986.16">2.1</a> and <a href="http://tools.ietf.org/html/rfc3986#section-2.2" id="rfc.xref.RFC3986.17">2.2</a> of <a href="#RFC3986" id="rfc.xref.RFC3986.18"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>).
     1162                  set are equivalent to their percent-encoded octets: the normal form is to not encode them (see Sections <a href="http://tools.ietf.org/html/rfc3986#section-2.1" id="rfc.xref.RFC3986.17">2.1</a> and <a href="http://tools.ietf.org/html/rfc3986#section-2.2" id="rfc.xref.RFC3986.18">2.2</a> of <a href="#RFC3986" id="rfc.xref.RFC3986.19"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>).
    11621163               </p>
    11631164               <p id="rfc.section.2.7.3.p.3">For example, the following three URIs are equivalent:</p>
     
    11771178            the end of the header section, and an optional message body.
    11781179         </p>
    1179          <div id="rfc.figure.u.11"></div><pre class="inline"><span id="rfc.iref.g.28"></span>  <a href="#http.message" class="smpl">HTTP-message</a>   = <a href="#http.message" class="smpl">start-line</a>
     1180         <div id="rfc.figure.u.11"></div><pre class="inline"><span id="rfc.iref.g.29"></span>  <a href="#http.message" class="smpl">HTTP-message</a>   = <a href="#http.message" class="smpl">start-line</a>
    11801181                   *( <a href="#header.fields" class="smpl">header-field</a> <a href="#core.rules" class="smpl">CRLF</a> )
    11811182                   <a href="#core.rules" class="smpl">CRLF</a>
     
    12151216               request method) and clients are implemented to only expect a response.
    12161217            </p>
    1217             <div id="rfc.figure.u.12"></div><pre class="inline"><span id="rfc.iref.g.29"></span>  <a href="#http.message" class="smpl">start-line</a>     = <a href="#request.line" class="smpl">request-line</a> / <a href="#status.line" class="smpl">status-line</a>
     1218            <div id="rfc.figure.u.12"></div><pre class="inline"><span id="rfc.iref.g.30"></span>  <a href="#http.message" class="smpl">start-line</a>     = <a href="#request.line" class="smpl">request-line</a> / <a href="#status.line" class="smpl">status-line</a>
    12181219</pre><div id="request.line">
    12191220               <h3 id="rfc.section.3.1.1"><a href="#rfc.section.3.1.1">3.1.1</a>&nbsp;<a href="#request.line">Request Line</a></h3>
     
    12211222                  the protocol version, and ending with CRLF.
    12221223               </p>
    1223                <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.30"></span>  <a href="#request.line" class="smpl">request-line</a>   = <a href="#method" class="smpl">method</a> <a href="#core.rules" class="smpl">SP</a> <a href="#request-target" class="smpl">request-target</a> <a href="#core.rules" class="smpl">SP</a> <a href="#http.version" class="smpl">HTTP-version</a> <a href="#core.rules" class="smpl">CRLF</a>
     1224               <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.31"></span>  <a href="#request.line" class="smpl">request-line</a>   = <a href="#method" class="smpl">method</a> <a href="#core.rules" class="smpl">SP</a> <a href="#request-target" class="smpl">request-target</a> <a href="#core.rules" class="smpl">SP</a> <a href="#http.version" class="smpl">HTTP-version</a> <a href="#core.rules" class="smpl">CRLF</a>
    12241225</pre><div id="rfc.iref.m.2"></div>
    12251226               <div id="method">
    12261227                  <p id="rfc.section.3.1.1.p.3">The method token indicates the request method to be performed on the target resource. The request method is case-sensitive.</p>
    12271228               </div>
    1228                <div id="rfc.figure.u.14"></div><pre class="inline"><span id="rfc.iref.g.31"></span>  <a href="#method" class="smpl">method</a>         = <a href="#rule.token.separators" class="smpl">token</a>
     1229               <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>
    12291230</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.
    12301231               </p>
     
    12491250                  another space, a possibly-empty textual phrase describing the status code, and ending with CRLF.
    12501251               </p>
    1251                <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.32"></span>  <a href="#status.line" class="smpl">status-line</a> = <a href="#http.version" class="smpl">HTTP-version</a> <a href="#core.rules" class="smpl">SP</a> <a href="#status.line" class="smpl">status-code</a> <a href="#core.rules" class="smpl">SP</a> <a href="#status.line" class="smpl">reason-phrase</a> <a href="#core.rules" class="smpl">CRLF</a>
     1252               <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.33"></span>  <a href="#status.line" class="smpl">status-line</a> = <a href="#http.version" class="smpl">HTTP-version</a> <a href="#core.rules" class="smpl">SP</a> <a href="#status.line" class="smpl">status-code</a> <a href="#core.rules" class="smpl">SP</a> <a href="#status.line" class="smpl">reason-phrase</a> <a href="#core.rules" class="smpl">CRLF</a>
    12521253</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
    12531254                  the client's corresponding request. The rest of the response message is to be interpreted in light of the semantics defined
     
    12551256                  the status codes defined by this specification, considerations for the definition of new status codes, and the IANA registry.
    12561257               </p>
    1257                <div id="rfc.figure.u.16"></div><pre class="inline"><span id="rfc.iref.g.33"></span>  <a href="#status.line" class="smpl">status-code</a>    = 3<a href="#core.rules" class="smpl">DIGIT</a>
     1258               <div id="rfc.figure.u.16"></div><pre class="inline"><span id="rfc.iref.g.34"></span>  <a href="#status.line" class="smpl">status-code</a>    = 3<a href="#core.rules" class="smpl">DIGIT</a>
    12581259</pre><p id="rfc.section.3.1.2.p.5">The reason-phrase element exists for the sole purpose of providing a textual description associated with the numeric status
    12591260                  code, mostly out of deference to earlier Internet application protocols that were more frequently used with interactive text
    12601261                  clients. A client <em class="bcp14">SHOULD</em> ignore the reason-phrase content.
    12611262               </p>
    1262                <div id="rfc.figure.u.17"></div><pre class="inline"><span id="rfc.iref.g.34"></span>  <a href="#status.line" class="smpl">reason-phrase</a>  = *( <a href="#core.rules" class="smpl">HTAB</a> / <a href="#core.rules" class="smpl">SP</a> / <a href="#core.rules" class="smpl">VCHAR</a> / <a href="#rule.quoted-string" class="smpl">obs-text</a> )
     1263               <div id="rfc.figure.u.17"></div><pre class="inline"><span id="rfc.iref.g.35"></span>  <a href="#status.line" class="smpl">reason-phrase</a>  = *( <a href="#core.rules" class="smpl">HTAB</a> / <a href="#core.rules" class="smpl">SP</a> / <a href="#core.rules" class="smpl">VCHAR</a> / <a href="#rule.quoted-string" class="smpl">obs-text</a> )
    12631264</pre></div>
    12641265         </div>
     
    12681269               value, and optional trailing whitespace.
    12691270            </p>
    1270             <div id="rfc.figure.u.18"></div><pre class="inline"><span id="rfc.iref.g.35"></span><span id="rfc.iref.g.36"></span><span id="rfc.iref.g.37"></span><span id="rfc.iref.g.38"></span><span id="rfc.iref.g.39"></span><span id="rfc.iref.g.40"></span>  <a href="#header.fields" class="smpl">header-field</a>   = <a href="#header.fields" class="smpl">field-name</a> ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.fields" class="smpl">field-value</a> <a href="#rule.whitespace" class="smpl">OWS</a>
     1271            <div id="rfc.figure.u.18"></div><pre class="inline"><span id="rfc.iref.g.36"></span><span id="rfc.iref.g.37"></span><span id="rfc.iref.g.38"></span><span id="rfc.iref.g.39"></span><span id="rfc.iref.g.40"></span><span id="rfc.iref.g.41"></span>  <a href="#header.fields" class="smpl">header-field</a>   = <a href="#header.fields" class="smpl">field-name</a> ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.fields" class="smpl">field-value</a> <a href="#rule.whitespace" class="smpl">OWS</a>
    12711272
    12721273  <a href="#header.fields" class="smpl">field-name</a>     = <a href="#rule.token.separators" class="smpl">token</a>
     
    13401341                  <p id="rfc.section.3.2.3.p.5">   </p>
    13411342               </div>
    1342                <div id="rfc.figure.u.19"></div><pre class="inline"><span id="rfc.iref.g.41"></span><span id="rfc.iref.g.42"></span><span id="rfc.iref.g.43"></span>  <a href="#rule.whitespace" class="smpl">OWS</a>            = *( <a href="#core.rules" class="smpl">SP</a> / <a href="#core.rules" class="smpl">HTAB</a> )
     1343               <div id="rfc.figure.u.19"></div><pre class="inline"><span id="rfc.iref.g.42"></span><span id="rfc.iref.g.43"></span><span id="rfc.iref.g.44"></span>  <a href="#rule.whitespace" class="smpl">OWS</a>            = *( <a href="#core.rules" class="smpl">SP</a> / <a href="#core.rules" class="smpl">HTAB</a> )
    13431344                 ; optional whitespace
    13441345  <a href="#rule.whitespace" class="smpl">RWS</a>            = 1*( <a href="#core.rules" class="smpl">SP</a> / <a href="#core.rules" class="smpl">HTAB</a> )
     
    13971398                  </p>
    13981399               </div>
    1399                <div id="rfc.figure.u.20"></div><pre class="inline"><span id="rfc.iref.g.44"></span><span id="rfc.iref.g.45"></span>  <a href="#rule.token.separators" class="smpl">token</a>          = 1*<a href="#rule.token.separators" class="smpl">tchar</a>
     1400               <div id="rfc.figure.u.20"></div><pre class="inline"><span id="rfc.iref.g.45"></span><span id="rfc.iref.g.46"></span>  <a href="#rule.token.separators" class="smpl">token</a>          = 1*<a href="#rule.token.separators" class="smpl">tchar</a>
    14001401
    14011402  <a href="#rule.token.separators" class="smpl">tchar</a>          = "!" / "#" / "$" / "%" / "&amp;" / "'" / "*"
     
    14061407                  <p id="rfc.section.3.2.6.p.3">   A string of text is parsed as a single value if it is quoted using double-quote marks.</p>
    14071408               </div>
    1408                <div id="rfc.figure.u.21"></div><pre class="inline"><span id="rfc.iref.g.46"></span><span id="rfc.iref.g.47"></span><span id="rfc.iref.g.48"></span>  <a href="#rule.quoted-string" class="smpl">quoted-string</a>  = <a href="#core.rules" class="smpl">DQUOTE</a> *( <a href="#rule.quoted-string" class="smpl">qdtext</a> / <a href="#rule.quoted-pair" class="smpl">quoted-pair</a> ) <a href="#core.rules" class="smpl">DQUOTE</a>
     1409               <div id="rfc.figure.u.21"></div><pre class="inline"><span id="rfc.iref.g.47"></span><span id="rfc.iref.g.48"></span><span id="rfc.iref.g.49"></span>  <a href="#rule.quoted-string" class="smpl">quoted-string</a>  = <a href="#core.rules" class="smpl">DQUOTE</a> *( <a href="#rule.quoted-string" class="smpl">qdtext</a> / <a href="#rule.quoted-pair" class="smpl">quoted-pair</a> ) <a href="#core.rules" class="smpl">DQUOTE</a>
    14091410  <a href="#rule.quoted-string" class="smpl">qdtext</a>         = <a href="#core.rules" class="smpl">HTAB</a> / <a href="#core.rules" class="smpl">SP</a> /%x21 / %x23-5B / %x5D-7E / <a href="#rule.quoted-string" class="smpl">obs-text</a>
    14101411  <a href="#rule.quoted-string" class="smpl">obs-text</a>       = %x80-FF
     
    14141415                  </p>
    14151416               </div>
    1416                <div id="rfc.figure.u.22"></div><pre class="inline"><span id="rfc.iref.g.49"></span><span id="rfc.iref.g.50"></span>  <a href="#rule.comment" class="smpl">comment</a>        = "(" *( <a href="#rule.comment" class="smpl">ctext</a> / <a href="#rule.quoted-pair" class="smpl">quoted-pair</a> / <a href="#rule.comment" class="smpl">comment</a> ) ")"
     1417               <div id="rfc.figure.u.22"></div><pre class="inline"><span id="rfc.iref.g.50"></span><span id="rfc.iref.g.51"></span>  <a href="#rule.comment" class="smpl">comment</a>        = "(" *( <a href="#rule.comment" class="smpl">ctext</a> / <a href="#rule.quoted-pair" class="smpl">quoted-pair</a> / <a href="#rule.comment" class="smpl">comment</a> ) ")"
    14171418  <a href="#rule.comment" class="smpl">ctext</a>          = <a href="#core.rules" class="smpl">HTAB</a> / <a href="#core.rules" class="smpl">SP</a> / %x21-27 / %x2A-5B / %x5D-7E / <a href="#rule.quoted-string" class="smpl">obs-text</a>
    14181419</pre><div id="rule.quoted-pair">
     
    14211422                  </p>
    14221423               </div>
    1423                <div id="rfc.figure.u.23"></div><pre class="inline"><span id="rfc.iref.g.51"></span>  <a href="#rule.quoted-pair" class="smpl">quoted-pair</a>    = "\" ( <a href="#core.rules" class="smpl">HTAB</a> / <a href="#core.rules" class="smpl">SP</a> / <a href="#core.rules" class="smpl">VCHAR</a> / <a href="#rule.quoted-string" class="smpl">obs-text</a> )
     1424               <div id="rfc.figure.u.23"></div><pre class="inline"><span id="rfc.iref.g.52"></span>  <a href="#rule.quoted-pair" class="smpl">quoted-pair</a>    = "\" ( <a href="#core.rules" class="smpl">HTAB</a> / <a href="#core.rules" class="smpl">SP</a> / <a href="#core.rules" class="smpl">VCHAR</a> / <a href="#rule.quoted-string" class="smpl">obs-text</a> )
    14241425</pre><p id="rfc.section.3.2.6.p.9">A sender <em class="bcp14">SHOULD NOT</em> generate a quoted-pair in a quoted-string except where necessary to quote DQUOTE and backslash octets occurring within that
    14251426                  string. A sender <em class="bcp14">SHOULD NOT</em> generate a quoted-pair in a comment except where necessary to quote parentheses ["(" and ")"] and backslash octets occurring
     
    14331434               is identical to the payload body unless a transfer coding has been applied, as described in <a href="#header.transfer-encoding" id="rfc.xref.header.transfer-encoding.1" title="Transfer-Encoding">Section&nbsp;3.3.1</a>.
    14341435            </p>
    1435             <div id="rfc.figure.u.24"></div><pre class="inline"><span id="rfc.iref.g.52"></span>  <a href="#message.body" class="smpl">message-body</a> = *OCTET
     1436            <div id="rfc.figure.u.24"></div><pre class="inline"><span id="rfc.iref.g.53"></span>  <a href="#message.body" class="smpl">message-body</a> = *OCTET
    14361437</pre><p id="rfc.section.3.3.p.3">The rules for when a message body is allowed in a message differ for requests and responses.</p>
    14371438            <p id="rfc.section.3.3.p.4">The presence of a message body in a request is signaled by a <a href="#header.content-length" class="smpl">Content-Length</a> or <a href="#header.transfer-encoding" class="smpl">Transfer-Encoding</a> header field. Request message framing is independent of method semantics, even if the method does not define any use for a
     
    14491450                  have been (or will be) applied to the payload body in order to form the message body. Transfer codings are defined in <a href="#transfer.codings" title="Transfer Codings">Section&nbsp;4</a>.
    14501451               </p>
    1451                <div id="rfc.figure.u.25"></div><pre class="inline"><span id="rfc.iref.g.53"></span>  <a href="#header.transfer-encoding" class="smpl">Transfer-Encoding</a> = 1#<a href="#transfer.codings" class="smpl">transfer-coding</a>
     1452               <div id="rfc.figure.u.25"></div><pre class="inline"><span id="rfc.iref.g.54"></span>  <a href="#header.transfer-encoding" class="smpl">Transfer-Encoding</a> = 1#<a href="#transfer.codings" class="smpl">transfer-coding</a>
    14521453</pre><p id="rfc.section.3.3.1.p.3">Transfer-Encoding is analogous to the Content-Transfer-Encoding field of MIME, which was designed to enable safe transport
    14531454                  of binary data over a 7-bit transport service (<a href="#RFC2045" id="rfc.xref.RFC2045.2"><cite title="Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies">[RFC2045]</cite></a>, <a href="http://tools.ietf.org/html/rfc2045#section-6">Section 6</a>). However, safe transport has a different focus for an 8bit-clean transfer protocol. In HTTP's case, Transfer-Encoding is
     
    14901491                  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>).
    14911492               </p>
    1492                <div id="rfc.figure.u.27"></div><pre class="inline"><span id="rfc.iref.g.54"></span>  <a href="#header.content-length" class="smpl">Content-Length</a> = 1*<a href="#core.rules" class="smpl">DIGIT</a>
     1493               <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>
    14931494</pre><p id="rfc.section.3.3.2.p.3">An example is</p>
    14941495               <div id="rfc.figure.u.28"></div><pre class="text">  Content-Length: 3495
     
    16381639            coding is a property of the message rather than a property of the representation that is being transferred.
    16391640         </p>
    1640          <div id="rfc.figure.u.29"></div><pre class="inline"><span id="rfc.iref.g.55"></span><span id="rfc.iref.g.56"></span>  <a href="#transfer.codings" class="smpl">transfer-coding</a>    = "chunked" ; <a href="#chunked.encoding" title="Chunked Transfer Coding">Section&nbsp;4.1</a>
     1641         <div id="rfc.figure.u.29"></div><pre class="inline"><span id="rfc.iref.g.56"></span><span id="rfc.iref.g.57"></span>  <a href="#transfer.codings" class="smpl">transfer-coding</a>    = "chunked" ; <a href="#chunked.encoding" title="Chunked Transfer Coding">Section&nbsp;4.1</a>
    16411642                     / "compress" ; <a href="#compress.coding" title="Compress Coding">Section&nbsp;4.2.1</a>
    16421643                     / "deflate" ; <a href="#deflate.coding" title="Deflate Coding">Section&nbsp;4.2.2</a>
     
    16471648            <p id="rfc.section.4.p.3"> Parameters are in the form of a name or name=value pair.</p>
    16481649         </div>
    1649          <div id="rfc.figure.u.30"></div><pre class="inline"><span id="rfc.iref.g.57"></span>  <a href="#rule.parameter" class="smpl">transfer-parameter</a> = <a href="#rule.token.separators" class="smpl">token</a> <a href="#rule.whitespace" class="smpl">BWS</a> "=" <a href="#rule.whitespace" class="smpl">BWS</a> ( <a href="#rule.token.separators" class="smpl">token</a> / <a href="#rule.quoted-string" class="smpl">quoted-string</a> )
     1650         <div id="rfc.figure.u.30"></div><pre class="inline"><span id="rfc.iref.g.58"></span>  <a href="#rule.parameter" class="smpl">transfer-parameter</a> = <a href="#rule.token.separators" class="smpl">token</a> <a href="#rule.whitespace" class="smpl">BWS</a> "=" <a href="#rule.whitespace" class="smpl">BWS</a> ( <a href="#rule.token.separators" class="smpl">token</a> / <a href="#rule.quoted-string" class="smpl">quoted-string</a> )
    16501651</pre><p id="rfc.section.4.p.5">All transfer-coding names are case-insensitive and ought to be registered within the HTTP Transfer Coding registry, as defined
    16511652            in <a href="#transfer.coding.registry" title="Transfer Coding Registry">Section&nbsp;8.4</a>. They are used in the <a href="#header.te" class="smpl">TE</a> (<a href="#header.te" id="rfc.xref.header.te.1" title="TE">Section&nbsp;4.3</a>) and <a href="#header.transfer-encoding" class="smpl">Transfer-Encoding</a> (<a href="#header.transfer-encoding" id="rfc.xref.header.transfer-encoding.2" title="Transfer-Encoding">Section&nbsp;3.3.1</a>) header fields.
     
    16591660               message.
    16601661            </p>
    1661             <div id="rfc.figure.u.31"></div><pre class="inline"><span id="rfc.iref.g.58"></span><span id="rfc.iref.g.59"></span><span id="rfc.iref.g.60"></span><span id="rfc.iref.g.61"></span><span id="rfc.iref.g.62"></span><span id="rfc.iref.g.63"></span><span id="rfc.iref.g.64"></span>  <a href="#chunked.encoding" class="smpl">chunked-body</a>   = *<a href="#chunked.encoding" class="smpl">chunk</a>
     1662            <div id="rfc.figure.u.31"></div><pre class="inline"><span id="rfc.iref.g.59"></span><span id="rfc.iref.g.60"></span><span id="rfc.iref.g.61"></span><span id="rfc.iref.g.62"></span><span id="rfc.iref.g.63"></span><span id="rfc.iref.g.64"></span><span id="rfc.iref.g.65"></span>  <a href="#chunked.encoding" class="smpl">chunked-body</a>   = *<a href="#chunked.encoding" class="smpl">chunk</a>
    16621663                   <a href="#chunked.encoding" class="smpl">last-chunk</a>
    16631664                   <a href="#chunked.trailer.part" class="smpl">trailer-part</a>
     
    16811682                  of message body size.
    16821683               </p>
    1683                <div id="rfc.figure.u.32"></div><pre class="inline"><span id="rfc.iref.g.65"></span><span id="rfc.iref.g.66"></span><span id="rfc.iref.g.67"></span><span id="rfc.iref.g.68"></span>  <a href="#chunked.extension" class="smpl">chunk-ext</a>      = *( ";" <a href="#chunked.extension" class="smpl">chunk-ext-name</a> [ "=" <a href="#chunked.extension" class="smpl">chunk-ext-val</a> ] )
     1684               <div id="rfc.figure.u.32"></div><pre class="inline"><span id="rfc.iref.g.66"></span><span id="rfc.iref.g.67"></span><span id="rfc.iref.g.68"></span><span id="rfc.iref.g.69"></span>  <a href="#chunked.extension" class="smpl">chunk-ext</a>      = *( ";" <a href="#chunked.extension" class="smpl">chunk-ext-name</a> [ "=" <a href="#chunked.extension" class="smpl">chunk-ext-val</a> ] )
    16841685
    16851686  <a href="#chunked.extension" class="smpl">chunk-ext-name</a> = <a href="#rule.token.separators" class="smpl">token</a>
     
    17021703                  header section.
    17031704               </p>
    1704                <div id="rfc.figure.u.33"></div><pre class="inline"><span id="rfc.iref.g.69"></span><span id="rfc.iref.g.70"></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> )
     1705               <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> )
    17051706</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>).
    17061707               </p>
     
    17551756            </div>
    17561757            <div id="gzip.coding">
    1757                <div id="rfc.iref.g.71"></div>
     1758               <div id="rfc.iref.g.72"></div>
    17581759               <h3 id="rfc.section.4.2.3"><a href="#rfc.section.4.2.3">4.2.3</a>&nbsp;<a href="#gzip.coding">Gzip Coding</a></h3>
    17591760               <p id="rfc.section.4.2.3.p.1">The "gzip" coding is an LZ77 coding with a 32 bit CRC that is commonly produced by the gzip file compression program <a href="#RFC1952" id="rfc.xref.RFC1952.1"><cite title="GZIP file format specification version 4.3">[RFC1952]</cite></a>. A recipient <em class="bcp14">SHOULD</em> consider "x-gzip" to be equivalent to "gzip".
     
    17701771               described in <a href="#transfer.codings" title="Transfer Codings">Section&nbsp;4</a>), and/or the keyword "trailers". A client <em class="bcp14">MUST NOT</em> send the chunked transfer coding name in TE; chunked is always acceptable for HTTP/1.1 recipients.
    17711772            </p>
    1772             <div id="rfc.figure.u.35"></div><pre class="inline"><span id="rfc.iref.g.72"></span><span id="rfc.iref.g.73"></span><span id="rfc.iref.g.74"></span><span id="rfc.iref.g.75"></span>  <a href="#header.te" class="smpl">TE</a>        = #<a href="#header.te" class="smpl">t-codings</a>
     1773            <div id="rfc.figure.u.35"></div><pre class="inline"><span id="rfc.iref.g.73"></span><span id="rfc.iref.g.74"></span><span id="rfc.iref.g.75"></span><span id="rfc.iref.g.76"></span>  <a href="#header.te" class="smpl">TE</a>        = #<a href="#header.te" class="smpl">t-codings</a>
    17731774  <a href="#header.te" class="smpl">t-codings</a> = "trailers" / ( <a href="#transfer.codings" class="smpl">transfer-coding</a> [ <a href="#header.te" class="smpl">t-ranking</a> ] )
    17741775  <a href="#header.te" class="smpl">t-ranking</a> = <a href="#rule.whitespace" class="smpl">OWS</a> ";" <a href="#rule.whitespace" class="smpl">OWS</a> "q=" <a href="#header.te" class="smpl">rank</a>
     
    18031804               and the recipient wishes to confirm an integrity check on the fly.
    18041805            </p>
    1805             <div id="rfc.figure.u.37"></div><pre class="inline"><span id="rfc.iref.g.76"></span><span id="rfc.iref.g.77"></span>  <a href="#header.trailer" class="smpl">Trailer</a> = 1#<a href="#header.fields" class="smpl">field-name</a>
     1806            <div id="rfc.figure.u.37"></div><pre class="inline"><span id="rfc.iref.g.77"></span><span id="rfc.iref.g.78"></span>  <a href="#header.trailer" class="smpl">Trailer</a> = 1#<a href="#header.fields" class="smpl">field-name</a>
    18061807</pre></div>
    18071808      </div>
     
    18221823            <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
    18231824               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
    1824                processing (<a href="#RFC3986" id="rfc.xref.RFC3986.19"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-3.5">Section 3.5</a>).
     1825               processing (<a href="#RFC3986" id="rfc.xref.RFC3986.20"><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>).
    18251826            </p>
    18261827         </div>
     
    18501851               both the method being requested and whether the request is to a proxy.
    18511852            </p>
    1852             <div id="rfc.figure.u.38"></div><pre class="inline"><span id="rfc.iref.g.78"></span><span id="rfc.iref.g.79"></span><span id="rfc.iref.g.80"></span><span id="rfc.iref.g.81"></span><span id="rfc.iref.g.82"></span>  <a href="#request-target" class="smpl">request-target</a> = <a href="#origin-form" class="smpl">origin-form</a>
     1853            <div id="rfc.figure.u.38"></div><pre class="inline"><span id="rfc.iref.g.79"></span><span id="rfc.iref.g.80"></span><span id="rfc.iref.g.81"></span><span id="rfc.iref.g.82"></span><span id="rfc.iref.g.83"></span>  <a href="#request-target" class="smpl">request-target</a> = <a href="#origin-form" class="smpl">origin-form</a>
    18531854                 / <a href="#absolute-form" class="smpl">absolute-form</a>
    18541855                 / <a href="#authority-form" class="smpl">authority-form</a>
     
    19181919               to distinguish among resources while servicing requests for multiple host names on a single IP address.
    19191920            </p>
    1920             <div id="rfc.figure.u.46"></div><pre class="inline"><span id="rfc.iref.g.83"></span>  <a href="#header.host" class="smpl">Host</a> = <a href="#uri" class="smpl">uri-host</a> [ ":" <a href="#uri" class="smpl">port</a> ] ; <a href="#http.uri" title="http URI scheme">Section&nbsp;2.7.1</a>
     1921            <div id="rfc.figure.u.46"></div><pre class="inline"><span id="rfc.iref.g.84"></span>  <a href="#header.host" class="smpl">Host</a> = <a href="#uri" class="smpl">uri-host</a> [ ":" <a href="#uri" class="smpl">port</a> ] ; <a href="#http.uri" title="http URI scheme">Section&nbsp;2.7.1</a>
    19211922</pre><p id="rfc.section.5.4.p.3">A client <em class="bcp14">MUST</em> send a Host header field in all HTTP/1.1 request messages. If the target URI includes an authority component, then a client <em class="bcp14">MUST</em> send a field-value for Host that is identical to that authority component, excluding any userinfo subcomponent and its "@"
    19221923               delimiter (<a href="#http.uri" title="http URI scheme">Section&nbsp;2.7.1</a>). If the authority component is missing or undefined for the target URI, then a client <em class="bcp14">MUST</em> send a Host header field with an empty field-value.
     
    19471948            <p id="rfc.section.5.5.p.1">Since the request-target often contains only part of the user agent's target URI, a server reconstructs the intended target
    19481949               as an "<dfn>effective request URI</dfn>" to properly service the request. This reconstruction involves both the server's local configuration and information communicated
    1949                in the request-target, <a href="#header.host" class="smpl">Host</a> header field, and connection context.
     1950               in the <a href="#request-target" class="smpl">request-target</a>, <a href="#header.host" class="smpl">Host</a> header field, and connection context.
    19501951            </p>
    19511952            <p id="rfc.section.5.5.p.2">For a user agent, the effective request URI is the target URI.</p>
    1952             <p id="rfc.section.5.5.p.3">If the request-target is in absolute-form, then the effective request URI is the same as the request-target. Otherwise, the
    1953                effective request URI is constructed as follows:
     1953            <p id="rfc.section.5.5.p.3">If the <a href="#request-target" class="smpl">request-target</a> is in <a href="#absolute-form" class="smpl">absolute-form</a>, the effective request URI is the same as the request-target. Otherwise, the effective request URI is constructed as follows:
    19541954            </p>
    19551955            <ul class="empty">
    1956                <li>If the server's configuration (or outbound gateway) provides a fixed URI scheme, that scheme is used for the effective request
    1957                   URI. Otherwise, if the request is received over a TLS-secured TCP connection, the effective request URI's scheme is "https";
    1958                   if not, the scheme is "http".
     1956               <li>If the server's configuration (or outbound gateway) provides a fixed URI <a href="#uri" class="smpl">scheme</a>, that scheme is used for the effective request URI. Otherwise, if the request is received over a TLS-secured TCP connection,
     1957                  the effective request URI's scheme is "https"; if not, the scheme is "http".
    19591958               </li>
    1960                <li>If the server's configuration (or outbound gateway) provides a fixed URI authority component, that authority is used for the
    1961                   effective request URI. If not, then if the request-target is in authority-form, the effective request URI's authority component
    1962                   is the same as the request-target. If not, then if a <a href="#header.host" class="smpl">Host</a> header field is supplied with a non-empty field-value, the authority component is the same as the Host field-value. Otherwise,
     1959               <li>If the server's configuration (or outbound gateway) provides a fixed URI <a href="#uri" class="smpl">authority</a> component, that authority is used for the effective request URI. If not, then if the request-target is in <a href="#authority-form" class="smpl">authority-form</a>, the effective request URI's authority component is the same as the request-target. If not, then if a <a href="#header.host" class="smpl">Host</a> header field is supplied with a non-empty field-value, the authority component is the same as the Host field-value. Otherwise,
    19631960                  the authority component is assigned the default name configured for the server and, if the connection's incoming TCP port
    19641961                  number differs from the default port for the effective request URI's scheme, then a colon (":") and the incoming port number
    19651962                  (in decimal form) are appended to the authority component.
    19661963               </li>
    1967                <li>If the request-target is in authority-form or asterisk-form, the effective request URI's combined path and query component
    1968                   is empty. Otherwise, the combined path and query component is the same as the request-target.
     1964               <li>If the request-target is in <a href="#authority-form" class="smpl">authority-form</a> or <a href="#asterisk-form" class="smpl">asterisk-form</a>, the effective request URI's combined <a href="#uri" class="smpl">path</a> and <a href="#uri" class="smpl">query</a> component is empty. Otherwise, the combined <a href="#uri" class="smpl">path</a> and <a href="#uri" class="smpl">query</a> component is the same as the request-target.
    19691965               </li>
    1970                <li>The components of the effective request URI, once determined as above, can be combined into absolute-URI form by concatenating
    1971                   the scheme, "://", authority, and combined path and query component.
     1966               <li>The components of the effective request URI, once determined as above, can be combined into <a href="#uri" class="smpl">absolute-URI</a> form by concatenating the scheme, "://", authority, and combined path and query component.
    19721967               </li>
    19731968            </ul>
     
    19871982            <p id="rfc.section.5.5.p.9">Once the effective request URI has been constructed, an origin server needs to decide whether or not to provide service for
    19881983               that URI via the connection in which the request was received. For example, the request might have been misdirected, deliberately
    1989                or accidentally, such that the information within a received absolute-form URI or <a href="#header.host" class="smpl">Host</a> header field differs from the host or port upon which the connection has been made. If the connection is from a trusted gateway,
     1984               or accidentally, such that the information within a received <a href="#request-target" class="smpl">request-target</a> or <a href="#header.host" class="smpl">Host</a> header field differs from the host or port upon which the connection has been made. If the connection is from a trusted gateway,
    19901985               that inconsistency might be expected; otherwise, it might indicate an attempt to bypass security filters, trick the server
    19911986               into delivering non-public content, or poison a cache. See <a href="#security.considerations" title="Security Considerations">Section&nbsp;9</a> for security considerations regarding message routing.
     
    20222017                  along the request/response chain.
    20232018               </p>
    2024                <div id="rfc.figure.u.52"></div><pre class="inline"><span id="rfc.iref.g.84"></span><span id="rfc.iref.g.85"></span><span id="rfc.iref.g.86"></span><span id="rfc.iref.g.87"></span><span id="rfc.iref.g.88"></span><span id="rfc.iref.g.89"></span>  <a href="#header.via" class="smpl">Via</a> = 1#( <a href="#header.via" class="smpl">received-protocol</a> <a href="#rule.whitespace" class="smpl">RWS</a> <a href="#header.via" class="smpl">received-by</a> [ <a href="#rule.whitespace" class="smpl">RWS</a> <a href="#rule.comment" class="smpl">comment</a> ] )
     2019               <div id="rfc.figure.u.52"></div><pre class="inline"><span id="rfc.iref.g.85"></span><span id="rfc.iref.g.86"></span><span id="rfc.iref.g.87"></span><span id="rfc.iref.g.88"></span><span id="rfc.iref.g.89"></span><span id="rfc.iref.g.90"></span>  <a href="#header.via" class="smpl">Via</a> = 1#( <a href="#header.via" class="smpl">received-protocol</a> <a href="#rule.whitespace" class="smpl">RWS</a> <a href="#header.via" class="smpl">received-by</a> [ <a href="#rule.whitespace" class="smpl">RWS</a> <a href="#rule.comment" class="smpl">comment</a> ] )
    20252020
    20262021  <a href="#header.via" class="smpl">received-protocol</a> = [ <a href="#header.upgrade" class="smpl">protocol-name</a> "/" ] <a href="#header.upgrade" class="smpl">protocol-version</a>
     
    21272122            </p>
    21282123            <p id="rfc.section.6.1.p.4">The Connection header field's value has the following grammar:</p>
    2129             <div id="rfc.figure.u.56"></div><pre class="inline"><span id="rfc.iref.g.90"></span><span id="rfc.iref.g.91"></span>  <a href="#header.connection" class="smpl">Connection</a>        = 1#<a href="#header.connection" class="smpl">connection-option</a>
     2124            <div id="rfc.figure.u.56"></div><pre class="inline"><span id="rfc.iref.g.91"></span><span id="rfc.iref.g.92"></span>  <a href="#header.connection" class="smpl">Connection</a>        = 1#<a href="#header.connection" class="smpl">connection-option</a>
    21302125  <a href="#header.connection" class="smpl">connection-option</a> = <a href="#rule.token.separators" class="smpl">token</a>
    21312126</pre><p id="rfc.section.6.1.p.6">Connection options are case-insensitive.</p>
     
    22962291               in order of descending preference, before sending the final response. A server <em class="bcp14">MAY</em> ignore a received Upgrade header field if it wishes to continue using the current protocol on that connection.
    22972292            </p>
    2298             <div id="rfc.figure.u.58"></div><pre class="inline"><span id="rfc.iref.g.92"></span>  <a href="#header.upgrade" class="smpl">Upgrade</a>          = 1#<a href="#header.upgrade" class="smpl">protocol</a>
     2293            <div id="rfc.figure.u.58"></div><pre class="inline"><span id="rfc.iref.g.93"></span>  <a href="#header.upgrade" class="smpl">Upgrade</a>          = 1#<a href="#header.upgrade" class="smpl">protocol</a>
    22992294
    23002295  <a href="#header.upgrade" class="smpl">protocol</a>         = <a href="#header.upgrade" class="smpl">protocol-name</a> ["/" <a href="#header.upgrade" class="smpl">protocol-version</a>]
     
    34003395 asterisk-form
    34013396
     3397<a href="#uri" class="smpl">scheme</a> = &lt;scheme, defined in [RFC3986], Section 3.1&gt;
    34023398<a href="#uri" class="smpl">segment</a> = &lt;segment, defined in [RFC3986], Section 3.3&gt;
    34033399<a href="#http.message" class="smpl">start-line</a> = request-line / status-line
     
    35153511                  <li><tt>Grammar</tt>&nbsp;&nbsp;
    35163512                     <ul>
    3517                         <li><tt>absolute-form</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.80"><b>5.3</b></a></li>
    3518                         <li><tt>absolute-path</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.19"><b>2.7</b></a></li>
     3513                        <li><tt>absolute-form</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.81"><b>5.3</b></a></li>
     3514                        <li><tt>absolute-path</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.20"><b>2.7</b></a></li>
    35193515                        <li><tt>absolute-URI</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.17"><b>2.7</b></a></li>
    35203516                        <li>ALPHA&nbsp;&nbsp;<a href="#rfc.iref.g.1"><b>1.2</b></a></li>
    3521                         <li><tt>asterisk-form</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.82"><b>5.3</b></a></li>
    3522                         <li><tt>authority</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.18"><b>2.7</b></a></li>
    3523                         <li><tt>authority-form</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.81"><b>5.3</b></a></li>
    3524                         <li><tt>BWS</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.43"><b>3.2.3</b></a></li>
    3525                         <li><tt>chunk</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.59"><b>4.1</b></a></li>
    3526                         <li><tt>chunk-data</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.64"><b>4.1</b></a></li>
    3527                         <li><tt>chunk-ext</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.63">4.1</a>, <a href="#rfc.iref.g.66"><b>4.1.1</b></a></li>
    3528                         <li><tt>chunk-ext-name</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.67"><b>4.1.1</b></a></li>
    3529                         <li><tt>chunk-ext-val</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.68"><b>4.1.1</b></a></li>
    3530                         <li><tt>chunk-size</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.60"><b>4.1</b></a></li>
    3531                         <li><tt>chunked-body</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.58"><b>4.1</b></a>, <a href="#rfc.iref.g.65"><b>4.1.1</b></a></li>
    3532                         <li><tt>comment</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.49"><b>3.2.6</b></a></li>
    3533                         <li><tt>Connection</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.90"><b>6.1</b></a></li>
    3534                         <li><tt>connection-option</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.91"><b>6.1</b></a></li>
    3535                         <li><tt>Content-Length</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.54"><b>3.3.2</b></a></li>
     3517                        <li><tt>asterisk-form</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.83"><b>5.3</b></a></li>
     3518                        <li><tt>authority</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.19"><b>2.7</b></a></li>
     3519                        <li><tt>authority-form</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.82"><b>5.3</b></a></li>
     3520                        <li><tt>BWS</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.44"><b>3.2.3</b></a></li>
     3521                        <li><tt>chunk</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.60"><b>4.1</b></a></li>
     3522                        <li><tt>chunk-data</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.65"><b>4.1</b></a></li>
     3523                        <li><tt>chunk-ext</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.64">4.1</a>, <a href="#rfc.iref.g.67"><b>4.1.1</b></a></li>
     3524                        <li><tt>chunk-ext-name</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.68"><b>4.1.1</b></a></li>
     3525                        <li><tt>chunk-ext-val</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.69"><b>4.1.1</b></a></li>
     3526                        <li><tt>chunk-size</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.61"><b>4.1</b></a></li>
     3527                        <li><tt>chunked-body</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.59"><b>4.1</b></a>, <a href="#rfc.iref.g.66"><b>4.1.1</b></a></li>
     3528                        <li><tt>comment</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.50"><b>3.2.6</b></a></li>
     3529                        <li><tt>Connection</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.91"><b>6.1</b></a></li>
     3530                        <li><tt>connection-option</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.92"><b>6.1</b></a></li>
     3531                        <li><tt>Content-Length</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.55"><b>3.3.2</b></a></li>
    35363532                        <li>CR&nbsp;&nbsp;<a href="#rfc.iref.g.2"><b>1.2</b></a></li>
    35373533                        <li>CRLF&nbsp;&nbsp;<a href="#rfc.iref.g.3"><b>1.2</b></a></li>
    3538                         <li><tt>ctext</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.50"><b>3.2.6</b></a></li>
     3534                        <li><tt>ctext</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.51"><b>3.2.6</b></a></li>
    35393535                        <li>CTL&nbsp;&nbsp;<a href="#rfc.iref.g.4"><b>1.2</b></a></li>
    35403536                        <li>DIGIT&nbsp;&nbsp;<a href="#rfc.iref.g.5"><b>1.2</b></a></li>
    35413537                        <li>DQUOTE&nbsp;&nbsp;<a href="#rfc.iref.g.6"><b>1.2</b></a></li>
    3542                         <li><tt>field-content</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.39"><b>3.2</b></a></li>
    3543                         <li><tt>field-name</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.36"><b>3.2</b></a>, <a href="#rfc.iref.g.77">4.4</a></li>
    3544                         <li><tt>field-value</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.37"><b>3.2</b></a></li>
    3545                         <li><tt>field-vchar</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.38"><b>3.2</b></a></li>
    3546                         <li><tt>fragment</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.22"><b>2.7</b></a></li>
    3547                         <li><tt>header-field</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.35"><b>3.2</b></a>, <a href="#rfc.iref.g.70">4.1.2</a></li>
     3538                        <li><tt>field-content</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.40"><b>3.2</b></a></li>
     3539                        <li><tt>field-name</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.37"><b>3.2</b></a>, <a href="#rfc.iref.g.78">4.4</a></li>
     3540                        <li><tt>field-value</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.38"><b>3.2</b></a></li>
     3541                        <li><tt>field-vchar</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.39"><b>3.2</b></a></li>
     3542                        <li><tt>fragment</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.23"><b>2.7</b></a></li>
     3543                        <li><tt>header-field</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.36"><b>3.2</b></a>, <a href="#rfc.iref.g.71">4.1.2</a></li>
    35483544                        <li>HEXDIG&nbsp;&nbsp;<a href="#rfc.iref.g.7"><b>1.2</b></a></li>
    3549                         <li><tt>Host</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.83"><b>5.4</b></a></li>
     3545                        <li><tt>Host</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.84"><b>5.4</b></a></li>
    35503546                        <li>HTAB&nbsp;&nbsp;<a href="#rfc.iref.g.8"><b>1.2</b></a></li>
    3551                         <li><tt>HTTP-message</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.28"><b>3</b></a></li>
     3547                        <li><tt>HTTP-message</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.29"><b>3</b></a></li>
    35523548                        <li><tt>HTTP-name</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.15"><b>2.6</b></a></li>
    3553                         <li><tt>http-URI</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.26"><b>2.7.1</b></a></li>
     3549                        <li><tt>http-URI</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.27"><b>2.7.1</b></a></li>
    35543550                        <li><tt>HTTP-version</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.14"><b>2.6</b></a></li>
    3555                         <li><tt>https-URI</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.27"><b>2.7.2</b></a></li>
    3556                         <li><tt>last-chunk</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.61"><b>4.1</b></a></li>
     3551                        <li><tt>https-URI</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.28"><b>2.7.2</b></a></li>
     3552                        <li><tt>last-chunk</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.62"><b>4.1</b></a></li>
    35573553                        <li>LF&nbsp;&nbsp;<a href="#rfc.iref.g.9"><b>1.2</b></a></li>
    3558                         <li><tt>message-body</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.52"><b>3.3</b></a></li>
    3559                         <li><tt>method</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.31"><b>3.1.1</b></a></li>
    3560                         <li><tt>obs-fold</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.40"><b>3.2</b></a></li>
    3561                         <li><tt>obs-text</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.48"><b>3.2.6</b></a></li>
     3554                        <li><tt>message-body</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.53"><b>3.3</b></a></li>
     3555                        <li><tt>method</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.32"><b>3.1.1</b></a></li>
     3556                        <li><tt>obs-fold</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.41"><b>3.2</b></a></li>
     3557                        <li><tt>obs-text</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.49"><b>3.2.6</b></a></li>
    35623558                        <li>OCTET&nbsp;&nbsp;<a href="#rfc.iref.g.10"><b>1.2</b></a></li>
    3563                         <li><tt>origin-form</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.79"><b>5.3</b></a></li>
    3564                         <li><tt>OWS</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.41"><b>3.2.3</b></a></li>
    3565                         <li><tt>partial-URI</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.25"><b>2.7</b></a></li>
    3566                         <li><tt>port</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.20"><b>2.7</b></a></li>
    3567                         <li><tt>protocol-name</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.86"><b>5.7.1</b></a></li>
    3568                         <li><tt>protocol-version</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.87"><b>5.7.1</b></a></li>
    3569                         <li><tt>pseudonym</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.89"><b>5.7.1</b></a></li>
    3570                         <li><tt>qdtext</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.47"><b>3.2.6</b></a></li>
    3571                         <li><tt>query</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.21"><b>2.7</b></a></li>
    3572                         <li><tt>quoted-pair</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.51"><b>3.2.6</b></a></li>
    3573                         <li><tt>quoted-string</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.46"><b>3.2.6</b></a></li>
    3574                         <li><tt>rank</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.75"><b>4.3</b></a></li>
    3575                         <li><tt>reason-phrase</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.34"><b>3.1.2</b></a></li>
    3576                         <li><tt>received-by</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.88"><b>5.7.1</b></a></li>
    3577                         <li><tt>received-protocol</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.85"><b>5.7.1</b></a></li>
    3578                         <li><tt>request-line</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.30"><b>3.1.1</b></a></li>
    3579                         <li><tt>request-target</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.78"><b>5.3</b></a></li>
    3580                         <li><tt>RWS</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.42"><b>3.2.3</b></a></li>
    3581                         <li><tt>segment</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.23"><b>2.7</b></a></li>
     3559                        <li><tt>origin-form</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.80"><b>5.3</b></a></li>
     3560                        <li><tt>OWS</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.42"><b>3.2.3</b></a></li>
     3561                        <li><tt>partial-URI</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.26"><b>2.7</b></a></li>
     3562                        <li><tt>port</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.21"><b>2.7</b></a></li>
     3563                        <li><tt>protocol-name</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.87"><b>5.7.1</b></a></li>
     3564                        <li><tt>protocol-version</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.88"><b>5.7.1</b></a></li>
     3565                        <li><tt>pseudonym</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.90"><b>5.7.1</b></a></li>
     3566                        <li><tt>qdtext</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.48"><b>3.2.6</b></a></li>
     3567                        <li><tt>query</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.22"><b>2.7</b></a></li>
     3568                        <li><tt>quoted-pair</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.52"><b>3.2.6</b></a></li>
     3569                        <li><tt>quoted-string</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.47"><b>3.2.6</b></a></li>
     3570                        <li><tt>rank</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.76"><b>4.3</b></a></li>
     3571                        <li><tt>reason-phrase</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.35"><b>3.1.2</b></a></li>
     3572                        <li><tt>received-by</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.89"><b>5.7.1</b></a></li>
     3573                        <li><tt>received-protocol</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.86"><b>5.7.1</b></a></li>
     3574                        <li><tt>request-line</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.31"><b>3.1.1</b></a></li>
     3575                        <li><tt>request-target</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.79"><b>5.3</b></a></li>
     3576                        <li><tt>RWS</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.43"><b>3.2.3</b></a></li>
     3577                        <li><tt>scheme</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.18"><b>2.7</b></a></li>
     3578                        <li><tt>segment</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.24"><b>2.7</b></a></li>
    35823579                        <li>SP&nbsp;&nbsp;<a href="#rfc.iref.g.11"><b>1.2</b></a></li>
    3583                         <li><tt>start-line</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.29"><b>3.1</b></a></li>
    3584                         <li><tt>status-code</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.33"><b>3.1.2</b></a></li>
    3585                         <li><tt>status-line</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.32"><b>3.1.2</b></a></li>
    3586                         <li><tt>t-codings</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.73"><b>4.3</b></a></li>
    3587                         <li><tt>t-ranking</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.74"><b>4.3</b></a></li>
    3588                         <li><tt>tchar</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.45"><b>3.2.6</b></a></li>
    3589                         <li><tt>TE</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.72"><b>4.3</b></a></li>
    3590                         <li><tt>token</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.44"><b>3.2.6</b></a></li>
    3591                         <li><tt>Trailer</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.76"><b>4.4</b></a></li>
    3592                         <li><tt>trailer-part</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.62">4.1</a>, <a href="#rfc.iref.g.69"><b>4.1.2</b></a></li>
    3593                         <li><tt>transfer-coding</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.55"><b>4</b></a></li>
    3594                         <li><tt>Transfer-Encoding</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.53"><b>3.3.1</b></a></li>
    3595                         <li><tt>transfer-extension</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.56"><b>4</b></a></li>
    3596                         <li><tt>transfer-parameter</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.57"><b>4</b></a></li>
    3597                         <li><tt>Upgrade</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.92"><b>6.7</b></a></li>
    3598                         <li><tt>uri-host</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.24"><b>2.7</b></a></li>
     3580                        <li><tt>start-line</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.30"><b>3.1</b></a></li>
     3581                        <li><tt>status-code</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.34"><b>3.1.2</b></a></li>
     3582                        <li><tt>status-line</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.33"><b>3.1.2</b></a></li>
     3583                        <li><tt>t-codings</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.74"><b>4.3</b></a></li>
     3584                        <li><tt>t-ranking</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.75"><b>4.3</b></a></li>
     3585                        <li><tt>tchar</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.46"><b>3.2.6</b></a></li>
     3586                        <li><tt>TE</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.73"><b>4.3</b></a></li>
     3587                        <li><tt>token</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.45"><b>3.2.6</b></a></li>
     3588                        <li><tt>Trailer</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.77"><b>4.4</b></a></li>
     3589                        <li><tt>trailer-part</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.63">4.1</a>, <a href="#rfc.iref.g.70"><b>4.1.2</b></a></li>
     3590                        <li><tt>transfer-coding</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.56"><b>4</b></a></li>
     3591                        <li><tt>Transfer-Encoding</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.54"><b>3.3.1</b></a></li>
     3592                        <li><tt>transfer-extension</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.57"><b>4</b></a></li>
     3593                        <li><tt>transfer-parameter</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.58"><b>4</b></a></li>
     3594                        <li><tt>Upgrade</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.93"><b>6.7</b></a></li>
     3595                        <li><tt>uri-host</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.25"><b>2.7</b></a></li>
    35993596                        <li><tt>URI-reference</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.16"><b>2.7</b></a></li>
    36003597                        <li>VCHAR&nbsp;&nbsp;<a href="#rfc.iref.g.12"><b>1.2</b></a></li>
    3601                         <li><tt>Via</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.84"><b>5.7.1</b></a></li>
     3598                        <li><tt>Via</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.85"><b>5.7.1</b></a></li>
    36023599                     </ul>
    36033600                  </li>
    3604                   <li>gzip (Coding Format)&nbsp;&nbsp;<a href="#rfc.iref.g.71">4.2.3</a></li>
     3601                  <li>gzip (Coding Format)&nbsp;&nbsp;<a href="#rfc.iref.g.72">4.2.3</a></li>
    36053602               </ul>
    36063603            </li>
     
    37283725                  </li>
    37293726                  <li><em>RFC3040</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3040.1">2.3</a>, <a href="#RFC3040"><b>11.2</b></a></li>
    3730                   <li><em>RFC3986</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.1">2.1</a>, <a href="#rfc.xref.RFC3986.2">2.7</a>, <a href="#rfc.xref.RFC3986.3">2.7</a>, <a href="#rfc.xref.RFC3986.4">2.7</a>, <a href="#rfc.xref.RFC3986.5">2.7</a>, <a href="#rfc.xref.RFC3986.6">2.7</a>, <a href="#rfc.xref.RFC3986.7">2.7</a>, <a href="#rfc.xref.RFC3986.8">2.7</a>, <a href="#rfc.xref.RFC3986.9">2.7</a>, <a href="#rfc.xref.RFC3986.10">2.7</a>, <a href="#rfc.xref.RFC3986.11">2.7</a>, <a href="#rfc.xref.RFC3986.12">2.7</a>, <a href="#rfc.xref.RFC3986.13">2.7.1</a>, <a href="#rfc.xref.RFC3986.14">2.7.1</a>, <a href="#rfc.xref.RFC3986.15">2.7.3</a>, <a href="#rfc.xref.RFC3986.16">2.7.3</a>, <a href="#rfc.xref.RFC3986.17">2.7.3</a>, <a href="#rfc.xref.RFC3986.18">2.7.3</a>, <a href="#rfc.xref.RFC3986.19">5.1</a>, <a href="#RFC3986"><b>11.1</b></a><ul>
    3731                         <li><em>Section 2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.16">2.7.3</a></li>
    3732                         <li><em>Section 2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.17">2.7.3</a></li>
    3733                         <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.6">2.7</a></li>
    3734                         <li><em>Section 3.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.14">2.7.1</a></li>
    3735                         <li><em>Section 3.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.7">2.7</a>, <a href="#rfc.xref.RFC3986.13">2.7.1</a></li>
    3736                         <li><em>Section 3.2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.8">2.7</a></li>
    3737                         <li><em>Section 3.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.9">2.7</a>, <a href="#rfc.xref.RFC3986.10">2.7</a></li>
    3738                         <li><em>Section 3.4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.11">2.7</a></li>
    3739                         <li><em>Section 3.5</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.12">2.7</a>, <a href="#rfc.xref.RFC3986.19">5.1</a></li>
     3727                  <li><em>RFC3986</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.1">2.1</a>, <a href="#rfc.xref.RFC3986.2">2.7</a>, <a href="#rfc.xref.RFC3986.3">2.7</a>, <a href="#rfc.xref.RFC3986.4">2.7</a>, <a href="#rfc.xref.RFC3986.5">2.7</a>, <a href="#rfc.xref.RFC3986.6">2.7</a>, <a href="#rfc.xref.RFC3986.7">2.7</a>, <a href="#rfc.xref.RFC3986.8">2.7</a>, <a href="#rfc.xref.RFC3986.9">2.7</a>, <a href="#rfc.xref.RFC3986.10">2.7</a>, <a href="#rfc.xref.RFC3986.11">2.7</a>, <a href="#rfc.xref.RFC3986.12">2.7</a>, <a href="#rfc.xref.RFC3986.13">2.7</a>, <a href="#rfc.xref.RFC3986.14">2.7.1</a>, <a href="#rfc.xref.RFC3986.15">2.7.1</a>, <a href="#rfc.xref.RFC3986.16">2.7.3</a>, <a href="#rfc.xref.RFC3986.17">2.7.3</a>, <a href="#rfc.xref.RFC3986.18">2.7.3</a>, <a href="#rfc.xref.RFC3986.19">2.7.3</a>, <a href="#rfc.xref.RFC3986.20">5.1</a>, <a href="#RFC3986"><b>11.1</b></a><ul>
     3728                        <li><em>Section 2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.17">2.7.3</a></li>
     3729                        <li><em>Section 2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.18">2.7.3</a></li>
     3730                        <li><em>Section 3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.6">2.7</a></li>
     3731                        <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.7">2.7</a></li>
     3732                        <li><em>Section 3.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.15">2.7.1</a></li>
     3733                        <li><em>Section 3.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.8">2.7</a>, <a href="#rfc.xref.RFC3986.14">2.7.1</a></li>
     3734                        <li><em>Section 3.2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.9">2.7</a></li>
     3735                        <li><em>Section 3.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.10">2.7</a>, <a href="#rfc.xref.RFC3986.11">2.7</a></li>
     3736                        <li><em>Section 3.4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.12">2.7</a></li>
     3737                        <li><em>Section 3.5</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.13">2.7</a>, <a href="#rfc.xref.RFC3986.20">5.1</a></li>
    37403738                        <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.3">2.7</a></li>
    37413739                        <li><em>Section 4.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.5">2.7</a></li>
    37423740                        <li><em>Section 4.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.4">2.7</a></li>
    3743                         <li><em>Section 6</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.15">2.7.3</a></li>
     3741                        <li><em>Section 6</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.16">2.7.3</a></li>
    37443742                     </ul>
    37453743                  </li>
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r2587 r2590  
    805805  <x:anchor-alias value="absolute-URI"/>
    806806  <x:anchor-alias value="relative-part"/>
     807  <x:anchor-alias value="scheme"/>
    807808  <x:anchor-alias value="authority"/>
    808809  <x:anchor-alias value="uri-host"/>
    809810  <x:anchor-alias value="port"/>
     811  <x:anchor-alias value="path"/>
    810812  <x:anchor-alias value="path-abempty"/>
    811813  <x:anchor-alias value="segment"/>
     
    816818<t>
    817819   The definitions of "URI-reference",
    818    "absolute-URI", "relative-part", "authority", "port", "host",
     820   "absolute-URI", "relative-part", "scheme", "authority", "port", "host",
    819821   "path-abempty", "segment", "query", and "fragment" are adopted from the
    820822   URI generic syntax.
     
    824826   that allow a relative URI but not a fragment.
    825827</t>
    826 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="URI-reference"><!--exported production--></iref><iref primary="true" item="Grammar" subitem="absolute-URI"/><iref primary="true" item="Grammar" subitem="authority"/><iref primary="true" item="Grammar" subitem="absolute-path"/><iref primary="true" item="Grammar" subitem="port"/><iref primary="true" item="Grammar" subitem="query"/><iref primary="true" item="Grammar" subitem="fragment"/><iref primary="true" item="Grammar" subitem="segment"/><iref primary="true" item="Grammar" subitem="uri-host"/><iref primary="true" item="Grammar" subitem="partial-URI"><!--exported production--></iref>
     828<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="URI-reference"><!--exported production--></iref><iref primary="true" item="Grammar" subitem="absolute-URI"/><iref primary="true" item="Grammar" subitem="scheme"/><iref primary="true" item="Grammar" subitem="authority"/><iref primary="true" item="Grammar" subitem="absolute-path"/><iref primary="true" item="Grammar" subitem="port"/><iref primary="true" item="Grammar" subitem="query"/><iref primary="true" item="Grammar" subitem="fragment"/><iref primary="true" item="Grammar" subitem="segment"/><iref primary="true" item="Grammar" subitem="uri-host"/><iref primary="true" item="Grammar" subitem="partial-URI"><!--exported production--></iref>
    827829  <x:ref>URI-reference</x:ref> = &lt;URI-reference, defined in <xref target="RFC3986" x:fmt="," x:sec="4.1"/>&gt;
    828830  <x:ref>absolute-URI</x:ref>  = &lt;absolute-URI, defined in <xref target="RFC3986" x:fmt="," x:sec="4.3"/>&gt;
    829831  <x:ref>relative-part</x:ref> = &lt;relative-part, defined in <xref target="RFC3986" x:fmt="," x:sec="4.2"/>&gt;
     832  <x:ref>scheme</x:ref>        = &lt;scheme, defined in <xref target="RFC3986" x:fmt="," x:sec="3.1"/>&gt;
    830833  <x:ref>authority</x:ref>     = &lt;authority, defined in <xref target="RFC3986" x:fmt="," x:sec="3.2"/>&gt;
    831834  <x:ref>uri-host</x:ref>      = &lt;host, defined in <xref target="RFC3986" x:fmt="," x:sec="3.2.2"/>&gt;
     
    25002503   "<x:dfn>effective request URI</x:dfn>" to properly service the request.
    25012504   This reconstruction involves both the server's local configuration and
    2502    information communicated in the request-target, <x:ref>Host</x:ref> header
    2503    field, and connection context.
     2505   information communicated in the <x:ref>request-target</x:ref>,
     2506   <x:ref>Host</x:ref> header field, and connection context.
    25042507</t>
    25052508<t>
     
    25072510</t>
    25082511<t>
    2509    If the request-target is in absolute-form, then the effective request URI
    2510    is the same as the request-target.  Otherwise, the effective request URI
    2511    is constructed as follows:
     2512   If the <x:ref>request-target</x:ref> is in <x:ref>absolute-form</x:ref>,
     2513   the effective request URI is the same as the request-target. Otherwise, the
     2514   effective request URI is constructed as follows:
    25122515<list style="empty">
    25132516<t>
    25142517   If the server's configuration (or outbound gateway) provides a fixed URI
    2515    scheme, that scheme is used for the effective request URI.
     2518   <x:ref>scheme</x:ref>, that scheme is used for the effective request URI.
    25162519   Otherwise, if the request is received over a TLS-secured TCP connection,
    25172520   the effective request URI's scheme is "https"; if not, the scheme is "http".
     
    25192522<t>
    25202523   If the server's configuration (or outbound gateway) provides a fixed URI
    2521    authority component, that authority is used for the effective request URI.
    2522    If not, then if the request-target is in authority-form, the effective
    2523    request URI's authority component is the same as the request-target.
     2524   <x:ref>authority</x:ref> component, that authority is used for the
     2525   effective request URI. If not, then if the request-target is in
     2526   <x:ref>authority-form</x:ref>, the effective request URI's authority
     2527   component is the same as the request-target.
    25242528   If not, then if a <x:ref>Host</x:ref> header field is supplied with a
    25252529   non-empty field-value, the authority component is the same as the
     
    25312535</t>
    25322536<t>
    2533    If the request-target is in authority-form or asterisk-form, the
    2534    effective request URI's combined path and query component is empty.
    2535    Otherwise, the combined path and query component is the same as the
    2536    request-target.
    2537 </t>
    2538 <t>
    2539    The components of the effective request URI, once determined as above,
    2540    can be combined into absolute-URI form by concatenating the scheme,
    2541    "://", authority, and combined path and query component.
     2537   If the request-target is in <x:ref>authority-form</x:ref> or
     2538   <x:ref>asterisk-form</x:ref>, the effective request URI's combined
     2539   <x:ref>path</x:ref> and <x:ref>query</x:ref> component is empty. Otherwise,
     2540   the combined <x:ref>path</x:ref> and <x:ref>query</x:ref> component is the
     2541   same as the request-target.
     2542</t>
     2543<t>
     2544   The components of the effective request URI, once determined as above, can
     2545   be combined into <x:ref>absolute-URI</x:ref> form by concatenating the
     2546   scheme, "://", authority, and combined path and query component.
    25422547</t>
    25432548</list>
     
    25862591   Once the effective request URI has been constructed, an origin server needs
    25872592   to decide whether or not to provide service for that URI via the connection
    2588    in which the request was received. For example, the request might have
    2589    been misdirected, deliberately or accidentally, such that the information
    2590    within a received absolute-form URI or <x:ref>Host</x:ref> header field
    2591    differs from the host or port upon which the connection has been made.
    2592    If the connection is from a trusted gateway, that inconsistency might be
    2593    expected; otherwise, it might indicate an attempt to bypass security
    2594    filters, trick the server into delivering non-public content, or poison
    2595    a cache. See <xref target="security.considerations"/> for security
     2593   in which the request was received. For example, the request might have been
     2594   misdirected, deliberately or accidentally, such that the information within
     2595   a received <x:ref>request-target</x:ref> or <x:ref>Host</x:ref> header
     2596   field differs from the host or port upon which the connection has been
     2597   made. If the connection is from a trusted gateway, that inconsistency might
     2598   be expected; otherwise, it might indicate an attempt to bypass security
     2599   filters, trick the server into delivering non-public content, or poison a
     2600   cache. See <xref target="security.considerations"/> for security
    25962601   considerations regarding message routing.
    25972602</t>
     
    53945399 asterisk-form
    53955400
     5401<x:ref>scheme</x:ref> = &lt;scheme, defined in [RFC3986], Section 3.1&gt;
    53965402<x:ref>segment</x:ref> = &lt;segment, defined in [RFC3986], Section 3.3&gt;
    53975403<x:ref>start-line</x:ref> = request-line / status-line
  • draft-ietf-httpbis/latest/p2-semantics.html

    r2586 r2590  
    448448  }
    449449  @bottom-center {
    450        content: "Expires July 30, 2014";
     450       content: "Expires July 31, 2014";
    451451  }
    452452  @bottom-right {
     
    493493      <meta name="dct.creator" content="Reschke, J. F.">
    494494      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
    495       <meta name="dct.issued" scheme="ISO8601" content="2014-01-26">
     495      <meta name="dct.issued" scheme="ISO8601" content="2014-01-27">
    496496      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    497497      <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.">
     
    521521            <tr>
    522522               <td class="left">Intended status: Standards Track</td>
    523                <td class="right">January 26, 2014</td>
     523               <td class="right">January 27, 2014</td>
    524524            </tr>
    525525            <tr>
    526                <td class="left">Expires: July 30, 2014</td>
     526               <td class="left">Expires: July 31, 2014</td>
    527527               <td class="right"></td>
    528528            </tr>
     
    553553            in progress”.
    554554         </p>
    555          <p>This Internet-Draft will expire on July 30, 2014.</p>
     555         <p>This Internet-Draft will expire on July 31, 2014.</p>
    556556      </div>
    557557      <div id="rfc.copyrightnotice">
  • draft-ietf-httpbis/latest/p4-conditional.html

    r2569 r2590  
    448448  }
    449449  @bottom-center {
    450        content: "Expires July 27, 2014";
     450       content: "Expires July 31, 2014";
    451451  }
    452452  @bottom-right {
     
    491491      <meta name="dct.creator" content="Reschke, J. F.">
    492492      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p4-conditional-latest">
    493       <meta name="dct.issued" scheme="ISO8601" content="2014-01-23">
     493      <meta name="dct.issued" scheme="ISO8601" content="2014-01-27">
    494494      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    495495      <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.">
     
    517517            </tr>
    518518            <tr>
    519                <td class="left">Expires: July 27, 2014</td>
    520                <td class="right">January 23, 2014</td>
     519               <td class="left">Expires: July 31, 2014</td>
     520               <td class="right">January 27, 2014</td>
    521521            </tr>
    522522         </tbody>
     
    546546            in progress”.
    547547         </p>
    548          <p>This Internet-Draft will expire on July 27, 2014.</p>
     548         <p>This Internet-Draft will expire on July 31, 2014.</p>
    549549      </div>
    550550      <div id="rfc.copyrightnotice">
  • draft-ietf-httpbis/latest/p5-range.html

    r2569 r2590  
    448448  }
    449449  @bottom-center {
    450        content: "Expires July 27, 2014";
     450       content: "Expires July 31, 2014";
    451451  }
    452452  @bottom-right {
     
    491491      <meta name="dct.creator" content="Reschke, J. F.">
    492492      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest">
    493       <meta name="dct.issued" scheme="ISO8601" content="2014-01-23">
     493      <meta name="dct.issued" scheme="ISO8601" content="2014-01-27">
    494494      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    495495      <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.">
     
    517517            </tr>
    518518            <tr>
    519                <td class="left">Expires: July 27, 2014</td>
     519               <td class="left">Expires: July 31, 2014</td>
    520520               <td class="right">J. Reschke, Editor</td>
    521521            </tr>
     
    526526            <tr>
    527527               <td class="left"></td>
    528                <td class="right">January 23, 2014</td>
     528               <td class="right">January 27, 2014</td>
    529529            </tr>
    530530         </tbody>
     
    553553            in progress”.
    554554         </p>
    555          <p>This Internet-Draft will expire on July 27, 2014.</p>
     555         <p>This Internet-Draft will expire on July 31, 2014.</p>
    556556      </div>
    557557      <div id="rfc.copyrightnotice">
  • draft-ietf-httpbis/latest/p6-cache.html

    r2569 r2590  
    451451  }
    452452  @bottom-center {
    453        content: "Expires July 27, 2014";
     453       content: "Expires July 31, 2014";
    454454  }
    455455  @bottom-right {
     
    495495      <meta name="dct.creator" content="Reschke, J. F.">
    496496      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest">
    497       <meta name="dct.issued" scheme="ISO8601" content="2014-01-23">
     497      <meta name="dct.issued" scheme="ISO8601" content="2014-01-27">
    498498      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    499499      <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.">
     
    521521            </tr>
    522522            <tr>
    523                <td class="left">Expires: July 27, 2014</td>
     523               <td class="left">Expires: July 31, 2014</td>
    524524               <td class="right">J. Reschke, Editor</td>
    525525            </tr>
     
    530530            <tr>
    531531               <td class="left"></td>
    532                <td class="right">January 23, 2014</td>
     532               <td class="right">January 27, 2014</td>
    533533            </tr>
    534534         </tbody>
     
    557557            in progress”.
    558558         </p>
    559          <p>This Internet-Draft will expire on July 27, 2014.</p>
     559         <p>This Internet-Draft will expire on July 31, 2014.</p>
    560560      </div>
    561561      <div id="rfc.copyrightnotice">
     
    774774            <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
    775775            </li>
    776             <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.1</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
     776            <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
    777777            </li>
    778778            <li>the response either:
     
    812812         <div id="caching.authenticated.responses">
    813813            <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>
    814             <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.1</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.
     814            <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.
    815815            </p>
    816816            <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.
     
    23092309                  </li>
    23102310                  <li><em>Part7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.1">3</a>, <a href="#rfc.xref.Part7.2">3.2</a>, <a href="#Part7"><b>10.1</b></a><ul>
    2311                         <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.1">3</a>, <a href="#rfc.xref.Part7.2">3.2</a></li>
     2311                        <li><em>Section 4.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.1">3</a>, <a href="#rfc.xref.Part7.2">3.2</a></li>
    23122312                     </ul>
    23132313                  </li>
  • draft-ietf-httpbis/latest/p7-auth.html

    r2577 r2590  
    448448  }
    449449  @bottom-center {
    450        content: "Expires July 28, 2014";
     450       content: "Expires July 31, 2014";
    451451  }
    452452  @bottom-right {
     
    488488      <meta name="dct.creator" content="Reschke, J. F.">
    489489      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p7-auth-latest">
    490       <meta name="dct.issued" scheme="ISO8601" content="2014-01-24">
     490      <meta name="dct.issued" scheme="ISO8601" content="2014-01-27">
    491491      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    492492      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for distributed, collaborative, hypermedia information systems. This document defines the HTTP Authentication framework.">
     
    516516            <tr>
    517517               <td class="left">Intended status: Standards Track</td>
    518                <td class="right">January 24, 2014</td>
     518               <td class="right">January 27, 2014</td>
    519519            </tr>
    520520            <tr>
    521                <td class="left">Expires: July 28, 2014</td>
     521               <td class="left">Expires: July 31, 2014</td>
    522522               <td class="right"></td>
    523523            </tr>
     
    546546            in progress”.
    547547         </p>
    548          <p>This Internet-Draft will expire on July 28, 2014.</p>
     548         <p>This Internet-Draft will expire on July 31, 2014.</p>
    549549      </div>
    550550      <div id="rfc.copyrightnotice">
Note: See TracChangeset for help on using the changeset viewer.