What is the difference between a PUT and a PATCH request? скачать в хорошем качестве

What is the difference between a PUT and a PATCH request?

🔥More exclusive content: https://productioncoder.com/you-decid... Twitter:   / _jgoebel   Website: https://jangoebel.com Blog: https://productioncoder.com PATCH RFC: https://datatracker.ietf.org/doc/html... The PUT HTTP verb is used to create or replace the resource under a specific URI completely. In case the resource under a particular URI already exists, it will be completely overwritten by the payload that you send. In case the resource under the particular URI does not exist, the resource will be created. Practically speaking PUT always almost means replacing an existing resource though because most APIs will not allow the client to choose the URI of a particular resource that does not exist. In contrast, the PATCH HTTP verb describes what changes should be applied to an existing resource to create a new version. In this case, only individual fields are modified to create a newer and updated version of the resource. In some sense you could argue that PATCH is less invasive than PUT in the sense that only individual fields are updated whereas with PUT you replace the resource completely with a new state. In the wild, you will oftentimes find APIs where the HTTP verbs are not properly mapped. I.e. you might find a PUT endpoint that only replaces individual fields of a resource.