Ignore:
Timestamp:
16/10/13 10:50:55 (7 years ago)
Author:
julian.reschke@…
Message:

Clarify that idempotency is about effects on the server, and mention that response messages may vary for repeated requests (see #501)

File:
1 edited

Legend:

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

    r2425 r2427  
    445445  }
    446446  @bottom-center {
    447        content: "Expires April 7, 2014";
     447       content: "Expires April 19, 2014";
    448448  }
    449449  @bottom-right {
     
    490490      <meta name="dct.creator" content="Reschke, J. F.">
    491491      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
    492       <meta name="dct.issued" scheme="ISO8601" content="2013-10-04">
     492      <meta name="dct.issued" scheme="ISO8601" content="2013-10-16">
    493493      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    494494      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines the semantics of HTTP/1.1 messages, as expressed by request methods, request header fields, response status codes, and response header fields, along with the payload of messages (metadata and body content) and mechanisms for content negotiation.">
     
    518518            <tr>
    519519               <td class="left">Intended status: Standards Track</td>
    520                <td class="right">October 4, 2013</td>
     520               <td class="right">October 16, 2013</td>
    521521            </tr>
    522522            <tr>
    523                <td class="left">Expires: April 7, 2014</td>
     523               <td class="left">Expires: April 19, 2014</td>
    524524               <td class="right"></td>
    525525            </tr>
     
    550550            in progress”.
    551551         </p>
    552          <p>This Internet-Draft will expire on April 7, 2014.</p>
     552         <p>This Internet-Draft will expire on April 19, 2014.</p>
    553553      </div>
    554554      <div id="rfc.copyrightnotice">
     
    14361436               <div id="rfc.iref.i.1"></div>
    14371437               <h3 id="rfc.section.4.2.2"><a href="#rfc.section.4.2.2">4.2.2</a>&nbsp;<a href="#idempotent.methods">Idempotent Methods</a></h3>
    1438                <p id="rfc.section.4.2.2.p.1">Request methods are considered "<dfn id="idempotent">idempotent</dfn>" if the intended effect of multiple identical requests is the same as for a single request. Of the request methods defined
    1439                   by this specification, the PUT, DELETE, and safe request methods are idempotent.
     1438               <p id="rfc.section.4.2.2.p.1">Request methods are considered "<dfn id="idempotent">idempotent</dfn>" if the intended effect of multiple identical requests on the server is the same as for a single request. Of the request
     1439                  methods defined by this specification, PUT, DELETE, and safe request methods are idempotent.
    14401440               </p>
    14411441               <p id="rfc.section.4.2.2.p.2">Like the definition of safe, the idempotent property only applies to what has been requested by the user; a server is free
     
    14461446                  the client is able to read the server's response. For example, if a client sends a PUT request and the underlying connection
    14471447                  is closed before any response is received, then it can establish a new connection and retry the idempotent request because
    1448                   it knows that repeating the request will have the same effect even if the original request succeeded. Note, however, that
    1449                   repeated failures would indicate a problem within the server.
     1448                  it knows that repeating the request will have the same effect even if the original request succeeded (response codes might
     1449                  vary, though). Note, however, that repeated failures would indicate a problem within the server.
    14501450               </p>
    14511451            </div>
     
    48414841            <ul>
    48424842               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/499">http://tools.ietf.org/wg/httpbis/trac/ticket/499</a>&gt;: "RFC 1305 ref needs to be updated to 5905"
     4843               </li>
     4844               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/501">http://tools.ietf.org/wg/httpbis/trac/ticket/501</a>&gt;: "idempotency: clarify 'effect'"
    48434845               </li>
    48444846            </ul>
Note: See TracChangeset for help on using the changeset viewer.