What is the difference between PUT, POST and PATCH?

Question

What is the difference between the PUT, POST, and PATCH methods in the HTTP protocol?

Answer 1

MESSAGE

HTTP.POST can be used when the client sends data to the server, and the server determines the URI for the newly created resource. The POST method is used to request that the source server accept the object included in the request as a new subordinate resource identified by the Request-URI in the query string.

GOT

HTTP.PUT can be used when the client sends data to the server, and the client determines the URI for the newly created resource. The PUT method requests that the nested object be stored under the provided Request-URI. If the Request-URI refers to an existing resource, the nested object SHOULD be considered as a modified version located on the source server. If the Request-URI does not indicate an existing resource, and this URI can be defined as a new resource by the requesting user agent, the source server can create a resource with this URI.

PATCH

HTTP.PATCH can be used when a client sends one or more changes that will be applied by the server. The PATCH method requests that the set of changes described in the request object be applied to the resource identified by the Request-URI. A set of changes is presented in a format called a patch document.

Refer to the URL below for more information.

POST vs. REST MAIL

Answer 2

The difference between the PUT, POST, GET, DELETE, and PATCH IN HTTP commands:

The most commonly used HTTP verbs POST, GET, PUT, DELETE are similar to CRUD operations (create, read, update and delete) in a database. We indicate these HTTP verbs in case of capitalization . So below is a comparison between the two.

1. create - POST
2. read - GET
3. update - PUT
4. delete - REMOVE

PATCH: Represents a partial modification of a resource. If you need to update only one field for a resource, you can use the PATCH method.

Note:
Since POST, PUT, DELETE change the content, the tests with Fiddler for the URL below simply mimic the updates. It does not delete or change in fact. We can just see the status codes to check if inserts, updates, deletes are occurring.

URL: http://jsonplaceholder.typicode.com/posts/

1) GET:

GET is the simplest type of HTTP request method; the one that browsers use every time you click on a link or enter a URL in the address bar. It tells the server to pass the data identified by the URL to the client. Data should never change on the server side as a result of a GET request. In this sense, the GET request is read-only.

Verification with Fiddler or PostMan: We can use Fiddler to verify the response. Open Fiddler and select the Compose tab. Enter the verb and URL as shown below and click "Run" to check the response.

Verb: GET

URL: http://jsonplaceholder.typicode.com/posts/

Answer: You will get an answer like:

"userId": 1, "id": 1, "title": "sunt aut ...", "body": "quia et suscipit ..."

In a “happy” (or non-error) path, GET returns a view in XML or JSON and an HTTP 200 response code (OK). In case of an error, it most often returns 404 (NOT FOUND) or 400 (BAD REQUEST).

2) POST:

The POST verb is mainly used to create new resources. In particular, it is used to create subordinate resources. That is, obey any other (e.g. parent) resource.

If successful, return HTTP status 201 by returning the Location header with a link to the newly created resource with HTTP status 201.

Verification with Fiddler or PostMan: We can use Fiddler to verify the response. Open Fiddler and select the Compose tab. Enter the verb and URL as shown below and click "Run" to check the response.

Verb: POST

URL: http://jsonplaceholder.typicode.com/posts/

Request body:

data: {title: 'foo', body: "bar", user ID: 1000, Id: 1000}

Answer: You will receive a 201 response code.

If we want to check the inserted record with Id = 1000, change the verb to Get and use the same URL and click Run.

As mentioned earlier, the above URL allows read only (GET), we cannot read the updated data in real time.

3) PUT:

PUT is most often used to update capabilities, PUT is for a known resource URI with a request body containing a recently updated representation of the original resource.

Verification with Fiddler or PostMan: We can use Fiddler to verify the response. Open Fiddler and select the Compose tab. Enter the verb and URL as shown below and click "Run" to check the response.

Verb: PUT

URL: http://jsonplaceholder.typicode.com/posts/1

Request body:

data: {title: 'foo', body: "bar", user ID: 1, Id: 1}

Answer: On a successful update, it returns 200 (or 204 if it does not return any content in the body) from PUT.

4) REMOVE:

DELETE is pretty easy to understand. It is used to delete a resource identified by a URI.

If the deletion is successful, return the HTTP status 200 (OK) along with the response body, possibly representing the deleted element (often requiring too much bandwidth) or a wrapped response (see "Return Values" below). Either so, or return the HTTP status 204 (NO CONTENT) without the response body. In other words, a status of 204 without a body or a JSEND-style response and an HTTP status of 200 are recommended answers.

Verification with Fiddler or PostMan: We can use Fiddler to verify the response. Open Fiddler and select the Compose tab. Enter the verb and URL as shown below and click "Run" to check the response.

Verb: DELETE

URL: http://jsonplaceholder.typicode.com/posts/1

Answer: Upon successful removal, the HTTP status 200 (OK) is returned along with the response body.

Example between PUT and PATCH

