Changeset 2427
- Timestamp:
- 16/10/13 10:50:55 (9 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r2425 r2427 445 445 } 446 446 @bottom-center { 447 content: "Expires April 7, 2014";447 content: "Expires April 19, 2014"; 448 448 } 449 449 @bottom-right { … … 490 490 <meta name="dct.creator" content="Reschke, J. F."> 491 491 <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"> 493 493 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 494 494 <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> 519 519 <td class="left">Intended status: Standards Track</td> 520 <td class="right">October 4, 2013</td>520 <td class="right">October 16, 2013</td> 521 521 </tr> 522 522 <tr> 523 <td class="left">Expires: April 7, 2014</td>523 <td class="left">Expires: April 19, 2014</td> 524 524 <td class="right"></td> 525 525 </tr> … … 550 550 in progress”. 551 551 </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> 553 553 </div> 554 554 <div id="rfc.copyrightnotice"> … … 1436 1436 <div id="rfc.iref.i.1"></div> 1437 1437 <h3 id="rfc.section.4.2.2"><a href="#rfc.section.4.2.2">4.2.2</a> <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 defined1439 by this specification, thePUT, 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. 1440 1440 </p> 1441 1441 <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 1447 1447 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, that1449 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. 1450 1450 </p> 1451 1451 </div> … … 4841 4841 <ul> 4842 4842 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/499">http://tools.ietf.org/wg/httpbis/trac/ticket/499</a>>: "RFC 1305 ref needs to be updated to 5905" 4843 </li> 4844 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/501">http://tools.ietf.org/wg/httpbis/trac/ticket/501</a>>: "idempotency: clarify 'effect'" 4843 4845 </li> 4844 4846 </ul> -
draft-ietf-httpbis/latest/p2-semantics.xml
r2425 r2427 1240 1240 <iref item="idempotent" primary="true"/> 1241 1241 <t> 1242 Request methods are considered 1243 "<x:dfn anchor="idempotent">idempotent</x:dfn>" if the intended effect 1244 of multiple identical requests is the same as for a single request. 1245 Of the request methods defined by this specification, the 1246 PUT, DELETE, and safe request methods are idempotent. 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 1245 specification, PUT, DELETE, and safe request methods are idempotent. 1247 1246 </t> 1248 1247 <t> … … 1259 1258 received, then it can establish a new connection and retry the idempotent 1260 1259 request because it knows that repeating the request will have the same 1261 effect even if the original request succeeded. Note, however, that 1262 repeated failures would indicate a problem within the server. 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. 1263 1263 </t> 1264 1264 </section> … … 6453 6453 "RFC 1305 ref needs to be updated to 5905" 6454 6454 </t> 6455 <t> 6456 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/501"/>: 6457 "idempotency: clarify 'effect'" 6458 </t> 6455 6459 </list> 6456 6460 </t>
Note: See TracChangeset
for help on using the changeset viewer.