Changeset 2596 for draft-ietf-httpbis


Ignore:
Timestamp:
28/01/14 02:53:11 (6 years ago)
Author:
fielding@…
Message:

(editorial) mention the purpose of fragment; see #531

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

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.html

    r2595 r2596  
    11001100               <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> ]
    11011101             [ "#" <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>.
    11041105               </p>
    11051106               <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.
     
    11251126                  — it is only the authoritative interface that is specific to TCP.
    11261127               </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.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
     1128               <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
    11281129                  configuration of authentication information, such as within command invocation options, configuration files, or bookmark lists,
    11291130                  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
     
    11561157               <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>
    11571158               <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.16"><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.
    11591160               </p>
    11601161               <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
     
    11621163                  "/", so the normal form is to provide a path of "/" instead. The scheme and host are case-insensitive and normally provided
    11631164                  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.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>).
     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>).
    11651166               </p>
    11661167               <p id="rfc.section.2.7.3.p.3">For example, the following three URIs are equivalent:</p>
     
    18251826            <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
    18261827               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
    1827                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>).
     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>).
    18281829            </p>
    18291830         </div>
     
    37263727                  </li>
    37273728                  <li><em>RFC3040</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3040.1">2.3</a>, <a href="#RFC3040"><b>11.2</b></a></li>
    3728                   <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>
    3729                         <li><em>Section 2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.17">2.7.3</a></li>
    3730                         <li><em>Section 2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.18">2.7.3</a></li>
     3729                  <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.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>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.18">2.7.3</a></li>
     3731                        <li><em>Section 2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.19">2.7.3</a></li>
    37313732                        <li><em>Section 3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.6">2.7</a></li>
    37323733                        <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.7">2.7</a></li>
    3733                         <li><em>Section 3.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.15">2.7.1</a></li>
     3734                        <li><em>Section 3.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.16">2.7.1</a></li>
    37343735                        <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>
    37353736                        <li><em>Section 3.2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.9">2.7</a></li>
    37363737                        <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>
    37373738                        <li><em>Section 3.4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.12">2.7</a></li>
    3738                         <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>
     3739                        <li><em>Section 3.5</em>&nbsp;&nbsp;<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>
    37393740                        <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.3">2.7</a></li>
    37403741                        <li><em>Section 4.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.5">2.7</a></li>
    37413742                        <li><em>Section 4.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.4">2.7</a></li>
    3742                         <li><em>Section 6</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.16">2.7.3</a></li>
     3743                        <li><em>Section 6</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.17">2.7.3</a></li>
    37433744                     </ul>
    37443745                  </li>
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r2595 r2596  
    873873   <x:ref>authority</x:ref> component, which includes a host identifier
    874874   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"/>.
    878880</t>
    879881<t>
Note: See TracChangeset for help on using the changeset viewer.