Ignore:
Timestamp:
19/01/14 02:53:35 (7 years ago)
Author:
fielding@…
Message:

(editorial) add section xrefs where the common method names are first used; see #531

File:
1 edited

Legend:

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

    r2556 r2561  
    738738   match is found:
    739739   <list style="numbers">
    740       <t>If the request is GET or HEAD and the response status code is
     740      <t>If the request method is GET or HEAD and the response status code is
    741741         <x:ref>200 (OK)</x:ref>,
    742742         <x:ref>204 (No Content)</x:ref>,
     
    745745         the payload is a representation of the resource identified by the
    746746         effective request URI (&effective-request-uri;).</t>
    747       <t>If the request is GET or HEAD and the response status code is
     747      <t>If the request method is GET or HEAD and the response status code is
    748748         <x:ref>203 (Non-Authoritative Information)</x:ref>, the payload is
    749749         a potentially modified or enhanced representation of the
     
    792792   the recipient &MAY; consider the payload to be a current representation of
    793793   that resource at the time indicated by the message origination date.
    794    For a GET or HEAD request, this is the same as the default semantics
    795    when no Content-Location is provided by the server.  For a state-changing
    796    request like PUT or POST, it implies that the server's response contains
    797    the new representation of that resource, thereby distinguishing it from
    798    representations that might only report about the action (e.g., "It worked!").
     794   For a GET (<xref target="GET"/>) or HEAD (<xref target="HEAD"/>) request,
     795   this is the same as the default semantics when no Content-Location is
     796   provided by the server.
     797   For a state-changing request like PUT (<xref target="PUT"/>) or
     798   POST (<xref target="POST"/>), it implies that the server's response
     799   contains the new representation of that resource, thereby distinguishing it
     800   from representations that might only report about the action
     801   (e.g., "It worked!").
    799802   This allows authoring applications to update their local copies without
    800803   the need for a subsequent GET request.
Note: See TracChangeset for help on using the changeset viewer.