Changeset 972 for draft-ietf-httpbis/latest/p2-semantics.xml
- Timestamp:
- 02/08/10 13:20:54 (12 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.xml
r971 r972 433 433 <x:anchor-alias value="extension-method"/> 434 434 <t> 435 The Method token indicates the method to be performed on the resource 436 identified by the effective request URI (&effective-request-uri;). The 437 method is case-sensitive. 435 The Method token indicates the method to be performed on the target 436 resource (&effective-request-uri;). The method is case-sensitive. 438 437 </t> 439 438 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Method"/><iref primary="true" item="Grammar" subitem="extension-method"/> … … 634 633 information about the response which cannot be placed in the Status-Line. 635 634 These header fields give information about the server and about 636 further access to the resource identified by the effective request URI 637 (&effective-request-uri;). 635 further access to the target resource (&effective-request-uri;). 638 636 </t> 639 637 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="response-header"/> … … 684 682 </t> 685 683 <t> 686 In the common case, an HTTP response is a representation of the resource 687 located at the effective request URI (see &effective-request-uri;). However, 688 this is not always the case. To determine the URI of the resource a 689 response is associated with, the following rules are used (with the first 690 applicable one being selected): 684 In the common case, an HTTP response is a representation of the target 685 resource (see &effective-request-uri;). However, this is not always the 686 case. To determine the URI of the resource a response is associated with, 687 the following rules are used (with the first applicable one being selected): 691 688 </t> 692 689 <t><list style="numbers"> 693 690 <t>If the response status code is 200 or 203 and the request method was GET, 694 the response payload is a representation of the resource identified by the effective request URI.</t>691 the response payload is a representation of the target resource.</t> 695 692 <t>If the response status code is 204, 206, or 304 and the request method was GET 696 or HEAD, the response payload is a partial representation of the resource identified697 by the effective request URI(see &caching-combining-headers;).</t>693 or HEAD, the response payload is a partial representation of the target 694 (see &caching-combining-headers;).</t> 698 695 <t>If the response has a Content-Location header, and that URI is the same 699 696 as the effective request URI, the response payload is a representation of the 700 resource identified by the effective request URI.</t>697 target resource.</t> 701 698 <t>If the response has a Content-Location header, and that URI is not the 702 699 same as the effective request URI, then the response asserts that its … … 833 830 <t> 834 831 The GET method means retrieve whatever information (in the form of a 835 representation) currently corresponds to the resource identified by the 836 effective request URI. 832 representation) currently corresponds to the target resource. 837 833 </t> 838 834 <t> 839 If the effective request URI identifies a data-producing process, it is the835 If the target resource is a data-producing process, it is the 840 836 produced data which shall be returned as the representation in the response and not 841 837 the source text of the process, unless that text happens to be the output of … … 901 897 <t> 902 898 The POST method is used to request that the origin server accept the 903 representation enclosed in the request as data to be processed by the resource904 identified by the effective request URI. POST is designed905 to allow a uniform method to cover thefollowing functions:899 representation enclosed in the request as data to be processed by the 900 target resource. POST is designed to allow a uniform method to cover the 901 following functions: 906 902 <list style="symbols"> 907 903 <t> … … 942 938 include explicit freshness information (see &p6-explicit;). A 943 939 cached POST response with a Content-Location header 944 (see &header-content-location;) whose value is the Effective940 (see &header-content-location;) whose value is the effective 945 941 Request URI &MAY; be used to satisfy subsequent GET and HEAD requests. 946 942 </t> … … 972 968 </t> 973 969 <t> 974 If the resource identified by the effective request URI could not be 975 created or modified, an appropriate error response &SHOULD; be given 976 that reflects the nature of the problem. 970 If the target resource could not be created or modified, an appropriate 971 error response &SHOULD; be given that reflects the nature of the problem. 977 972 The recipient of the representation &MUST-NOT; ignore any Content-* 978 973 headers (headers starting with the prefix "Content-") that it does … … 1024 1019 <iref primary="true" item="Methods" subitem="DELETE" x:for-anchor=""/> 1025 1020 <t> 1026 The DELETE method requests that the origin server delete the resource1027 identified by the effective request URI. This method &MAY; be overridden by1021 The DELETE method requests that the origin server delete the target 1022 resource. This method &MAY; be overridden by 1028 1023 human intervention (or other means) on the origin server. The client cannot 1029 1024 be guaranteed that the operation has been carried out, even if the … … 1171 1166 <list style="hanging"> 1172 1167 <t hangText="GET"> 1173 a representation of the resource corresponding to the effective 1174 request URI is sent in the response; 1168 a representation of the target resource is sent in the response; 1175 1169 </t> 1176 1170 <t hangText="HEAD">
Note: See TracChangeset
for help on using the changeset viewer.