Changeset 992 for draft-ietf-httpbis/latest/p1-messaging.html
- Timestamp:
- 06/09/10 15:49:57 (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r991 r992 1422 1422 </p> 1423 1423 <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> 1424 <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> 1424 <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 1425 request URI is constructed by concatenating 1426 </p> 1425 1427 <p id="rfc.section.4.3.p.4"> </p> 1426 1428 <ul> … … 1429 1431 </li> 1430 1432 <li>the character sequence "://",</li> 1431 <li>the authority component, as specified in the Host header field (<a href="#header.host" id="rfc.xref.header.host.1" title="Host">Section 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 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 4.2</a>? -- See <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/221">http://tools.ietf.org/wg/httpbis/trac/ticket/221</a>> --jre]</span>and1433 <li>the authority component, as specified in the Host header field (<a href="#header.host" id="rfc.xref.header.host.1" title="Host">Section 9.4</a>), and 1432 1434 </li> 1433 1435 <li>the request-target obtained from the Request-Line, unless the request-target is just the asterisk "*".</li> 1434 1436 </ul> 1435 <p id="rfc.section.4.3.p.5">Otherwise, when request-target uses the authority form, the effective request URI is undefined.</p> 1437 <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 1438 effective request URI is undefined. 1439 </p> 1440 <p id="rfc.section.4.3.p.6">Otherwise, when request-target uses the authority form, the effective request URI is undefined.</p> 1436 1441 <div id="rfc.figure.u.40"></div> 1437 1442 <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". 1447 1452 </p> 1448 <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 2.6.3</a>, except that empty path components <em class="bcp14">MUST NOT</em> be treated as equivalent to an absolute path of "/".1453 <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 2.6.3</a>, except that empty path components <em class="bcp14">MUST NOT</em> be treated as equivalent to an absolute path of "/". 1449 1454 </p> 1450 1455 <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a> <a id="response" href="#response">Response</a></h1> … … 3449 3454 </ul> 3450 3455 <h2 id="rfc.section.D.13"><a href="#rfc.section.D.13">D.13</a> <a id="changes.since.11" href="#changes.since.11">Since draft-ietf-httpbis-p1-messaging-11</a></h2> 3451 <p id="rfc.section.D.13.p.1">None yet.</p> 3456 <p id="rfc.section.D.13.p.1">Closed issues: </p> 3457 <ul> 3458 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/221">http://tools.ietf.org/wg/httpbis/trac/ticket/221</a>>: "effective request URI: handling of missing host in HTTP/1.0" 3459 </li> 3460 </ul> 3452 3461 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> 3453 3462 <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>
Note: See TracChangeset
for help on using the changeset viewer.