* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Changeset 785


Ignore:
Timestamp:
2010-03-10 02:28:36 (5 years ago)
Author:
julian.reschke@gmx.de
Message:

Allow URI-reference instead of URI in Location; state that there are currently no defined precedence rules for fragment identifiers (relates to #43 and #185)

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

Legend:

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

    r776 r785  
    404404      <meta name="dct.creator" content="Reschke, J. F."> 
    405405      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest"> 
    406       <meta name="dct.issued" scheme="ISO8601" content="2010-03-08"> 
     406      <meta name="dct.issued" scheme="ISO8601" content="2010-03-10"> 
    407407      <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 
    408408      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 1 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 1 provides an overview of HTTP and its associated terminology, defines the &#34;http&#34; and &#34;https&#34; Uniform Resource Identifier (URI) schemes, defines the generic message syntax and parsing requirements for HTTP message frames, and describes general security concerns for implementations."> 
     
    435435            </tr> 
    436436            <tr> 
    437                <td class="left">Expires: September 9, 2010</td> 
     437               <td class="left">Expires: September 11, 2010</td> 
    438438               <td class="right">HP</td> 
    439439            </tr> 
     
    488488            <tr> 
    489489               <td class="left"></td> 
    490                <td class="right">March 8, 2010</td> 
     490               <td class="right">March 10, 2010</td> 
    491491            </tr> 
    492492         </tbody> 
     
    520520      <p>The list of Internet-Draft Shadow Directories can be accessed at <a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>. 
    521521      </p> 
    522       <p>This Internet-Draft will expire in September 9, 2010.</p> 
     522      <p>This Internet-Draft will expire in September 11, 2010.</p> 
    523523      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 
    524524      <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> 
     
    10311031         "path-absolute", "query", and "authority" from <a href="#RFC3986" id="rfc.xref.RFC3986.4"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>. In addition, we define a partial-URI rule for protocol elements that allow a relative URI without a fragment. 
    10321032      </p> 
    1033       <div id="rfc.figure.u.21"></div><pre class="inline"><span id="rfc.iref.g.26"></span><span id="rfc.iref.g.27"></span><span id="rfc.iref.g.28"></span><span id="rfc.iref.g.29"></span><span id="rfc.iref.g.30"></span><span id="rfc.iref.g.31"></span><span id="rfc.iref.g.32"></span>  <a href="#uri" class="smpl">URI</a>           = &lt;URI, defined in <a href="#RFC3986" id="rfc.xref.RFC3986.5"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-3">Section 3</a>&gt; 
    1034   <a href="#uri" class="smpl">URI-reference</a> = &lt;URI-reference, defined in <a href="#RFC3986" id="rfc.xref.RFC3986.6"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-4.1">Section 4.1</a>&gt; 
    1035   <a href="#uri" class="smpl">absolute-URI</a>  = &lt;absolute-URI, defined in <a href="#RFC3986" id="rfc.xref.RFC3986.7"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-4.3">Section 4.3</a>&gt; 
    1036   <a href="#uri" class="smpl">relative-part</a> = &lt;relative-part, 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-4.2">Section 4.2</a>&gt; 
    1037   <a href="#uri" class="smpl">authority</a>     = &lt;authority, 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">Section 3.2</a>&gt; 
    1038   <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; 
    1039   <a href="#uri" class="smpl">path-absolute</a> = &lt;path-absolute, 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; 
    1040   <a href="#uri" class="smpl">port</a>          = &lt;port, 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.2.3">Section 3.2.3</a>&gt; 
    1041   <a href="#uri" class="smpl">query</a>         = &lt;query, 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.4">Section 3.4</a>&gt; 
    1042   <a href="#uri" class="smpl">uri-host</a>      = &lt;host, defined in <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>&gt; 
     1033      <div id="rfc.figure.u.21"></div><pre class="inline"><span id="rfc.iref.g.26"></span><span id="rfc.iref.g.27"></span><span id="rfc.iref.g.28"></span><span id="rfc.iref.g.29"></span><span id="rfc.iref.g.30"></span><span id="rfc.iref.g.31"></span><span id="rfc.iref.g.32"></span>  <a href="#uri" class="smpl">URI-reference</a> = &lt;URI-reference, 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.1">Section 4.1</a>&gt; 
     1034  <a href="#uri" class="smpl">absolute-URI</a>  = &lt;absolute-URI, defined in <a href="#RFC3986" id="rfc.xref.RFC3986.6"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-4.3">Section 4.3</a>&gt; 
     1035  <a href="#uri" class="smpl">relative-part</a> = &lt;relative-part, defined in <a href="#RFC3986" id="rfc.xref.RFC3986.7"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-4.2">Section 4.2</a>&gt; 
     1036  <a href="#uri" class="smpl">authority</a>     = &lt;authority, 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">Section 3.2</a>&gt; 
     1037  <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; 
     1038  <a href="#uri" class="smpl">path-absolute</a> = &lt;path-absolute, 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; 
     1039  <a href="#uri" class="smpl">port</a>          = &lt;port, 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.2.3">Section 3.2.3</a>&gt; 
     1040  <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; 
     1041  <a href="#uri" class="smpl">uri-host</a>      = &lt;host, 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.2.2">Section 3.2.2</a>&gt; 
    10431042   
    10441043  <a href="#uri" class="smpl">partial-URI</a>   = relative-part [ "?" query ] 
     
    10571056      </p> 
    10581057      <div id="rfc.figure.u.22"></div><pre class="inline"><span id="rfc.iref.g.33"></span>  <a href="#http.uri" class="smpl">http-URI</a> = "http:" "//" <a href="#uri" class="smpl">authority</a> <a href="#uri" class="smpl">path-abempty</a> [ "?" <a href="#uri" class="smpl">query</a> ] 
    1059 </pre><p id="rfc.section.2.6.1.p.3">The host identifier within an <a href="#uri" class="smpl">authority</a> component is defined in <a href="#RFC3986" id="rfc.xref.RFC3986.15"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-3.2.2">Section 3.2.2</a>. If host is provided as an IP literal or IPv4 address, then the HTTP server is any listener on the indicated TCP port at 
     1058</pre><p id="rfc.section.2.6.1.p.3">The host identifier within an <a href="#uri" class="smpl">authority</a> component is defined in <a href="#RFC3986" id="rfc.xref.RFC3986.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>. If host is provided as an IP literal or IPv4 address, then the HTTP server is any listener on the indicated TCP port at 
    10601059         that IP address. If host is a registered name, then that name is considered an indirect identifier and the recipient might 
    10611060         use a name resolution service, such as DNS, to find the address of a listener for that host. The host <em class="bcp14">MUST NOT</em> be empty; if an "http" URI is received with an empty host, then it <em class="bcp14">MUST</em> be rejected as invalid. If the port subcomponent is empty or not given, then TCP port 80 is assumed (the default reserved 
     
    10951094      <h3 id="rfc.section.2.6.3"><a href="#rfc.section.2.6.3">2.6.3</a>&nbsp;<a id="uri.comparison" href="#uri.comparison">http and https URI Normalization and Comparison</a></h3> 
    10961095      <p id="rfc.section.2.6.3.p.1">Since the "http" and "https" schemes conform to the URI generic syntax, such URIs are normalized and compared according to 
    1097          the algorithm defined in <a href="#RFC3986" id="rfc.xref.RFC3986.16"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-6">Section 6</a>, using the defaults described above for each scheme. 
     1096         the algorithm defined in <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-6">Section 6</a>, using the defaults described above for each scheme. 
    10981097      </p> 
    10991098      <p id="rfc.section.2.6.3.p.2">If the port is equal to the default port for a scheme, the normal form is to elide the port subcomponent. Likewise, an empty 
    11001099         path component is equivalent to an absolute path of "/", so the normal form is to provide a path of "/" instead. The scheme 
    11011100         and host are case-insensitive and normally provided in lowercase; all other components are compared in a case-sensitive manner. 
    1102          Characters other than those in the "reserved" set are equivalent to their percent-encoded octets (see <a href="#RFC3986" id="rfc.xref.RFC3986.17"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-2.1">Section 2.1</a>): the normal form is to not encode them. 
     1101         Characters other than those in the "reserved" set are equivalent to their percent-encoded octets (see <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-2.1">Section 2.1</a>): the normal form is to not encode them. 
    11031102      </p> 
    11041103      <p id="rfc.section.2.6.3.p.3">For example, the following three URIs are equivalent:</p> 
     
    13421341  Host: www.example.org:8001 
    13431342</pre>  <p>after connecting to port 8001 of host "www.example.org".</p>  
    1344       <p id="rfc.section.4.1.2.p.15">The request-target is transmitted in the format specified in <a href="#http.uri" title="http URI scheme">Section&nbsp;2.6.1</a>. If the request-target is percent-encoded (<a href="#RFC3986" id="rfc.xref.RFC3986.18"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-2.1">Section 2.1</a>), the origin server <em class="bcp14">MUST</em> decode the request-target in order to properly interpret the request. Servers <em class="bcp14">SHOULD</em> respond to invalid request-targets with an appropriate status code. 
     1343      <p id="rfc.section.4.1.2.p.15">The request-target is transmitted in the format specified in <a href="#http.uri" title="http URI scheme">Section&nbsp;2.6.1</a>. If the request-target is percent-encoded (<a href="#RFC3986" id="rfc.xref.RFC3986.17"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-2.1">Section 2.1</a>), the origin server <em class="bcp14">MUST</em> decode the request-target in order to properly interpret the request. Servers <em class="bcp14">SHOULD</em> respond to invalid request-targets with an appropriate status code. 
    13451344      </p> 
    13461345      <p id="rfc.section.4.1.2.p.16">A transparent proxy <em class="bcp14">MUST NOT</em> rewrite the "path-absolute" part of the received request-target when forwarding it to the next inbound server, except as noted 
     
    29802979 transfer-coding ] ) 
    29812980 
    2982 <a href="#uri" class="smpl">URI</a> = &lt;URI, defined in [RFC3986], Section 3&gt; 
    29832981<a href="#uri" class="smpl">URI-reference</a> = &lt;URI-reference, defined in [RFC3986], Section 4.1&gt; 
    29842982<a href="#header.upgrade" class="smpl">Upgrade</a> = "Upgrade:" OWS Upgrade-v 
     
    31303128; Response defined but not used 
    31313129; TE defined but not used 
    3132 ; URI defined but not used 
    31333130; URI-reference defined but not used 
    31343131; http-URI defined but not used 
     
    36513648                  <li class="indline1"><em>RFC2965</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2965.1">3.2</a>, <a class="iref" href="#RFC2965"><b>13.2</b></a></li> 
    36523649                  <li class="indline1"><em>RFC3864</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3864.1">10.1</a>, <a class="iref" href="#RFC3864"><b>13.2</b></a></li> 
    3653                   <li class="indline1"><em>RFC3986</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3986.1">1</a>, <a class="iref" href="#rfc.xref.RFC3986.2">2.6</a>, <a class="iref" href="#rfc.xref.RFC3986.3">2.6</a>, <a class="iref" href="#rfc.xref.RFC3986.4">2.6</a>, <a class="iref" href="#rfc.xref.RFC3986.5">2.6</a>, <a class="iref" href="#rfc.xref.RFC3986.6">2.6</a>, <a class="iref" href="#rfc.xref.RFC3986.7">2.6</a>, <a class="iref" href="#rfc.xref.RFC3986.8">2.6</a>, <a class="iref" href="#rfc.xref.RFC3986.9">2.6</a>, <a class="iref" href="#rfc.xref.RFC3986.10">2.6</a>, <a class="iref" href="#rfc.xref.RFC3986.11">2.6</a>, <a class="iref" href="#rfc.xref.RFC3986.12">2.6</a>, <a class="iref" href="#rfc.xref.RFC3986.13">2.6</a>, <a class="iref" href="#rfc.xref.RFC3986.14">2.6</a>, <a class="iref" href="#rfc.xref.RFC3986.15">2.6.1</a>, <a class="iref" href="#rfc.xref.RFC3986.16">2.6.3</a>, <a class="iref" href="#rfc.xref.RFC3986.17">2.6.3</a>, <a class="iref" href="#rfc.xref.RFC3986.18">4.1.2</a>, <a class="iref" href="#RFC3986"><b>13.1</b></a><ul class="ind"> 
    3654                         <li class="indline1"><em>Section 2.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3986.17">2.6.3</a>, <a class="iref" href="#rfc.xref.RFC3986.18">4.1.2</a></li> 
    3655                         <li class="indline1"><em>Section 3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3986.5">2.6</a></li> 
    3656                         <li class="indline1"><em>Section 3.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3986.9">2.6</a></li> 
    3657                         <li class="indline1"><em>Section 3.2.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3986.14">2.6</a>, <a class="iref" href="#rfc.xref.RFC3986.15">2.6.1</a></li> 
    3658                         <li class="indline1"><em>Section 3.2.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3986.12">2.6</a></li> 
    3659                         <li class="indline1"><em>Section 3.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3986.10">2.6</a>, <a class="iref" href="#rfc.xref.RFC3986.11">2.6</a></li> 
    3660                         <li class="indline1"><em>Section 3.4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3986.13">2.6</a></li> 
    3661                         <li class="indline1"><em>Section 4.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3986.6">2.6</a></li> 
    3662                         <li class="indline1"><em>Section 4.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3986.8">2.6</a></li> 
    3663                         <li class="indline1"><em>Section 4.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3986.7">2.6</a></li> 
    3664                         <li class="indline1"><em>Section 6</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3986.16">2.6.3</a></li> 
     3650                  <li class="indline1"><em>RFC3986</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3986.1">1</a>, <a class="iref" href="#rfc.xref.RFC3986.2">2.6</a>, <a class="iref" href="#rfc.xref.RFC3986.3">2.6</a>, <a class="iref" href="#rfc.xref.RFC3986.4">2.6</a>, <a class="iref" href="#rfc.xref.RFC3986.5">2.6</a>, <a class="iref" href="#rfc.xref.RFC3986.6">2.6</a>, <a class="iref" href="#rfc.xref.RFC3986.7">2.6</a>, <a class="iref" href="#rfc.xref.RFC3986.8">2.6</a>, <a class="iref" href="#rfc.xref.RFC3986.9">2.6</a>, <a class="iref" href="#rfc.xref.RFC3986.10">2.6</a>, <a class="iref" href="#rfc.xref.RFC3986.11">2.6</a>, <a class="iref" href="#rfc.xref.RFC3986.12">2.6</a>, <a class="iref" href="#rfc.xref.RFC3986.13">2.6</a>, <a class="iref" href="#rfc.xref.RFC3986.14">2.6.1</a>, <a class="iref" href="#rfc.xref.RFC3986.15">2.6.3</a>, <a class="iref" href="#rfc.xref.RFC3986.16">2.6.3</a>, <a class="iref" href="#rfc.xref.RFC3986.17">4.1.2</a>, <a class="iref" href="#RFC3986"><b>13.1</b></a><ul class="ind"> 
     3651                        <li class="indline1"><em>Section 2.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3986.16">2.6.3</a>, <a class="iref" href="#rfc.xref.RFC3986.17">4.1.2</a></li> 
     3652                        <li class="indline1"><em>Section 3.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3986.8">2.6</a></li> 
     3653                        <li class="indline1"><em>Section 3.2.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3986.13">2.6</a>, <a class="iref" href="#rfc.xref.RFC3986.14">2.6.1</a></li> 
     3654                        <li class="indline1"><em>Section 3.2.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3986.11">2.6</a></li> 
     3655                        <li class="indline1"><em>Section 3.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3986.9">2.6</a>, <a class="iref" href="#rfc.xref.RFC3986.10">2.6</a></li> 
     3656                        <li class="indline1"><em>Section 3.4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3986.12">2.6</a></li> 
     3657                        <li class="indline1"><em>Section 4.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3986.5">2.6</a></li> 
     3658                        <li class="indline1"><em>Section 4.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3986.7">2.6</a></li> 
     3659                        <li class="indline1"><em>Section 4.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3986.6">2.6</a></li> 
     3660                        <li class="indline1"><em>Section 6</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3986.15">2.6.3</a></li> 
    36653661                     </ul> 
    36663662                  </li> 
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r773 r785  
    858858   the scope of URIs and resources can be found in <xref target="RFC3986"/>. 
    859859</t> 
    860   <x:anchor-alias value="URI"/> 
    861860  <x:anchor-alias value="URI-reference"/> 
    862861  <x:anchor-alias value="absolute-URI"/> 
     
    877876</t> 
    878877<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="URI-reference"/><iref primary="true" item="Grammar" subitem="absolute-URI"/><iref primary="true" item="Grammar" subitem="authority"/><iref primary="true" item="Grammar" subitem="path-absolute"/><iref primary="true" item="Grammar" subitem="port"/><iref primary="true" item="Grammar" subitem="query"/><iref primary="true" item="Grammar" subitem="uri-host"/> 
    879   <x:ref>URI</x:ref>           = &lt;URI, defined in <xref target="RFC3986" x:fmt="," x:sec="3"/>&gt; 
    880878  <x:ref>URI-reference</x:ref> = &lt;URI-reference, defined in <xref target="RFC3986" x:fmt="," x:sec="4.1"/>&gt; 
    881879  <x:ref>absolute-URI</x:ref>  = &lt;absolute-URI, defined in <xref target="RFC3986" x:fmt="," x:sec="4.3"/>&gt; 
     
    48654863 transfer-coding ] ) 
    48664864 
    4867 <x:ref>URI</x:ref> = &lt;URI, defined in [RFC3986], Section 3&gt; 
    48684865<x:ref>URI-reference</x:ref> = &lt;URI-reference, defined in [RFC3986], Section 4.1&gt; 
    48694866<x:ref>Upgrade</x:ref> = "Upgrade:" OWS Upgrade-v 
     
    50175014; Response defined but not used 
    50185015; TE defined but not used 
    5019 ; URI defined but not used 
    50205016; URI-reference defined but not used 
    50215017; http-URI defined but not used 
  • draft-ietf-httpbis/latest/p2-semantics.html

    r776 r785  
    403403      <meta name="dct.creator" content="Reschke, J. F."> 
    404404      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 
    405       <meta name="dct.issued" scheme="ISO8601" content="2010-03-08"> 
     405      <meta name="dct.issued" scheme="ISO8601" content="2010-03-10"> 
    406406      <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 
    407407      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 2 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages as expressed by request methods, request-header fields, response status codes, and response-header fields."> 
     
    434434            </tr> 
    435435            <tr> 
    436                <td class="left">Expires: September 9, 2010</td> 
     436               <td class="left">Expires: September 11, 2010</td> 
    437437               <td class="right">HP</td> 
    438438            </tr> 
     
    487487            <tr> 
    488488               <td class="left"></td> 
    489                <td class="right">March 8, 2010</td> 
     489               <td class="right">March 10, 2010</td> 
    490490            </tr> 
    491491         </tbody> 
     
    518518      <p>The list of Internet-Draft Shadow Directories can be accessed at <a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>. 
    519519      </p> 
    520       <p>This Internet-Draft will expire in September 9, 2010.</p> 
     520      <p>This Internet-Draft will expire in September 11, 2010.</p> 
    521521      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 
    522522      <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> 
     
    728728  <a href="#abnf.dependencies" class="smpl">product</a>       = &lt;product, defined in <a href="#Part1" id="rfc.xref.Part1.14"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#product.tokens" title="Product Tokens">Section 6.3</a>&gt; 
    729729  <a href="#abnf.dependencies" class="smpl">TE</a>            = &lt;TE, defined in <a href="#Part1" id="rfc.xref.Part1.15"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 9.8</a>&gt; 
    730   <a href="#abnf.dependencies" class="smpl">URI</a>           = &lt;URI, defined in <a href="#Part1" id="rfc.xref.Part1.16"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.6</a>&gt; 
     730  <a href="#abnf.dependencies" class="smpl">URI-reference</a> = &lt;URI-reference, defined in <a href="#Part1" id="rfc.xref.Part1.16"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.6</a>&gt; 
    731731</pre><div id="rfc.figure.u.3"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">Accept</a>        = &lt;Accept, defined in <a href="#Part3" id="rfc.xref.Part3.1"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept" title="Accept">Section 5.1</a>&gt; 
    732732  <a href="#abnf.dependencies" class="smpl">Accept-Charset</a> = 
     
    15791579         the location <em class="bcp14">SHOULD</em> indicate the server's preferred URI for automatic redirection to the resource. 
    15801580      </p> 
    1581       <p id="rfc.section.9.4.p.3">The field value consists of a single URI.</p> 
     1581      <p id="rfc.section.9.4.p.3">The field value consists of a single URI-reference. When it has the form of a relative reference (<a href="#RFC3986" id="rfc.xref.RFC3986.1"><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>), the final value is computed by resolving it against the effective request URI (<a href="#RFC3986" id="rfc.xref.RFC3986.2"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-5">Section 5</a>). 
     1582      </p> 
    15821583      <div id="rfc.figure.u.17"></div><pre class="inline"><span id="rfc.iref.g.18"></span><span id="rfc.iref.g.19"></span>  <a href="#header.location" class="smpl">Location</a>       = "Location" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.location" class="smpl">Location-v</a> 
    1583   <a href="#header.location" class="smpl">Location-v</a>     = <a href="#abnf.dependencies" class="smpl">URI</a> 
    1584 </pre><p id="rfc.section.9.4.p.5">An example is:</p> 
    1585       <div id="rfc.figure.u.18"></div><pre class="text">  Location: http://www.example.org/pub/WWW/People.html 
     1584  <a href="#header.location" class="smpl">Location-v</a>     = <a href="#abnf.dependencies" class="smpl">URI-reference</a> 
     1585</pre><div id="rfc.figure.u.18"></div>  
     1586      <p>Examples are:</p>  <pre class="text">  Location: http://www.example.org/pub/WWW/People.html#tim 
     1587</pre><div id="rfc.figure.u.19"></div><pre class="text">  Location: /index.html 
    15861588</pre><p id="rfc.section.9.4.p.7">There are circumstances in which a fragment identifier in a Location URI would not be appropriate: </p> 
    15871589      <ul> 
     
    15901592      </ul> 
    15911593      <div class="note" id="rfc.section.9.4.p.8">  
     1594         <p> <b>Note:</b> This specification does not define precedence rules for the case where the original URI, as navigated to be the user agent, 
     1595            and the Location header field value both contain fragment identifiers. 
     1596         </p>  
     1597      </div> 
     1598      <div class="note" id="rfc.section.9.4.p.9">  
    15921599         <p> <b>Note:</b> The Content-Location header field (<a href="p3-payload.html#header.content-location" title="Content-Location">Section 5.7</a> of <a href="#Part3" id="rfc.xref.Part3.11"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) differs from Location in that the Content-Location identifies the original location of the entity enclosed in the response. 
    15931600            It is therefore possible for a response to contain header fields for both Location and Content-Location. 
     
    16001607         is attempting to trace a request which appears to be failing or looping in mid-chain. 
    16011608      </p> 
    1602       <div id="rfc.figure.u.19"></div><pre class="inline"><span id="rfc.iref.g.20"></span><span id="rfc.iref.g.21"></span>  <a href="#header.max-forwards" class="smpl">Max-Forwards</a>   = "Max-Forwards" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.max-forwards" class="smpl">Max-Forwards-v</a> 
     1609      <div id="rfc.figure.u.20"></div><pre class="inline"><span id="rfc.iref.g.20"></span><span id="rfc.iref.g.21"></span>  <a href="#header.max-forwards" class="smpl">Max-Forwards</a>   = "Max-Forwards" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.max-forwards" class="smpl">Max-Forwards-v</a> 
    16031610  <a href="#header.max-forwards" class="smpl">Max-Forwards-v</a> = 1*<a href="#notation" class="smpl">DIGIT</a> 
    16041611</pre><p id="rfc.section.9.5.p.3">The Max-Forwards value is a decimal integer indicating the remaining number of times this request message may be forwarded.</p> 
     
    16231630         apply to sources with non-HTTP URIs (e.g., FTP). 
    16241631      </p> 
    1625       <div id="rfc.figure.u.20"></div><pre class="inline"><span id="rfc.iref.g.22"></span><span id="rfc.iref.g.23"></span>  <a href="#header.referer" class="smpl">Referer</a>        = "Referer" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.referer" class="smpl">Referer-v</a> 
     1632      <div id="rfc.figure.u.21"></div><pre class="inline"><span id="rfc.iref.g.22"></span><span id="rfc.iref.g.23"></span>  <a href="#header.referer" class="smpl">Referer</a>        = "Referer" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.referer" class="smpl">Referer-v</a> 
    16261633  <a href="#header.referer" class="smpl">Referer-v</a>      = <a href="#abnf.dependencies" class="smpl">absolute-URI</a> / <a href="#abnf.dependencies" class="smpl">partial-URI</a> 
    16271634</pre><p id="rfc.section.9.6.p.5">Example:</p> 
    1628       <div id="rfc.figure.u.21"></div><pre class="text">  Referer: http://www.example.org/hypertext/Overview.html 
     1635      <div id="rfc.figure.u.22"></div><pre class="text">  Referer: http://www.example.org/hypertext/Overview.html 
    16291636</pre><p id="rfc.section.9.6.p.7">If the field value is a relative URI, it <em class="bcp14">SHOULD</em> be interpreted relative to the request-target. The URI <em class="bcp14">MUST NOT</em> include a fragment. See <a href="#encoding.sensitive.information.in.uris" title="Encoding Sensitive Information in URIs">Section&nbsp;11.2</a> for security considerations. 
    16301637      </p> 
     
    16371644      </p> 
    16381645      <p id="rfc.section.9.7.p.2">The value of this field can be either an HTTP-date or an integer number of seconds (in decimal) after the time of the response.</p> 
    1639       <div id="rfc.figure.u.22"></div><pre class="inline"><span id="rfc.iref.g.24"></span><span id="rfc.iref.g.25"></span>  <a href="#header.retry-after" class="smpl">Retry-After</a>   = "Retry-After" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.retry-after" class="smpl">Retry-After-v</a> 
     1646      <div id="rfc.figure.u.23"></div><pre class="inline"><span id="rfc.iref.g.24"></span><span id="rfc.iref.g.25"></span>  <a href="#header.retry-after" class="smpl">Retry-After</a>   = "Retry-After" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.retry-after" class="smpl">Retry-After-v</a> 
    16401647  <a href="#header.retry-after" class="smpl">Retry-After-v</a> = <a href="#abnf.dependencies" class="smpl">HTTP-date</a> / <a href="#rule.delta-seconds" class="smpl">delta-seconds</a> 
    16411648</pre><div id="rule.delta-seconds"> 
    16421649         <p id="rfc.section.9.7.p.4">  Time spans are non-negative decimal integers, representing time in seconds.</p> 
    16431650      </div> 
    1644       <div id="rfc.figure.u.23"></div><pre class="inline"><span id="rfc.iref.g.26"></span>  <a href="#rule.delta-seconds" class="smpl">delta-seconds</a>  = 1*<a href="#notation" class="smpl">DIGIT</a> 
     1651      <div id="rfc.figure.u.24"></div><pre class="inline"><span id="rfc.iref.g.26"></span>  <a href="#rule.delta-seconds" class="smpl">delta-seconds</a>  = 1*<a href="#notation" class="smpl">DIGIT</a> 
    16451652</pre><p id="rfc.section.9.7.p.6">Two examples of its use are</p> 
    1646       <div id="rfc.figure.u.24"></div><pre class="text">  Retry-After: Fri, 31 Dec 1999 23:59:59 GMT 
     1653      <div id="rfc.figure.u.25"></div><pre class="text">  Retry-After: Fri, 31 Dec 1999 23:59:59 GMT 
    16471654  Retry-After: 120 
    16481655</pre><p id="rfc.section.9.7.p.8">In the latter example, the delay is 2 minutes.</p> 
     
    16541661         identifying the application. 
    16551662      </p> 
    1656       <div id="rfc.figure.u.25"></div><pre class="inline"><span id="rfc.iref.g.27"></span><span id="rfc.iref.g.28"></span>  <a href="#header.server" class="smpl">Server</a>         = "Server" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.server" class="smpl">Server-v</a> 
     1663      <div id="rfc.figure.u.26"></div><pre class="inline"><span id="rfc.iref.g.27"></span><span id="rfc.iref.g.28"></span>  <a href="#header.server" class="smpl">Server</a>         = "Server" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.server" class="smpl">Server-v</a> 
    16571664  <a href="#header.server" class="smpl">Server-v</a>       = <a href="#abnf.dependencies" class="smpl">product</a> 
    16581665                   *( <a href="#core.rules" class="smpl">RWS</a> ( <a href="#abnf.dependencies" class="smpl">product</a> / <a href="#abnf.dependencies" class="smpl">comment</a> ) ) 
    16591666</pre><p id="rfc.section.9.8.p.4">Example:</p> 
    1660       <div id="rfc.figure.u.26"></div><pre class="text">  Server: CERN/3.0 libwww/2.17 
     1667      <div id="rfc.figure.u.27"></div><pre class="text">  Server: CERN/3.0 libwww/2.17 
    16611668</pre><p id="rfc.section.9.8.p.6">If the response is being forwarded through a proxy, the proxy application <em class="bcp14">MUST NOT</em> modify the Server response-header. Instead, it <em class="bcp14">MUST</em> include a Via field (as described in <a href="p1-messaging.html#header.via" title="Via">Section 9.9</a> of <a href="#Part1" id="rfc.xref.Part1.27"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). 
    16621669      </p> 
     
    16771684         are listed in order of their significance for identifying the application. 
    16781685      </p> 
    1679       <div id="rfc.figure.u.27"></div><pre class="inline"><span id="rfc.iref.g.29"></span><span id="rfc.iref.g.30"></span>  <a href="#header.user-agent" class="smpl">User-Agent</a>     = "User-Agent" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.user-agent" class="smpl">User-Agent-v</a> 
     1686      <div id="rfc.figure.u.28"></div><pre class="inline"><span id="rfc.iref.g.29"></span><span id="rfc.iref.g.30"></span>  <a href="#header.user-agent" class="smpl">User-Agent</a>     = "User-Agent" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.user-agent" class="smpl">User-Agent-v</a> 
    16801687  <a href="#header.user-agent" class="smpl">User-Agent-v</a>   = <a href="#abnf.dependencies" class="smpl">product</a> 
    16811688                   *( <a href="#core.rules" class="smpl">RWS</a> ( <a href="#abnf.dependencies" class="smpl">product</a> / <a href="#abnf.dependencies" class="smpl">comment</a> ) ) 
    16821689</pre><p id="rfc.section.9.9.p.4">Example:</p> 
    1683       <div id="rfc.figure.u.28"></div><pre class="text">  User-Agent: CERN-LineMode/2.15 libwww/2.17b3 
     1690      <div id="rfc.figure.u.29"></div><pre class="text">  User-Agent: CERN-LineMode/2.15 libwww/2.17b3 
    16841691</pre><h1 id="rfc.section.10"><a href="#rfc.section.10">10.</a>&nbsp;<a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1> 
    16851692      <h2 id="rfc.section.10.1"><a href="#rfc.section.10.1">10.1</a>&nbsp;<a id="method.registration" href="#method.registration">Method Registry</a></h2> 
     
    21222129      <h2 id="rfc.references.1"><a href="#rfc.section.13.1" id="rfc.section.13.1">13.1</a> Normative References 
    21232130      </h2> 
    2124       <table>                 
     2131      <table>                   
    21252132         <tr> 
    21262133            <td class="reference"><b id="Part1">[Part1]</b></td> 
     
    21562163            <td class="reference"><b id="RFC2119">[RFC2119]</b></td> 
    21572164            <td class="top"><a href="mailto:sob@harvard.edu" title="Harvard University">Bradner, S.</a>, “<a href="http://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>”, BCP&nbsp;14, RFC&nbsp;2119, March&nbsp;1997. 
     2165            </td> 
     2166         </tr> 
     2167         <tr> 
     2168            <td class="reference"><b id="RFC3986">[RFC3986]</b></td> 
     2169            <td class="top"><a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R.</a>, and <a href="mailto:LMM@acm.org" title="Adobe Systems Incorporated">L. Masinter</a>, “<a href="http://tools.ietf.org/html/rfc3986">Uniform Resource Identifier (URI): Generic Syntax</a>”, RFC&nbsp;3986, STD&nbsp;66, January&nbsp;2005. 
    21582170            </td> 
    21592171         </tr> 
     
    22662278         on the contents of the Allow header and remove requirement on clients to always trust the header value. (<a href="#header.allow" id="rfc.xref.header.allow.4" title="Allow">Section&nbsp;9.1</a>) 
    22672279      </p> 
    2268       <p id="rfc.section.A.2.p.6">Correct syntax of Location header to allow fragment, as referred symbol wasn't what was expected, and add some clarifications 
    2269          as to when it would not be appropriate. (<a href="#header.location" id="rfc.xref.header.location.4" title="Location">Section&nbsp;9.4</a>) 
     2280      <p id="rfc.section.A.2.p.6">Correct syntax of Location header to allow URI references (including relative references and fragments), as referred symbol 
     2281         "absoluteURI" wasn't what was expected, and add some clarifications as to when use of fragments would not be appropriate. 
     2282         (<a href="#header.location" id="rfc.xref.header.location.4" title="Location">Section&nbsp;9.4</a>) 
    22702283      </p> 
    22712284      <p id="rfc.section.A.2.p.7">Allow Referer value of "about:blank" as alternative to not specifying it. (<a href="#header.referer" id="rfc.xref.header.referer.3" title="Referer">Section&nbsp;9.6</a>) 
     
    22752288      </p> 
    22762289      <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1> 
    2277       <div id="rfc.figure.u.29"></div> <pre class="inline"><a href="#abnf.dependencies" class="smpl">Accept</a> = &lt;Accept, defined in [Part3], Section 5.1&gt; 
     2290      <div id="rfc.figure.u.30"></div> <pre class="inline"><a href="#abnf.dependencies" class="smpl">Accept</a> = &lt;Accept, defined in [Part3], Section 5.1&gt; 
    22782291<a href="#abnf.dependencies" class="smpl">Accept-Charset</a> = &lt;Accept-Charset, defined in [Part3], Section 5.2&gt; 
    22792292<a href="#abnf.dependencies" class="smpl">Accept-Encoding</a> = &lt;Accept-Encoding, defined in [Part3], Section 5.3&gt; 
     
    23042317 
    23052318<a href="#header.location" class="smpl">Location</a> = "Location:" OWS Location-v 
    2306 <a href="#header.location" class="smpl">Location-v</a> = URI 
     2319<a href="#header.location" class="smpl">Location-v</a> = URI-reference 
    23072320 
    23082321<a href="#header.max-forwards" class="smpl">Max-Forwards</a> = "Max-Forwards:" OWS Max-Forwards-v 
     
    23442357<a href="#abnf.dependencies" class="smpl">TE</a> = &lt;TE, defined in [Part1], Section 9.8&gt; 
    23452358 
    2346 <a href="#abnf.dependencies" class="smpl">URI</a> = &lt;URI, defined in [Part1], Section 2.6&gt; 
     2359<a href="#abnf.dependencies" class="smpl">URI-reference</a> = &lt;URI-reference, defined in [Part1], Section 2.6&gt; 
    23472360<a href="#header.user-agent" class="smpl">User-Agent</a> = "User-Agent:" OWS User-Agent-v 
    23482361<a href="#header.user-agent" class="smpl">User-Agent-v</a> = product *( RWS ( product / comment ) ) 
     
    23842397 
    23852398<a href="#core.rules" class="smpl">token</a> = &lt;token, defined in [Part1], Section 1.2.2&gt; 
    2386 </pre> <div id="rfc.figure.u.30"></div> 
     2399</pre> <div id="rfc.figure.u.31"></div> 
    23872400      <p>ABNF diagnostics:</p><pre class="inline">; Reason-Phrase defined but not used 
    23882401; Status-Code defined but not used 
     
    25472560      </ul> 
    25482561      <h2 id="rfc.section.C.11"><a href="#rfc.section.C.11">C.11</a>&nbsp;<a id="changes.since.09" href="#changes.since.09">Since draft-ietf-httpbis-p2-semantics-09</a></h2> 
    2549       <p id="rfc.section.C.11.p.1">None yet.</p> 
     2562      <p id="rfc.section.C.11.p.1">Closed issues: </p> 
     2563      <ul> 
     2564         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/43">http://tools.ietf.org/wg/httpbis/trac/ticket/43</a>&gt;: "Fragment combination / precedence during redirects" 
     2565         </li> 
     2566      </ul> 
     2567      <p id="rfc.section.C.11.p.2">Partly resolved issues: </p> 
     2568      <ul> 
     2569         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/185">http://tools.ietf.org/wg/httpbis/trac/ticket/185</a>&gt;: "Location header payload handling" 
     2570         </li> 
     2571      </ul> 
    25502572      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> 
    25512573      <p class="noprint"><a href="#rfc.index.1">1</a> <a href="#rfc.index.2">2</a> <a href="#rfc.index.3">3</a> <a href="#rfc.index.4">4</a> <a href="#rfc.index.5">5</a> <a href="#rfc.index.A">A</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.D">D</a> <a href="#rfc.index.E">E</a> <a href="#rfc.index.F">F</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.L">L</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.O">O</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> <a href="#rfc.index.T">T</a> <a href="#rfc.index.U">U</a>  
     
    28022824                  </li> 
    28032825                  <li class="indline1"><em>RFC3864</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3864.1">10.3</a>, <a class="iref" href="#RFC3864"><b>13.2</b></a></li> 
     2826                  <li class="indline1"><em>RFC3986</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3986.1">9.4</a>, <a class="iref" href="#rfc.xref.RFC3986.2">9.4</a>, <a class="iref" href="#RFC3986"><b>13.1</b></a><ul class="ind"> 
     2827                        <li class="indline1"><em>Section 4.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3986.1">9.4</a></li> 
     2828                        <li class="indline1"><em>Section 5</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3986.2">9.4</a></li> 
     2829                     </ul> 
     2830                  </li> 
    28042831                  <li class="indline1"><em>RFC5226</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5226.1">2.1</a>, <a class="iref" href="#rfc.xref.RFC5226.2">4.1</a>, <a class="iref" href="#RFC5226"><b>13.2</b></a><ul class="ind"> 
    28052832                        <li class="indline1"><em>Section 4.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5226.1">2.1</a>, <a class="iref" href="#rfc.xref.RFC5226.2">4.1</a></li> 
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r773 r785  
    362362  <x:anchor-alias value="Range"/> 
    363363  <x:anchor-alias value="TE"/> 
    364   <x:anchor-alias value="URI"/> 
     364  <x:anchor-alias value="URI-reference"/> 
    365365  <x:anchor-alias value="Vary"/> 
    366366  <x:anchor-alias value="WWW-Authenticate"/> 
     
    376376  <x:ref>product</x:ref>       = &lt;product, defined in &product-tokens;&gt; 
    377377  <x:ref>TE</x:ref>            = &lt;TE, defined in &header-te;&gt; 
    378   <x:ref>URI</x:ref>           = &lt;URI, defined in &uri;&gt; 
     378  <x:ref>URI-reference</x:ref> = &lt;URI-reference, defined in &uri;&gt; 
    379379</artwork></figure> 
    380380<figure><!--Part3--><artwork type="abnf2616"> 
     
    20422042</t> 
    20432043<t> 
    2044    The field value consists of a single URI. 
     2044   The field value consists of a single URI-reference. When it has the form 
     2045   of a relative reference (<xref target="RFC3986" x:fmt="," x:sec="4.2"/>), 
     2046   the final value is computed by resolving it against the effective request 
     2047   URI (<xref target="RFC3986" x:fmt="," x:sec="5"/>). 
    20452048</t> 
    20462049<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Location"/><iref primary="true" item="Grammar" subitem="Location-v"/> 
    20472050  <x:ref>Location</x:ref>       = "Location" ":" <x:ref>OWS</x:ref> <x:ref>Location-v</x:ref> 
    2048   <x:ref>Location-v</x:ref>     = <x:ref>URI</x:ref> 
     2051  <x:ref>Location-v</x:ref>     = <x:ref>URI-reference</x:ref> 
    20492052</artwork></figure> 
    2050 <t> 
    2051    An example is: 
    2052 </t> 
    2053 <figure><artwork type="example"> 
    2054   Location: http://www.example.org/pub/WWW/People.html 
     2053<figure> 
     2054<preamble>Examples are:</preamble><!--DO NOT DARE changing the vertical WSP below, it's necessary this way for xml2rfc--> 
     2055<artwork type="example"> 
     2056  Location: http://www.example.org/pub/WWW/People.html#tim 
     2057</artwork></figure><figure><artwork type="example">  Location: /index.html 
    20552058</artwork></figure> 
    20562059<t> 
    2057    There are circumstances in which a fragment identifier in a Location URI would not be appropriate: 
     2060   There are circumstances in which a fragment identifier in a Location URI 
     2061   would not be appropriate: 
    20582062   <list style="symbols"> 
    2059       <t>With a 201 Created response, because in this usage the Location header specifies the URI for the entire created resource.</t> 
     2063      <t>With a 201 Created response, because in this usage the Location header 
     2064      specifies the URI for the entire created resource.</t> 
    20602065      <t>With 305 Use Proxy.</t> 
    20612066   </list> 
    20622067</t> 
     2068<x:note> 
     2069  <t> 
     2070    <x:h>Note:</x:h> This specification does not define precedence rules 
     2071    for the case where the original URI, as navigated to be the user 
     2072    agent, and the Location header field value both contain fragment 
     2073    identifiers. 
     2074  </t> 
     2075</x:note> 
    20632076<x:note> 
    20642077  <t> 
     
    30023015</reference> 
    30033016 
     3017<reference anchor="RFC3986"> 
     3018 <front> 
     3019  <title abbrev='URI Generic Syntax'>Uniform Resource Identifier (URI): Generic Syntax</title> 
     3020  <author initials='T.' surname='Berners-Lee' fullname='Tim Berners-Lee'> 
     3021    <organization abbrev="W3C/MIT">World Wide Web Consortium</organization> 
     3022    <address> 
     3023       <email>timbl@w3.org</email> 
     3024       <uri>http://www.w3.org/People/Berners-Lee/</uri> 
     3025    </address> 
     3026  </author> 
     3027  <author initials='R.' surname='Fielding' fullname='Roy T. Fielding'> 
     3028    <organization abbrev="Day Software">Day Software</organization> 
     3029    <address> 
     3030      <email>fielding@gbiv.com</email> 
     3031      <uri>http://roy.gbiv.com/</uri> 
     3032    </address> 
     3033  </author> 
     3034  <author initials='L.' surname='Masinter' fullname='Larry Masinter'> 
     3035    <organization abbrev="Adobe Systems">Adobe Systems Incorporated</organization> 
     3036    <address> 
     3037      <email>LMM@acm.org</email> 
     3038      <uri>http://larry.masinter.net/</uri> 
     3039    </address> 
     3040  </author> 
     3041  <date month='January' year='2005'></date> 
     3042 </front> 
     3043 <seriesInfo name="RFC" value="3986"/> 
     3044 <seriesInfo name="STD" value="66"/> 
     3045</reference> 
     3046 
    30043047<reference anchor="RFC5234"> 
    30053048  <front> 
     
    32703313</t> 
    32713314<t> 
    3272   Correct syntax of Location header to allow fragment, 
    3273   as referred symbol wasn't what was expected, and add some 
    3274   clarifications as to when it would not be appropriate. 
     3315  Correct syntax of Location header to allow URI references (including 
     3316  relative references and fragments), as referred symbol "absoluteURI" wasn't 
     3317  what was expected, and add some clarifications as to when use of fragments  
     3318  would not be appropriate. 
    32753319  (<xref target="header.location"/>) 
    32763320</t> 
     
    33223366 
    33233367<x:ref>Location</x:ref> = "Location:" OWS Location-v 
    3324 <x:ref>Location-v</x:ref> = URI 
     3368<x:ref>Location-v</x:ref> = URI-reference 
    33253369 
    33263370<x:ref>Max-Forwards</x:ref> = "Max-Forwards:" OWS Max-Forwards-v 
     
    33623406<x:ref>TE</x:ref> = &lt;TE, defined in [Part1], Section 9.8&gt; 
    33633407 
    3364 <x:ref>URI</x:ref> = &lt;URI, defined in [Part1], Section 2.6&gt; 
     3408<x:ref>URI-reference</x:ref> = &lt;URI-reference, defined in [Part1], Section 2.6&gt; 
    33653409<x:ref>User-Agent</x:ref> = "User-Agent:" OWS User-Agent-v 
    33663410<x:ref>User-Agent-v</x:ref> = product *( RWS ( product / comment ) ) 
     
    37213765<section title="Since draft-ietf-httpbis-p2-semantics-09" anchor="changes.since.09"> 
    37223766<t> 
    3723   None yet. 
     3767  Closed issues: 
     3768  <list style="symbols">  
     3769    <t> 
     3770      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/43"/>: 
     3771      "Fragment combination / precedence during redirects" 
     3772    </t> 
     3773  </list> 
     3774</t> 
     3775<t> 
     3776  Partly resolved issues: 
     3777  <list style="symbols">  
     3778    <t> 
     3779      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/185"/>: 
     3780      "Location header payload handling" 
     3781    </t> 
     3782  </list> 
    37243783</t> 
    37253784</section> 
Note: See TracChangeset for help on using the changeset viewer.