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

Timestamp:

May 26, 2010, 10:25:13 AM (10 years ago)

Author:

julian.reschke@…

Message:

Introduce term "effective request URI" and use it throughout; may require some more fine-tuning (see #196)

File:

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

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

@@ -1595 +1595 @@
    exact resource is being requested.
 </t>
+</section>
+
+<section title="Effective Request URI" anchor="effective.request.uri">
+  <iref primary="true" item="Effective Request URI"/>
+<t>
+   HTTP requests often do not carry the absolute URI (<xref target="RFC3986" x:fmt="," x:sec="4.3"/>)
+   for the resource they are intended for; instead, the value needs to be inferred from the
+   request-target, Host header and other context. The result of this process is
+   the "Effective Request URI".
+</t>
+<t>
+   If the request-target is an absolute-URI, then the Effective Request URI is
+   the request-target.
+</t>
+<t>
+   If the request-target uses the path-absolute (plus optional query) syntax
+   or if it is just the asterisk "*", then the Effective Request URI is
+   constructed by concatenating
+</t>
+<t>
+  <list style="symbols">
+    <t>
+      the scheme name: "http" if the request was received over an insecure
+      TCP connection, or "https" when received over SSL/TLS-secured TCP
+      connection,
+    </t>
+    <t>
+      the character sequence "://",
+    </t>
+    <t>
+      the authority component, as specified in the Host header
+      (<xref target="header.host"/>) and determined by the rules in
+      <xref target="the.resource.identified.by.a.request"/>,
+      <cref anchor="effrequri-nohost" source="jre">Do we need to include the handling of missing hosts in HTTP/1.0 messages, as
+      described in <xref target="the.resource.identified.by.a.request"/>?</cref>
+      and
+    </t>
+    <t>
+      the request-target obtained from the Request-Line, unless the
+      request-target is just the asterisk "*".
+    </t>
+  </list>
+</t>
+<t>
+   Otherwise, when request-target uses the authority form, the Effective
+   Request URI is undefined.
+</t>
+<figure>
+<preamble>
+   Example 1: the Effective Request URI for the message
+</preamble> 
+<artwork type="example" x:indent-with="  ">
+GET /pub/WWW/TheProject.html HTTP/1.1
+Host: www.example.org:8080
+</artwork>
+<postamble>
+  (received over an insecure TCP connection) is "http", plus "://", plus the
+  authority component "www.example.org:8080", plus the request-target
+  "/pub/WWW/TheProject.html", thus
+  "http://www.example.org:8080/pub/WWW/TheProject.html".
+</postamble>
+</figure>
+<figure>
+<preamble>
+   Example 2: the Effective Request URI for the message
+</preamble> 
+<artwork type="example" x:indent-with="  ">
+GET * HTTP/1.1
+Host: www.example.org
+</artwork>
+<postamble>
+  (received over an SSL/TLS secured TCP connection) is "https", plus "://", plus the
+  authority component "www.example.org", thus "https://www.example.org".
+</postamble>
+</figure>
+<t>
+   Effective Request URIs are compared using the rules described in 
+   <xref target="uri.comparison"/>, except that empty path components &MUST-NOT;
+   be treated as equivalent to an absolute path of "/".
+</t>  
 </section>
 
@@ -5556 +5636 @@
   </list>
 </t>
+<t>
+  Partly resolved issues:
+  <list style="symbols"> 
+    <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/196"/>:
+      "Term for the requested resource's URI"
+    </t>
+  </list>
+</t>
 </section>