HTTP POST vs PUT

[teazean]

link: https://restfulapi.net/rest-put-vs-post/

PUT	POST
RFC-2616 clearly mention that PUT method requests for the enclosed entity be stored under the supplied Request-URI. 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).	The 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 of a collection URI.
PUT /questions/{question-id}	POST /questions
PUT method is idempotent.	POST is NOT idempotent.
Use PUT 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.	Use POST when you want to add a child resource under resources collection.