Changeset 874 for draft-ietf-httpbis/latest/p2-semantics.xml
- Timestamp:
- 23/07/10 05:43:26 (12 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.xml
r867 r874 654 654 </section> 655 655 656 <section title="Representation" anchor=" entity">656 <section title="Representation" anchor="representation"> 657 657 <t> 658 658 Request and Response messages &MAY; transfer a representation if not otherwise … … 779 779 </t> 780 780 <t> 781 If the OPTIONS request includes a n entity-body (as indicated by the781 If the OPTIONS request includes a message-body (as indicated by the 782 782 presence of Content-Length or Transfer-Encoding), then the media type 783 783 &MUST; be indicated by a Content-Type field. Although this … … 833 833 <iref primary="true" item="Methods" subitem="GET" x:for-anchor=""/> 834 834 <t> 835 The GET method means retrieve whatever information (in the form of a n836 entity) currently corresponds to the resource identified by the835 The GET method means retrieve whatever information (in the form of a 836 representation) currently corresponds to the resource identified by the 837 837 Effective Request URI. 838 838 </t> … … 850 850 circumstances described by the conditional header field(s). The 851 851 conditional GET method is intended to reduce unnecessary network 852 usage by allowing cached entities to be refreshed without requiring852 usage by allowing cached representations to be refreshed without requiring 853 853 multiple requests or transferring data already held by the client. 854 854 </t> … … 889 889 The response to a HEAD request &MAY; be cacheable in the sense that the 890 890 information contained in the response &MAY; be used to update a 891 previously cached entityfrom that resource. If the new field values892 indicate that the cached entity differs from the current entity(as891 previously cached representation from that resource. If the new field values 892 indicate that the cached representation differs from the current representation (as 893 893 would be indicated by a change in Content-Length, Content-MD5, ETag 894 894 or Last-Modified), then the cache &MUST; treat the cache entry as … … 902 902 <t> 903 903 The POST method is used to request that the origin server accept the 904 entityenclosed in the request as data to be processed by the resource904 representation enclosed in the request as data to be processed by the resource 905 905 identified by the Effective Request URI. POST is designed 906 906 to allow a uniform method to cover the following functions: … … 930 930 resource that can be identified by a URI. In this case, either 200 931 931 (OK) or 204 (No Content) is the appropriate response status, 932 depending on whether or not the response includes a n entitythat932 depending on whether or not the response includes a representation that 933 933 describes the result. 934 934 </t> 935 935 <t> 936 936 If a resource has been created on the origin server, the response 937 &SHOULD; be 201 (Created) and contain a n entitywhich describes the937 &SHOULD; be 201 (Created) and contain a representation which describes the 938 938 status of the request and refers to the new resource, and a Location 939 939 header (see <xref target="header.location"/>). … … 1030 1030 <t> 1031 1031 A successful response &SHOULD; be 200 (OK) if the response includes an 1032 entitydescribing the status, 202 (Accepted) if the action has not1032 representation describing the status, 202 (Accepted) if the action has not 1033 1033 yet been enacted, or 204 (No Content) if the action has been enacted 1034 1034 but the response does not include a representation. … … 1036 1036 <t> 1037 1037 If the request passes through a cache and the Effective Request URI 1038 identifies one or more currently cached entities, those entries &SHOULD; be1039 treated as stale. Responses to th is method are not cacheable.1038 identifies one or more currently cached representations, those entries &SHOULD; be 1039 treated as stale. Responses to the DELETE method &MUST-NOT; be cached. 1040 1040 </t> 1041 1041 </section> … … 1051 1051 of the request message. The final recipient of the request 1052 1052 &SHOULD; reflect the message received back to the client as the 1053 entity-body of a 200 (OK) response. The final recipient is either the1053 message-body of a 200 (OK) response. The final recipient is either the 1054 1054 origin server or the first proxy or gateway to receive a Max-Forwards 1055 1055 value of zero (0) in the request (see <xref target="header.max-forwards"/>). … … 1066 1066 </t> 1067 1067 <t> 1068 If the request is valid, the response &SHOULD; contain the entire1069 request message in the entity-body, with a Content-Type of1070 "message/http" (see &media-type-message-http;). Responses to this method1071 &MUST-NOT; be cached.1068 If the request is valid, the response &SHOULD; have a Content-Type of 1069 "message/http" (see &media-type-message-http;) and contain a message-body 1070 that encloses a copy of the entire request message. 1071 Responses to the TRACE method &MUST-NOT; be cached. 1072 1072 </t> 1073 1073 </section> … … 1165 1165 <list style="hanging"> 1166 1166 <t hangText="GET"> 1167 a n entitycorresponding to the requested resource is sent in1167 a representation corresponding to the requested resource is sent in 1168 1168 the response; 1169 1169 </t> … … 1173 1173 </t> 1174 1174 <t hangText="POST"> 1175 a n entitydescribing or containing the result of the action;1175 a representation describing or containing the result of the action; 1176 1176 </t> 1177 1177 <t hangText="TRACE"> 1178 a n entitycontaining the request message as received by the1178 a representation containing the request message as received by the 1179 1179 end server. 1180 1180 </t> … … 1201 1201 <t> 1202 1202 A 201 response &MAY; contain an ETag response header field indicating 1203 the current value of the entity 1203 the current value of the entity-tag for the representation of the resource 1204 1204 just created (see &header-etag;). 1205 1205 </t> … … 1292 1292 <t> 1293 1293 The server has fulfilled the partial GET request for the resource 1294 and the enclosed entityis a partial representation as defined in &status-206;.1294 and the enclosed payload is a partial representation as defined in &status-206;. 1295 1295 </t> 1296 1296 </section> … … 1525 1525 The 4xx class of status code is intended for cases in which the 1526 1526 client seems to have erred. Except when responding to a HEAD request, 1527 the server &SHOULD; include a n entitycontaining an explanation of the1527 the server &SHOULD; include a representation containing an explanation of the 1528 1528 error situation, and whether it is a temporary or permanent 1529 1529 condition. These status codes are applicable to any request method. 1530 User agents &SHOULD; display any included entityto the user.1530 User agents &SHOULD; display any included representation to the user. 1531 1531 </t> 1532 1532 <t> … … 1614 1614 <t> 1615 1615 The resource identified by the request is only capable of generating 1616 response entities which have content characteristics not acceptable1616 response representations which have content characteristics not acceptable 1617 1617 according to the accept headers sent in the request. 1618 1618 </t> … … 1671 1671 and resubmit the request. The response body &SHOULD; include enough 1672 1672 information for the user to recognize the source of the conflict. 1673 Ideally, the response entitywould include enough information for the1673 Ideally, the response representation would include enough information for the 1674 1674 user or user agent to fix the problem; however, that might not be 1675 1675 possible and is not required. … … 1741 1741 <t> 1742 1742 The server is refusing to process a request because the request 1743 entityis larger than the server is willing or able to process. The1743 representation is larger than the server is willing or able to process. The 1744 1744 server &MAY; close the connection to prevent the client from continuing 1745 1745 the request. … … 1808 1808 which the server is aware that it has erred or is incapable of 1809 1809 performing the request. Except when responding to a HEAD request, the 1810 server &SHOULD; include a n entitycontaining an explanation of the1810 server &SHOULD; include a representation containing an explanation of the 1811 1811 error situation, and whether it is a temporary or permanent 1812 condition. User agents &SHOULD; display any included entityto the1812 condition. User agents &SHOULD; display any included representation to the 1813 1813 user. These response codes are applicable to any request method. 1814 1814 </t> … … 1890 1890 using the same major version as the client, as described in &http-version;, 1891 1891 other than with this error message. The response &SHOULD; contain 1892 a n entitydescribing why that version is not supported and what other1892 a representation describing why that version is not supported and what other 1893 1893 protocols are supported by that server. 1894 1894 </t>
Note: See TracChangeset
for help on using the changeset viewer.