Changeset 1161 for draft-ietf-httpbis/latest/p2-semantics.xml
- Timestamp:
- 11/03/11 05:37:52 (12 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.xml
r1160 r1161 430 430 <x:anchor-alias value="extension-method"/> 431 431 <t> 432 The Method token indicates the method to be performed on the target432 The Method token indicates the request method to be performed on the target 433 433 resource (&effective-request-uri;). The method is case-sensitive. 434 434 </t> … … 468 468 </texttable> 469 469 <t> 470 Note that this list is not exhaustive — it does not include methods defined470 Note that this list is not exhaustive — it does not include request methods defined 471 471 in other specifications. 472 472 </t> … … 811 811 <section title="Method Definitions" anchor="method.definitions"> 812 812 <t> 813 The set of common methods for HTTP/1.1 is defined below. Although813 The set of common request methods for HTTP/1.1 is defined below. Although 814 814 this set can be expanded, additional methods cannot be assumed to 815 815 share the same semantics for separately extended clients and servers. … … 828 828 <t> 829 829 In particular, the convention has been established that the GET, HEAD, 830 OPTIONS, and TRACE methods &SHOULD-NOT; have the significance of taking an action 831 other than retrieval. These methods ought to be considered "<x:dfn anchor="safe">safe</x:dfn>". 830 OPTIONS, and TRACE request methods &SHOULD-NOT; have the significance 831 of taking an action other than retrieval. These request methods ought 832 to be considered "<x:dfn anchor="safe">safe</x:dfn>". 832 833 This allows user agents to represent other methods, such as POST, PUT 833 834 and DELETE, in a special way, so that the user is made aware of the … … 846 847 <iref item="Idempotent Methods" primary="true"/> 847 848 <t> 848 Methods can also have the property of "idempotence" in that, aside849 from error or expiration issues, the intended effect of multiple849 Request methods can also have the property of "idempotence" in that, 850 aside from error or expiration issues, the intended effect of multiple 850 851 identical requests is the same as for a single request. 851 The methods PUT, DELETE, and all safemethods are idempotent.852 PUT, DELETE, and all safe request methods are idempotent. 852 853 It is important to note that idempotence refers only to changes 853 854 requested by the client: a server is free to change its state due … … 865 866 <iref primary="true" item="Methods" subitem="OPTIONS" x:for-anchor=""/> 866 867 <t> 867 The OPTIONS method re presents a request forinformation about the868 The OPTIONS method requests information about the 868 869 communication options available on the request/response chain 869 identified by the effective request URI. This method allows theclient to870 identified by the effective request URI. This method allows a client to 870 871 determine the options and/or requirements associated with a resource, 871 872 or the capabilities of a server, without implying a resource action … … 873 874 </t> 874 875 <t> 875 Responses to th ismethod are not cacheable.876 Responses to the OPTIONS method are not cacheable. 876 877 </t> 877 878 <t> … … 924 925 <iref primary="true" item="Methods" subitem="GET" x:for-anchor=""/> 925 926 <t> 926 The GET method means retrieve whatever information (in the form of a927 representation) currently corresponds tothe target resource.927 The GET method requests transfer of a current representation of 928 the target resource. 928 929 </t> 929 930 <t> … … 937 938 request message includes an If-Modified-Since, If-Unmodified-Since, 938 939 If-Match, If-None-Match, or If-Range header field. A conditional GET 939 methodrequests that the representation be transferred only under the940 requests that the representation be transferred only under the 940 941 circumstances described by the conditional header field(s). The 941 conditional GET methodis intended to reduce unnecessary network942 conditional GET request is intended to reduce unnecessary network 942 943 usage by allowing cached representations to be refreshed without requiring 943 944 multiple requests or transferring data already held by the client. … … 947 948 request message includes a Range header field. A partial GET requests 948 949 that only part of the representation be transferred, as described in &header-range;. 949 The partial GET methodis intended to reduce unnecessary950 The partial GET request is intended to reduce unnecessary 950 951 network usage by allowing partially-retrieved representations to be 951 952 completed without transferring data already held by the client. … … 991 992 <iref primary="true" item="Methods" subitem="POST" x:for-anchor=""/> 992 993 <t> 993 The POST method is used to requestthat the origin server accept the994 The POST method requests that the origin server accept the 994 995 representation enclosed in the request as data to be processed by the 995 996 target resource. POST is designed to allow a uniform method to cover the … … 1047 1048 <iref primary="true" item="Methods" subitem="PUT" x:for-anchor=""/> 1048 1049 <t> 1049 The PUT method is used to requestthat the state of the target resource1050 The PUT method requests that the state of the target resource 1050 1051 be created or replaced with the state defined by the representation 1051 1052 enclosed in the request message payload. A successful PUT of a given … … 1198 1199 <iref primary="true" item="Methods" subitem="TRACE" x:for-anchor=""/> 1199 1200 <t> 1200 The TRACE method is used to invokea remote, application-layer loop-back1201 The TRACE method requests a remote, application-layer loop-back 1201 1202 of the request message. The final recipient of the request 1202 1203 &SHOULD; reflect the message received back to the client as the … … 1227 1228 <iref primary="true" item="Methods" subitem="CONNECT" x:for-anchor=""/> 1228 1229 <t> 1229 The CONNECT method is used with a proxy to dynamically switch 1230 the connection to a tunnel. 1231 </t> 1232 <t> 1233 When using CONNECT, the request-target &MUST; be use the authority form 1234 (&request-target;); i.e., the host name and port number destination of the 1235 requested connection separated by a colon: 1230 The CONNECT method requests that the proxy establish a tunnel 1231 to the request-target and then restrict its behavior to blind 1232 forwarding of packets until the connection is closed. 1233 </t> 1234 <t> 1235 When using CONNECT, the request-target &MUST; use the authority form 1236 (&request-target;); i.e., the request-target consists of only the 1237 host name and port number of the tunnel destination, separated by a colon. 1238 For example, 1236 1239 </t> 1237 1240 <figure><artwork type="message/http; msgtype="request"" x:indent-with=" "> … … 2006 2009 <iref primary="true" item="Status Codes" subitem="415 Unsupported Media Type" x:for-anchor=""/> 2007 2010 <t> 2008 The server is refusing to service the request because the re presentation of2009 the request is in a format not supported by the target resource2010 for the requested method.2011 The server is refusing to service the request because the request 2012 payload is in a format not supported by this request method on the 2013 target resource. 2011 2014 </t> 2012 2015 </section> … … 2170 2173 The "Allow" response-header field lists the set of methods advertised as 2171 2174 supported by the target resource. The purpose of this field is strictly to 2172 inform the recipient of valid methods associated with the resource.2175 inform the recipient of valid request methods associated with the resource. 2173 2176 </t> 2174 2177 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Allow"/><iref primary="true" item="Grammar" subitem="Allow-v"/> … … 2390 2393 </t> 2391 2394 <t> 2392 The Max-Forwards header field &MAY; be ignored for all other methods. 2395 The Max-Forwards header field &MAY; be ignored for all other request 2396 methods. 2393 2397 </t> 2394 2398 </section> … … 2571 2575 <section title="Method Registry" anchor="method.registration"> 2572 2576 <t> 2573 The registration procedure for HTTP Methods is defined by2577 The registration procedure for HTTP request methods is defined by 2574 2578 <xref target="method.registry"/> of this document. 2575 2579 </t> … … 2976 2980 </t> 2977 2981 <t> 2978 Some methods, like TRACE (<xref target="TRACE"/>), expose information2982 Some request methods, like TRACE (<xref target="TRACE"/>), expose information 2979 2983 that was sent in request header fields within the body of their response. 2980 2984 Clients &SHOULD; be careful with sensitive information, like Cookies, 2981 Authorization credentials and other header fields that might be used to2985 Authorization credentials, and other header fields that might be used to 2982 2986 collect data from the client. 2983 2987 </t>
Note: See TracChangeset
for help on using the changeset viewer.