Changeset 1957
- Timestamp:
- 30/10/12 13:39:53 (10 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 4 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r1943 r1957 449 449 } 450 450 @bottom-center { 451 content: "Expires April 25, 2013";451 content: "Expires May 3, 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-10- 22">493 <meta name="dct.issued" scheme="ISO8601" content="2012-10-30"> 494 494 <meta name="dct.replaces" content="urn:ietf:rfc:2145"> 495 495 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> … … 520 520 <tr> 521 521 <td class="left">Intended status: Standards Track</td> 522 <td class="right">October 22, 2012</td>522 <td class="right">October 30, 2012</td> 523 523 </tr> 524 524 <tr> 525 <td class="left">Expires: April 25, 2013</td>525 <td class="left">Expires: May 3, 2013</td> 526 526 <td class="right"></td> 527 527 </tr> … … 551 551 in progress”. 552 552 </p> 553 <p>This Internet-Draft will expire on April 25, 2013.</p>553 <p>This Internet-Draft will expire on May 3, 2013.</p> 554 554 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 555 555 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1431 1431 <li> 1432 1432 <p>If a message is received without <a href="#header.transfer-encoding" class="smpl">Transfer-Encoding</a> and with either multiple <a href="#header.content-length" class="smpl">Content-Length</a> header fields having differing field-values or a single Content-Length header field having an invalid value, then the message 1433 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 <a href="p2-semantics.html#status.400" class="smpl">400 (Bad Request)</a> status code and then close the connection. If this is a response message received by a proxy, 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,1433 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 <a href="p2-semantics.html#status.400" class="smpl">400 (Bad Request)</a> status code and then close the connection. If this is a response message received by a proxy, 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, 1434 1434 it <em class="bcp14">MUST</em> be treated as an error by discarding the message and closing the connection. 1435 1435 </p> … … 1438 1438 <p>If a valid <a href="#header.content-length" class="smpl">Content-Length</a> header field is present without <a href="#header.transfer-encoding" class="smpl">Transfer-Encoding</a>, its decimal value defines the message body length in octets. If the actual number of octets sent in the message is less 1439 1439 than the indicated Content-Length, the recipient <em class="bcp14">MUST</em> consider the message to be incomplete and treat the connection as no longer usable. If the actual number of octets sent in 1440 the message is more than the indicated Content-Length, the recipient <em class="bcp14">MUST</em> only process the message body up to the field value's number of octets; the remainder of the message <em class="bcp14">MUST</em> either be discarded or treated as the next message in a pipeline. For the sake of robustness, a user -agent <em class="bcp14">MAY</em> attempt to detect and correct such an error in message framing if it is parsing the response to the last request on a connection1440 the message is more than the indicated Content-Length, the recipient <em class="bcp14">MUST</em> only process the message body up to the field value's number of octets; the remainder of the message <em class="bcp14">MUST</em> either be discarded or treated as the next message in a pipeline. For the sake of robustness, a user agent <em class="bcp14">MAY</em> attempt to detect and correct such an error in message framing if it is parsing the response to the last request on a connection 1441 1441 and the connection has been closed by the server. 1442 1442 </p> … … 2026 2026 <h4 id="rfc.section.6.2.2.2"><a href="#rfc.section.6.2.2.2">6.2.2.2</a> <a id="persistent.retrying.requests" href="#persistent.retrying.requests">Retrying Requests</a></h4> 2027 2027 <p id="rfc.section.6.2.2.2.p.1">Senders can close the transport connection at any time. Therefore, clients, servers, and proxies <em class="bcp14">MUST</em> be able to recover from asynchronous close events. Client software <em class="bcp14">MAY</em> reopen the transport connection and retransmit the aborted sequence of requests without user interaction so long as the request 2028 sequence is idempotent (see <a href="p2-semantics.html#idempotent.methods" title="Idempotent Methods">Section 5.2.2</a> of <a href="#Part2" id="rfc.xref.Part2.28"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>). Non-idempotent request methods or sequences <em class="bcp14">MUST NOT</em> be automatically retried, although user agents <em class="bcp14">MAY</em> offer a human operator the choice of retrying the request(s). Confirmation by user -agent software with semantic understanding2028 sequence is idempotent (see <a href="p2-semantics.html#idempotent.methods" title="Idempotent Methods">Section 5.2.2</a> of <a href="#Part2" id="rfc.xref.Part2.28"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>). Non-idempotent request methods or sequences <em class="bcp14">MUST NOT</em> be automatically retried, although user agents <em class="bcp14">MAY</em> offer a human operator the choice of retrying the request(s). Confirmation by user agent software with semantic understanding 2029 2029 of the application <em class="bcp14">MAY</em> substitute for user confirmation. The automatic retry <em class="bcp14">SHOULD NOT</em> be repeated if the second sequence of requests fails. 2030 2030 </p> -
draft-ietf-httpbis/latest/p1-messaging.xml
r1943 r1957 1677 1677 &MUST; discard the received response, send a <x:ref>502 (Bad Gateway)</x:ref> 1678 1678 status code as its downstream response, and then close the connection. 1679 If this is a response message received by a user -agent, it &MUST; be1679 If this is a response message received by a user agent, it &MUST; be 1680 1680 treated as an error by discarding the message and closing the connection. 1681 1681 </t></x:lt> … … 1691 1691 field value's number of octets; the remainder of the message &MUST; either 1692 1692 be discarded or treated as the next message in a pipeline. For the sake of 1693 robustness, a user -agent &MAY; attempt to detect and correct such an error1693 robustness, a user agent &MAY; attempt to detect and correct such an error 1694 1694 in message framing if it is parsing the response to the last request on 1695 1695 a connection and the connection has been closed by the server. … … 2908 2908 &MUST-NOT; be automatically retried, although user agents &MAY; offer a 2909 2909 human operator the choice of retrying the request(s). Confirmation by 2910 user -agent software with semantic understanding of the application2910 user agent software with semantic understanding of the application 2911 2911 &MAY; substitute for user confirmation. The automatic retry &SHOULD-NOT; 2912 2912 be repeated if the second sequence of requests fails. -
draft-ietf-httpbis/latest/p2-semantics.html
r1950 r1957 449 449 } 450 450 @bottom-center { 451 content: "Expires April 27, 2013";451 content: "Expires May 3, 2013"; 452 452 } 453 453 @bottom-right { … … 496 496 <meta name="dct.creator" content="Reschke, J. F."> 497 497 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 498 <meta name="dct.issued" scheme="ISO8601" content="2012-10- 24">498 <meta name="dct.issued" scheme="ISO8601" content="2012-10-30"> 499 499 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 500 500 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines the semantics of HTTP/1.1 messages, as expressed by request methods, request header fields, response status codes, and response header fields, along with the payload of messages (metadata and body content) and mechanisms for content negotiation."> … … 524 524 <tr> 525 525 <td class="left">Intended status: Standards Track</td> 526 <td class="right">October 24, 2012</td>526 <td class="right">October 30, 2012</td> 527 527 </tr> 528 528 <tr> 529 <td class="left">Expires: April 27, 2013</td>529 <td class="left">Expires: May 3, 2013</td> 530 530 <td class="right"></td> 531 531 </tr> … … 555 555 in progress”. 556 556 </p> 557 <p>This Internet-Draft will expire on April 27, 2013.</p>557 <p>This Internet-Draft will expire on May 3, 2013.</p> 558 558 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 559 559 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1211 1211 <p id="rfc.section.3.4.p.4">These patterns are all widely used, and have trade-offs in applicability and practicality. In particular, when the number 1212 1212 of preferences or capabilities to be expressed by a client are large (such as when many different formats are supported by 1213 a user -agent), proactive negotiation becomes unwieldy, and might not be appropriate. Conversely, when the number of representations1213 a user agent), proactive negotiation becomes unwieldy, and might not be appropriate. Conversely, when the number of representations 1214 1214 to choose from is very large, reactive negotiation might not be appropriate. 1215 1215 </p> … … 2954 2954 <h3 id="rfc.section.8.1.3"><a href="#rfc.section.8.1.3">8.1.3</a> <a id="header.retry-after" href="#header.retry-after">Retry-After</a></h3> 2955 2955 <p id="rfc.section.8.1.3.p.1">The header "Retry-After" field can be used with a <a href="#status.503" class="smpl">503 (Service 2956 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 <a href="#status.3xx" class="smpl">3xx (Redirection)</a> response to indicate the minimum time the user -agent is asked to wait before issuing the redirected request.2956 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 <a href="#status.3xx" class="smpl">3xx (Redirection)</a> response to indicate the minimum time the user agent is asked to wait before issuing the redirected request. 2957 2957 </p> 2958 2958 <p id="rfc.section.8.1.3.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> -
draft-ietf-httpbis/latest/p2-semantics.xml
r1950 r1957 940 940 and practicality. In particular, when the number of preferences or 941 941 capabilities to be expressed by a client are large (such as when many 942 different formats are supported by a user -agent), proactive942 different formats are supported by a user agent), proactive 943 943 negotiation becomes unwieldy, and might not be appropriate. Conversely, 944 944 when the number of representations to choose from is very large, … … 3775 3775 be unavailable to the requesting client. This field &MAY; also be used 3776 3776 with any <x:ref>3xx (Redirection)</x:ref> response to indicate the minimum time the 3777 user -agent is asked to wait before issuing the redirected request.3777 user agent is asked to wait before issuing the redirected request. 3778 3778 </t> 3779 3779 <t>
Note: See TracChangeset
for help on using the changeset viewer.