Changeset 785 for draft-ietf-httpbis/latest/p2-semantics.html
- Timestamp:
- 10/03/10 10:28:36 (11 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r776 r785 403 403 <meta name="dct.creator" content="Reschke, J. F."> 404 404 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 405 <meta name="dct.issued" scheme="ISO8601" content="2010-03- 08">405 <meta name="dct.issued" scheme="ISO8601" content="2010-03-10"> 406 406 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 407 407 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 2 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages as expressed by request methods, request-header fields, response status codes, and response-header fields."> … … 434 434 </tr> 435 435 <tr> 436 <td class="left">Expires: September 9, 2010</td>436 <td class="left">Expires: September 11, 2010</td> 437 437 <td class="right">HP</td> 438 438 </tr> … … 487 487 <tr> 488 488 <td class="left"></td> 489 <td class="right">March 8, 2010</td>489 <td class="right">March 10, 2010</td> 490 490 </tr> 491 491 </tbody> … … 518 518 <p>The list of Internet-Draft Shadow Directories can be accessed at <a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>. 519 519 </p> 520 <p>This Internet-Draft will expire in September 9, 2010.</p>520 <p>This Internet-Draft will expire in September 11, 2010.</p> 521 521 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 522 522 <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 728 728 <a href="#abnf.dependencies" class="smpl">product</a> = <product, defined in <a href="#Part1" id="rfc.xref.Part1.14"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#product.tokens" title="Product Tokens">Section 6.3</a>> 729 729 <a href="#abnf.dependencies" class="smpl">TE</a> = <TE, defined in <a href="#Part1" id="rfc.xref.Part1.15"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 9.8</a>> 730 <a href="#abnf.dependencies" class="smpl">URI </a> = <URI, defined in <a href="#Part1" id="rfc.xref.Part1.16"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.6</a>>730 <a href="#abnf.dependencies" class="smpl">URI-reference</a> = <URI-reference, defined in <a href="#Part1" id="rfc.xref.Part1.16"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.6</a>> 731 731 </pre><div id="rfc.figure.u.3"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">Accept</a> = <Accept, defined in <a href="#Part3" id="rfc.xref.Part3.1"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept" title="Accept">Section 5.1</a>> 732 732 <a href="#abnf.dependencies" class="smpl">Accept-Charset</a> = … … 1579 1579 the location <em class="bcp14">SHOULD</em> indicate the server's preferred URI for automatic redirection to the resource. 1580 1580 </p> 1581 <p id="rfc.section.9.4.p.3">The field value consists of a single URI.</p> 1581 <p id="rfc.section.9.4.p.3">The field value consists of a single URI-reference. When it has the form of a relative reference (<a href="#RFC3986" id="rfc.xref.RFC3986.1"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-4.2">Section 4.2</a>), the final value is computed by resolving it against the effective request URI (<a href="#RFC3986" id="rfc.xref.RFC3986.2"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-5">Section 5</a>). 1582 </p> 1582 1583 <div id="rfc.figure.u.17"></div><pre class="inline"><span id="rfc.iref.g.18"></span><span id="rfc.iref.g.19"></span> <a href="#header.location" class="smpl">Location</a> = "Location" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.location" class="smpl">Location-v</a> 1583 <a href="#header.location" class="smpl">Location-v</a> = <a href="#abnf.dependencies" class="smpl">URI</a> 1584 </pre><p id="rfc.section.9.4.p.5">An example is:</p> 1585 <div id="rfc.figure.u.18"></div><pre class="text"> Location: http://www.example.org/pub/WWW/People.html 1584 <a href="#header.location" class="smpl">Location-v</a> = <a href="#abnf.dependencies" class="smpl">URI-reference</a> 1585 </pre><div id="rfc.figure.u.18"></div> 1586 <p>Examples are:</p> <pre class="text"> Location: http://www.example.org/pub/WWW/People.html#tim 1587 </pre><div id="rfc.figure.u.19"></div><pre class="text"> Location: /index.html 1586 1588 </pre><p id="rfc.section.9.4.p.7">There are circumstances in which a fragment identifier in a Location URI would not be appropriate: </p> 1587 1589 <ul> … … 1590 1592 </ul> 1591 1593 <div class="note" id="rfc.section.9.4.p.8"> 1594 <p> <b>Note:</b> This specification does not define precedence rules for the case where the original URI, as navigated to be the user agent, 1595 and the Location header field value both contain fragment identifiers. 1596 </p> 1597 </div> 1598 <div class="note" id="rfc.section.9.4.p.9"> 1592 1599 <p> <b>Note:</b> The Content-Location header field (<a href="p3-payload.html#header.content-location" title="Content-Location">Section 5.7</a> of <a href="#Part3" id="rfc.xref.Part3.11"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) differs from Location in that the Content-Location identifies the original location of the entity enclosed in the response. 1593 1600 It is therefore possible for a response to contain header fields for both Location and Content-Location. … … 1600 1607 is attempting to trace a request which appears to be failing or looping in mid-chain. 1601 1608 </p> 1602 <div id="rfc.figure.u. 19"></div><pre class="inline"><span id="rfc.iref.g.20"></span><span id="rfc.iref.g.21"></span> <a href="#header.max-forwards" class="smpl">Max-Forwards</a> = "Max-Forwards" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.max-forwards" class="smpl">Max-Forwards-v</a>1609 <div id="rfc.figure.u.20"></div><pre class="inline"><span id="rfc.iref.g.20"></span><span id="rfc.iref.g.21"></span> <a href="#header.max-forwards" class="smpl">Max-Forwards</a> = "Max-Forwards" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.max-forwards" class="smpl">Max-Forwards-v</a> 1603 1610 <a href="#header.max-forwards" class="smpl">Max-Forwards-v</a> = 1*<a href="#notation" class="smpl">DIGIT</a> 1604 1611 </pre><p id="rfc.section.9.5.p.3">The Max-Forwards value is a decimal integer indicating the remaining number of times this request message may be forwarded.</p> … … 1623 1630 apply to sources with non-HTTP URIs (e.g., FTP). 1624 1631 </p> 1625 <div id="rfc.figure.u.2 0"></div><pre class="inline"><span id="rfc.iref.g.22"></span><span id="rfc.iref.g.23"></span> <a href="#header.referer" class="smpl">Referer</a> = "Referer" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.referer" class="smpl">Referer-v</a>1632 <div id="rfc.figure.u.21"></div><pre class="inline"><span id="rfc.iref.g.22"></span><span id="rfc.iref.g.23"></span> <a href="#header.referer" class="smpl">Referer</a> = "Referer" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.referer" class="smpl">Referer-v</a> 1626 1633 <a href="#header.referer" class="smpl">Referer-v</a> = <a href="#abnf.dependencies" class="smpl">absolute-URI</a> / <a href="#abnf.dependencies" class="smpl">partial-URI</a> 1627 1634 </pre><p id="rfc.section.9.6.p.5">Example:</p> 1628 <div id="rfc.figure.u.2 1"></div><pre class="text"> Referer: http://www.example.org/hypertext/Overview.html1635 <div id="rfc.figure.u.22"></div><pre class="text"> Referer: http://www.example.org/hypertext/Overview.html 1629 1636 </pre><p id="rfc.section.9.6.p.7">If the field value is a relative URI, it <em class="bcp14">SHOULD</em> be interpreted relative to the request-target. The URI <em class="bcp14">MUST NOT</em> include a fragment. See <a href="#encoding.sensitive.information.in.uris" title="Encoding Sensitive Information in URIs">Section 11.2</a> for security considerations. 1630 1637 </p> … … 1637 1644 </p> 1638 1645 <p id="rfc.section.9.7.p.2">The value of this field can be either an HTTP-date or an integer number of seconds (in decimal) after the time of the response.</p> 1639 <div id="rfc.figure.u.2 2"></div><pre class="inline"><span id="rfc.iref.g.24"></span><span id="rfc.iref.g.25"></span> <a href="#header.retry-after" class="smpl">Retry-After</a> = "Retry-After" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.retry-after" class="smpl">Retry-After-v</a>1646 <div id="rfc.figure.u.23"></div><pre class="inline"><span id="rfc.iref.g.24"></span><span id="rfc.iref.g.25"></span> <a href="#header.retry-after" class="smpl">Retry-After</a> = "Retry-After" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.retry-after" class="smpl">Retry-After-v</a> 1640 1647 <a href="#header.retry-after" class="smpl">Retry-After-v</a> = <a href="#abnf.dependencies" class="smpl">HTTP-date</a> / <a href="#rule.delta-seconds" class="smpl">delta-seconds</a> 1641 1648 </pre><div id="rule.delta-seconds"> 1642 1649 <p id="rfc.section.9.7.p.4"> Time spans are non-negative decimal integers, representing time in seconds.</p> 1643 1650 </div> 1644 <div id="rfc.figure.u.2 3"></div><pre class="inline"><span id="rfc.iref.g.26"></span> <a href="#rule.delta-seconds" class="smpl">delta-seconds</a> = 1*<a href="#notation" class="smpl">DIGIT</a>1651 <div id="rfc.figure.u.24"></div><pre class="inline"><span id="rfc.iref.g.26"></span> <a href="#rule.delta-seconds" class="smpl">delta-seconds</a> = 1*<a href="#notation" class="smpl">DIGIT</a> 1645 1652 </pre><p id="rfc.section.9.7.p.6">Two examples of its use are</p> 1646 <div id="rfc.figure.u.2 4"></div><pre class="text"> Retry-After: Fri, 31 Dec 1999 23:59:59 GMT1653 <div id="rfc.figure.u.25"></div><pre class="text"> Retry-After: Fri, 31 Dec 1999 23:59:59 GMT 1647 1654 Retry-After: 120 1648 1655 </pre><p id="rfc.section.9.7.p.8">In the latter example, the delay is 2 minutes.</p> … … 1654 1661 identifying the application. 1655 1662 </p> 1656 <div id="rfc.figure.u.2 5"></div><pre class="inline"><span id="rfc.iref.g.27"></span><span id="rfc.iref.g.28"></span> <a href="#header.server" class="smpl">Server</a> = "Server" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.server" class="smpl">Server-v</a>1663 <div id="rfc.figure.u.26"></div><pre class="inline"><span id="rfc.iref.g.27"></span><span id="rfc.iref.g.28"></span> <a href="#header.server" class="smpl">Server</a> = "Server" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.server" class="smpl">Server-v</a> 1657 1664 <a href="#header.server" class="smpl">Server-v</a> = <a href="#abnf.dependencies" class="smpl">product</a> 1658 1665 *( <a href="#core.rules" class="smpl">RWS</a> ( <a href="#abnf.dependencies" class="smpl">product</a> / <a href="#abnf.dependencies" class="smpl">comment</a> ) ) 1659 1666 </pre><p id="rfc.section.9.8.p.4">Example:</p> 1660 <div id="rfc.figure.u.2 6"></div><pre class="text"> Server: CERN/3.0 libwww/2.171667 <div id="rfc.figure.u.27"></div><pre class="text"> Server: CERN/3.0 libwww/2.17 1661 1668 </pre><p id="rfc.section.9.8.p.6">If the response is being forwarded through a proxy, the proxy application <em class="bcp14">MUST NOT</em> modify the Server response-header. Instead, it <em class="bcp14">MUST</em> include a Via field (as described in <a href="p1-messaging.html#header.via" title="Via">Section 9.9</a> of <a href="#Part1" id="rfc.xref.Part1.27"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). 1662 1669 </p> … … 1677 1684 are listed in order of their significance for identifying the application. 1678 1685 </p> 1679 <div id="rfc.figure.u.2 7"></div><pre class="inline"><span id="rfc.iref.g.29"></span><span id="rfc.iref.g.30"></span> <a href="#header.user-agent" class="smpl">User-Agent</a> = "User-Agent" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.user-agent" class="smpl">User-Agent-v</a>1686 <div id="rfc.figure.u.28"></div><pre class="inline"><span id="rfc.iref.g.29"></span><span id="rfc.iref.g.30"></span> <a href="#header.user-agent" class="smpl">User-Agent</a> = "User-Agent" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.user-agent" class="smpl">User-Agent-v</a> 1680 1687 <a href="#header.user-agent" class="smpl">User-Agent-v</a> = <a href="#abnf.dependencies" class="smpl">product</a> 1681 1688 *( <a href="#core.rules" class="smpl">RWS</a> ( <a href="#abnf.dependencies" class="smpl">product</a> / <a href="#abnf.dependencies" class="smpl">comment</a> ) ) 1682 1689 </pre><p id="rfc.section.9.9.p.4">Example:</p> 1683 <div id="rfc.figure.u.2 8"></div><pre class="text"> User-Agent: CERN-LineMode/2.15 libwww/2.17b31690 <div id="rfc.figure.u.29"></div><pre class="text"> User-Agent: CERN-LineMode/2.15 libwww/2.17b3 1684 1691 </pre><h1 id="rfc.section.10"><a href="#rfc.section.10">10.</a> <a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1> 1685 1692 <h2 id="rfc.section.10.1"><a href="#rfc.section.10.1">10.1</a> <a id="method.registration" href="#method.registration">Method Registry</a></h2> … … 2122 2129 <h2 id="rfc.references.1"><a href="#rfc.section.13.1" id="rfc.section.13.1">13.1</a> Normative References 2123 2130 </h2> 2124 <table> 2131 <table> 2125 2132 <tr> 2126 2133 <td class="reference"><b id="Part1">[Part1]</b></td> … … 2156 2163 <td class="reference"><b id="RFC2119">[RFC2119]</b></td> 2157 2164 <td class="top"><a href="mailto:sob@harvard.edu" title="Harvard University">Bradner, S.</a>, “<a href="http://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>”, BCP 14, RFC 2119, March 1997. 2165 </td> 2166 </tr> 2167 <tr> 2168 <td class="reference"><b id="RFC3986">[RFC3986]</b></td> 2169 <td class="top"><a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R.</a>, and <a href="mailto:LMM@acm.org" title="Adobe Systems Incorporated">L. Masinter</a>, “<a href="http://tools.ietf.org/html/rfc3986">Uniform Resource Identifier (URI): Generic Syntax</a>”, RFC 3986, STD 66, January 2005. 2158 2170 </td> 2159 2171 </tr> … … 2266 2278 on the contents of the Allow header and remove requirement on clients to always trust the header value. (<a href="#header.allow" id="rfc.xref.header.allow.4" title="Allow">Section 9.1</a>) 2267 2279 </p> 2268 <p id="rfc.section.A.2.p.6">Correct syntax of Location header to allow fragment, as referred symbol wasn't what was expected, and add some clarifications 2269 as to when it would not be appropriate. (<a href="#header.location" id="rfc.xref.header.location.4" title="Location">Section 9.4</a>) 2280 <p id="rfc.section.A.2.p.6">Correct syntax of Location header to allow URI references (including relative references and fragments), as referred symbol 2281 "absoluteURI" wasn't what was expected, and add some clarifications as to when use of fragments would not be appropriate. 2282 (<a href="#header.location" id="rfc.xref.header.location.4" title="Location">Section 9.4</a>) 2270 2283 </p> 2271 2284 <p id="rfc.section.A.2.p.7">Allow Referer value of "about:blank" as alternative to not specifying it. (<a href="#header.referer" id="rfc.xref.header.referer.3" title="Referer">Section 9.6</a>) … … 2275 2288 </p> 2276 2289 <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a> <a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1> 2277 <div id="rfc.figure.u. 29"></div> <pre class="inline"><a href="#abnf.dependencies" class="smpl">Accept</a> = <Accept, defined in [Part3], Section 5.1>2290 <div id="rfc.figure.u.30"></div> <pre class="inline"><a href="#abnf.dependencies" class="smpl">Accept</a> = <Accept, defined in [Part3], Section 5.1> 2278 2291 <a href="#abnf.dependencies" class="smpl">Accept-Charset</a> = <Accept-Charset, defined in [Part3], Section 5.2> 2279 2292 <a href="#abnf.dependencies" class="smpl">Accept-Encoding</a> = <Accept-Encoding, defined in [Part3], Section 5.3> … … 2304 2317 2305 2318 <a href="#header.location" class="smpl">Location</a> = "Location:" OWS Location-v 2306 <a href="#header.location" class="smpl">Location-v</a> = URI 2319 <a href="#header.location" class="smpl">Location-v</a> = URI-reference 2307 2320 2308 2321 <a href="#header.max-forwards" class="smpl">Max-Forwards</a> = "Max-Forwards:" OWS Max-Forwards-v … … 2344 2357 <a href="#abnf.dependencies" class="smpl">TE</a> = <TE, defined in [Part1], Section 9.8> 2345 2358 2346 <a href="#abnf.dependencies" class="smpl">URI </a> = <URI, defined in [Part1], Section 2.6>2359 <a href="#abnf.dependencies" class="smpl">URI-reference</a> = <URI-reference, defined in [Part1], Section 2.6> 2347 2360 <a href="#header.user-agent" class="smpl">User-Agent</a> = "User-Agent:" OWS User-Agent-v 2348 2361 <a href="#header.user-agent" class="smpl">User-Agent-v</a> = product *( RWS ( product / comment ) ) … … 2384 2397 2385 2398 <a href="#core.rules" class="smpl">token</a> = <token, defined in [Part1], Section 1.2.2> 2386 </pre> <div id="rfc.figure.u.3 0"></div>2399 </pre> <div id="rfc.figure.u.31"></div> 2387 2400 <p>ABNF diagnostics:</p><pre class="inline">; Reason-Phrase defined but not used 2388 2401 ; Status-Code defined but not used … … 2547 2560 </ul> 2548 2561 <h2 id="rfc.section.C.11"><a href="#rfc.section.C.11">C.11</a> <a id="changes.since.09" href="#changes.since.09">Since draft-ietf-httpbis-p2-semantics-09</a></h2> 2549 <p id="rfc.section.C.11.p.1">None yet.</p> 2562 <p id="rfc.section.C.11.p.1">Closed issues: </p> 2563 <ul> 2564 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/43">http://tools.ietf.org/wg/httpbis/trac/ticket/43</a>>: "Fragment combination / precedence during redirects" 2565 </li> 2566 </ul> 2567 <p id="rfc.section.C.11.p.2">Partly resolved issues: </p> 2568 <ul> 2569 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/185">http://tools.ietf.org/wg/httpbis/trac/ticket/185</a>>: "Location header payload handling" 2570 </li> 2571 </ul> 2550 2572 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> 2551 2573 <p class="noprint"><a href="#rfc.index.1">1</a> <a href="#rfc.index.2">2</a> <a href="#rfc.index.3">3</a> <a href="#rfc.index.4">4</a> <a href="#rfc.index.5">5</a> <a href="#rfc.index.A">A</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.F">F</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.L">L</a> <a href="#rfc.index.M">M</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> … … 2802 2824 </li> 2803 2825 <li class="indline1"><em>RFC3864</em> <a class="iref" href="#rfc.xref.RFC3864.1">10.3</a>, <a class="iref" href="#RFC3864"><b>13.2</b></a></li> 2826 <li class="indline1"><em>RFC3986</em> <a class="iref" href="#rfc.xref.RFC3986.1">9.4</a>, <a class="iref" href="#rfc.xref.RFC3986.2">9.4</a>, <a class="iref" href="#RFC3986"><b>13.1</b></a><ul class="ind"> 2827 <li class="indline1"><em>Section 4.2</em> <a class="iref" href="#rfc.xref.RFC3986.1">9.4</a></li> 2828 <li class="indline1"><em>Section 5</em> <a class="iref" href="#rfc.xref.RFC3986.2">9.4</a></li> 2829 </ul> 2830 </li> 2804 2831 <li class="indline1"><em>RFC5226</em> <a class="iref" href="#rfc.xref.RFC5226.1">2.1</a>, <a class="iref" href="#rfc.xref.RFC5226.2">4.1</a>, <a class="iref" href="#RFC5226"><b>13.2</b></a><ul class="ind"> 2805 2832 <li class="indline1"><em>Section 4.1</em> <a class="iref" href="#rfc.xref.RFC5226.1">2.1</a>, <a class="iref" href="#rfc.xref.RFC5226.2">4.1</a></li>
Note: See TracChangeset
for help on using the changeset viewer.