![(please configure the [header_logo] section in trac.ini)](https://www.ietf.org/images/ietflogotrans.gif)
Changeset 2596
- Timestamp:
- 28/01/14 02:53:11 (8 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
-
p1-messaging.html (modified) (6 diffs)
-
p1-messaging.xml (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r2595 r2596 1100 1100 <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> ] 1101 1101 [ "#" <a href="#uri" class="smpl">fragment</a> ] 1102 </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 1103 identifier for a potential resource within that origin server's name space. 1102 </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 hierarchical path component and optional query component serve as an identifier for a potential target resource within 1103 that origin server's name space. The optional fragment component allows for indirect identification of a secondary resource, 1104 independent of the URI scheme, as defined in <a href="http://tools.ietf.org/html/rfc3986#section-3.5">Section 3.5</a> of <a href="#RFC3986" id="rfc.xref.RFC3986.15"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>. 1104 1105 </p> 1105 1106 <p id="rfc.section.2.7.1.p.4">A sender <em class="bcp14">MUST NOT</em> generate an "http" URI with an empty host identifier. A recipient that processes such a URI reference <em class="bcp14">MUST</em> reject it as invalid. … … 1125 1126 — it is only the authoritative interface that is specific to TCP. 1126 1127 </p> 1127 <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.1 5"><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 internal1128 <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.16"><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 1128 1129 configuration of authentication information, such as within command invocation options, configuration files, or bookmark lists, 1129 1130 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 … … 1156 1157 <h3 id="rfc.section.2.7.3"><a href="#rfc.section.2.7.3">2.7.3</a> <a href="#uri.comparison">http and https URI Normalization and Comparison</a></h3> 1157 1158 <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 1158 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.1 6"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, using the defaults described above for each scheme.1159 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.17"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, using the defaults described above for each scheme. 1159 1160 </p> 1160 1161 <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 … … 1162 1163 "/", so the normal form is to provide a path of "/" instead. The scheme and host are case-insensitive and normally provided 1163 1164 in lowercase; all other components are compared in a case-sensitive manner. Characters other than those in the "reserved" 1164 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.1 7">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>).1165 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.18">2.1</a> and <a href="http://tools.ietf.org/html/rfc3986#section-2.2" id="rfc.xref.RFC3986.19">2.2</a> of <a href="#RFC3986" id="rfc.xref.RFC3986.20"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>). 1165 1166 </p> 1166 1167 <p id="rfc.section.2.7.3.p.3">For example, the following three URIs are equivalent:</p> … … 1825 1826 <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 1826 1827 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 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 1827 processing (<a href="#RFC3986" id="rfc.xref.RFC3986.2 0"><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>).1828 processing (<a href="#RFC3986" id="rfc.xref.RFC3986.21"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-3.5">Section 3.5</a>). 1828 1829 </p> 1829 1830 </div> … … 3726 3727 </li> 3727 3728 <li><em>RFC3040</em> <a href="#rfc.xref.RFC3040.1">2.3</a>, <a href="#RFC3040"><b>11.2</b></a></li> 3728 <li><em>RFC3986</em> <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>3729 <li><em>Section 2.1</em> <a href="#rfc.xref.RFC3986.1 7">2.7.3</a></li>3730 <li><em>Section 2.2</em> <a href="#rfc.xref.RFC3986.1 8">2.7.3</a></li>3729 <li><em>RFC3986</em> <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.1</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">2.7.3</a>, <a href="#rfc.xref.RFC3986.21">5.1</a>, <a href="#RFC3986"><b>11.1</b></a><ul> 3730 <li><em>Section 2.1</em> <a href="#rfc.xref.RFC3986.18">2.7.3</a></li> 3731 <li><em>Section 2.2</em> <a href="#rfc.xref.RFC3986.19">2.7.3</a></li> 3731 3732 <li><em>Section 3.1</em> <a href="#rfc.xref.RFC3986.6">2.7</a></li> 3732 3733 <li><em>Section 3.2</em> <a href="#rfc.xref.RFC3986.7">2.7</a></li> 3733 <li><em>Section 3.2.1</em> <a href="#rfc.xref.RFC3986.1 5">2.7.1</a></li>3734 <li><em>Section 3.2.1</em> <a href="#rfc.xref.RFC3986.16">2.7.1</a></li> 3734 3735 <li><em>Section 3.2.2</em> <a href="#rfc.xref.RFC3986.8">2.7</a>, <a href="#rfc.xref.RFC3986.14">2.7.1</a></li> 3735 3736 <li><em>Section 3.2.3</em> <a href="#rfc.xref.RFC3986.9">2.7</a></li> 3736 3737 <li><em>Section 3.3</em> <a href="#rfc.xref.RFC3986.10">2.7</a>, <a href="#rfc.xref.RFC3986.11">2.7</a></li> 3737 3738 <li><em>Section 3.4</em> <a href="#rfc.xref.RFC3986.12">2.7</a></li> 3738 <li><em>Section 3.5</em> <a href="#rfc.xref.RFC3986.13">2.7</a>, <a href="#rfc.xref.RFC3986. 20">5.1</a></li>3739 <li><em>Section 3.5</em> <a href="#rfc.xref.RFC3986.13">2.7</a>, <a href="#rfc.xref.RFC3986.15">2.7.1</a>, <a href="#rfc.xref.RFC3986.21">5.1</a></li> 3739 3740 <li><em>Section 4.1</em> <a href="#rfc.xref.RFC3986.3">2.7</a></li> 3740 3741 <li><em>Section 4.2</em> <a href="#rfc.xref.RFC3986.5">2.7</a></li> 3741 3742 <li><em>Section 4.3</em> <a href="#rfc.xref.RFC3986.4">2.7</a></li> 3742 <li><em>Section 6</em> <a href="#rfc.xref.RFC3986.1 6">2.7.3</a></li>3743 <li><em>Section 6</em> <a href="#rfc.xref.RFC3986.17">2.7.3</a></li> 3743 3744 </ul> 3744 3745 </li> -
draft-ietf-httpbis/latest/p1-messaging.xml
r2595 r2596 873 873 <x:ref>authority</x:ref> component, which includes a host identifier 874 874 and optional TCP port (<xref target="RFC3986" x:fmt="," x:sec="3.2.2"/>). 875 The remainder of the URI, consisting of both the hierarchical path 876 component and optional query component, serves as an identifier for 877 a potential resource within that origin server's name space. 875 The hierarchical path component and optional query component serve as an 876 identifier for a potential target resource within that origin server's name 877 space. The optional fragment component allows for indirect identification 878 of a secondary resource, independent of the URI scheme, as defined in 879 <xref target="RFC3986" x:fmt="of" x:sec="3.5"/>. 878 880 </t> 879 881 <t>
Note: See TracChangeset
for help on using the changeset viewer.
