Changeset 2091 for draft-ietf-httpbis/latest/p2-semantics.xml
- Timestamp:
- 06/01/13 07:26:25 (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.xml
r2090 r2091 848 848 <t> 849 849 Some HTTP messages transfer a complete or partial representation as the 850 message "<x:dfn>payload</x:dfn>". In some cases, a payload might only851 containthe associated representation's header fields (e.g., responses to850 message "<x:dfn>payload</x:dfn>". In some cases, a payload might contain 851 only the associated representation's header fields (e.g., responses to 852 852 HEAD) or only some part(s) of the representation data 853 853 (e.g., the <x:ref>206 (Partial Content)</x:ref> status code). … … 855 855 <t> 856 856 The purpose of a payload in a request is defined by the method semantics. 857 In a response, the payload's purpose is defined by both the request method858 and the response status code.859 </t>860 <t>861 857 For example, a representation in the payload of a PUT request 862 858 (<xref target="PUT"/>) represents the desired state of the <x:ref>target resource</x:ref> … … 867 863 </t> 868 864 <t> 869 Likewise, the payload of a <x:ref>200 (OK)</x:ref> response to GET 870 (<xref target="GET"/>) ought to contain a representation of the 865 In a response, the payload's purpose is defined by both the request method 866 and the response status code. 867 For example, the payload of a <x:ref>200 (OK)</x:ref> response to GET 868 (<xref target="GET"/>) represents the current state of the 871 869 <x:ref>target resource</x:ref>, as observed at the time of the message 872 origination date (<xref target="header.date"/>), whereas the same status 873 code in a response to POST might contain either a representation of the 874 processing result or a current representation of the target resource after 875 applying the processing. Response messages with an error status code 876 usually contain a representation of the error condition, such that it 877 describes the error state and what next steps are suggested for resolving 878 it. 870 origination date (<xref target="header.date"/>), whereas the payload of 871 the same status code in a response to POST might represent either the 872 processing result or the new state of the target resource after applying 873 the processing. Response messages with an error status code usually contain 874 a payload that represents the error condition, such that it describes the 875 error state and what next steps are suggested for resolving it. 879 876 </t> 880 877 <t> … … 1079 1076 <c><xref target="GET" format="counter"/></c> 1080 1077 <c>HEAD</c> 1081 <c>Same as GET, but do not include a message body in the response.</c>1078 <c>Same as GET, but only transfer the status line and header block.</c> 1082 1079 <c><xref target="HEAD" format="counter"/></c> 1083 1080 <c>POST</c> … … 1286 1283 <t> 1287 1284 The HEAD method is identical to GET except that the server &MUST-NOT; 1288 send a message body in the response . The metadata contained1289 in the HTTP header fields in response to a HEAD request &SHOULD; be identical1290 to the information sent in response to a GET request. This method can1291 be used for obtaining metadata about the selected representation1292 without transferring the representation data. This method is1293 often used for testing hypertext links for validity, accessibility,1294 and recent modification.1285 send a message body in the response (i.e., the response terminates at the 1286 end of the header block). The metadata contained in the HTTP header fields 1287 in response to a HEAD request &SHOULD; be identical to the information sent 1288 in response to a GET request. This method can be used for obtaining 1289 metadata about the selected representation without transferring the 1290 representation data. This method is often used for testing hypertext links 1291 for validity, accessibility, and recent modification. 1295 1292 </t> 1296 1293 <t>
Note: See TracChangeset
for help on using the changeset viewer.