Changeset 992 for draft-ietf-httpbis/latest/p1-messaging.html

Timestamp:

Sep 6, 2010, 8:49:57 AM (9 years ago)

Author:

julian.reschke@…

Message:

State that the effective request URI is undefined if you don't know the host (see #221)

File:

• draft-ietf-httpbis/latest/p1-messaging.html (modified) (4 diffs)

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

@@ -1422 +1422 @@
       </p>
       <p id="rfc.section.4.3.p.2">If the request-target is an absolute-URI, then the effective request URI is the request-target.</p>
-      <p id="rfc.section.4.3.p.3">If the request-target uses the path-absolute form or the asterisk form, then the effective request URI is constructed by concatenating</p>
+      <p id="rfc.section.4.3.p.3">If the request-target uses the path-absolute form or the asterisk form, and the Host header field is present, then the effective
+         request URI is constructed by concatenating
+      </p>
       <p id="rfc.section.4.3.p.4"> </p>
       <ul>
@@ -1429 +1431 @@
          </li>
          <li>the character sequence "://",</li>
-         <li>the authority component, as specified in the Host header field (<a href="#header.host" id="rfc.xref.header.host.1" title="Host">Section&nbsp;9.4</a>) and determined by the rules in <a href="#the.resource.identified.by.a.request" title="The Resource Identified by a Request">Section&nbsp;4.2</a>, <span class="comment" id="effrequri-nohost">[<a href="#effrequri-nohost" class="smpl">effrequri-nohost</a>: Do we need to include the handling of missing hosts in HTTP/1.0 messages, as described in <a href="#the.resource.identified.by.a.request" title="The Resource Identified by a Request">Section&nbsp;4.2</a>? -- See &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/221">http://tools.ietf.org/wg/httpbis/trac/ticket/221</a>&gt; --jre]</span> and
+         <li>the authority component, as specified in the Host header field (<a href="#header.host" id="rfc.xref.header.host.1" title="Host">Section&nbsp;9.4</a>), and
          </li>
          <li>the request-target obtained from the Request-Line, unless the request-target is just the asterisk "*".</li>
       </ul>
-      <p id="rfc.section.4.3.p.5">Otherwise, when request-target uses the authority form, the effective request URI is undefined.</p>
+      <p id="rfc.section.4.3.p.5">If the request-target uses the path-absolute form or the asterisk form, and the Host header field is not present, then the
+         effective request URI is undefined.
+      </p>
+      <p id="rfc.section.4.3.p.6">Otherwise, when request-target uses the authority form, the effective request URI is undefined.</p>
       <div id="rfc.figure.u.40"></div> 
       <p>Example 1: the effective request URI for the message</p>  <pre class="text">GET /pub/WWW/TheProject.html HTTP/1.1
@@ -1446 +1451 @@
          thus "https://www.example.org".
       </p> 
-      <p id="rfc.section.4.3.p.8">Effective request URIs are compared using the rules described in <a href="#uri.comparison" title="http and https URI Normalization and Comparison">Section&nbsp;2.6.3</a>, except that empty path components <em class="bcp14">MUST NOT</em> be treated as equivalent to an absolute path of "/".
+      <p id="rfc.section.4.3.p.9">Effective request URIs are compared using the rules described in <a href="#uri.comparison" title="http and https URI Normalization and Comparison">Section&nbsp;2.6.3</a>, except that empty path components <em class="bcp14">MUST NOT</em> be treated as equivalent to an absolute path of "/".
       </p>
       <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a id="response" href="#response">Response</a></h1>
@@ -3449 +3454 @@
       </ul>
       <h2 id="rfc.section.D.13"><a href="#rfc.section.D.13">D.13</a>&nbsp;<a id="changes.since.11" href="#changes.since.11">Since draft-ietf-httpbis-p1-messaging-11</a></h2>
-      <p id="rfc.section.D.13.p.1">None yet.</p>
+      <p id="rfc.section.D.13.p.1">Closed issues: </p>
+      <ul>
+         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/221">http://tools.ietf.org/wg/httpbis/trac/ticket/221</a>&gt;: "effective request URI: handling of missing host in HTTP/1.0"
+         </li>
+      </ul>
       <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
       <p class="noprint"><a href="#rfc.index.A">A</a> <a href="#rfc.index.B">B</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.D">D</a> <a href="#rfc.index.E">E</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.K">K</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.N">N</a> <a href="#rfc.index.O">O</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> <a href="#rfc.index.T">T</a> <a href="#rfc.index.U">U</a> <a href="#rfc.index.V">V</a>