Ignore:
Timestamp:
09/11/13 01:30:29 (7 years ago)
Author:
fielding@…
Message:

(editorial) slight wording change to [2427] for idempotent methods; see #501

File:
1 edited

Legend:

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

    r2477 r2481  
    12401240<iref item="idempotent" primary="true"/>
    12411241<t>
    1242    Request methods are considered "<x:dfn anchor="idempotent">idempotent</x:dfn>"
    1243    if the intended effect of multiple identical requests on the server is the
    1244    same as for a single request. Of the request methods defined by this
     1242   A request method is considered
     1243   "<x:dfn anchor="idempotent">idempotent</x:dfn>"
     1244   if the intended effect on the server of multiple identical requests with
     1245   that method is the same as the effect for a single such request.
     1246   Of the request methods defined by this
    12451247   specification, PUT, DELETE, and safe request methods are idempotent.
    12461248</t>
     
    12561258   able to read the server's response.  For example, if a client sends a PUT
    12571259   request and the underlying connection is closed before any response is
    1258    received, then it can establish a new connection and retry the idempotent
    1259    request because it knows that repeating the request will have the same
    1260    effect even if the original request succeeded (response codes might vary,
    1261    though).  Note, however, that repeated failures would indicate a problem
    1262    within the server.
     1260   received, then the client can establish a new connection and retry the
     1261   idempotent request because it knows that repeating the request will have
     1262   the same effect (even if the original request succeeded, though the
     1263   status codes might differ in response).
     1264   Note, however, that repeated communication failures might indicate that
     1265   the server has failed in general, or that something in the request is
     1266   triggering a connection drop.
    12631267</t>
    12641268</section>
Note: See TracChangeset for help on using the changeset viewer.