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/p3-payload.xml

    r1153 r1161  
    14431443   For a GET or HEAD request, this is the same as the default semantics
    14441444   when no Content-Location is provided by the server.  For a state-changing
    1445    method like PUT or POST, it implies that the server's response contains
     1445   request like PUT or POST, it implies that the server's response contains
    14461446   the new representation of that resource, thereby distinguishing it from
    14471447   representations that might only report about the action (e.g., "It worked!").
     
    14601460   contains a report on the action's status and the same report is
    14611461   available (for future access with GET) at the given URI.  For
    1462    example, a purchase transaction made via the POST method might
     1462   example, a purchase transaction made via a POST request might
    14631463   include a receipt document as the payload of the 200 response;
    14641464   the Content-Location value provides an identifier for retrieving
Note: See TracChangeset for help on using the changeset viewer.