Changeset 2181 for draft-ietf-httpbis/latest/p1-messaging.xml

Timestamp:

Feb 11, 2013, 6:10:03 AM (7 years ago)

Author:

julian.reschke@…

Message:

allow origin-form to use a path starting with "" (see #431)

File:

• draft-ietf-httpbis/latest/p1-messaging.xml (modified) (9 diffs)

draft-ietf-httpbis/latest/p1-messaging.xml

@@ -779 +779 @@
   <x:anchor-alias value="authority"/>
   <x:anchor-alias value="path-abempty"/>
-  <x:anchor-alias value="path-absolute"/>
   <x:anchor-alias value="port"/>
   <x:anchor-alias value="query"/>
+  <x:anchor-alias value="segment"/>
   <x:anchor-alias value="uri-host"/>
+  <x:anchor-alias value="absolute-path"/>
   <x:anchor-alias value="partial-URI"/>
 <t>
    This specification adopts the definitions of "URI-reference",
    "absolute-URI", "relative-part", "port", "host",
-   "path-abempty", "path-absolute", "query", and "authority" from the
+   "path-abempty", "query", "segment", and "authority" from the
    URI generic syntax.
-   In addition, we define a partial-URI rule for protocol elements
+   In addition, we define an "absolute-path" rule (that differs from 
+   RFC 3986's "path-absolute" in that it allows a leading "//")
+   and a "partial-URI" rule for protocol elements
    that allow a relative URI but not a fragment.
 </t>
-<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="URI-reference"><!--exported production--></iref><iref primary="true" item="Grammar" subitem="absolute-URI"/><iref primary="true" item="Grammar" subitem="authority"/><iref primary="true" item="Grammar" subitem="path-absolute"/><iref primary="true" item="Grammar" subitem="port"/><iref primary="true" item="Grammar" subitem="query"/><iref primary="true" item="Grammar" subitem="uri-host"/><iref primary="true" item="Grammar" subitem="partial-URI"><!--exported production--></iref>
+<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="URI-reference"><!--exported production--></iref><iref primary="true" item="Grammar" subitem="absolute-URI"/><iref primary="true" item="Grammar" subitem="authority"/><iref primary="true" item="Grammar" subitem="absolute-path"/><iref primary="true" item="Grammar" subitem="port"/><iref primary="true" item="Grammar" subitem="query"/><iref primary="true" item="Grammar" subitem="segment"/><iref primary="true" item="Grammar" subitem="uri-host"/><iref primary="true" item="Grammar" subitem="partial-URI"><!--exported production--></iref>
   <x:ref>URI-reference</x:ref> = &lt;URI-reference, defined in <xref target="RFC3986" x:fmt="," x:sec="4.1"/>&gt;
   <x:ref>absolute-URI</x:ref>  = &lt;absolute-URI, defined in <xref target="RFC3986" x:fmt="," x:sec="4.3"/>&gt;
@@ -798 +801 @@
   <x:ref>authority</x:ref>     = &lt;authority, defined in <xref target="RFC3986" x:fmt="," x:sec="3.2"/>&gt;
   <x:ref>path-abempty</x:ref>  = &lt;path-abempty, defined in <xref target="RFC3986" x:fmt="," x:sec="3.3"/>&gt;
-  <x:ref>path-absolute</x:ref> = &lt;path-absolute, defined in <xref target="RFC3986" x:fmt="," x:sec="3.3"/>&gt;
   <x:ref>port</x:ref>          = &lt;port, defined in <xref target="RFC3986" x:fmt="," x:sec="3.2.3"/>&gt;
   <x:ref>query</x:ref>         = &lt;query, defined in <xref target="RFC3986" x:fmt="," x:sec="3.4"/>&gt;
+  <x:ref>segment</x:ref>       = &lt;segment, defined in <xref target="RFC3986" x:fmt="," x:sec="3.3"/>&gt;
   <x:ref>uri-host</x:ref>      = &lt;host, defined in <xref target="RFC3986" x:fmt="," x:sec="3.2.2"/>&gt;
   
+  <x:ref>absolute-path</x:ref> = 1*( "/" segment )
   <x:ref>partial-URI</x:ref>   = relative-part [ "?" query ]
 </artwork></figure>
@@ -2230 +2234 @@
                  / <x:ref>asterisk-form</x:ref>
 
-  <x:ref>origin-form</x:ref>    = <x:ref>path-absolute</x:ref> [ "?" <x:ref>query</x:ref> ]
+  <x:ref>origin-form</x:ref>    = <x:ref>absolute-path</x:ref> [ "?" <x:ref>query</x:ref> ]
   <x:ref>absolute-form</x:ref>  = <x:ref>absolute-URI</x:ref>
   <x:ref>authority-form</x:ref> = <x:ref>authority</x:ref>
@@ -2647 +2651 @@
 </t>
 <t>
-   A proxy &MUST-NOT; modify the "path-absolute" and "query" parts of the
+   A proxy &MUST-NOT; modify the "absolute-path" and "query" parts of the
    received request-target when forwarding it to the next inbound server,
    except as noted above to replace an empty path with "/" or "*".
@@ -4857 +4861 @@
 </t>
 <t>
-  The path-absolute + query components of RFC3986 have been used to define the
+  The segment + query components of RFC3986 have been used to define the
   request-target, instead of abs_path from RFC 1808.
   (<xref target="request-target"/>)
@@ -5030 +5034 @@
 <x:ref>absolute-URI</x:ref> = &lt;absolute-URI, defined in [RFC3986], Section 4.3&gt;
 <x:ref>absolute-form</x:ref> = absolute-URI
+<x:ref>absolute-path</x:ref> = 1*( "/" segment )
 <x:ref>asterisk-form</x:ref> = "*"
 <x:ref>attribute</x:ref> = token
@@ -5064 +5069 @@
 <x:ref>obs-fold</x:ref> = CRLF ( SP / HTAB )
 <x:ref>obs-text</x:ref> = %x80-FF
-<x:ref>origin-form</x:ref> = path-absolute [ "?" query ]
+<x:ref>origin-form</x:ref> = absolute-path [ "?" query ]
 
 <x:ref>partial-URI</x:ref> = relative-part [ "?" query ]
 <x:ref>path-abempty</x:ref> = &lt;path-abempty, defined in [RFC3986], Section 3.3&gt;
-<x:ref>path-absolute</x:ref> = &lt;path-absolute, defined in [RFC3986], Section 3.3&gt;
 <x:ref>port</x:ref> = &lt;port, defined in [RFC3986], Section 3.2.3&gt;
 <x:ref>protocol</x:ref> = protocol-name [ "/" protocol-version ]
@@ -5096 +5100 @@
  asterisk-form
 
+<x:ref>segment</x:ref> = &lt;segment, defined in [RFC3986], Section 3.3&gt;
 <x:ref>special</x:ref> = "(" / ")" / "&lt;" / "&gt;" / "@" / "," / ";" / ":" / "\" /
  DQUOTE / "/" / "[" / "]" / "?" / "=" / "{" / "}"
@@ -5205 +5210 @@
       "Content-Length SHOULD be sent"
     </t>
+    <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/431"/>:
+      "origin-form does not allow path starting with "//""
+    </t>
   </list>
 </t>