Changeset 823 for draft-ietf-httpbis/latest/p1-messaging.xml
- Timestamp:
- 26/05/10 17:25:13 (12 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.xml
r822 r823 1595 1595 exact resource is being requested. 1596 1596 </t> 1597 </section> 1598 1599 <section title="Effective Request URI" anchor="effective.request.uri"> 1600 <iref primary="true" item="Effective Request URI"/> 1601 <t> 1602 HTTP requests often do not carry the absolute URI (<xref target="RFC3986" x:fmt="," x:sec="4.3"/>) 1603 for the resource they are intended for; instead, the value needs to be inferred from the 1604 request-target, Host header and other context. The result of this process is 1605 the "Effective Request URI". 1606 </t> 1607 <t> 1608 If the request-target is an absolute-URI, then the Effective Request URI is 1609 the request-target. 1610 </t> 1611 <t> 1612 If the request-target uses the path-absolute (plus optional query) syntax 1613 or if it is just the asterisk "*", then the Effective Request URI is 1614 constructed by concatenating 1615 </t> 1616 <t> 1617 <list style="symbols"> 1618 <t> 1619 the scheme name: "http" if the request was received over an insecure 1620 TCP connection, or "https" when received over SSL/TLS-secured TCP 1621 connection, 1622 </t> 1623 <t> 1624 the character sequence "://", 1625 </t> 1626 <t> 1627 the authority component, as specified in the Host header 1628 (<xref target="header.host"/>) and determined by the rules in 1629 <xref target="the.resource.identified.by.a.request"/>, 1630 <cref anchor="effrequri-nohost" source="jre">Do we need to include the handling of missing hosts in HTTP/1.0 messages, as 1631 described in <xref target="the.resource.identified.by.a.request"/>?</cref> 1632 and 1633 </t> 1634 <t> 1635 the request-target obtained from the Request-Line, unless the 1636 request-target is just the asterisk "*". 1637 </t> 1638 </list> 1639 </t> 1640 <t> 1641 Otherwise, when request-target uses the authority form, the Effective 1642 Request URI is undefined. 1643 </t> 1644 <figure> 1645 <preamble> 1646 Example 1: the Effective Request URI for the message 1647 </preamble> 1648 <artwork type="example" x:indent-with=" "> 1649 GET /pub/WWW/TheProject.html HTTP/1.1 1650 Host: www.example.org:8080 1651 </artwork> 1652 <postamble> 1653 (received over an insecure TCP connection) is "http", plus "://", plus the 1654 authority component "www.example.org:8080", plus the request-target 1655 "/pub/WWW/TheProject.html", thus 1656 "http://www.example.org:8080/pub/WWW/TheProject.html". 1657 </postamble> 1658 </figure> 1659 <figure> 1660 <preamble> 1661 Example 2: the Effective Request URI for the message 1662 </preamble> 1663 <artwork type="example" x:indent-with=" "> 1664 GET * HTTP/1.1 1665 Host: www.example.org 1666 </artwork> 1667 <postamble> 1668 (received over an SSL/TLS secured TCP connection) is "https", plus "://", plus the 1669 authority component "www.example.org", thus "https://www.example.org". 1670 </postamble> 1671 </figure> 1672 <t> 1673 Effective Request URIs are compared using the rules described in 1674 <xref target="uri.comparison"/>, except that empty path components &MUST-NOT; 1675 be treated as equivalent to an absolute path of "/". 1676 </t> 1597 1677 </section> 1598 1678 … … 5556 5636 </list> 5557 5637 </t> 5638 <t> 5639 Partly resolved issues: 5640 <list style="symbols"> 5641 <t> 5642 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/196"/>: 5643 "Term for the requested resource's URI" 5644 </t> 5645 </list> 5646 </t> 5558 5647 </section> 5559 5648
Note: See TracChangeset
for help on using the changeset viewer.