Changeset 2075 for draft-ietf-httpbis/latest/p2-semantics.xml
- Timestamp:
- 01/01/13 01:58:12 (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.xml
r2074 r2075 3719 3719 of a relative reference (<xref target="RFC3986" x:fmt="," x:sec="4.2"/>), 3720 3720 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"/>). 3725 3722 </t> 3726 3723 <t> … … 3730 3727 to the preferred target resource for automatically redirecting the request. 3731 3728 </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> 3732 3738 <figure> 3733 <preamble>For example, a GET request for the URI reference3739 <preamble>For example, a GET request generated for the URI reference 3734 3740 "http://www.example.org/~tim" might result in a 3735 3741 <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--> 3736 3742 <artwork type="example"> 3737 Location: / pub/WWW/People.html#tim3743 Location: /People.html#tim 3738 3744 </artwork> 3739 3745 <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> 3741 3747 </figure> 3742 3748 <figure> 3743 <preamble>Likewise, a GET request for the URI reference3749 <preamble>Likewise, a GET request generated for the URI reference 3744 3750 "http://www.example.org/index.html#larry" might result in a 3745 3751 <x:ref>301 (Moved Permanently)</x:ref> response containing the header
Note: See TracChangeset
for help on using the changeset viewer.