Changeset 2075 for draft-ietf-httpbis/latest/p2-semantics.html

Timestamp:

01/01/13 01:58:12 (9 years ago)

Author:

fielding@…

Message:

(editorial) tweak Location description so that it doesn't sound like fragment is literally appended to the field value

File:

• draft-ietf-httpbis/latest/p2-semantics.html (modified) (1 diff)

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

@@ -2918 +2918 @@
       </p>
       <div id="rfc.figure.u.51"></div><pre class="inline"><span id="rfc.iref.g.56"></span>  <a href="#header.location" class="smpl">Location</a> = <a href="#imported.abnf" class="smpl">URI-reference</a>
-</pre><p id="rfc.section.7.1.2.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.2"><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.3"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-5">Section 5</a>). If the original URI, as navigated to by the user agent, contains a fragment identifier, and the Location value does not,
-         then the original URI's fragment identifier is appended to the Location value.
+</pre><p id="rfc.section.7.1.2.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.2"><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.3"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-5">Section 5</a>).
       </p>
       <p id="rfc.section.7.1.2.p.4">For <a href="#status.201" class="smpl">201 (Created)</a> responses, the Location value refers to the primary resource created by the request. For <a href="#status.3xx" class="smpl">3xx (Redirection)</a> responses, the Location value refers to the preferred target resource for automatically redirecting the request.
       </p>
+      <p id="rfc.section.7.1.2.p.5">When Location is provided in a <a href="#status.3xx" class="smpl">3xx (Redirection)</a> response and the URI reference that the user agent used to generate the request target contains a fragment identifier, the
+         user agent <em class="bcp14">SHOULD</em> process the redirection as if the Location field value inherits the original fragment. In other words, if the Location does
+         not have a fragment component, the user agent <em class="bcp14">SHOULD</em> interpret the Location reference as if it had the original reference's fragment.
+      </p>
       <div id="rfc.figure.u.52"></div> 
-      <p>For example, a GET request for the URI reference "http://www.example.org/~tim" might result in a <a href="#status.303" class="smpl">303 (See Other)</a> response containing the header field:
-      </p>  <pre class="text">  Location: /pub/WWW/People.html#tim
-</pre>  <p>which suggests that the user agent redirect to "http://www.example.org/pub/WWW/People.html#tim"</p> 
+      <p>For example, a GET request generated for the URI reference "http://www.example.org/~tim" might result in a <a href="#status.303" class="smpl">303 (See Other)</a> response containing the header field:
+      </p>  <pre class="text">  Location: /People.html#tim
+</pre>  <p>which suggests that the user agent redirect to "http://www.example.org/People.html#tim"</p> 
       <div id="rfc.figure.u.53"></div> 
-      <p>Likewise, a GET request for the URI reference "http://www.example.org/index.html#larry" might result in a <a href="#status.301" class="smpl">301 (Moved Permanently)</a> response containing the header field:
+      <p>Likewise, a GET request generated for the URI reference "http://www.example.org/index.html#larry" might result in a <a href="#status.301" class="smpl">301 (Moved Permanently)</a> response containing the header field:
       </p>  <pre class="text">  Location: http://www.example.net/index.html
 </pre>  <p>which suggests that the user agent redirect to "http://www.example.net/index.html#larry", preserving the original fragment
          identifier.
       </p> 
-      <p id="rfc.section.7.1.2.p.7">There are circumstances in which a fragment identifier in a Location value would not be appropriate. For example, the Location
+      <p id="rfc.section.7.1.2.p.8">There are circumstances in which a fragment identifier in a Location value would not be appropriate. For example, the Location
          header field in a <a href="#status.201" class="smpl">201 (Created)</a> response is supposed to provide a URI that is specific to the created resource.
       </p>
-      <div class="note" id="rfc.section.7.1.2.p.8"> 
+      <div class="note" id="rfc.section.7.1.2.p.9"> 
          <p> <b>Note:</b> Some recipients attempt to recover from Location fields that are not valid URI references. This specification does not mandate
             or define such processing, but does allow it for the sake of robustness.
          </p> 
       </div>
-      <div class="note" id="rfc.section.7.1.2.p.9"> 
+      <div class="note" id="rfc.section.7.1.2.p.10"> 
          <p> <b>Note:</b> The <a href="#header.content-location" class="smpl">Content-Location</a> header field (<a href="#header.content-location" id="rfc.xref.header.content-location.3" title="Content-Location">Section&nbsp;3.1.4.2</a>) differs from Location in that the Content-Location refers to the most specific resource corresponding to the enclosed representation.
             It is therefore possible for a response to contain both the Location and Content-Location header fields.