05/07/12 17:20:04 (9 years ago)

add idempotency to the registration fields for new methods (see #364)

1 edited


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

    r1727 r1728  
    922922         <li>Safe ("yes" or "no", see <a href="#safe.methods" title="Safe Methods">Section&nbsp;2.1.1</a>)
    923923         </li>
     924         <li>Idempotent ("yes" or "no", see <a href="#safe.methods" title="Safe Methods">Section&nbsp;2.1.1</a>)
     925         </li>
    924926         <li>Pointer to specification text</li>
    925927      </ul>
    10311033      <p id="rfc.section.2.3.4.p.6">Note that POST caching is not widely implemented. However, the <a href="#status.303" class="smpl">303 (See Other)</a> response can be used to direct the user agent to retrieve a cacheable representation of the resource.
    10321034      </p>
     1035      <h3 id="rfc.section.2.3.5"><a href="#rfc.section.2.3.5">2.3.5</a>&nbsp;<a id="PUT" href="#PUT">PUT</a></h3>
    10331036      <div id="rfc.iref.p.2"></div>
    10341037      <div id="rfc.iref.m.5"></div>
    1035       <h3 id="rfc.section.2.3.5"><a href="#rfc.section.2.3.5">2.3.5</a>&nbsp;<a id="PUT" href="#PUT">PUT</a></h3>
    10361038      <p id="rfc.section.2.3.5.p.1">The PUT method requests that the state of the target resource be created or replaced with the state defined by the representation
    10371039         enclosed in the request message payload. A successful PUT of a given representation would suggest that a subsequent GET on
    10901092         for the effective request URI, those stored responses will be invalidated (see <a href="p6-cache.html#invalidation.after.updates.or.deletions" title="Request Methods that Invalidate">Section 2.6</a> of <a href="#Part6" id="rfc.xref.Part6.5"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).
    10911093      </p>
     1094      <h3 id="rfc.section.2.3.6"><a href="#rfc.section.2.3.6">2.3.6</a>&nbsp;<a id="DELETE" href="#DELETE">DELETE</a></h3>
    10921095      <div id="rfc.iref.d.1"></div>
    10931096      <div id="rfc.iref.m.6"></div>
    1094       <h3 id="rfc.section.2.3.6"><a href="#rfc.section.2.3.6">2.3.6</a>&nbsp;<a id="DELETE" href="#DELETE">DELETE</a></h3>
    10951097      <p id="rfc.section.2.3.6.p.1">The DELETE method requests that the origin server delete the target resource. This method <em class="bcp14">MAY</em> be overridden by human intervention (or other means) on the origin server. The client cannot be guaranteed that the operation
    10961098         has been carried out, even if the status code returned from the origin server indicates that the action has been completed
    31083110                  <th>Method</th>
    31093111                  <th>Safe</th>
     3112                  <th>Idempotent</th>
    31103113                  <th>Reference</th>
    31113114               </tr>
    31153118                  <td class="left">CONNECT</td>
    31163119                  <td class="left">no</td>
     3120                  <td class="left">no</td>
    31173121                  <td class="left"> <a href="#CONNECT" id="rfc.xref.CONNECT.1" title="CONNECT">Section&nbsp;2.3.8</a>
    31183122                  </td>
    31213125                  <td class="left">DELETE</td>
    31223126                  <td class="left">no</td>
     3127                  <td class="left">yes</td>
    31233128                  <td class="left"> <a href="#DELETE" id="rfc.xref.DELETE.1" title="DELETE">Section&nbsp;2.3.6</a>
    31243129                  </td>
    31273132                  <td class="left">GET</td>
    31283133                  <td class="left">yes</td>
     3134                  <td class="left">yes</td>
    31293135                  <td class="left"> <a href="#GET" id="rfc.xref.GET.1" title="GET">Section&nbsp;2.3.2</a>
    31303136                  </td>
    31333139                  <td class="left">HEAD</td>
    31343140                  <td class="left">yes</td>
     3141                  <td class="left">yes</td>
    31353142                  <td class="left"> <a href="#HEAD" id="rfc.xref.HEAD.1" title="HEAD">Section&nbsp;2.3.3</a>
    31363143                  </td>
    31393146                  <td class="left">OPTIONS</td>
    31403147                  <td class="left">yes</td>
     3148                  <td class="left">yes</td>
    31413149                  <td class="left"> <a href="#OPTIONS" id="rfc.xref.OPTIONS.2" title="OPTIONS">Section&nbsp;2.3.1</a>
    31423150                  </td>
    31453153                  <td class="left">POST</td>
    31463154                  <td class="left">no</td>
     3155                  <td class="left">no</td>
    31473156                  <td class="left"> <a href="#POST" id="rfc.xref.POST.1" title="POST">Section&nbsp;2.3.4</a>
    31483157                  </td>
    31513160                  <td class="left">PUT</td>
    31523161                  <td class="left">no</td>
     3162                  <td class="left">yes</td>
    31533163                  <td class="left"> <a href="#PUT" id="rfc.xref.PUT.1" title="PUT">Section&nbsp;2.3.5</a>
    31543164                  </td>
    31563166               <tr>
    31573167                  <td class="left">TRACE</td>
     3168                  <td class="left">yes</td>
    31583169                  <td class="left">yes</td>
    31593170                  <td class="left"> <a href="#TRACE" id="rfc.xref.TRACE.2" title="TRACE">Section&nbsp;2.3.7</a>
    47274738         </li>
    47284739         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/361">http://tools.ietf.org/wg/httpbis/trac/ticket/361</a>&gt;: "ABNF requirements for recipients"
     4740         </li>
     4741         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/364">http://tools.ietf.org/wg/httpbis/trac/ticket/364</a>&gt;: "Capturing more information in the method registry"
    47294742         </li>
    47304743      </ul>
Note: See TracChangeset for help on using the changeset viewer.