Changeset 1161 for draft-ietf-httpbis/latest/p1-messaging.xml
- Timestamp:
- 11/03/11 05:37:52 (11 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.xml
r1159 r1161 1405 1405 because the associated response header fields (e.g., Transfer-Encoding, 1406 1406 Content-Length, etc.) only indicate what their values would have been 1407 if the method had been GET. All 1xx (Informational), 204 (No Content),1407 if the request method had been GET. All 1xx (Informational), 204 (No Content), 1408 1408 and 304 (Not Modified) responses &MUST-NOT; include a message-body. 1409 1409 All other responses do include a message-body, although the body … … 1604 1604 <x:anchor-alias value="Method"/> 1605 1605 <t> 1606 The Method token indicates themethod to be performed on the1607 resource identified by the request-target. Themethod is case-sensitive.1606 The Method token indicates the request method to be performed on the 1607 target resource. The request method is case-sensitive. 1608 1608 </t> 1609 1609 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Method"/> … … 1615 1615 <x:anchor-alias value="request-target"/> 1616 1616 <t> 1617 The request-target identifies the resource upon which to apply the request.1617 The request-target identifies the target resource upon which to apply the request. 1618 1618 </t> 1619 1619 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="request-target"/> … … 1630 1630 The asterisk "*" ("asterisk form") means that the request does not apply to a 1631 1631 particular resource, but to the server itself. This is only allowed for the 1632 OPTIONS method. Thus, the only valid example is1632 OPTIONS request method. Thus, the only valid example is 1633 1633 </t> 1634 1634 <figure><artwork type="message/http; msgtype="request"" x:indent-with=" "> … … 1655 1655 </t> 1656 1656 <t><iref item="authority form (of request-target)"/> 1657 The "authority form" is only used by the CONNECT method (&CONNECT;).1657 The "authority form" is only used by the CONNECT request method (&CONNECT;). 1658 1658 </t> 1659 1659 <t><iref item="path-absolute form (of request-target)"/> … … 1677 1677 </t> 1678 1678 <t> 1679 If a proxy receives a request without any path in the request-target and 1680 the method specified is capable of supporting the asterisk form of 1681 request-target, then the last proxy on the request chain &MUST; forward the 1682 request with "*" as the final request-target. 1679 If a proxy receives an OPTIONS request without any path in the 1680 request-target, then the last proxy on the request chain &MUST; 1681 forward the request with "*" as the final request-target. 1683 1682 </t> 1684 1683 <figure><preamble> … … 1688 1687 </artwork></figure> 1689 1688 <figure><preamble> 1690 would be forwarded by the proxy as1689 would be forwarded by the final proxy as 1691 1690 </preamble><artwork type="message/http; msgtype="request"" x:indent-with=" "> 1692 1691 OPTIONS * HTTP/1.1 … … 2525 2524 </t> 2526 2525 <t> 2527 Clients &SHOULD-NOT; pipeline requests using non-idempotent methods or2528 non-idempotent sequences of methods (see &idempotent-methods;). Otherwise, a2526 Clients &SHOULD-NOT; pipeline requests using non-idempotent request methods or 2527 non-idempotent sequences of request methods (see &idempotent-methods;). Otherwise, a 2529 2528 premature termination of the transport connection could lead to 2530 2529 indeterminate results. A client wishing to send a non-idempotent … … 2696 2695 transport connection and retransmit the aborted sequence of requests 2697 2696 without user interaction so long as the request sequence is 2698 idempotent (see &idempotent-methods;). Non-idempotent methods or sequences2697 idempotent (see &idempotent-methods;). Non-idempotent request methods or sequences 2699 2698 &MUST-NOT; be automatically retried, although user agents &MAY; offer a 2700 2699 human operator the choice of retrying the request(s). Confirmation by … … 2804 2803 code, it &MAY; close the transport connection or it &MAY; continue 2805 2804 to read and discard the rest of the request. It &MUST-NOT; 2806 perform the request edmethod if it returns a final status code.2805 perform the request method if it returns a final status code. 2807 2806 </t> 2808 2807 <t> An origin server &SHOULD-NOT; send a 100 (Continue) response if … … 3038 3037 The "Content-Length" header field indicates the size of the 3039 3038 message-body, in decimal number of octets, for any message other than 3040 a response to the HEAD method or a response with a status code of 304. 3041 In the case of responses to the HEAD method, it indicates the size of 3042 the payload body (not including any potential transfer-coding) that 3043 would have been sent had the request been a GET. 3044 In the case of the 304 (Not Modified) response, it indicates the size of 3045 the payload body (not including any potential transfer-coding) that 3046 would have been sent in a 200 (OK) response. 3039 a response to a HEAD request or a response with a status code of 304. 3040 In the case of a response to a HEAD request, Content-Length indicates 3041 the size of the payload body (not including any potential transfer-coding) 3042 that would have been sent had the request been a GET. 3043 In the case of a 304 (Not Modified) response to a GET request, 3044 Content-Length indicates the size of the payload body (not including 3045 any potential transfer-coding) that would have been sent in a 200 (OK) 3046 response. 3047 3047 </t> 3048 3048 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Content-Length"/><iref primary="true" item="Grammar" subitem="Content-Length-v"/> … … 3384 3384 supported protocol while indicating to the server that it would like 3385 3385 to use a "better" protocol if available (where "better" is determined 3386 by the server, possibly according to the nature of the method and/or3387 resource being requested).3386 by the server, possibly according to the nature of the request method 3387 or target resource). 3388 3388 </t> 3389 3389 <t> … … 4868 4868 since 1990. The first version of HTTP, later referred to as HTTP/0.9, 4869 4869 was a simple protocol for hypertext data transfer across the Internet 4870 with only a single methodand no metadata.4870 with only a single request method (GET) and no metadata. 4871 4871 HTTP/1.0, as defined by <xref target="RFC1945"/>, added a range of request 4872 4872 methods and MIME-like messaging that could include metadata about the data … … 5023 5023 Update use of abs_path production from RFC 1808 to the path-absolute + query 5024 5024 components of RFC 3986. State that the asterisk form is allowed for the OPTIONS 5025 method only.5025 request method only. 5026 5026 (<xref target="request-target"/>) 5027 5027 </t>
Note: See TracChangeset
for help on using the changeset viewer.