Put

If I had to change my name, send a PUT request for update:

{"first": "Nazmul", "last": "hasan"} So, here, to update the name, we need to send all the data parameters again.

PATCH:

A request for correction indicates that we will only send the data that we need to change, without changing or affecting other parts of the data. Example: if we need to update only the name, we pass only the name.

Please refer to the links below for more information:

https://jsonplaceholder.typicode.com/

https://github.com/typicode/jsonplaceholder#how-to

What is the main difference between PATCH and PUT requests?

http://www.restapitutorial.com/lessons/httpmethods.html

Answer 3

PUT = replace FULL RESOURCE with a new view

PATCH = replace parts of the original resource with the values ​​provided by AND | OR other parts of the resource updated that you provided (timestamps) AND | OR updated resource effects with other resources (relationships)

https://laracasts.com/discuss/channels/general-discussion/whats-the-differences-between-put-and-patch?page=1

Answer 4

Types of Queries

• create - POST
• read - GET
• create or update - PUT
• delete - REMOVE
• update - PATCH

GET / PUT is idempotent. A patch can sometimes be idempotent.

What is idempotent - This means that if we run the request several times, this should not affect its result (the same result. Suppose the cow is pregnant, and if we breed her again, then she cannot be pregnant several times)

get : -

just get it. Get data from the server and show it to the user

 { id:1 name:parth email:[e-mail] } 

post : -

create a new resource in the database. This means that it is adding new data. This is not idempotent.

put : -

Create a new resource, otherwise add to the existing one. Idempotent, because it will update the same resource every time, and the result will be the same. ex. - initial data

 { id:1 name:parth email:[e-mail] } 

• run put-localhost / 1 specify the email address: [e-mail]

 { id:1 email:[e-mail] } 

patch

so now the patch request has come The patch may be sometimes idempotent

 id:1 name:parth email:[e-mail] } 

patch name: w

 { id:1 name:w email:[e-mail] } 

 HTTP Method
 Get yes
 Post no
 Put yes
 PATCH no *
 OPTIONS yes
 HEAD yes
 DELETE yes

Resources: Idempotent - What is Idempotency?

Answer 5

The following definition is taken from an example from the real world.

Sample review
For each client information, we store an identifier to find this client data, and we will send this identifier to the client for reference.

1. MESSAGE

   • If the Client sends data without an identifier using the POST method, we save it and assign a new identifier.
   • If the Client again sends the same data without an identifier using the POST method, we save it and assign a new identifier.
   • Note : duplication is allowed here

2. GOT

   • If the Client sends data with an identifier, we will check whether this identifier exists. If the identifier exists, we will update the data, otherwise we will create it and assign a new identifier.

3. PATCH

   • If the Client sends data with an identifier, we will check whether this identifier exists. If the identifier exists, we will update the data, otherwise we will throw an exception.

Note. In the Put method, we do not throw an exception if the identifier is not found. But in the Patch method, we throw an exception if the identifier is not found.

Let me know if you have any questions about the above.

Answer 6

The main difference between PUT and PATCH requests:

Suppose we have a resource that contains the person’s name and surname.

If we want to change the name, we send an update request to update

{ "first": "Michael", "last": "Angelo" }

Here, although we only change the name, with the help of the PUT request, we must send both parameters: the first and the last.
In other words, you need to send all the values ​​again, all the payload.

However, when we send a PATCH request, we send only the data that we want to update. In other words, we only send the name for updating, no need to send the last name.

Answer 7

The following definition from a real example 1.POST: for each client, we store an identifier to find this client data.

Answer 8

Here is the difference between the POST, PUT, and PATCH methods of the HTTP protocol.

Post

The HTTP.POST method always creates a new resource on the server. His non-idempotent request, i.e. If the user accesses the same requests 2 times, he will create a new new resource if there are no restrictions.

http post method is like a INSERT query in SQL which always creates a new record in database.

Example. Use the POST method to save the new user, order, etc., when the server server decides on the resource identifier for the new resource.

Put

In the HTTP.PUT method, the resource is first identified from the URL, and if it exists, it is updated, otherwise a new resource is created. When the target resource exists, it overwrites that resource with a complete new body. This is the HTTP.PUT method used to CREATE or UPDATE a resource.

http put method is like a MERGE query in SQL which inserts or updates a record depending upon whether the given record exists.

The PUT request is idempotent, i.e. beats of the same queries will double-update the existing record (no new record is created). In the PUT method, the resource identifier is determined by the client and is specified in the request URL.

Example. Use the PUT method to update an existing user or order.

PATCH

The HTTP.PATCH method is used for partial modifications of a resource update, that is, a delta update.

http patch method is like a UPDATE query in SQL which sets or updates selected columns only and not the whole row.

Example. You can use the PATCH method to update the order status.

PATCH / api / users / 40450236 / order / 10234557

Request body: {status: 'Delivered'}