Ignore:
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:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r2074 r2075  
    37193719   of a relative reference (<xref target="RFC3986" x:fmt="," x:sec="4.2"/>),
    37203720   the final value is computed by resolving it against the effective request
    3721    URI (<xref target="RFC3986" x:fmt="," x:sec="5"/>). If the original URI, as
    3722    navigated to by the user agent, contains a fragment identifier, and the
    3723    Location value does not, then the original URI's fragment identifier is
    3724    appended to the Location value.
     3721   URI (<xref target="RFC3986" x:fmt="," x:sec="5"/>).
    37253722</t>
    37263723<t>
     
    37303727   to the preferred target resource for automatically redirecting the request.
    37313728</t>
     3729<t>
     3730   When Location is provided in a <x:ref>3xx (Redirection)</x:ref> response
     3731   and the URI reference that the user agent used to generate the request
     3732   target contains a fragment identifier, the user agent &SHOULD; process the
     3733   redirection as if the Location field value inherits the original fragment.
     3734   In other words, if the Location does not have a fragment component, the
     3735   user agent &SHOULD; interpret the Location reference as if it had the
     3736   original reference's fragment.
     3737</t>
    37323738<figure>
    3733 <preamble>For example, a GET request for the URI reference
     3739<preamble>For example, a GET request generated for the URI reference
    37343740   "http://www.example.org/~tim" might result in a
    37353741   <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-->
    37363742<artwork type="example">
    3737   Location: /pub/WWW/People.html#tim
     3743  Location: /People.html#tim
    37383744</artwork>
    37393745<postamble>which suggests that the user agent redirect to
    3740    "http://www.example.org/pub/WWW/People.html#tim"</postamble>
     3746   "http://www.example.org/People.html#tim"</postamble>
    37413747</figure>
    37423748<figure>
    3743 <preamble>Likewise, a GET request for the URI reference
     3749<preamble>Likewise, a GET request generated for the URI reference
    37443750   "http://www.example.org/index.html#larry" might result in a
    37453751   <x:ref>301 (Moved Permanently)</x:ref> response containing the header
Note: See TracChangeset for help on using the changeset viewer.