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

Timestamp:

Dec 31, 2012, 5:58:12 PM (7 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.xml (modified) (2 diffs)

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

@@ -3719 +3719 @@
    of a relative reference (<xref target="RFC3986" x:fmt="," x:sec="4.2"/>),
    the final value is computed by resolving it against the effective request
-   URI (<xref target="RFC3986" x:fmt="," x:sec="5"/>). 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.
+   URI (<xref target="RFC3986" x:fmt="," x:sec="5"/>).
 </t>
 <t>
@@ -3730 +3727 @@
    to the preferred target resource for automatically redirecting the request.
 </t>
+<t>
+   When Location is provided in a <x:ref>3xx (Redirection)</x:ref> response
+   and the URI reference that the user agent used to generate the request
+   target contains a fragment identifier, the user agent &SHOULD; 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 &SHOULD; interpret the Location reference as if it had the
+   original reference's fragment.
+</t>
 <figure>
-<preamble>For example, a GET request for the URI reference
+<preamble>For example, a GET request generated for the URI reference
    "http://www.example.org/~tim" might result in a
    <x:ref>303 (See Other)</x:ref> response containing the header field:</preamble><!--DO NOT DARE changing the vertical spacing below, it's necessary this way for xml2rfc-->
 <artwork type="example">
-  Location: /pub/WWW/People.html#tim
+  Location: /People.html#tim
 </artwork>
 <postamble>which suggests that the user agent redirect to
-   "http://www.example.org/pub/WWW/People.html#tim"</postamble>
+   "http://www.example.org/People.html#tim"</postamble>
 </figure>
 <figure>
-<preamble>Likewise, a GET request for the URI reference
+<preamble>Likewise, a GET request generated for the URI reference
    "http://www.example.org/index.html#larry" might result in a
    <x:ref>301 (Moved Permanently)</x:ref> response containing the header