Difference between HTTP PUT and HTTP POST Methods
| HTTP PUT | HTTP POST |
|---|---|
PUT request is made to a particular resource. 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 the POST-request-URIclient is allowed to determine resource identifier). Example: PUT /article/{article-id} | POST 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 POST-request-URI should be a collection URI. Example: POST /articles |
That method is idempotent. So if you send retry a request multiple times, that should be equivalent to a single request modification. | POST is NOT idempotent. So if you retry the request N times, you will end up having N resources with N different URIs created on the server. |
Use PUT when you want to modify a single resource that is already a part of the resources collection. PUT overwrites the resource in its entirety. Use PATCH if the request updates part of the resource. | Use POST when you want to add a child resource under resources collection. |
Generally, in practice, always use PUT for UPDATE operations. | Always use POST for CREATE operations. |
Difference between PUT and POST HTTP requests
Pre-Requisite: Hyper Text Transfer Protocol
PUT and POST requests have lots of similarities certainly when making an HTTP request and both can be meddled with so that one performs the functions of the other. This article revolves around the major differences between PUT and POST Requests.