Changeset 1071 for draft-ietf-httpbis
- Timestamp:
- 30/10/10 17:00:59 (12 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 4 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r1069 r1071 404 404 <meta name="dct.creator" content="Reschke, J. F."> 405 405 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest"> 406 <meta name="dct.issued" scheme="ISO8601" content="2010-10- 28">406 <meta name="dct.issued" scheme="ISO8601" content="2010-10-30"> 407 407 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 408 408 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 1 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 1 provides an overview of HTTP and its associated terminology, defines the "http" and "https" Uniform Resource Identifier (URI) schemes, defines the generic message syntax and parsing requirements for HTTP message frames, and describes general security concerns for implementations."> … … 435 435 </tr> 436 436 <tr> 437 <td class="left">Expires: May 1, 2011</td>437 <td class="left">Expires: May 3, 2011</td> 438 438 <td class="right">HP</td> 439 439 </tr> … … 488 488 <tr> 489 489 <td class="left"></td> 490 <td class="right">October 28, 2010</td>490 <td class="right">October 30, 2010</td> 491 491 </tr> 492 492 </tbody> … … 516 516 in progress”. 517 517 </p> 518 <p>This Internet-Draft will expire on May 1, 2011.</p>518 <p>This Internet-Draft will expire on May 3, 2011.</p> 519 519 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 520 520 <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 2199 2199 <h2 id="rfc.section.9.8"><a href="#rfc.section.9.8">9.8</a> <a id="header.upgrade" href="#header.upgrade">Upgrade</a></h2> 2200 2200 <p id="rfc.section.9.8.p.1">The "Upgrade" general-header field allows the client to specify what additional communication protocols it would like to use, 2201 if the server chooses to switch protocols. Additionally, the server <em class="bcp14">MUST</em> use the Upgrade header field within a 101 (Switching Protocols) response to indicate which protocol(s) are being switched 2202 to. 2201 if the server chooses to switch protocols. Servers can use it to indicate what protocols they are willing to switch to. 2203 2202 </p> 2204 2203 <div id="rfc.figure.u.72"></div><pre class="inline"><span id="rfc.iref.g.112"></span><span id="rfc.iref.g.113"></span> <a href="#header.upgrade" class="smpl">Upgrade</a> = "Upgrade" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.upgrade" class="smpl">Upgrade-v</a> … … 2223 2222 is more appropriate to use a 3xx redirection response (<a href="p2-semantics.html#status.3xx" title="Redirection 3xx">Section 8.3</a> of <a href="#Part2" id="rfc.xref.Part2.12"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>). 2224 2223 </p> 2225 <p id="rfc.section.9.8.p.9">This specification only defines the protocol name "HTTP" for use by the family of Hypertext Transfer Protocols, as defined 2224 <p id="rfc.section.9.8.p.9">Servers <em class="bcp14">MUST</em> include the "Upgrade" header field in 101 (Switching Protocols) responses to indicate which protocol(s) are being switched 2225 to, and <em class="bcp14">MUST</em> include it in 426 (Upgrade Required) responses to indicate acceptable protocols to upgrade to. Servers <em class="bcp14">MAY</em> include it in any other response to indicate that they are willing to upgrade to one of the specified protocols. 2226 </p> 2227 <p id="rfc.section.9.8.p.10">This specification only defines the protocol name "HTTP" for use by the family of Hypertext Transfer Protocols, as defined 2226 2228 by the HTTP version rules of <a href="#http.version" title="HTTP Version">Section 2.5</a> and future updates to this specification. Additional tokens can be registered with IANA using the registration procedure defined 2227 2229 below. … … 2981 2983 <p id="rfc.section.B.3.p.10">Clarify exactly when close connection options must be sent. (<a href="#header.connection" id="rfc.xref.header.connection.9" title="Connection">Section 9.1</a>) 2982 2984 </p> 2985 <p id="rfc.section.B.3.p.11">Define the semantics of the "Upgrade" header field in responses other than 101 (this was incorporated from <a href="#RFC2817" id="rfc.xref.RFC2817.2"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>). (<a href="#header.upgrade" id="rfc.xref.header.upgrade.3" title="Upgrade">Section 9.8</a>) 2986 </p> 2983 2987 <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a> <a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1> 2984 2988 <div id="rfc.figure.u.78"></div> <pre class="inline"><a href="#rule.whitespace" class="smpl">BWS</a> = OWS … … 3476 3480 <ul> 3477 3481 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/233">http://tools.ietf.org/wg/httpbis/trac/ticket/233</a>>: "Is * usable as a request-uri for new methods?" 3482 </li> 3483 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/240">http://tools.ietf.org/wg/httpbis/trac/ticket/240</a>>: "Migrate Upgrade details from RFC2817" 3478 3484 </li> 3479 3485 </ul> … … 3664 3670 <li class="indline1">Trailer <a class="iref" href="#rfc.xref.header.trailer.1">3.4</a>, <a class="iref" href="#rfc.xref.header.trailer.2">6.2.1</a>, <a class="iref" href="#rfc.iref.h.12"><b>9.6</b></a>, <a class="iref" href="#rfc.xref.header.trailer.3">10.1</a></li> 3665 3671 <li class="indline1">Transfer-Encoding <a class="iref" href="#rfc.xref.header.transfer-encoding.1">3.3</a>, <a class="iref" href="#rfc.xref.header.transfer-encoding.2">3.3</a>, <a class="iref" href="#rfc.xref.header.transfer-encoding.3">3.4</a>, <a class="iref" href="#rfc.xref.header.transfer-encoding.4">6.2</a>, <a class="iref" href="#rfc.iref.h.13"><b>9.7</b></a>, <a class="iref" href="#rfc.xref.header.transfer-encoding.5">10.1</a></li> 3666 <li class="indline1">Upgrade <a class="iref" href="#rfc.xref.header.upgrade.1">3.4</a>, <a class="iref" href="#rfc.iref.h.14"><b>9.8</b></a>, <a class="iref" href="#rfc.xref.header.upgrade.2">10.1</a> </li>3672 <li class="indline1">Upgrade <a class="iref" href="#rfc.xref.header.upgrade.1">3.4</a>, <a class="iref" href="#rfc.iref.h.14"><b>9.8</b></a>, <a class="iref" href="#rfc.xref.header.upgrade.2">10.1</a>, <a class="iref" href="#rfc.xref.header.upgrade.3">B.3</a></li> 3667 3673 <li class="indline1">Via <a class="iref" href="#rfc.xref.header.via.1">3.4</a>, <a class="iref" href="#rfc.iref.h.15"><b>9.9</b></a>, <a class="iref" href="#rfc.xref.header.via.2">10.1</a></li> 3668 3674 </ul> … … 3764 3770 <li class="indline1"><em>RFC2145</em> <a class="iref" href="#rfc.xref.RFC2145.1">2.5</a>, <a class="iref" href="#rfc.xref.RFC2145.2">2.5</a>, <a class="iref" href="#RFC2145"><b>13.2</b></a></li> 3765 3771 <li class="indline1"><em>RFC2616</em> <a class="iref" href="#rfc.xref.RFC2616.1">1</a>, <a class="iref" href="#rfc.xref.RFC2616.2">12</a>, <a class="iref" href="#RFC2616"><b>13.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.3">D.1</a></li> 3766 <li class="indline1"><em>RFC2817</em> <a class="iref" href="#rfc.xref.RFC2817.1">10.5</a>, <a class="iref" href="#RFC2817"><b>13.2</b></a> <ul class="ind">3772 <li class="indline1"><em>RFC2817</em> <a class="iref" href="#rfc.xref.RFC2817.1">10.5</a>, <a class="iref" href="#RFC2817"><b>13.2</b></a>, <a class="iref" href="#rfc.xref.RFC2817.2">B.3</a><ul class="ind"> 3767 3773 <li class="indline1"><em>Section 7.2</em> <a class="iref" href="#rfc.xref.RFC2817.1">10.5</a></li> 3768 3774 </ul> … … 3820 3826 </li> 3821 3827 <li class="indline0"><a id="rfc.index.U" href="#rfc.index.U"><b>U</b></a><ul class="ind"> 3822 <li class="indline1">Upgrade header <a class="iref" href="#rfc.xref.header.upgrade.1">3.4</a>, <a class="iref" href="#rfc.iref.u.5"><b>9.8</b></a>, <a class="iref" href="#rfc.xref.header.upgrade.2">10.1</a> </li>3828 <li class="indline1">Upgrade header <a class="iref" href="#rfc.xref.header.upgrade.1">3.4</a>, <a class="iref" href="#rfc.iref.u.5"><b>9.8</b></a>, <a class="iref" href="#rfc.xref.header.upgrade.2">10.1</a>, <a class="iref" href="#rfc.xref.header.upgrade.3">B.3</a></li> 3823 3829 <li class="indline1">upstream <a class="iref" href="#rfc.iref.u.2"><b>2.2</b></a></li> 3824 3830 <li class="indline1">URI scheme -
draft-ietf-httpbis/latest/p1-messaging.xml
r1069 r1071 3247 3247 The "Upgrade" general-header field allows the client to specify what 3248 3248 additional communication protocols it would like to use, if the server 3249 chooses to switch protocols. Additionally, the server &MUST; use the Upgrade 3250 header field within a 101 (Switching Protocols) response to indicate which 3251 protocol(s) are being switched to. 3249 chooses to switch protocols. Servers can use it to indicate what protocols 3250 they are willing to switch to. 3252 3251 </t> 3253 3252 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Upgrade"/><iref primary="true" item="Grammar" subitem="Upgrade-v"/> … … 3294 3293 protocol on a different connection. For that purpose, it is more 3295 3294 appropriate to use a 3xx redirection response (&status-3xx;). 3295 </t> 3296 <t> 3297 Servers &MUST; include the "Upgrade" header field in 101 (Switching 3298 Protocols) responses to indicate which protocol(s) are being switched to, 3299 and &MUST; include it in 426 (Upgrade Required) responses to indicate 3300 acceptable protocols to upgrade to. Servers &MAY; include it in any other 3301 response to indicate that they are willing to upgrade to one of the 3302 specified protocols. 3296 3303 </t> 3297 3304 <t> … … 4893 4900 (<xref target="header.connection"/>) 4894 4901 </t> 4902 <t> 4903 Define the semantics of the "Upgrade" header field in responses other than 4904 101 (this was incorporated from <xref target="RFC2817"/>). 4905 (<xref target="header.upgrade"/>) 4906 </t> 4895 4907 </section> 4896 4908 </section> … … 5694 5706 "Is * usable as a request-uri for new methods?" 5695 5707 </t> 5708 <t> 5709 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/240"/>: 5710 "Migrate Upgrade details from RFC2817" 5711 </t> 5696 5712 </list> 5697 5713 </t> -
draft-ietf-httpbis/latest/p2-semantics.html
r1070 r1071 626 626 <li class="tocline1">8.4.17 <a href="#status.416">416 Requested Range Not Satisfiable</a></li> 627 627 <li class="tocline1">8.4.18 <a href="#status.417">417 Expectation Failed</a></li> 628 <li class="tocline1">8.4.19 <a href="#status.426">426 Upgrade Required</a></li> 628 629 </ul> 629 630 </li> … … 884 885 / "416" ; <a href="#Part5" id="rfc.xref.Part5.8"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, <a href="p5-range.html#status.416" title="416 Requested Range Not Satisfiable">Section 3.2</a>: Requested range not satisfiable 885 886 / "417" ; <a href="#status.417" id="rfc.xref.status.417.1" title="417 Expectation Failed">Section 8.4.18</a>: Expectation Failed 887 / "426" ; <a href="#status.426" id="rfc.xref.status.426.1" title="426 Upgrade Required">Section 8.4.19</a>: Upgrade Required 886 888 / "500" ; <a href="#status.500" id="rfc.xref.status.500.1" title="500 Internal Server Error">Section 8.5.1</a>: Internal Server Error 887 889 / "501" ; <a href="#status.501" id="rfc.xref.status.501.1" title="501 Not Implemented">Section 8.5.2</a>: Not Implemented … … 1540 1542 not be met by the next-hop server. 1541 1543 </p> 1544 <div id="rfc.iref.60"></div> 1545 <div id="rfc.iref.s.37"></div> 1546 <h3 id="rfc.section.8.4.19"><a href="#rfc.section.8.4.19">8.4.19</a> <a id="status.426" href="#status.426">426 Upgrade Required</a></h3> 1547 <p id="rfc.section.8.4.19.p.1">The request can not be completed without a prior protocol upgrade. This response <em class="bcp14">MUST</em> include an Upgrade header field (<a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 9.8</a> of <a href="#Part1" id="rfc.xref.Part1.30"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) specifying the required protocols. 1548 </p> 1549 <div id="rfc.figure.u.14"></div> 1550 <p>Example:</p> <pre class="text2">HTTP/1.1 426 Upgrade Required 1551 Upgrade: HTTP/2.0 1552 Connection: Upgrade 1553 1554 </pre><p id="rfc.section.8.4.19.p.3">The server <em class="bcp14">SHOULD</em> include a message body in the 426 response which indicates in human readable form the reason for the error and describes any 1555 alternative courses which may be available to the user. 1556 </p> 1542 1557 <h2 id="rfc.section.8.5"><a href="#rfc.section.8.5">8.5</a> <a id="status.5xx" href="#status.5xx">Server Error 5xx</a></h2> 1543 1558 <p id="rfc.section.8.5.p.1">Response status codes beginning with the digit "5" indicate cases in which the server is aware that it has erred or is incapable … … 1545 1560 User agents <em class="bcp14">SHOULD</em> display any included representation to the user. These response codes are applicable to any request method. 1546 1561 </p> 1547 <div id="rfc.iref.6 0"></div>1548 <div id="rfc.iref.s.3 7"></div>1562 <div id="rfc.iref.61"></div> 1563 <div id="rfc.iref.s.38"></div> 1549 1564 <h3 id="rfc.section.8.5.1"><a href="#rfc.section.8.5.1">8.5.1</a> <a id="status.500" href="#status.500">500 Internal Server Error</a></h3> 1550 1565 <p id="rfc.section.8.5.1.p.1">The server encountered an unexpected condition which prevented it from fulfilling the request.</p> 1551 <div id="rfc.iref.6 1"></div>1552 <div id="rfc.iref.s.3 8"></div>1566 <div id="rfc.iref.62"></div> 1567 <div id="rfc.iref.s.39"></div> 1553 1568 <h3 id="rfc.section.8.5.2"><a href="#rfc.section.8.5.2">8.5.2</a> <a id="status.501" href="#status.501">501 Not Implemented</a></h3> 1554 1569 <p id="rfc.section.8.5.2.p.1">The server does not support the functionality required to fulfill the request. This is the appropriate response when the server 1555 1570 does not recognize the request method and is not capable of supporting it for any resource. 1556 1571 </p> 1557 <div id="rfc.iref.6 2"></div>1558 <div id="rfc.iref.s. 39"></div>1572 <div id="rfc.iref.63"></div> 1573 <div id="rfc.iref.s.40"></div> 1559 1574 <h3 id="rfc.section.8.5.3"><a href="#rfc.section.8.5.3">8.5.3</a> <a id="status.502" href="#status.502">502 Bad Gateway</a></h3> 1560 1575 <p id="rfc.section.8.5.3.p.1">The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting 1561 1576 to fulfill the request. 1562 1577 </p> 1563 <div id="rfc.iref.6 3"></div>1564 <div id="rfc.iref.s.4 0"></div>1578 <div id="rfc.iref.64"></div> 1579 <div id="rfc.iref.s.41"></div> 1565 1580 <h3 id="rfc.section.8.5.4"><a href="#rfc.section.8.5.4">8.5.4</a> <a id="status.503" href="#status.503">503 Service Unavailable</a></h3> 1566 1581 <p id="rfc.section.8.5.4.p.1">The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication … … 1572 1587 </p> 1573 1588 </div> 1574 <div id="rfc.iref.6 4"></div>1575 <div id="rfc.iref.s.4 1"></div>1589 <div id="rfc.iref.65"></div> 1590 <div id="rfc.iref.s.42"></div> 1576 1591 <h3 id="rfc.section.8.5.5"><a href="#rfc.section.8.5.5">8.5.5</a> <a id="status.504" href="#status.504">504 Gateway Timeout</a></h3> 1577 1592 <p id="rfc.section.8.5.5.p.1">The server, while acting as a gateway or proxy, did not receive a timely response from the upstream server specified by the … … 1582 1597 </p> 1583 1598 </div> 1584 <div id="rfc.iref.6 5"></div>1585 <div id="rfc.iref.s.4 2"></div>1599 <div id="rfc.iref.66"></div> 1600 <div id="rfc.iref.s.43"></div> 1586 1601 <h3 id="rfc.section.8.5.6"><a href="#rfc.section.8.5.6">8.5.6</a> <a id="status.505" href="#status.505">505 HTTP Version Not Supported</a></h3> 1587 1602 <p id="rfc.section.8.5.6.p.1">The server does not support, or refuses to support, the protocol version that was used in the request message. The server 1588 1603 is indicating that it is unable or unwilling to complete the request using the same major version as the client, as described 1589 in <a href="p1-messaging.html#http.version" title="HTTP Version">Section 2.5</a> of <a href="#Part1" id="rfc.xref.Part1.3 0"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, other than with this error message. The response <em class="bcp14">SHOULD</em> contain a representation describing why that version is not supported and what other protocols are supported by that server.1604 in <a href="p1-messaging.html#http.version" title="HTTP Version">Section 2.5</a> of <a href="#Part1" id="rfc.xref.Part1.31"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, other than with this error message. The response <em class="bcp14">SHOULD</em> contain a representation describing why that version is not supported and what other protocols are supported by that server. 1590 1605 </p> 1591 1606 <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a> <a id="header.fields" href="#header.fields">Header Field Definitions</a></h1> … … 1597 1612 this field is strictly to inform the recipient of valid methods associated with the resource. 1598 1613 </p> 1599 <div id="rfc.figure.u.1 4"></div><pre class="inline"><span id="rfc.iref.g.9"></span><span id="rfc.iref.g.10"></span> <a href="#header.allow" class="smpl">Allow</a> = "Allow" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.allow" class="smpl">Allow-v</a>1614 <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.9"></span><span id="rfc.iref.g.10"></span> <a href="#header.allow" class="smpl">Allow</a> = "Allow" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.allow" class="smpl">Allow-v</a> 1600 1615 <a href="#header.allow" class="smpl">Allow-v</a> = #<a href="#method" class="smpl">Method</a> 1601 1616 </pre><p id="rfc.section.9.1.p.3">Example of use:</p> 1602 <div id="rfc.figure.u.1 5"></div><pre class="text"> Allow: GET, HEAD, PUT1617 <div id="rfc.figure.u.16"></div><pre class="text"> Allow: GET, HEAD, PUT 1603 1618 </pre><p id="rfc.section.9.1.p.5">The actual set of allowed methods is defined by the origin server at the time of each request.</p> 1604 1619 <p id="rfc.section.9.1.p.6">A proxy <em class="bcp14">MUST NOT</em> modify the Allow header field -- it does not need to understand all the methods specified in order to handle them according … … 1609 1624 <h2 id="rfc.section.9.2"><a href="#rfc.section.9.2">9.2</a> <a id="header.expect" href="#header.expect">Expect</a></h2> 1610 1625 <p id="rfc.section.9.2.p.1">The "Expect" request-header field is used to indicate that particular server behaviors are required by the client.</p> 1611 <div id="rfc.figure.u.1 6"></div><pre class="inline"><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></span> <a href="#header.expect" class="smpl">Expect</a> = "Expect" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.expect" class="smpl">Expect-v</a>1626 <div id="rfc.figure.u.17"></div><pre class="inline"><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></span> <a href="#header.expect" class="smpl">Expect</a> = "Expect" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.expect" class="smpl">Expect-v</a> 1612 1627 <a href="#header.expect" class="smpl">Expect-v</a> = 1#<a href="#header.expect" class="smpl">expectation</a> 1613 1628 … … 1629 1644 </p> 1630 1645 <p id="rfc.section.9.2.p.7">Many older HTTP/1.0 and HTTP/1.1 applications do not understand the Expect header field.</p> 1631 <p id="rfc.section.9.2.p.8">See <a href="p1-messaging.html#use.of.the.100.status" title="Use of the 100 (Continue) Status">Section 7.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.3 1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for the use of the 100 (Continue) status code.1646 <p id="rfc.section.9.2.p.8">See <a href="p1-messaging.html#use.of.the.100.status" title="Use of the 100 (Continue) Status">Section 7.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.32"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for the use of the 100 (Continue) status code. 1632 1647 </p> 1633 1648 <div id="rfc.iref.f.1"></div> … … 1636 1651 <p id="rfc.section.9.3.p.1">The "From" request-header field, if given, <em class="bcp14">SHOULD</em> contain an Internet e-mail address for the human user who controls the requesting user agent. The address <em class="bcp14">SHOULD</em> be machine-usable, as defined by "mailbox" in <a href="http://tools.ietf.org/html/rfc5322#section-3.4">Section 3.4</a> of <a href="#RFC5322" id="rfc.xref.RFC5322.1"><cite title="Internet Message Format">[RFC5322]</cite></a>: 1637 1652 </p> 1638 <div id="rfc.figure.u.1 7"></div><pre class="inline"><span id="rfc.iref.g.16"></span><span id="rfc.iref.g.17"></span> <a href="#header.from" class="smpl">From</a> = "From" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.from" class="smpl">From-v</a>1653 <div id="rfc.figure.u.18"></div><pre class="inline"><span id="rfc.iref.g.16"></span><span id="rfc.iref.g.17"></span> <a href="#header.from" class="smpl">From</a> = "From" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.from" class="smpl">From-v</a> 1639 1654 <a href="#header.from" class="smpl">From-v</a> = <a href="#header.from" class="smpl">mailbox</a> 1640 1655 1641 1656 <a href="#header.from" class="smpl">mailbox</a> = <mailbox, defined in <a href="#RFC5322" id="rfc.xref.RFC5322.2"><cite title="Internet Message Format">[RFC5322]</cite></a>, <a href="http://tools.ietf.org/html/rfc5322#section-3.4">Section 3.4</a>> 1642 1657 </pre><p id="rfc.section.9.3.p.3">An example is:</p> 1643 <div id="rfc.figure.u.1 8"></div><pre class="text"> From: webmaster@example.org1658 <div id="rfc.figure.u.19"></div><pre class="text"> From: webmaster@example.org 1644 1659 </pre><p id="rfc.section.9.3.p.5">This header field <em class="bcp14">MAY</em> be used for logging purposes and as a means for identifying the source of invalid or unwanted requests. It <em class="bcp14">SHOULD NOT</em> be used as an insecure form of access protection. The interpretation of this field is that the request is being performed 1645 1660 on behalf of the person given, who accepts responsibility for the method performed. In particular, robot agents <em class="bcp14">SHOULD</em> include this header field so that the person responsible for running the robot can be contacted if problems occur on the receiving … … 1664 1679 <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>). 1665 1680 </p> 1666 <div id="rfc.figure.u. 19"></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>1681 <div id="rfc.figure.u.20"></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> 1667 1682 <a href="#header.location" class="smpl">Location-v</a> = <a href="#abnf.dependencies" class="smpl">URI-reference</a> 1668 </pre><div id="rfc.figure.u.2 0"></div>1683 </pre><div id="rfc.figure.u.21"></div> 1669 1684 <p>Examples are:</p> <pre class="text"> Location: http://www.example.org/pub/WWW/People.html#tim 1670 </pre><div id="rfc.figure.u.2 1"></div><pre class="text"> Location: /index.html1685 </pre><div id="rfc.figure.u.22"></div><pre class="text"> Location: /index.html 1671 1686 </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> 1672 1687 <ul> … … 1690 1705 is attempting to trace a request which appears to be failing or looping in mid-chain. 1691 1706 </p> 1692 <div id="rfc.figure.u.2 2"></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>1707 <div id="rfc.figure.u.23"></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> 1693 1708 <a href="#header.max-forwards" class="smpl">Max-Forwards-v</a> = 1*<a href="#notation" class="smpl">DIGIT</a> 1694 1709 </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 can be forwarded.</p> … … 1711 1726 non-HTTP URIs (e.g., FTP). 1712 1727 </p> 1713 <div id="rfc.figure.u.2 3"></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>1728 <div id="rfc.figure.u.24"></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> 1714 1729 <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> 1715 1730 </pre><p id="rfc.section.9.6.p.5">Example:</p> 1716 <div id="rfc.figure.u.2 4"></div><pre class="text"> Referer: http://www.example.org/hypertext/Overview.html1731 <div id="rfc.figure.u.25"></div><pre class="text"> Referer: http://www.example.org/hypertext/Overview.html 1717 1732 </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 effective request URI. 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. 1718 1733 </p> … … 1725 1740 </p> 1726 1741 <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> 1727 <div id="rfc.figure.u.2 5"></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>1742 <div id="rfc.figure.u.26"></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> 1728 1743 <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> 1729 1744 </pre><div id="rule.delta-seconds"> 1730 1745 <p id="rfc.section.9.7.p.4"> Time spans are non-negative decimal integers, representing time in seconds.</p> 1731 1746 </div> 1732 <div id="rfc.figure.u.2 6"></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>1747 <div id="rfc.figure.u.27"></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> 1733 1748 </pre><p id="rfc.section.9.7.p.6">Two examples of its use are</p> 1734 <div id="rfc.figure.u.2 7"></div><pre class="text"> Retry-After: Fri, 31 Dec 1999 23:59:59 GMT1749 <div id="rfc.figure.u.28"></div><pre class="text"> Retry-After: Fri, 31 Dec 1999 23:59:59 GMT 1735 1750 Retry-After: 120 1736 1751 </pre><p id="rfc.section.9.7.p.8">In the latter example, the delay is 2 minutes.</p> 1737 <div id="rfc.iref.s.4 3"></div>1752 <div id="rfc.iref.s.44"></div> 1738 1753 <div id="rfc.iref.h.9"></div> 1739 1754 <h2 id="rfc.section.9.8"><a href="#rfc.section.9.8">9.8</a> <a id="header.server" href="#header.server">Server</a></h2> 1740 1755 <p id="rfc.section.9.8.p.1">The "Server" response-header field contains information about the software used by the origin server to handle the request.</p> 1741 <p id="rfc.section.9.8.p.2">The field can contain multiple product tokens (<a href="p1-messaging.html#product.tokens" title="Product Tokens">Section 6.3</a> of <a href="#Part1" id="rfc.xref.Part1.3 2"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) and comments (<a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.33"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) identifying the server and any significant subproducts. The product tokens are listed in order of their significance for1756 <p id="rfc.section.9.8.p.2">The field can contain multiple product tokens (<a href="p1-messaging.html#product.tokens" title="Product Tokens">Section 6.3</a> of <a href="#Part1" id="rfc.xref.Part1.33"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) and comments (<a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.34"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) identifying the server and any significant subproducts. The product tokens are listed in order of their significance for 1742 1757 identifying the application. 1743 1758 </p> 1744 <div id="rfc.figure.u.2 8"></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>1759 <div id="rfc.figure.u.29"></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> 1745 1760 <a href="#header.server" class="smpl">Server-v</a> = <a href="#abnf.dependencies" class="smpl">product</a> 1746 1761 *( <a href="#core.rules" class="smpl">RWS</a> ( <a href="#abnf.dependencies" class="smpl">product</a> / <a href="#abnf.dependencies" class="smpl">comment</a> ) ) 1747 1762 </pre><p id="rfc.section.9.8.p.4">Example:</p> 1748 <div id="rfc.figure.u. 29"></div><pre class="text"> Server: CERN/3.0 libwww/2.171749 </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 field. 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.3 4"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).1763 <div id="rfc.figure.u.30"></div><pre class="text"> Server: CERN/3.0 libwww/2.17 1764 </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 field. 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.35"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). 1750 1765 </p> 1751 1766 <div class="note" id="rfc.section.9.8.p.7"> … … 1763 1778 user agent limitations. 1764 1779 </p> 1765 <p id="rfc.section.9.9.p.3">The field can contain multiple product tokens (<a href="p1-messaging.html#product.tokens" title="Product Tokens">Section 6.3</a> of <a href="#Part1" id="rfc.xref.Part1.3 5"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) and comments (<a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.36"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) identifying the agent and its significant subproducts. By convention, the product tokens are listed in order of their significance1780 <p id="rfc.section.9.9.p.3">The field can contain multiple product tokens (<a href="p1-messaging.html#product.tokens" title="Product Tokens">Section 6.3</a> of <a href="#Part1" id="rfc.xref.Part1.36"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) and comments (<a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.37"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) identifying the agent and its significant subproducts. By convention, the product tokens are listed in order of their significance 1766 1781 for identifying the application. 1767 1782 </p> … … 1774 1789 doing so makes the field value more difficult to parse. 1775 1790 </p> 1776 <div id="rfc.figure.u.3 0"></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>1791 <div id="rfc.figure.u.31"></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> 1777 1792 <a href="#header.user-agent" class="smpl">User-Agent-v</a> = <a href="#abnf.dependencies" class="smpl">product</a> 1778 1793 *( <a href="#core.rules" class="smpl">RWS</a> ( <a href="#abnf.dependencies" class="smpl">product</a> / <a href="#abnf.dependencies" class="smpl">comment</a> ) ) 1779 1794 </pre><p id="rfc.section.9.9.p.7">Example:</p> 1780 <div id="rfc.figure.u.3 1"></div><pre class="text"> User-Agent: CERN-LineMode/2.15 libwww/2.17b31795 <div id="rfc.figure.u.32"></div><pre class="text"> User-Agent: CERN-LineMode/2.15 libwww/2.17b3 1781 1796 </pre><h1 id="rfc.section.10"><a href="#rfc.section.10">10.</a> <a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1> 1782 1797 <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> … … 2041 2056 <td class="left">Expectation Failed</td> 2042 2057 <td class="left"> <a href="#status.417" id="rfc.xref.status.417.2" title="417 Expectation Failed">Section 8.4.18</a> 2058 </td> 2059 </tr> 2060 <tr> 2061 <td class="left">426</td> 2062 <td class="left">Upgrade Required</td> 2063 <td class="left"> <a href="#status.426" id="rfc.xref.status.426.2" title="426 Upgrade Required">Section 8.4.19</a> 2043 2064 </td> 2044 2065 </tr> … … 2346 2367 was expected to repeat this single request via the proxy. (<a href="#status.305" id="rfc.xref.status.305.3" title="305 Use Proxy">Section 8.3.6</a>) 2347 2368 </p> 2348 <p id="rfc.section.A.p.6">Reclassify "Allow" as response header field, removing the option to specify it in a PUT request. Relax the server requirement 2369 <p id="rfc.section.A.p.6">Define status 426 (Upgrade Required) (this was incorporated from <a href="#RFC2817" id="rfc.xref.RFC2817.4"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>). (<a href="#status.426" id="rfc.xref.status.426.3" title="426 Upgrade Required">Section 8.4.19</a>) 2370 </p> 2371 <p id="rfc.section.A.p.7">Reclassify "Allow" as response header field, removing the option to specify it in a PUT request. Relax the server requirement 2349 2372 on the contents of the Allow header field and remove requirement on clients to always trust the header field value. (<a href="#header.allow" id="rfc.xref.header.allow.4" title="Allow">Section 9.1</a>) 2350 2373 </p> 2351 <p id="rfc.section.A.p. 7">Correct syntax of Location header field to allow URI references (including relative references and fragments), as referred2374 <p id="rfc.section.A.p.8">Correct syntax of Location header field to allow URI references (including relative references and fragments), as referred 2352 2375 symbol "absoluteURI" wasn't what was expected, and add some clarifications as to when use of fragments would not be appropriate. 2353 2376 (<a href="#header.location" id="rfc.xref.header.location.4" title="Location">Section 9.4</a>) 2354 2377 </p> 2355 <p id="rfc.section.A.p. 8">Restrict Max-Forwards header field to OPTIONS and TRACE (previously, extension methods could have used it as well). (<a href="#header.max-forwards" id="rfc.xref.header.max-forwards.5" title="Max-Forwards">Section 9.5</a>)2356 </p> 2357 <p id="rfc.section.A.p. 9">Allow Referer field 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>)2358 </p> 2359 <p id="rfc.section.A.p.1 0">In the description of the Server header field, the Via field was described as a SHOULD. The requirement was and is stated2360 correctly in the description of the Via header field in <a href="p1-messaging.html#header.via" title="Via">Section 9.9</a> of <a href="#Part1" id="rfc.xref.Part1.3 7"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. (<a href="#header.server" id="rfc.xref.header.server.4" title="Server">Section 9.8</a>)2378 <p id="rfc.section.A.p.9">Restrict Max-Forwards header field to OPTIONS and TRACE (previously, extension methods could have used it as well). (<a href="#header.max-forwards" id="rfc.xref.header.max-forwards.5" title="Max-Forwards">Section 9.5</a>) 2379 </p> 2380 <p id="rfc.section.A.p.10">Allow Referer field 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>) 2381 </p> 2382 <p id="rfc.section.A.p.11">In the description of the Server header field, the Via field was described as a SHOULD. The requirement was and is stated 2383 correctly in the description of the Via header field in <a href="p1-messaging.html#header.via" title="Via">Section 9.9</a> of <a href="#Part1" id="rfc.xref.Part1.38"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. (<a href="#header.server" id="rfc.xref.header.server.4" title="Server">Section 9.8</a>) 2361 2384 </p> 2362 2385 <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a> <a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1> 2363 <div id="rfc.figure.u.3 2"></div> <pre class="inline"><a href="#abnf.dependencies" class="smpl">Accept</a> = <Accept, defined in [Part3], Section 6.1>2386 <div id="rfc.figure.u.33"></div> <pre class="inline"><a href="#abnf.dependencies" class="smpl">Accept</a> = <Accept, defined in [Part3], Section 6.1> 2364 2387 <a href="#abnf.dependencies" class="smpl">Accept-Charset</a> = <Accept-Charset, defined in [Part3], Section 6.2> 2365 2388 <a href="#abnf.dependencies" class="smpl">Accept-Encoding</a> = <Accept-Encoding, defined in [Part3], Section 6.3> … … 2425 2448 "307" / "400" / "401" / "402" / "403" / "404" / "405" / "406" / 2426 2449 "407" / "408" / "409" / "410" / "411" / "412" / "413" / "414" / 2427 "415" / "416" / "417" / " 500" / "501" / "502" / "503" / "504" /2428 "50 5" / extension-code2450 "415" / "416" / "417" / "426" / "500" / "501" / "502" / "503" / 2451 "504" / "505" / extension-code 2429 2452 2430 2453 <a href="#abnf.dependencies" class="smpl">TE</a> = <TE, defined in [Part1], Section 9.5> … … 2470 2493 2471 2494 <a href="#core.rules" class="smpl">token</a> = <token, defined in [Part1], Section 1.2.2> 2472 </pre> <div id="rfc.figure.u.3 3"></div>2495 </pre> <div id="rfc.figure.u.34"></div> 2473 2496 <p>ABNF diagnostics:</p><pre class="inline">; Reason-Phrase defined but not used 2474 2497 ; Status-Code defined but not used … … 2681 2704 </li> 2682 2705 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/239">http://tools.ietf.org/wg/httpbis/trac/ticket/239</a>>: "Migrate CONNECT from RFC2817 to p2" 2706 </li> 2707 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/240">http://tools.ietf.org/wg/httpbis/trac/ticket/240</a>>: "Migrate Upgrade details from RFC2817" 2683 2708 </li> 2684 2709 </ul> … … 2733 2758 <li class="indline1">416 Requested Range Not Satisfiable (status code) <a class="iref" href="#rfc.iref.58"><b>8.4.17</b></a></li> 2734 2759 <li class="indline1">417 Expectation Failed (status code) <a class="iref" href="#rfc.xref.status.417.1">4</a>, <a class="iref" href="#rfc.iref.59"><b>8.4.18</b></a>, <a class="iref" href="#rfc.xref.status.417.2">10.2</a></li> 2760 <li class="indline1">426 Upgrade Required (status code) <a class="iref" href="#rfc.xref.status.426.1">4</a>, <a class="iref" href="#rfc.iref.60"><b>8.4.19</b></a>, <a class="iref" href="#rfc.xref.status.426.2">10.2</a>, <a class="iref" href="#rfc.xref.status.426.3">A</a></li> 2735 2761 </ul> 2736 2762 </li> 2737 2763 <li class="indline0"><a id="rfc.index.5" href="#rfc.index.5"><b>5</b></a><ul class="ind"> 2738 <li class="indline1">500 Internal Server Error (status code) <a class="iref" href="#rfc.xref.status.500.1">4</a>, <a class="iref" href="#rfc.iref.6 0"><b>8.5.1</b></a>, <a class="iref" href="#rfc.xref.status.500.2">10.2</a></li>2739 <li class="indline1">501 Not Implemented (status code) <a class="iref" href="#rfc.xref.status.501.1">4</a>, <a class="iref" href="#rfc.iref.6 1"><b>8.5.2</b></a>, <a class="iref" href="#rfc.xref.status.501.2">10.2</a></li>2740 <li class="indline1">502 Bad Gateway (status code) <a class="iref" href="#rfc.xref.status.502.1">4</a>, <a class="iref" href="#rfc.iref.6 2"><b>8.5.3</b></a>, <a class="iref" href="#rfc.xref.status.502.2">10.2</a></li>2741 <li class="indline1">503 Service Unavailable (status code) <a class="iref" href="#rfc.xref.status.503.1">4</a>, <a class="iref" href="#rfc.iref.6 3"><b>8.5.4</b></a>, <a class="iref" href="#rfc.xref.status.503.2">10.2</a></li>2742 <li class="indline1">504 Gateway Timeout (status code) <a class="iref" href="#rfc.xref.status.504.1">4</a>, <a class="iref" href="#rfc.iref.6 4"><b>8.5.5</b></a>, <a class="iref" href="#rfc.xref.status.504.2">10.2</a></li>2743 <li class="indline1">505 HTTP Version Not Supported (status code) <a class="iref" href="#rfc.xref.status.505.1">4</a>, <a class="iref" href="#rfc.iref.6 5"><b>8.5.6</b></a>, <a class="iref" href="#rfc.xref.status.505.2">10.2</a></li>2764 <li class="indline1">500 Internal Server Error (status code) <a class="iref" href="#rfc.xref.status.500.1">4</a>, <a class="iref" href="#rfc.iref.61"><b>8.5.1</b></a>, <a class="iref" href="#rfc.xref.status.500.2">10.2</a></li> 2765 <li class="indline1">501 Not Implemented (status code) <a class="iref" href="#rfc.xref.status.501.1">4</a>, <a class="iref" href="#rfc.iref.62"><b>8.5.2</b></a>, <a class="iref" href="#rfc.xref.status.501.2">10.2</a></li> 2766 <li class="indline1">502 Bad Gateway (status code) <a class="iref" href="#rfc.xref.status.502.1">4</a>, <a class="iref" href="#rfc.iref.63"><b>8.5.3</b></a>, <a class="iref" href="#rfc.xref.status.502.2">10.2</a></li> 2767 <li class="indline1">503 Service Unavailable (status code) <a class="iref" href="#rfc.xref.status.503.1">4</a>, <a class="iref" href="#rfc.iref.64"><b>8.5.4</b></a>, <a class="iref" href="#rfc.xref.status.503.2">10.2</a></li> 2768 <li class="indline1">504 Gateway Timeout (status code) <a class="iref" href="#rfc.xref.status.504.1">4</a>, <a class="iref" href="#rfc.iref.65"><b>8.5.5</b></a>, <a class="iref" href="#rfc.xref.status.504.2">10.2</a></li> 2769 <li class="indline1">505 HTTP Version Not Supported (status code) <a class="iref" href="#rfc.xref.status.505.1">4</a>, <a class="iref" href="#rfc.iref.66"><b>8.5.6</b></a>, <a class="iref" href="#rfc.xref.status.505.2">10.2</a></li> 2744 2770 </ul> 2745 2771 </li> … … 2847 2873 </li> 2848 2874 <li class="indline0"><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul class="ind"> 2849 <li class="indline1"><em>Part1</em> <a class="iref" href="#rfc.xref.Part1.1">1</a>, <a class="iref" href="#rfc.xref.Part1.2">1.2</a>, <a class="iref" href="#rfc.xref.Part1.3">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.4">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.5">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.6">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.7">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.8">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.9">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.10">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.11">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.12">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.13">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.14">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.15">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.16">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.17">2</a>, <a class="iref" href="#rfc.xref.Part1.18">2.1.1</a>, <a class="iref" href="#rfc.xref.Part1.19">3</a>, <a class="iref" href="#rfc.xref.Part1.20">3</a>, <a class="iref" href="#rfc.xref.Part1.21">5</a>, <a class="iref" href="#rfc.xref.Part1.22">6</a>, <a class="iref" href="#rfc.xref.Part1.23">6.1</a>, <a class="iref" href="#rfc.xref.Part1.24">7.8</a>, <a class="iref" href="#rfc.xref.Part1.25">7.8</a>, <a class="iref" href="#rfc.xref.Part1.26">7.9</a>, <a class="iref" href="#rfc.xref.Part1.27">8.1.1</a>, <a class="iref" href="#rfc.xref.Part1.28">8.1.2</a>, <a class="iref" href="#rfc.xref.Part1.29">8.2.6</a>, <a class="iref" href="#rfc.xref.Part1.30">8. 5.6</a>, <a class="iref" href="#rfc.xref.Part1.31">9.2</a>, <a class="iref" href="#rfc.xref.Part1.32">9.8</a>, <a class="iref" href="#rfc.xref.Part1.33">9.8</a>, <a class="iref" href="#rfc.xref.Part1.34">9.8</a>, <a class="iref" href="#rfc.xref.Part1.35">9.9</a>, <a class="iref" href="#rfc.xref.Part1.36">9.9</a>, <a class="iref" href="#Part1"><b>13.1</b></a>, <a class="iref" href="#rfc.xref.Part1.37">A</a><ul class="ind">2875 <li class="indline1"><em>Part1</em> <a class="iref" href="#rfc.xref.Part1.1">1</a>, <a class="iref" href="#rfc.xref.Part1.2">1.2</a>, <a class="iref" href="#rfc.xref.Part1.3">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.4">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.5">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.6">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.7">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.8">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.9">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.10">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.11">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.12">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.13">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.14">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.15">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.16">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.17">2</a>, <a class="iref" href="#rfc.xref.Part1.18">2.1.1</a>, <a class="iref" href="#rfc.xref.Part1.19">3</a>, <a class="iref" href="#rfc.xref.Part1.20">3</a>, <a class="iref" href="#rfc.xref.Part1.21">5</a>, <a class="iref" href="#rfc.xref.Part1.22">6</a>, <a class="iref" href="#rfc.xref.Part1.23">6.1</a>, <a class="iref" href="#rfc.xref.Part1.24">7.8</a>, <a class="iref" href="#rfc.xref.Part1.25">7.8</a>, <a class="iref" href="#rfc.xref.Part1.26">7.9</a>, <a class="iref" href="#rfc.xref.Part1.27">8.1.1</a>, <a class="iref" href="#rfc.xref.Part1.28">8.1.2</a>, <a class="iref" href="#rfc.xref.Part1.29">8.2.6</a>, <a class="iref" href="#rfc.xref.Part1.30">8.4.19</a>, <a class="iref" href="#rfc.xref.Part1.31">8.5.6</a>, <a class="iref" href="#rfc.xref.Part1.32">9.2</a>, <a class="iref" href="#rfc.xref.Part1.33">9.8</a>, <a class="iref" href="#rfc.xref.Part1.34">9.8</a>, <a class="iref" href="#rfc.xref.Part1.35">9.8</a>, <a class="iref" href="#rfc.xref.Part1.36">9.9</a>, <a class="iref" href="#rfc.xref.Part1.37">9.9</a>, <a class="iref" href="#Part1"><b>13.1</b></a>, <a class="iref" href="#rfc.xref.Part1.38">A</a><ul class="ind"> 2850 2876 <li class="indline1"><em>Section 1.2</em> <a class="iref" href="#rfc.xref.Part1.2">1.2</a></li> 2851 2877 <li class="indline1"><em>Section 1.2.2</em> <a class="iref" href="#rfc.xref.Part1.3">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.4">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.5">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.6">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.7">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.8">1.2.1</a></li> 2852 <li class="indline1"><em>Section 2.5</em> <a class="iref" href="#rfc.xref.Part1.3 0">8.5.6</a></li>2878 <li class="indline1"><em>Section 2.5</em> <a class="iref" href="#rfc.xref.Part1.31">8.5.6</a></li> 2853 2879 <li class="indline1"><em>Section 2.6</em> <a class="iref" href="#rfc.xref.Part1.9">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.11">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.13">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.16">1.2.2</a></li> 2854 <li class="indline1"><em>Section 3.2</em> <a class="iref" href="#rfc.xref.Part1.10">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.3 3">9.8</a>, <a class="iref" href="#rfc.xref.Part1.36">9.9</a></li>2880 <li class="indline1"><em>Section 3.2</em> <a class="iref" href="#rfc.xref.Part1.10">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.34">9.8</a>, <a class="iref" href="#rfc.xref.Part1.37">9.9</a></li> 2855 2881 <li class="indline1"><em>Section 3.3</em> <a class="iref" href="#rfc.xref.Part1.18">2.1.1</a>, <a class="iref" href="#rfc.xref.Part1.22">6</a>, <a class="iref" href="#rfc.xref.Part1.29">8.2.6</a></li> 2856 2882 <li class="indline1"><em>Section 4.1.2</em> <a class="iref" href="#rfc.xref.Part1.26">7.9</a></li> 2857 2883 <li class="indline1"><em>Section 4.3</em> <a class="iref" href="#rfc.xref.Part1.17">2</a>, <a class="iref" href="#rfc.xref.Part1.21">5</a>, <a class="iref" href="#rfc.xref.Part1.23">6.1</a></li> 2858 2884 <li class="indline1"><em>Section 6.1</em> <a class="iref" href="#rfc.xref.Part1.12">1.2.2</a></li> 2859 <li class="indline1"><em>Section 6.3</em> <a class="iref" href="#rfc.xref.Part1.14">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.3 2">9.8</a>, <a class="iref" href="#rfc.xref.Part1.35">9.9</a></li>2860 <li class="indline1"><em>Section 7.2.3</em> <a class="iref" href="#rfc.xref.Part1.27">8.1.1</a>, <a class="iref" href="#rfc.xref.Part1.3 1">9.2</a></li>2885 <li class="indline1"><em>Section 6.3</em> <a class="iref" href="#rfc.xref.Part1.14">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.33">9.8</a>, <a class="iref" href="#rfc.xref.Part1.36">9.9</a></li> 2886 <li class="indline1"><em>Section 7.2.3</em> <a class="iref" href="#rfc.xref.Part1.27">8.1.1</a>, <a class="iref" href="#rfc.xref.Part1.32">9.2</a></li> 2861 2887 <li class="indline1"><em>Section 9.4</em> <a class="iref" href="#rfc.xref.Part1.19">3</a></li> 2862 2888 <li class="indline1"><em>Section 9.5</em> <a class="iref" href="#rfc.xref.Part1.15">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.20">3</a></li> 2863 <li class="indline1"><em>Section 9.8</em> <a class="iref" href="#rfc.xref.Part1.28">8.1.2</a> </li>2864 <li class="indline1"><em>Section 9.9</em> <a class="iref" href="#rfc.xref.Part1.24">7.8</a>, <a class="iref" href="#rfc.xref.Part1.3 4">9.8</a>, <a class="iref" href="#rfc.xref.Part1.37">A</a></li>2889 <li class="indline1"><em>Section 9.8</em> <a class="iref" href="#rfc.xref.Part1.28">8.1.2</a>, <a class="iref" href="#rfc.xref.Part1.30">8.4.19</a></li> 2890 <li class="indline1"><em>Section 9.9</em> <a class="iref" href="#rfc.xref.Part1.24">7.8</a>, <a class="iref" href="#rfc.xref.Part1.35">9.8</a>, <a class="iref" href="#rfc.xref.Part1.38">A</a></li> 2865 2891 <li class="indline1"><em>Section 10.3.1</em> <a class="iref" href="#rfc.xref.Part1.25">7.8</a></li> 2866 2892 </ul> … … 2934 2960 </ul> 2935 2961 </li> 2936 <li class="indline1"><em>RFC2817</em> <a class="iref" href="#rfc.xref.RFC2817.1">10.2</a>, <a class="iref" href="#RFC2817"><b>13.2</b></a>, <a class="iref" href="#rfc.xref.RFC2817.2">A</a>, <a class="iref" href="#rfc.xref.RFC2817.3">A</a> <ul class="ind">2962 <li class="indline1"><em>RFC2817</em> <a class="iref" href="#rfc.xref.RFC2817.1">10.2</a>, <a class="iref" href="#RFC2817"><b>13.2</b></a>, <a class="iref" href="#rfc.xref.RFC2817.2">A</a>, <a class="iref" href="#rfc.xref.RFC2817.3">A</a>, <a class="iref" href="#rfc.xref.RFC2817.4">A</a><ul class="ind"> 2937 2963 <li class="indline1"><em>Section 7.1</em> <a class="iref" href="#rfc.xref.RFC2817.1">10.2</a>, <a class="iref" href="#rfc.xref.RFC2817.2">A</a></li> 2938 2964 </ul> … … 2960 2986 <li class="indline0"><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul class="ind"> 2961 2987 <li class="indline1">Safe Methods <a class="iref" href="#rfc.iref.s.1"><b>7.1.1</b></a></li> 2962 <li class="indline1">Server header <a class="iref" href="#rfc.xref.header.server.1">5</a>, <a class="iref" href="#rfc.iref.s.4 3"><b>9.8</b></a>, <a class="iref" href="#rfc.xref.header.server.2">10.3</a>, <a class="iref" href="#rfc.xref.header.server.3">11.1</a>, <a class="iref" href="#rfc.xref.header.server.4">A</a></li>2988 <li class="indline1">Server header <a class="iref" href="#rfc.xref.header.server.1">5</a>, <a class="iref" href="#rfc.iref.s.44"><b>9.8</b></a>, <a class="iref" href="#rfc.xref.header.server.2">10.3</a>, <a class="iref" href="#rfc.xref.header.server.3">11.1</a>, <a class="iref" href="#rfc.xref.header.server.4">A</a></li> 2963 2989 <li class="indline1">Status Codes 2964 2990 <ul class="ind"> … … 2998 3024 <li class="indline1">416 Requested Range Not Satisfiable <a class="iref" href="#rfc.iref.s.35"><b>8.4.17</b></a></li> 2999 3025 <li class="indline1">417 Expectation Failed <a class="iref" href="#rfc.xref.status.417.1">4</a>, <a class="iref" href="#rfc.iref.s.36"><b>8.4.18</b></a>, <a class="iref" href="#rfc.xref.status.417.2">10.2</a></li> 3000 <li class="indline1">500 Internal Server Error <a class="iref" href="#rfc.xref.status.500.1">4</a>, <a class="iref" href="#rfc.iref.s.37"><b>8.5.1</b></a>, <a class="iref" href="#rfc.xref.status.500.2">10.2</a></li> 3001 <li class="indline1">501 Not Implemented <a class="iref" href="#rfc.xref.status.501.1">4</a>, <a class="iref" href="#rfc.iref.s.38"><b>8.5.2</b></a>, <a class="iref" href="#rfc.xref.status.501.2">10.2</a></li> 3002 <li class="indline1">502 Bad Gateway <a class="iref" href="#rfc.xref.status.502.1">4</a>, <a class="iref" href="#rfc.iref.s.39"><b>8.5.3</b></a>, <a class="iref" href="#rfc.xref.status.502.2">10.2</a></li> 3003 <li class="indline1">503 Service Unavailable <a class="iref" href="#rfc.xref.status.503.1">4</a>, <a class="iref" href="#rfc.iref.s.40"><b>8.5.4</b></a>, <a class="iref" href="#rfc.xref.status.503.2">10.2</a></li> 3004 <li class="indline1">504 Gateway Timeout <a class="iref" href="#rfc.xref.status.504.1">4</a>, <a class="iref" href="#rfc.iref.s.41"><b>8.5.5</b></a>, <a class="iref" href="#rfc.xref.status.504.2">10.2</a></li> 3005 <li class="indline1">505 HTTP Version Not Supported <a class="iref" href="#rfc.xref.status.505.1">4</a>, <a class="iref" href="#rfc.iref.s.42"><b>8.5.6</b></a>, <a class="iref" href="#rfc.xref.status.505.2">10.2</a></li> 3026 <li class="indline1">426 Upgrade Required <a class="iref" href="#rfc.xref.status.426.1">4</a>, <a class="iref" href="#rfc.iref.s.37"><b>8.4.19</b></a>, <a class="iref" href="#rfc.xref.status.426.2">10.2</a>, <a class="iref" href="#rfc.xref.status.426.3">A</a></li> 3027 <li class="indline1">500 Internal Server Error <a class="iref" href="#rfc.xref.status.500.1">4</a>, <a class="iref" href="#rfc.iref.s.38"><b>8.5.1</b></a>, <a class="iref" href="#rfc.xref.status.500.2">10.2</a></li> 3028 <li class="indline1">501 Not Implemented <a class="iref" href="#rfc.xref.status.501.1">4</a>, <a class="iref" href="#rfc.iref.s.39"><b>8.5.2</b></a>, <a class="iref" href="#rfc.xref.status.501.2">10.2</a></li> 3029 <li class="indline1">502 Bad Gateway <a class="iref" href="#rfc.xref.status.502.1">4</a>, <a class="iref" href="#rfc.iref.s.40"><b>8.5.3</b></a>, <a class="iref" href="#rfc.xref.status.502.2">10.2</a></li> 3030 <li class="indline1">503 Service Unavailable <a class="iref" href="#rfc.xref.status.503.1">4</a>, <a class="iref" href="#rfc.iref.s.41"><b>8.5.4</b></a>, <a class="iref" href="#rfc.xref.status.503.2">10.2</a></li> 3031 <li class="indline1">504 Gateway Timeout <a class="iref" href="#rfc.xref.status.504.1">4</a>, <a class="iref" href="#rfc.iref.s.42"><b>8.5.5</b></a>, <a class="iref" href="#rfc.xref.status.504.2">10.2</a></li> 3032 <li class="indline1">505 HTTP Version Not Supported <a class="iref" href="#rfc.xref.status.505.1">4</a>, <a class="iref" href="#rfc.iref.s.43"><b>8.5.6</b></a>, <a class="iref" href="#rfc.xref.status.505.2">10.2</a></li> 3006 3033 </ul> 3007 3034 </li> -
draft-ietf-httpbis/latest/p2-semantics.xml
r1070 r1071 612 612 / "416" ; &status-416;: Requested range not satisfiable 613 613 / "417" ; <xref target="status.417"/>: Expectation Failed 614 / "426" ; <xref target="status.426"/>: Upgrade Required 614 615 / "500" ; <xref target="status.500"/>: Internal Server Error 615 616 / "501" ; <xref target="status.501"/>: Not Implemented … … 1952 1953 </t> 1953 1954 </section> 1955 1956 <section title="426 Upgrade Required" anchor="status.426"> 1957 <iref primary="true" item="426 Upgrade Required (status code)" x:for-anchor=""/> 1958 <iref primary="true" item="Status Codes" subitem="426 Upgrade Required" x:for-anchor=""/> 1959 <t> 1960 The request can not be completed without a prior protocol upgrade. This 1961 response &MUST; include an Upgrade header field (&header-upgrade;) 1962 specifying the required protocols. 1963 </t> 1964 <figure> 1965 <preamble>Example:</preamble> 1966 <artwork type="message/http; msgtype="request"" x:indent-with=" "> 1967 HTTP/1.1 426 Upgrade Required 1968 Upgrade: HTTP/2.0 1969 Connection: Upgrade 1970 1971 </artwork></figure> 1972 <t> 1973 The server &SHOULD; include a message body in the 426 response which 1974 indicates in human readable form the reason for the error and describes any 1975 alternative courses which may be available to the user. 1976 </t> 1977 </section> 1954 1978 </section> 1955 1979 … … 2687 2711 <c> 2688 2712 <xref target="status.417"/> 2713 </c> 2714 <c>426</c> 2715 <c>Upgrade Required</c> 2716 <c> 2717 <xref target="status.426"/> 2689 2718 </c> 2690 2719 <c>500</c> … … 3448 3477 </t> 3449 3478 <t> 3479 Define status 426 (Upgrade Required) (this was incorporated from 3480 <xref target="RFC2817"/>). 3481 (<xref target="status.426"/>) 3482 </t> 3483 <t> 3450 3484 Reclassify "Allow" as response header field, removing the option to 3451 3485 specify it in a PUT request. … … 3546 3580 "307" / "400" / "401" / "402" / "403" / "404" / "405" / "406" / 3547 3581 "407" / "408" / "409" / "410" / "411" / "412" / "413" / "414" / 3548 "415" / "416" / "417" / " 500" / "501" / "502" / "503" / "504" /3549 "50 5" / extension-code3582 "415" / "416" / "417" / "426" / "500" / "501" / "502" / "503" / 3583 "504" / "505" / extension-code 3550 3584 3551 3585 <x:ref>TE</x:ref> = <TE, defined in [Part1], Section 9.5> … … 4005 4039 "Migrate CONNECT from RFC2817 to p2" 4006 4040 </t> 4041 <t> 4042 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/240"/>: 4043 "Migrate Upgrade details from RFC2817" 4044 </t> 4007 4045 </list> 4008 4046 </t>
Note: See TracChangeset
for help on using the changeset viewer.