HTTPPUT vs HTTPPOST

Question

Why to use HTTPPUT when same can be done with HTTPPOST in WEBAPI

Shailesh Uke · Answer

Hello Piyush, An HTTP PUT is supposed to accept the body of the request, and then store that at the resource identified by the URI. An HTTP POST is more general. It is supposed to initiate an action on the server. That action could be to store the request body at the resource identified by the URI, or it could be a different URI, or it could be a different action. PUT is like a file upload. A put to a URI affects exactly that URI. A POST to a URI could have any effect at all. Thanks, Shailesh

Tamal Marick · Answer

I have talked about the HTTP verbs, POST and PUT. The problem is not with using which one, the problem is how to use the HTTP verbs in a way that they are meant to be used. Using bad practices, I can upload something, update something or even create a new record all using the GET method HTTP request. I can pass the data which is to be saved as a query string and there, it is saved. That is not the good way of using the HTTP verbs when you are going to publish the API someday for public. That is why, you should always go and read the actual documentation before doing something. Anyways, the HTTP verbs are used as: 1. HTTP GET: For requesting to get the resource at that URI. 2. HTTP DELETE: For requesting to delete the resource at that URI. 3. HTTP POST: For requesting to upload and save the data being uploaded to the data. Server then stores the entity and provides a new URI for that resource. 4. HTTP PUT: Same as POST but with a condition that it checks if that resources is already saved. If that resource is available then it simply updates. These are the differences in the HTTP verbs that everyone should know and should write their web APIs using HTTP as protocol, accordingly.

Rajanikant Hawaldar · Answer

Hi Piyush, HTTP POST is not idempotent, it is intended to work when you want to, let's say, add more records to the database. Increments the records always. HTTP PUT on other hand create a new record (if it doesn't exist) keeps updating it Here is complete details on HTTPPUT and HTTPPOST https://www.codeproject.com/Articles/1018082/ASP-NET-Web-API-RESTful-CRUDs-and-Windows-native Thanks

Bidyasagar Mishra · Answer

Basically we need HTTPPUT during update a record in web-api and HTTPPOST for insert records in webapi

Sanwar Ranwa · Answer

Hello Piyush The PUT method requests that the enclosed entity be stored under the supplied Request-URI.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 https://sookocheff.com/post/api/when-to-use-http-put-and-http-post/

Vishal Patel · Answer

An HTTP PUT is supposed to accept the body of the request, and then store that at the resource identified by the URI. An HTTP POST is more general. It is supposed to initiate an action on the server. That action could be to store the request body at the resource identified by the URI, or it could be a different URI, or it could be a different action. PUT is like a file upload. A put to a URI affects exactly that URI. A POST to a URI could have any effect at all.

Chittaranjan Swain · Answer

Hi Piyush, HTTPPUT used for update/Edit records and HTTPPOST used for Insert recod in API. Both are attributes.

Sonu Gupta · Answer

Hi, Go to following URL - https://www.dotnettricks.com/learn/aspnet/difference-between-httpget-and-httppost-method https://www.tutorialsteacher.com/mvc/actionverbs-in-mvc

Jignesh Kumar · Answer

Hi Piyus, Please find below link which will help you to understand. https://restfulapi.net/rest-put-vs-post/