http put和post的区别

拼搏现实的明天。 2023-07-17 15:59 40阅读 0赞

<table> 
 <tbody> 
  <tr> 
   <th><strong>PUT</strong></th> 
   <th><strong>POST</strong></th> 
  </tr> 
  <tr> 
   <td>RFC-2616 clearly mention that&nbsp;<code>PUT</code>&nbsp;method requests for the enclosed entity be stored under the supplied&nbsp;<a href="https://restfulapi.net/resource-naming/" rel="nofollow">Request-URI</a>. If the Request-URI refers to an already existing resource – an update operation will happen, otherwise create operation should happen if Request-URI is a valid resource URI (assuming client is allowed to determine resource identifier). <p>&nbsp;</p> <pre>PUT /questions/{question-id}</pre> </td> 
   <td>The&nbsp;<code>POST</code>&nbsp;method is used to request that the origin server accept the entity enclosed in the request as a new subordinate of the resource identified by the Request-URI in the Request-Line. It essentially means that&nbsp;<code>POST</code>&nbsp;request-URI should be of a collection URI. <p>&nbsp;</p> <pre>POST /questions</pre> </td> 
  </tr> 
  <tr> 
   <td><code>PUT</code>&nbsp;method is&nbsp;<a href="https://restfulapi.net/idempotent-rest-apis/" rel="nofollow">idempotent</a>. So if you send retry a request multiple times, that should be equivalent to single request modification.</td> 
   <td><code>POST</code>&nbsp;is NOT idempotent. So if you retry the request N times, you will end up having N resources with N different URIs created on server.</td> 
  </tr> 
  <tr> 
   <td>Use&nbsp;<code>PUT</code>&nbsp;when you want to modify a singular resource which is already a part of resources collection. PUT replaces the resource in its entirety. Use PATCH if request updates part of the resource.</td> 
   <td>Use&nbsp;<code>POST</code>&nbsp;when you want to add a child resource under resources collection.</td> 
  </tr> 
  <tr> 
   <td>Though&nbsp;<code>PUT</code>&nbsp;is idempotent, we shall not cache it’s response.</td> 
   <td>Responses to this method are not&nbsp;<a href="https://restfulapi.net/caching/" rel="nofollow">cacheable</a>, unless the response includes appropriate Cache-Control or Expires header fields. However, the 303 (See Other) response can be used to direct the user agent to retrieve a cacheable resource.</td> 
  </tr> 
  <tr> 
   <td>Generally, in practice, always use&nbsp;<code>PUT</code>&nbsp;for UPDATE operations.</td> 
   <td>Always use&nbsp;<code>POST</code>&nbsp;for CREATE operations.</td> 
  </tr> 
 </tbody> 
</table>