Changeset 2427

Timestamp:

Oct 16, 2013, 3:50:55 AM (6 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)

Location:

draft-ietf-httpbis/latest

Files:

• p2-semantics.html (modified) (7 diffs)
• p2-semantics.xml (modified) (3 diffs)

draft-ietf-httpbis/latest/p2-semantics.html

@@ -445 +445 @@
   }
   @bottom-center {
-       content: "Expires April 7, 2014";
+       content: "Expires April 19, 2014";
   }
   @bottom-right {
@@ -490 +490 @@
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2013-10-04">
+      <meta name="dct.issued" scheme="ISO8601" content="2013-10-16">
       <meta name="dct.replaces" content="urn:ietf:rfc:2616">
       <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.">
@@ -518 +518 @@
             <tr>
                <td class="left">Intended status: Standards Track</td>
-               <td class="right">October 4, 2013</td>
+               <td class="right">October 16, 2013</td>
             </tr>
             <tr>
-               <td class="left">Expires: April 7, 2014</td>
+               <td class="left">Expires: April 19, 2014</td>
                <td class="right"></td>
             </tr>
@@ -550 +550 @@
             in progress”.
          </p>
-         <p>This Internet-Draft will expire on April 7, 2014.</p>
+         <p>This Internet-Draft will expire on April 19, 2014.</p>
       </div>
       <div id="rfc.copyrightnotice">
@@ -1436 +1436 @@
                <div id="rfc.iref.i.1"></div>
                <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>
-               <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
-                  by this specification, the PUT, DELETE, and safe request methods are idempotent.
+               <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
+                  methods defined by this specification, PUT, DELETE, and safe request methods are idempotent.
                </p>
                <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
@@ -1446 +1446 @@
                   the client is able to read the server's response. For example, if a client sends a PUT request and the underlying connection
                   is closed before any response is received, then it can establish a new connection and retry the idempotent request because
-                  it knows that repeating the request will have the same effect even if the original request succeeded. Note, however, that
-                  repeated failures would indicate a problem within the server.
+                  it knows that repeating the request will have the same effect even if the original request succeeded (response codes might
+                  vary, though). Note, however, that repeated failures would indicate a problem within the server.
                </p>
             </div>
@@ -4841 +4841 @@
             <ul>
                <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"
+               </li>
+               <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'"
                </li>
             </ul>

draft-ietf-httpbis/latest/p2-semantics.xml

@@ -1240 +1240 @@
 <iref item="idempotent" primary="true"/>
 <t>
-   Request methods are considered
-   "<x:dfn anchor="idempotent">idempotent</x:dfn>" if the intended effect
-   of multiple identical requests is the same as for a single request.
-   Of the request methods defined by this specification, the
-   PUT, DELETE, and safe request methods are idempotent.
+   Request methods are considered "<x:dfn anchor="idempotent">idempotent</x:dfn>"
+   if the intended effect of multiple identical requests on the server is the
+   same as for a single request. Of the request methods defined by this
+   specification, PUT, DELETE, and safe request methods are idempotent.
 </t>
 <t>
@@ -1259 +1258 @@
    received, then it can establish a new connection and retry the idempotent
    request because it knows that repeating the request will have the same
-   effect even if the original request succeeded.  Note, however, that
-   repeated failures would indicate a problem within the server.
+   effect even if the original request succeeded (response codes might vary,
+   though).  Note, however, that repeated failures would indicate a problem
+   within the server.
 </t>
 </section>
@@ -6453 +6453 @@
       "RFC 1305 ref needs to be updated to 5905"
     </t>
+    <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/501"/>:
+      "idempotency: clarify 'effect'"
+    </t>
   </list>
 </t>