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/p4-conditional.xml

    r1145 r1161  
    802802   representation exists, the server &MUST-NOT; perform the requested method, and
    803803   &MUST; return a 412 (Precondition Failed) response. This behavior is
    804    most useful when the client wants to prevent an updating method, such
    805    as PUT, from modifying a resource that has changed since the client
     804   most useful when the client wants to prevent an updating request method,
     805   such as PUT, from modifying a resource that has changed since the client
    806806   last retrieved it.
    807807</t>
     
    812812</t>
    813813<t>
    814    The meaning of "If-Match: *" is that the method &SHOULD; be performed
     814   The meaning of "If-Match: *" is that the request method &SHOULD; be performed
    815815   if the representation selected by the origin server (or by a cache,
    816816   possibly using the Vary mechanism, see &header-vary;) exists, and
     
    937937<t>
    938938   This allows efficient updates of cached information with a minimum amount of
    939    transaction overhead. It is also used to prevent a method (e.g., PUT)
     939   transaction overhead. It is also used to prevent a request method (e.g., PUT)
    940940   from inadvertently modifying an existing resource when the client
    941941   believes that the resource does not exist.
     
    978978</t>
    979979<t>
    980    The meaning of "If-None-Match: *" is that the method &MUST-NOT; be
     980   The meaning of "If-None-Match: *" is that the request method &MUST-NOT; be
    981981   performed if the representation selected by the origin server (or by
    982982   a cache, possibly using the Vary mechanism, see &header-vary;)
Note: See TracChangeset for help on using the changeset viewer.