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/p1-messaging.xml

    r1159 r1161  
    14051405   because the associated response header fields (e.g., Transfer-Encoding,
    14061406   Content-Length, etc.) only indicate what their values would have been
    1407    if the method had been GET.  All 1xx (Informational), 204 (No Content),
     1407   if the request method had been GET.  All 1xx (Informational), 204 (No Content),
    14081408   and 304 (Not Modified) responses &MUST-NOT; include a message-body.
    14091409   All other responses do include a message-body, although the body
     
    16041604  <x:anchor-alias value="Method"/>
    16051605<t>
    1606    The Method  token indicates the method to be performed on the
    1607    resource identified by the request-target. The method is case-sensitive.
     1606   The Method token indicates the request method to be performed on the
     1607   target resource. The request method is case-sensitive.
    16081608</t>
    16091609<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Method"/>
     
    16151615  <x:anchor-alias value="request-target"/>
    16161616<t>
    1617    The request-target identifies the resource upon which to apply the request.
     1617   The request-target identifies the target resource upon which to apply the request.
    16181618</t>
    16191619<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="request-target"/>
     
    16301630   The asterisk "*" ("asterisk form") means that the request does not apply to a
    16311631   particular resource, but to the server itself. This is only allowed for the
    1632    OPTIONS method. Thus, the only valid example is
     1632   OPTIONS request method. Thus, the only valid example is
    16331633</t>
    16341634<figure><artwork type="message/http; msgtype=&#34;request&#34;" x:indent-with="  ">
     
    16551655</t>
    16561656<t><iref item="authority form (of request-target)"/>
    1657    The "authority form" is only used by the CONNECT method (&CONNECT;).
     1657   The "authority form" is only used by the CONNECT request method (&CONNECT;).
    16581658</t>
    16591659<t><iref item="path-absolute form (of request-target)"/>
     
    16771677</t>
    16781678<t>
    1679    If a proxy receives a request without any path in the request-target and
    1680    the method specified is capable of supporting the asterisk form of
    1681    request-target, then the last proxy on the request chain &MUST; forward the
    1682    request with "*" as the final request-target.
     1679   If a proxy receives an OPTIONS request without any path in the
     1680   request-target, then the last proxy on the request chain &MUST;
     1681   forward the request with "*" as the final request-target.
    16831682</t>
    16841683<figure><preamble>   
     
    16881687</artwork></figure>
    16891688<figure><preamble>   
    1690   would be forwarded by the proxy as
     1689  would be forwarded by the final proxy as
    16911690</preamble><artwork type="message/http; msgtype=&#34;request&#34;" x:indent-with="  ">
    16921691OPTIONS * HTTP/1.1
     
    25252524</t>
    25262525<t>
    2527    Clients &SHOULD-NOT;  pipeline requests using non-idempotent methods or
    2528    non-idempotent sequences of methods (see &idempotent-methods;). Otherwise, a
     2526   Clients &SHOULD-NOT; pipeline requests using non-idempotent request methods or
     2527   non-idempotent sequences of request methods (see &idempotent-methods;). Otherwise, a
    25292528   premature termination of the transport connection could lead to
    25302529   indeterminate results. A client wishing to send a non-idempotent
     
    26962695   transport connection and retransmit the aborted sequence of requests
    26972696   without user interaction so long as the request sequence is
    2698    idempotent (see &idempotent-methods;). Non-idempotent methods or sequences
     2697   idempotent (see &idempotent-methods;). Non-idempotent request methods or sequences
    26992698   &MUST-NOT; be automatically retried, although user agents &MAY; offer a
    27002699   human operator the choice of retrying the request(s). Confirmation by
     
    28042803        code, it &MAY; close the transport connection or it &MAY; continue
    28052804        to read and discard the rest of the request.  It &MUST-NOT;
    2806         perform the requested method if it returns a final status code.
     2805        perform the request method if it returns a final status code.
    28072806    </t>
    28082807    <t> An origin server &SHOULD-NOT;  send a 100 (Continue) response if
     
    30383037   The "Content-Length" header field indicates the size of the
    30393038   message-body, in decimal number of octets, for any message other than
    3040    a response to the HEAD method or a response with a status code of 304.
    3041    In the case of responses to the HEAD method, it indicates the size of
    3042    the payload body (not including any potential transfer-coding) that
    3043    would have been sent had the request been a GET.
    3044    In the case of the 304 (Not Modified) response, it indicates the size of
    3045    the payload body (not including any potential transfer-coding) that
    3046    would have been sent in a 200 (OK) response.
     3039   a response to a HEAD request or a response with a status code of 304.
     3040   In the case of a response to a HEAD request, Content-Length indicates
     3041   the size of the payload body (not including any potential transfer-coding)
     3042   that would have been sent had the request been a GET.
     3043   In the case of a 304 (Not Modified) response to a GET request,
     3044   Content-Length indicates the size of the payload body (not including
     3045   any potential transfer-coding) that would have been sent in a 200 (OK)
     3046   response.
    30473047</t>
    30483048<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Content-Length"/><iref primary="true" item="Grammar" subitem="Content-Length-v"/>
     
    33843384   supported protocol while indicating to the server that it would like
    33853385   to use a "better" protocol if available (where "better" is determined
    3386    by the server, possibly according to the nature of the method and/or
    3387    resource being requested).
     3386   by the server, possibly according to the nature of the request method
     3387   or target resource).
    33883388</t>
    33893389<t>
     
    48684868   since 1990. The first version of HTTP, later referred to as HTTP/0.9,
    48694869   was a simple protocol for hypertext data transfer across the Internet
    4870    with only a single method and no metadata.
     4870   with only a single request method (GET) and no metadata.
    48714871   HTTP/1.0, as defined by <xref target="RFC1945"/>, added a range of request
    48724872   methods and MIME-like messaging that could include metadata about the data
     
    50235023  Update use of abs_path production from RFC 1808 to the path-absolute + query
    50245024  components of RFC 3986. State that the asterisk form is allowed for the OPTIONS
    5025   method only.
     5025  request method only.
    50265026  (<xref target="request-target"/>)
    50275027</t>
Note: See TracChangeset for help on using the changeset viewer.