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

Timestamp:

Mar 10, 2010, 2:28:36 AM (10 years ago)

Author:

julian.reschke@…

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)

File:

• draft-ietf-httpbis/latest/p2-semantics.xml (modified) (8 diffs)

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

@@ -362 +362 @@
   <x:anchor-alias value="Range"/>
   <x:anchor-alias value="TE"/>
-  <x:anchor-alias value="URI"/>
+  <x:anchor-alias value="URI-reference"/>
   <x:anchor-alias value="Vary"/>
   <x:anchor-alias value="WWW-Authenticate"/>
@@ -376 +376 @@
   <x:ref>product</x:ref>       = &lt;product, defined in &product-tokens;&gt;
   <x:ref>TE</x:ref>            = &lt;TE, defined in &header-te;&gt;
-  <x:ref>URI</x:ref>           = &lt;URI, defined in &uri;&gt;
+  <x:ref>URI-reference</x:ref> = &lt;URI-reference, defined in &uri;&gt;
 </artwork></figure>
 <figure><!--Part3--><artwork type="abnf2616">
@@ -2042 +2042 @@
 </t>
 <t>
-   The field value consists of a single URI.
+   The field value consists of a single URI-reference. When it has the form
+   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"/>).
 </t>
 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Location"/><iref primary="true" item="Grammar" subitem="Location-v"/>
   <x:ref>Location</x:ref>       = "Location" ":" <x:ref>OWS</x:ref> <x:ref>Location-v</x:ref>
-  <x:ref>Location-v</x:ref>     = <x:ref>URI</x:ref>
+  <x:ref>Location-v</x:ref>     = <x:ref>URI-reference</x:ref>
 </artwork></figure>
-<t>
-   An example is:
-</t>
-<figure><artwork type="example">
-  Location: http://www.example.org/pub/WWW/People.html
+<figure>
+<preamble>Examples are:</preamble><!--DO NOT DARE changing the vertical WSP below, it's necessary this way for xml2rfc-->
+<artwork type="example">
+  Location: http://www.example.org/pub/WWW/People.html#tim
+</artwork></figure><figure><artwork type="example">  Location: /index.html
 </artwork></figure>
 <t>
-   There are circumstances in which a fragment identifier in a Location URI would not be appropriate:
+   There are circumstances in which a fragment identifier in a Location URI
+   would not be appropriate:
    <list style="symbols">
-      <t>With a 201 Created response, because in this usage the Location header specifies the URI for the entire created resource.</t>
+      <t>With a 201 Created response, because in this usage the Location header
+      specifies the URI for the entire created resource.</t>
       <t>With 305 Use Proxy.</t>
    </list>
 </t>
+<x:note>
+  <t>
+    <x:h>Note:</x:h> This specification does not define precedence rules
+    for the case where the original URI, as navigated to be the user
+    agent, and the Location header field value both contain fragment
+    identifiers.
+  </t>
+</x:note>
 <x:note>
   <t>
@@ -3002 +3015 @@
 </reference>
 
+<reference anchor="RFC3986">
+ <front>
+  <title abbrev='URI Generic Syntax'>Uniform Resource Identifier (URI): Generic Syntax</title>
+  <author initials='T.' surname='Berners-Lee' fullname='Tim Berners-Lee'>
+    <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
+    <address>
+       <email>timbl@w3.org</email>
+       <uri>http://www.w3.org/People/Berners-Lee/</uri>
+    </address>
+  </author>
+  <author initials='R.' surname='Fielding' fullname='Roy T. Fielding'>
+    <organization abbrev="Day Software">Day Software</organization>
+    <address>
+      <email>fielding@gbiv.com</email>
+      <uri>http://roy.gbiv.com/</uri>
+    </address>
+  </author>
+  <author initials='L.' surname='Masinter' fullname='Larry Masinter'>
+    <organization abbrev="Adobe Systems">Adobe Systems Incorporated</organization>
+    <address>
+      <email>LMM@acm.org</email>
+      <uri>http://larry.masinter.net/</uri>
+    </address>
+  </author>
+  <date month='January' year='2005'></date>
+ </front>
+ <seriesInfo name="RFC" value="3986"/>
+ <seriesInfo name="STD" value="66"/>
+</reference>
+
 <reference anchor="RFC5234">
   <front>
@@ -3270 +3313 @@
 </t>
 <t>
-  Correct syntax of Location header to allow fragment,
-  as referred symbol wasn't what was expected, and add some
-  clarifications as to when it would not be appropriate.
+  Correct syntax of Location header to allow URI references (including
+  relative references and fragments), as referred symbol "absoluteURI" wasn't
+  what was expected, and add some clarifications as to when use of fragments 
+  would not be appropriate.
   (<xref target="header.location"/>)
 </t>
@@ -3322 +3366 @@
 
 <x:ref>Location</x:ref> = "Location:" OWS Location-v
-<x:ref>Location-v</x:ref> = URI
+<x:ref>Location-v</x:ref> = URI-reference
 
 <x:ref>Max-Forwards</x:ref> = "Max-Forwards:" OWS Max-Forwards-v
@@ -3362 +3406 @@
 <x:ref>TE</x:ref> = &lt;TE, defined in [Part1], Section 9.8&gt;
 
-<x:ref>URI</x:ref> = &lt;URI, defined in [Part1], Section 2.6&gt;
+<x:ref>URI-reference</x:ref> = &lt;URI-reference, defined in [Part1], Section 2.6&gt;
 <x:ref>User-Agent</x:ref> = "User-Agent:" OWS User-Agent-v
 <x:ref>User-Agent-v</x:ref> = product *( RWS ( product / comment ) )
@@ -3721 +3765 @@
 <section title="Since draft-ietf-httpbis-p2-semantics-09" anchor="changes.since.09">
 <t>
-  None yet.
+  Closed issues:
+  <list style="symbols"> 
+    <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/43"/>:
+      "Fragment combination / precedence during redirects"
+    </t>
+  </list>
+</t>
+<t>
+  Partly resolved issues:
+  <list style="symbols"> 
+    <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/185"/>:
+      "Location header payload handling"
+    </t>
+  </list>
 </t>
 </section>