Changeset 1710 for draft-ietf-httpbis
- Timestamp:
- 04/07/12 08:44:42 (10 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 6 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r1708 r1710 449 449 } 450 450 @bottom-center { 451 content: "Expires January 4, 2013";451 content: "Expires January 5, 2013"; 452 452 } 453 453 @bottom-right { … … 491 491 <meta name="dct.creator" content="Reschke, J. F."> 492 492 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest"> 493 <meta name="dct.issued" scheme="ISO8601" content="2012-07-0 3">493 <meta name="dct.issued" scheme="ISO8601" content="2012-07-04"> 494 494 <meta name="dct.replaces" content="urn:ietf:rfc:2145"> 495 495 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> … … 523 523 </tr> 524 524 <tr> 525 <td class="left">Expires: January 4, 2013</td>525 <td class="left">Expires: January 5, 2013</td> 526 526 <td class="right">greenbytes</td> 527 527 </tr> 528 528 <tr> 529 529 <td class="left"></td> 530 <td class="right">July 3, 2012</td>530 <td class="right">July 4, 2012</td> 531 531 </tr> 532 532 </tbody> … … 561 561 in progress”. 562 562 </p> 563 <p>This Internet-Draft will expire on January 4, 2013.</p>563 <p>This Internet-Draft will expire on January 5, 2013.</p> 564 564 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 565 565 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1005 1005 </p> 1006 1006 <p id="rfc.section.2.6.p.11">An HTTP server <em class="bcp14">SHOULD</em> send a response version equal to the highest version to which the server is conformant and whose major version is less than 1007 or equal to the one received in the request. An HTTP server <em class="bcp14">MUST NOT</em> send a version to which it is not conformant. A server <em class="bcp14">MAY</em> send a 505 (HTTP Version Not Supported) response if it cannot send a response using the major version used in the client's1008 request.1007 or equal to the one received in the request. An HTTP server <em class="bcp14">MUST NOT</em> send a version to which it is not conformant. A server <em class="bcp14">MAY</em> send a <a href="p2-semantics.html#status.505" class="smpl">505 (HTTP Version Not 1008 Supported)</a> response if it cannot send a response using the major version used in the client's request. 1009 1009 </p> 1010 1010 <p id="rfc.section.2.6.p.12">An HTTP server <em class="bcp14">MAY</em> send an HTTP/1.0 response to an HTTP/1.0 request if it is known or suspected that the client incorrectly implements the HTTP … … 1176 1176 </p> 1177 1177 <p id="rfc.section.3.1.1.p.9">HTTP does not place a pre-defined limit on the length of a request-line. A server that receives a method longer than any that 1178 it implements <em class="bcp14">SHOULD</em> respond with either a 405 (Not Allowed), if it is an origin server, or a 501 (Not Implemented)status code. A server <em class="bcp14">MUST</em> be prepared to receive URIs of unbounded length and respond with the 414 (URI Too Long) status code if the received request-target1178 it implements <em class="bcp14">SHOULD</em> respond with either a 405 (Not Allowed), if it is an origin server, or a <a href="p2-semantics.html#status.501" class="smpl">501 (Not Implemented)</a> status code. A server <em class="bcp14">MUST</em> be prepared to receive URIs of unbounded length and respond with the 414 (URI Too Long) status code if the received request-target 1179 1179 would be longer than the server wishes to handle (see <a href="p2-semantics.html#status.414" title="414 URI Too Long">Section 4.6.12</a> of <a href="#Part2" id="rfc.xref.Part2.5"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>). 1180 1180 </p> … … 1416 1416 might be in the form of specific user configuration or by remembering the version of a prior received response. A server <em class="bcp14">MUST NOT</em> send a response containing Transfer-Encoding unless the corresponding request indicates HTTP/1.1 (or later). 1417 1417 </p> 1418 <p id="rfc.section.3.3.1.p.10">A server that receives a request message with a transfer-coding it does not understand <em class="bcp14">SHOULD</em> respond with 501 (Not Implemented)and then close the connection.1418 <p id="rfc.section.3.3.1.p.10">A server that receives a request message with a transfer-coding it does not understand <em class="bcp14">SHOULD</em> respond with <a href="p2-semantics.html#status.501" class="smpl">501 (Not Implemented)</a> and then close the connection. 1419 1419 </p> 1420 1420 <div id="rfc.iref.c.6"></div> … … 1477 1477 <p>If a message is received without Transfer-Encoding and with either multiple Content-Length header fields having differing 1478 1478 field-values or a single Content-Length header field having an invalid value, then the message framing is invalid and <em class="bcp14">MUST</em> be treated as an error to prevent request or response smuggling. If this is a request message, the server <em class="bcp14">MUST</em> respond with a 400 (Bad Request) status code and then close the connection. If this is a response message received by a proxy, 1479 the proxy <em class="bcp14">MUST</em> discard the received response, send a 502 (Bad Gateway) status code as its downstream response, and then close the connection.1480 If this is a response message received by a user-agent,it <em class="bcp14">MUST</em> be treated as an error by discarding the message and closing the connection.1479 the proxy <em class="bcp14">MUST</em> discard the received response, send a <a href="p2-semantics.html#status.502" class="smpl">502 (Bad Gateway)</a> status code as its downstream response, and then close the connection. If this is a response message received by a user-agent, 1480 it <em class="bcp14">MUST</em> be treated as an error by discarding the message and closing the connection. 1481 1481 </p> 1482 1482 </li> -
draft-ietf-httpbis/latest/p1-messaging.xml
r1708 r1710 706 706 whose major version is less than or equal to the one received in the 707 707 request. An HTTP server &MUST-NOT; send a version to which it is not 708 conformant. A server &MAY; send a 505 (HTTP709 Version Not Supported)response if it cannot send a response using the708 conformant. A server &MAY; send a <x:ref>505 (HTTP Version Not 709 Supported)</x:ref> response if it cannot send a response using the 710 710 major version used in the client's request. 711 711 </t> … … 1070 1070 A server that receives a method longer than any that it implements 1071 1071 &SHOULD; respond with either a 405 (Not Allowed), if it is an origin 1072 server, or a 501 (Not Implemented)status code.1072 server, or a <x:ref>501 (Not Implemented)</x:ref> status code. 1073 1073 A server &MUST; be prepared to receive URIs of unbounded length and 1074 1074 respond with the 414 (URI Too Long) status code if the received … … 1573 1573 <t> 1574 1574 A server that receives a request message with a transfer-coding it does 1575 not understand &SHOULD; respond with 501 (Not Implemented)and then1575 not understand &SHOULD; respond with <x:ref>501 (Not Implemented)</x:ref> and then 1576 1576 close the connection. 1577 1577 </t> … … 1690 1690 a 400 (Bad Request) status code and then close the connection. 1691 1691 If this is a response message received by a proxy, the proxy 1692 &MUST; discard the received response, send a 502 (Bad Gateway)1692 &MUST; discard the received response, send a <x:ref>502 (Bad Gateway)</x:ref> 1693 1693 status code as its downstream response, and then close the connection. 1694 1694 If this is a response message received by a user-agent, it &MUST; be … … 4108 4108 </front> 4109 4109 <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p2-semantics-&ID-VERSION;"/> 4110 <x:source href="p2-semantics.xml" basename="p2-semantics"/> 4110 <x:source href="p2-semantics.xml" basename="p2-semantics"> 4111 <x:defines>501 (Not Implemented)</x:defines> 4112 <x:defines>502 (Bad Gateway)</x:defines> 4113 <x:defines>505 (HTTP Version Not Supported)</x:defines> 4114 </x:source> 4111 4115 </reference> 4112 4116 -
draft-ietf-httpbis/latest/p2-semantics.html
r1708 r1710 449 449 } 450 450 @bottom-center { 451 content: "Expires January 4, 2013";451 content: "Expires January 5, 2013"; 452 452 } 453 453 @bottom-right { … … 497 497 <meta name="dct.creator" content="Reschke, J. F."> 498 498 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 499 <meta name="dct.issued" scheme="ISO8601" content="2012-07-0 3">499 <meta name="dct.issued" scheme="ISO8601" content="2012-07-04"> 500 500 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 501 501 <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 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. Furthermore, it defines HTTP message content, metadata, and content negotiation."> … … 528 528 </tr> 529 529 <tr> 530 <td class="left">Expires: January 4, 2013</td>530 <td class="left">Expires: January 5, 2013</td> 531 531 <td class="right">greenbytes</td> 532 532 </tr> 533 533 <tr> 534 534 <td class="left"></td> 535 <td class="right">July 3, 2012</td>535 <td class="right">July 4, 2012</td> 536 536 </tr> 537 537 </tbody> … … 563 563 in progress”. 564 564 </p> 565 <p>This Internet-Draft will expire on January 4, 2013.</p>565 <p>This Internet-Draft will expire on January 5, 2013.</p> 566 566 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 567 567 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 891 891 </pre><p id="rfc.section.2.p.3">The list of methods allowed by a resource can be specified in an Allow header field (<a href="#header.allow" id="rfc.xref.header.allow.1" title="Allow">Section 9.5</a>). The status code of the response always notifies the client whether a method is currently allowed on a resource, since the 892 892 set of allowed methods can change dynamically. An origin server <em class="bcp14">SHOULD</em> respond with the status code 405 (Method Not Allowed) if the method is known by the origin server but not allowed for the 893 resource, and 501 (Not Implemented) if the method is unrecognized or not implemented by the origin server. The methods GET 894 and HEAD <em class="bcp14">MUST</em> be supported by all general-purpose servers. All other methods are <em class="bcp14">OPTIONAL</em>; however, if the above methods are implemented, they <em class="bcp14">MUST</em> be implemented with the same semantics as those specified in <a href="#method.definitions" title="Method Definitions">Section 2.3</a>. 893 resource, and <a href="#status.501" class="smpl">501 (Not Implemented)</a> if the method is unrecognized or not implemented by the origin server. The methods GET and HEAD <em class="bcp14">MUST</em> be supported by all general-purpose servers. All other methods are <em class="bcp14">OPTIONAL</em>; however, if the above methods are implemented, they <em class="bcp14">MUST</em> be implemented with the same semantics as those specified in <a href="#method.definitions" title="Method Definitions">Section 2.3</a>. 895 894 </p> 896 895 <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a> <a id="safe.and.idempotent" href="#safe.and.idempotent">Safe and Idempotent Methods</a></h2> … … 2910 2909 <li>If the response status code is 100 (Continue) or 101 (Switching Protocols), the response <em class="bcp14">MAY</em> include a Date header field, at the server's option. 2911 2910 </li> 2912 <li>If the response status code conveys a server error, e.g., 500 (Internal Server Error) or 503 (Service Unavailable), and it 2913 is inconvenient or impossible to generate a valid Date. 2911 <li>If the response status code conveys a server error, e.g., 500 (Internal Server Error) or <a href="#status.503" class="smpl">503 (Service Unavailable)</a>, and it is inconvenient or impossible to generate a valid Date. 2914 2912 </li> 2915 2913 <li>If the server does not have a clock that can provide a reasonable approximation of the current time, its responses <em class="bcp14">MUST NOT</em> include a Date header field. … … 3039 3037 <div id="rfc.iref.h.17"></div> 3040 3038 <h2 id="rfc.section.9.16"><a href="#rfc.section.9.16">9.16</a> <a id="header.retry-after" href="#header.retry-after">Retry-After</a></h2> 3041 <p id="rfc.section.9.16.p.1">The header "Retry-After" field can be used with a 503 (Service Unavailable) response to indicate how long the service is expected3042 to be unavailable to the requesting client. This field <em class="bcp14">MAY</em> also be used with any 3xx (Redirection) response to indicate the minimum time the user-agent is asked to wait before issuing3039 <p id="rfc.section.9.16.p.1">The header "Retry-After" field can be used with a <a href="#status.503" class="smpl">503 (Service 3040 Unavailable)</a> response to indicate how long the service is expected to be unavailable to the requesting client. This field <em class="bcp14">MAY</em> also be used with any 3xx (Redirection) response to indicate the minimum time the user-agent is asked to wait before issuing 3043 3041 the redirected request. 3044 3042 </p> -
draft-ietf-httpbis/latest/p2-semantics.xml
r1708 r1710 392 392 origin server &SHOULD; respond with the status code 405 (Method Not Allowed) 393 393 if the method is known by the origin server but not allowed for the 394 resource, and 501 (Not Implemented)if the method is394 resource, and <x:ref>501 (Not Implemented)</x:ref> if the method is 395 395 unrecognized or not implemented by the origin server. The methods GET 396 396 and HEAD &MUST; be supported by all general-purpose servers. All other … … 2030 2030 <iref primary="true" item="501 Not Implemented (status code)" x:for-anchor=""/> 2031 2031 <iref primary="true" item="Status Codes" subitem="501 Not Implemented" x:for-anchor=""/> 2032 <x:anchor-alias value="501 (Not Implemented)"/> 2032 2033 <t> 2033 2034 The server does not support the functionality required to fulfill the … … 2041 2042 <iref primary="true" item="502 Bad Gateway (status code)" x:for-anchor=""/> 2042 2043 <iref primary="true" item="Status Codes" subitem="502 Bad Gateway" x:for-anchor=""/> 2044 <x:anchor-alias value="502 (Bad Gateway)"/> 2043 2045 <t> 2044 2046 The server, while acting as a gateway or proxy, received an invalid … … 2051 2053 <iref primary="true" item="503 Service Unavailable (status code)" x:for-anchor=""/> 2052 2054 <iref primary="true" item="Status Codes" subitem="503 Service Unavailable" x:for-anchor=""/> 2055 <x:anchor-alias value="503 (Service Unavailable)"/> 2053 2056 <t> 2054 2057 The server is currently unable to handle the request due to a … … 2074 2077 <iref primary="true" item="504 Gateway Timeout (status code)" x:for-anchor=""/> 2075 2078 <iref primary="true" item="Status Codes" subitem="504 Gateway Timeout" x:for-anchor=""/> 2079 <x:anchor-alias value="504 (Gateway Timeout)"/> 2076 2080 <t> 2077 2081 The server, while acting as a gateway or proxy, did not receive a … … 2091 2095 <iref primary="true" item="505 HTTP Version Not Supported (status code)" x:for-anchor=""/> 2092 2096 <iref primary="true" item="Status Codes" subitem="505 HTTP Version Not Supported" x:for-anchor=""/> 2097 <x:anchor-alias value="505 (HTTP Version Not Supported)"/> 2093 2098 <t> 2094 2099 The server does not support, or refuses to support, the protocol … … 3516 3521 3517 3522 <t>If the response status code conveys a server error, e.g., 500 3518 (Internal Server Error) or 503 (Service Unavailable), and it is3519 inconvenient or impossible to generate a valid Date.</t>3523 (Internal Server Error) or <x:ref>503 (Service Unavailable)</x:ref>, 3524 and it is inconvenient or impossible to generate a valid Date.</t> 3520 3525 3521 3526 <t>If the server does not have a clock that can provide a … … 3792 3797 <x:anchor-alias value="Retry-After"/> 3793 3798 <t> 3794 The header "Retry-After" field can be used with a 503 (Service3795 Unavailable) response to indicate how long the service is expected to3799 The header "Retry-After" field can be used with a <x:ref>503 (Service 3800 Unavailable)</x:ref> response to indicate how long the service is expected to 3796 3801 be unavailable to the requesting client. This field &MAY; also be used 3797 3802 with any 3xx (Redirection) response to indicate the minimum time the -
draft-ietf-httpbis/latest/p6-cache.html
r1708 r1710 452 452 } 453 453 @bottom-center { 454 content: "Expires January 4, 2013";454 content: "Expires January 5, 2013"; 455 455 } 456 456 @bottom-right { … … 494 494 <meta name="dct.creator" content="Reschke, J. F."> 495 495 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest"> 496 <meta name="dct.issued" scheme="ISO8601" content="2012-07-0 3">496 <meta name="dct.issued" scheme="ISO8601" content="2012-07-04"> 497 497 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 498 498 <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 6 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 6 defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages."> … … 520 520 </tr> 521 521 <tr> 522 <td class="left">Expires: January 4, 2013</td>522 <td class="left">Expires: January 5, 2013</td> 523 523 <td class="right">M. Nottingham, Editor</td> 524 524 </tr> … … 537 537 <tr> 538 538 <td class="left"></td> 539 <td class="right">July 3, 2012</td>539 <td class="right">July 4, 2012</td> 540 540 </tr> 541 541 </tbody> … … 567 567 in progress”. 568 568 </p> 569 <p>This Internet-Draft will expire on January 4, 2013.</p>569 <p>This Internet-Draft will expire on January 5, 2013.</p> 570 570 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 571 571 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1317 1317 <h4 id="rfc.section.3.2.1.7"><a href="#rfc.section.3.2.1.7">3.2.1.7</a> <a id="cache-request-directive.only-if-cached" href="#cache-request-directive.only-if-cached">only-if-cached</a></h4> 1318 1318 <p id="rfc.section.3.2.1.7.p.1">The only-if-cached request directive indicates that the client only wishes to obtain a stored response. If it receives 3ive, 1319 a cache <em class="bcp14">SHOULD</em> either respond using a stored response that is consistent with the other constraints of the request, or respond with a 504 1320 (Gateway Timeout) status code. If a group of caches is being operated as a unified system with good internal connectivity, 1321 a member cache <em class="bcp14">MAY</em> forward such a request within that group of caches. 1319 a cache <em class="bcp14">SHOULD</em> either respond using a stored response that is consistent with the other constraints of the request, or respond with a <a href="p2-semantics.html#status.504" class="smpl">504 1320 (Gateway Timeout)</a> status code. If a group of caches is being operated as a unified system with good internal connectivity, a member cache <em class="bcp14">MAY</em> forward such a request within that group of caches. 1322 1321 </p> 1323 1322 <h3 id="rfc.section.3.2.2"><a href="#rfc.section.3.2.2">3.2.2</a> <a id="cache-response-directive" href="#cache-response-directive">Response Cache-Control Directives</a></h3> … … 1388 1387 </p> 1389 1388 <p id="rfc.section.3.2.2.5.p.2">The must-revalidate directive is necessary to support reliable operation for certain protocol features. In all circumstances 1390 a cache <em class="bcp14">MUST</em> obey the must-revalidate directive; in particular, if a cache cannot reach the origin server for any reason, it <em class="bcp14">MUST</em> generate a 504 (Gateway Timeout)response.1389 a cache <em class="bcp14">MUST</em> obey the must-revalidate directive; in particular, if a cache cannot reach the origin server for any reason, it <em class="bcp14">MUST</em> generate a <a href="p2-semantics.html#status.504" class="smpl">504 (Gateway Timeout)</a> response. 1391 1390 </p> 1392 1391 <p id="rfc.section.3.2.2.5.p.3">The must-revalidate directive ought to be used by servers if and only if failure to validate a request on the representation -
draft-ietf-httpbis/latest/p6-cache.xml
r1708 r1710 1361 1361 wishes to obtain a stored response. If it receives 3ive, a 1362 1362 cache &SHOULD; either respond using a stored response that is consistent 1363 with the other constraints of the request, or respond with a 5041364 (Gateway Timeout) status code. If a group of caches is being operated as1363 with the other constraints of the request, or respond with a <x:ref>504 1364 (Gateway Timeout)</x:ref> status code. If a group of caches is being operated as 1365 1365 a unified system with good internal connectivity, a member cache &MAY; 1366 1366 forward such a request within that group of caches. … … 1504 1504 cache &MUST; obey the must-revalidate directive; in particular, 1505 1505 if a cache cannot reach the origin server for any reason, it &MUST; 1506 generate a 504 (Gateway Timeout)response.1506 generate a <x:ref>504 (Gateway Timeout)</x:ref> response. 1507 1507 </t> 1508 1508 <t> … … 2287 2287 </front> 2288 2288 <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p2-semantics-&ID-VERSION;" /> 2289 <x:source basename="p2-semantics" href="p2-semantics.xml" /> 2289 <x:source basename="p2-semantics" href="p2-semantics.xml"> 2290 <x:defines>504 (Gateway Timeout)</x:defines> 2291 </x:source> 2290 2292 </reference> 2291 2293
Note: See TracChangeset
for help on using the changeset viewer.