Safe:
users should be safe and should be aware of any action he takes which may have an unexpected significance to himself or others
i.e GET , HEAD only perform a get requesti.e retrieve
Clients will do n>0 requests i.e clients will make multiple requests while getting the same output
Clients can make that same call repeatedly while producing the same result.
Making multiple identical requests has the same effect as making a single request. Idempotent operations produce the same result on the server (no side effects), the response itself may not be the same (e.g. a resource’s state may change between requests).
eg. PUT and DELETE
But Delete returns 200(OK)
204(No Content)
4o4(Not Found)
once deleted and then again performing deletion will give 404 but the state on the server is the same.
It will get the output after reading the URL and now will be the same for the entire operation.
Conditional Get :-
If-Modified-Since,
If-Unmodified-Since,
If-Match,
If-None-Match,
or If-Range header field.
The PUT method requests that the enclosed entity be stored under the supplied Request-URI. If the Request-URI refers to an already existing resource, the enclosed entity SHOULD be considered as a modified version of the one residing on the origin server.
If the Request-URI does not point to an existing resource, and that URI is capable of being defined as a new resource by the requesting user agent, the origin server can create the resource with that URI.
If a new resource is created, the origin server MUST inform the user agent via the 201 (Created) response.
If an existing resource is modified, either the 200 (OK) or 204 (No Content) response codes SHOULD be sent to indicate successful completion of the request.
If the resource could not be created or modified with the Request-URI, an appropriate error response SHOULD be given that reflects the nature of the problem.
putting a resource twice no effects by using PUT while POST is not idempotent
put works as specific while POST work as abstract
We can create or update a resource using PUT and then can make the same call, again, and again, the resource is still there with the same state as it did with the first call while PUT makes two identical post requests will most result in two resources containing the same information.
if we name URL objects we create explicitly, or let the server decide? If you name them then use PUT. If you let the server decide then use POST
Jquery, it’s time to master, but how much?
Mumbai, often referred to as the financial capital of India, is a hub for businesses and industries. With countless corporate…
When it comes to security services in Noida, there are several reputable companies that cater to various needs. Let me…
Are you tired of dealing with tooth decay, gum problems, and expensive dental treatments? Look no further! Steel Bite Pro…
In the world of fine jewelry, oval moissanite rings have emerged as a captivating choice for those seeking elegance and…
Noida, located in the state of Uttar Pradesh, is a fast-growing hub of digital marketing agencies in India. Choosing the…
As we move into 2023, the world of motorcycles in India is set to see some exciting changes. Manufacturers are…
View Comments
Thanks in support of sharing such a pleasant opinion, paragraph is nice,
thats why i have read it completely
Thank you so much for your valuable feedback..
Amazing blog! Is your theme custom made or did you download it from somewhere?
A design like yours with a few simple tweeks would really make my blog jump out.
Please let me know where you got your design. Many
thanks
Thank you! It comes prebuilt but you need to customize it, how you would like to display it out. Our team will be delighted if we can aid you.Thank you.