Contents
Which rest method is safe?
An HTTP method is safe if it doesn’t alter the state of the server. In other words, a method is safe if it leads to a read-only operation. Several common HTTP methods are safe: GET , HEAD , or OPTIONS . All safe methods are also idempotent, but not all idempotent methods are safe.
Why POST method is not safe?
Since POST is not a idempotent method, calling it multiple times can result in wrong updates. What would happen if you sent out the POST request to the server, but you get a timeout.
Which HTTP method is a safe method?
Several common HTTP methods are safe: GET , HEAD , or OPTIONS . All safe methods are also idempotent, but not all idempotent methods are safe. For example, PUT and DELETE are both idempotent but unsafe. Even if safe methods have a read-only semantic, servers can alter their state: e.g. they can log or keep statistics.
Do you use put or post in rest?
If you want to use PUT, then you would do that to a particular question. Great, both can be used, so which one should I use in my RESTful design: You do not need to support both PUT and POST. Which you use is up to you. But just remember to use the right one depending on what object you are referencing in the request.
What’s the difference between a post and a put?
Some other considerations: 1 POST invalidates cached copies of the entire containing resource (better consistency) 2 PUT responses are not cacheable while POST ones are (Require Content-Location and expiration) 3 PUT is less supported by e.g. Java ME, older browsers, firewalls
What’s the difference between a put request and a POST request?
PUT replaces the resource at the known url if it already exists, so sending the same request twice has no effect. In other words, calls to PUT are idempotent. The fundamental difference between the POST and PUT requests is reflected in the different meaning of the Request-URI.
What should the client send in a put request?
The client should, in case of a PUT request, always send the entire resource, having all the data that is needed to create a new item: usually the same data as a POST-create would require.