Ignore:
Timestamp:
Mar 10, 2011, 9:37:52 PM (9 years ago)
Author:
fielding@…
Message:

editorial consistency:
Use "request method" when talking about HTTP method tokens
unless it is obvious from context.
Make method descriptions a bit more consistent.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r1160 r1161  
    430430  <x:anchor-alias value="extension-method"/>
    431431<t>
    432    The Method token indicates the method to be performed on the target
     432   The Method token indicates the request method to be performed on the target
    433433   resource (&effective-request-uri;). The method is case-sensitive.
    434434</t>
     
    468468</texttable>
    469469<t>
    470   Note that this list is not exhaustive &mdash; it does not include methods defined
     470  Note that this list is not exhaustive &mdash; it does not include request methods defined
    471471  in other specifications.
    472472</t>
     
    811811<section title="Method Definitions" anchor="method.definitions">
    812812<t>
    813    The set of common methods for HTTP/1.1 is defined below. Although
     813   The set of common request methods for HTTP/1.1 is defined below. Although
    814814   this set can be expanded, additional methods cannot be assumed to
    815815   share the same semantics for separately extended clients and servers.
     
    828828<t>
    829829   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>".
    832833   This allows user agents to represent other methods, such as POST, PUT
    833834   and DELETE, in a special way, so that the user is made aware of the
     
    846847<iref item="Idempotent Methods" primary="true"/>
    847848<t>
    848    Methods can also have the property of "idempotence" in that, aside
    849    from error or expiration issues, the intended effect of multiple
     849   Request methods can also have the property of "idempotence" in that,
     850   aside from error or expiration issues, the intended effect of multiple
    850851   identical requests is the same as for a single request.
    851    The methods PUT, DELETE, and all safe methods are idempotent.
     852   PUT, DELETE, and all safe request methods are idempotent.
    852853   It is important to note that idempotence refers only to changes
    853854   requested by the client: a server is free to change its state due
     
    865866  <iref primary="true" item="Methods" subitem="OPTIONS" x:for-anchor=""/>
    866867<t>
    867    The OPTIONS method represents a request for information about the
     868   The OPTIONS method requests information about the
    868869   communication options available on the request/response chain
    869    identified by the effective request URI. This method allows the client to
     870   identified by the effective request URI. This method allows a client to
    870871   determine the options and/or requirements associated with a resource,
    871872   or the capabilities of a server, without implying a resource action
     
    873874</t>
    874875<t>
    875    Responses to this method are not cacheable.
     876   Responses to the OPTIONS method are not cacheable.
    876877</t>
    877878<t>
     
    924925  <iref primary="true" item="Methods" subitem="GET" x:for-anchor=""/>
    925926<t>
    926    The GET method means retrieve whatever information (in the form of a
    927    representation) currently corresponds to the target resource.
     927   The GET method requests transfer of a current representation of
     928   the target resource.
    928929</t>
    929930<t>   
     
    937938   request message includes an If-Modified-Since, If-Unmodified-Since,
    938939   If-Match, If-None-Match, or If-Range header field. A conditional GET
    939    method requests that the representation be transferred only under the
     940   requests that the representation be transferred only under the
    940941   circumstances described by the conditional header field(s). The
    941    conditional GET method is intended to reduce unnecessary network
     942   conditional GET request is intended to reduce unnecessary network
    942943   usage by allowing cached representations to be refreshed without requiring
    943944   multiple requests or transferring data already held by the client.
     
    947948   request message includes a Range header field. A partial GET requests
    948949   that only part of the representation be transferred, as described in &header-range;.
    949    The partial GET method is intended to reduce unnecessary
     950   The partial GET request is intended to reduce unnecessary
    950951   network usage by allowing partially-retrieved representations to be
    951952   completed without transferring data already held by the client.
     
    991992  <iref primary="true" item="Methods" subitem="POST" x:for-anchor=""/>
    992993<t>
    993    The POST method is used to request that the origin server accept the
     994   The POST method requests that the origin server accept the
    994995   representation enclosed in the request as data to be processed by the
    995996   target resource. POST is designed to allow a uniform method to cover the
     
    10471048  <iref primary="true" item="Methods" subitem="PUT" x:for-anchor=""/>
    10481049<t>
    1049    The PUT method is used to request that the state of the target resource
     1050   The PUT method requests that the state of the target resource
    10501051   be created or replaced with the state defined by the representation
    10511052   enclosed in the request message payload.  A successful PUT of a given
     
    11981199  <iref primary="true" item="Methods" subitem="TRACE" x:for-anchor=""/>
    11991200<t>
    1200    The TRACE method is used to invoke a remote, application-layer loop-back
     1201   The TRACE method requests a remote, application-layer loop-back
    12011202   of the request message. The final recipient of the request
    12021203   &SHOULD; reflect the message received back to the client as the
     
    12271228  <iref primary="true" item="Methods" subitem="CONNECT" x:for-anchor=""/>
    12281229<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,
    12361239</t>
    12371240<figure><artwork type="message/http; msgtype=&#34;request&#34;" x:indent-with="  ">
     
    20062009  <iref primary="true" item="Status Codes" subitem="415 Unsupported Media Type" x:for-anchor=""/>
    20072010<t>
    2008    The server is refusing to service the request because the representation of
    2009    the request is in a format not supported by the target resource
    2010    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.
    20112014</t>
    20122015</section>
     
    21702173   The "Allow" response-header field lists the set of methods advertised as
    21712174   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.
    21732176</t>
    21742177<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Allow"/><iref primary="true" item="Grammar" subitem="Allow-v"/>
     
    23902393</t>
    23912394<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.
    23932397</t>
    23942398</section>
     
    25712575<section title="Method Registry" anchor="method.registration">
    25722576<t>
    2573   The registration procedure for HTTP Methods is defined by
     2577  The registration procedure for HTTP request methods is defined by
    25742578  <xref target="method.registry"/> of this document.
    25752579</t>
     
    29762980</t>
    29772981<t>
    2978    Some methods, like TRACE (<xref target="TRACE"/>), expose information
     2982   Some request methods, like TRACE (<xref target="TRACE"/>), expose information
    29792983   that was sent in request header fields within the body of their response.
    29802984   Clients &SHOULD; be careful with sensitive information, like Cookies,
    2981    Authorization credentials and other header fields that might be used to
     2985   Authorization credentials, and other header fields that might be used to
    29822986   collect data from the client.
    29832987</t>
Note: See TracChangeset for help on using the changeset viewer.