blocks|key|1536591|text|给出REST风格资源的示例：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1536592|包含大量图书信息的POST+/books可能会创建一本新书，并返回标识该书的新URL：/books/5。|offset|length|style|CODE|1536593|PUT+/books/5必须创建一个id为5的新书，或者用ID+5替换现有的书。|1536594|在非资源风格中，POST几乎可以用于任何有副作用的事情。另一个不同之处在于PUT应该是幂等的--将相同数据的多个PUTs指向相同的URL应该是可以的，而多个POSTs可能会创建多个对象，或者无论您的POST操作做什么。|1536595|entityMap^0|0|9|B|17|8|0|0|C|0|8|4|11|3|1K|4|26|5|2R|4|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@$D|P|E|Q|F|G]|$D|R|E|S|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|T|8|@$D|U|E|V|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|W|8|@$D|X|E|Y|F|G]|$D|Z|E|10|F|G]|$D|11|E|12|F|G]|$D|13|E|14|F|G]|$D|15|E|16|F|G]]|9|@]|A|$]]|$1|L|3|-4|5|6|7|17|8|@]|9|@]|A|$]]]|M|$]]

To give examples of REST-style resources:
<code>POST /books</code> with a bunch of book information might create a new book, and respond with the new URL identifying that book: <code>/books/5</code>.
<code>PUT /books/5</code> would have to either create a new book with the id of 5, or replace the existing book with ID 5.
In non-resource style, <code>POST</code> can be used for just about anything that has a side effect. One other difference is that <code>PUT</code> should be idempotent - multiple <code>PUTs</code> of the same data to the same URL should be fine, whereas multiple <code>POSTs</code> might create multiple objects or whatever it is your <code>POST</code> action does.

blocks|key|1536490|text|PUT是一种用于将内容“上传”到特定URI或覆盖该URI中已有内容的方法。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1536491|另一方面，POST是提交与给定URI相关的数据的一种方式。|1536492|请参阅the+HTTP+RFC|offset|length|1536493|entityMap|0|LINK|mutability|MUTABLE|url|http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.6^0|0|0|3|C|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@$F|S|G|T|1|U]]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

PUT is meant as a a method for "uploading" stuff to a particular URI, or overwriting what is already in that URI.

POST, on the other hand, is a way of submitting data RELATED to a given URI.

Refer to <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.6" rel="noreferrer">the HTTP RFC</a>

blocks|key|1751620|text|其他人已经发布了很好的答案，我只想补充说，对于大多数语言、框架和用例，您将比PUT更经常地处理POST。到了PUT,+DELETE,等基本上都是琐碎问题的地步。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1751621|entityMap^0|12|3|1B|4|1I|C|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|O|8|@]|D|@]|E|$]]]|G|$]]

Others have already posted excellent answers, I just wanted to add that with most languages, frameworks, and use cases you'll be dealing with <code>POST</code> much, much more often than <code>PUT</code>. To the point where <code>PUT, DELETE,</code> etc. are basically trivia questions.

blocks|key|1536537|text|POST被认为是某种工厂类型的方法。您可以将数据包含在其中以创建您想要的内容，而另一端的任何内容都知道如何处理这些数据。PUT用于更新给定URL上的现有数据，或者当您知道URI将是什么而它还不存在时创建新的东西(与POST相反，POST将创建东西并在必要时返回URL+)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1536538|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

A POST is considered something of a factory type method. You include data with it to create what you want and whatever is on the other end knows what to do with it. A PUT is used to update existing data at a given URL, or to create something new when you know what the URI is going to be and it doesn't already exist (as opposed to a POST which will create something and return a URL to it if necessary).

blocks|key|1536735|text|POST和PUT的区别在于PUT是幂等的，这意味着多次调用相同的PUT请求将始终产生相同的结果(即没有副作用)，而另一方面，重复调用POST请求可能会产生多次创建相同资源的(额外)副作用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1536736|GET：使用GET的请求仅检索数据，即它请求指定资源的表示形式|offset|length|style|CODE|1536737|POST：它将数据发送到服务器以创建资源。请求主体的类型由Content-Type头指示。它通常会导致状态更改或对服务器产生副作用|1536738|PUT：创建新资源或用请求有效负载替换目标资源的表示形式|1536739|PATCH：用于对资源进行部分修改|1536740|DELETE：删除指定的资源|1536741|TRACE：它沿着目标资源的路径执行消息回送测试，提供了一种有用的调试机制|1536742|OPTIONS：用于描述目标资源的通信选项，客户端可以为options方法指定一个URL，也可以指定一个星号(*)来引用整个服务器。|1536743|HEAD：它请求与GET请求相同的响应，但没有响应体|1536744|CONNECT：建立到目标资源所标识的服务器的隧道，可用于访问使用SSL的网站|1536745|entityMap^0|0|0|3|0|0|4|0|0|3|0|0|5|0|0|6|0|0|5|0|0|7|0|0|4|0|0|7|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|10|8|@$D|11|E|12|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|13|8|@$D|14|E|15|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|16|8|@$D|17|E|18|F|G]]|9|@]|A|$]]|$1|L|3|M|5|6|7|19|8|@$D|1A|E|1B|F|G]]|9|@]|A|$]]|$1|N|3|O|5|6|7|1C|8|@$D|1D|E|1E|F|G]]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1F|8|@$D|1G|E|1H|F|G]]|9|@]|A|$]]|$1|R|3|S|5|6|7|1I|8|@$D|1J|E|1K|F|G]]|9|@]|A|$]]|$1|T|3|U|5|6|7|1L|8|@$D|1M|E|1N|F|G]]|9|@]|A|$]]|$1|V|3|W|5|6|7|1O|8|@$D|1P|E|1Q|F|G]]|9|@]|A|$]]|$1|X|3|-4|5|6|7|1R|8|@]|9|@]|A|$]]]|Y|$]]

The difference between POST and PUT is that PUT is idempotent, that means, calling the same PUT request multiple times will always produce the same result(that is no side effect), while on the other hand, calling a POST request repeatedly may have (additional) side effects of creating the same resource multiple times.

<code>GET</code> : Requests using GET only retrieve data , that is it requests a representation of the specified resource

<code>POST</code> : It sends data to the server to create a resource. The type of the body of the request is indicated by the Content-Type header. It often causes a change in state or side effects on the server

<code>PUT</code> : Creates a new resource or replaces a representation of the target resource with the request payload

<code>PATCH</code> : It is used to apply partial modifications to a resource

<code>DELETE</code> : It deletes the specified resource

<code>TRACE</code> : It performs a message loop-back test along the path to the target resource, providing a useful debugging mechanism

<code>OPTIONS</code> : It is used to describe the communication options for the target resource, the client can specify a URL for the OPTIONS method, or an asterisk (*) to refer to the entire server.

<code>HEAD</code> : It asks for a response identical to that of a GET request, but without the response body

<code>CONNECT</code> : It establishes a tunnel to the server identified by the target resource , can be used to access websites that use SSL (HTTPS)

blocks|key|1536990|text|简单来说，你可以说：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1536991|1.+1.HTTP+:用于获取一个或多个项|1536992|2.+2.HTTP+:用于创建项目|1536993|3.HTTP+Put:用于更新项目|1536994|4.+4.HTTP补丁:用于部分更新项目|1536995|5.+5.HTTP+:删除项目|1536996|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Q|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

In simple words you can say:

1.HTTP Get:It is used to get one or more items

2.HTTP Post:It is used to create an item

3.HTTP Put:It is used to update an item

4.HTTP Patch:It is used to partially update an item

5.HTTP Delete:It is used to delete an item

blocks|key|1536868|text|实际上，除了它们的标题之外，没有其他区别。GET和其他代码之间实际上有一个基本的区别。使用"GET"-Request方法，您可以在url-address-line中发送数据，这些数据首先用问号分隔，然后用&号分隔。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1536869|但是使用"POST"-request方法，你不能通过url传递数据，但你必须在所谓的请求“主体”中将数据作为对象传递。在服务器端，您必须读出接收到的内容的主体，才能获得发送的数据。但另一方面，当你发送一个"GET"-Request时，就不可能在正文中发送内容了。|1536870|"GET“只用于获取数据，"POST”用于发布数据的说法是完全错误的。没有人可以阻止你创建新的内容，删除已有的内容，编辑已有的内容或在后台做任何事情，基于"GET“请求或"POST”请求发送的数据。而且没有人能阻止你以某种方式编写后端代码，即通过"POST"-Request，客户端请求一些数据。|1536871|对于请求，无论您使用哪种方法，您都可以调用URL并发送或不发送一些数据来指定您想要传递给服务器以处理您的请求的信息，然后客户端从服务器获得答案。数据可以包含您想要发送的任何内容，允许后端对数据做任何它想要做的事情，响应可以包含您想放入其中的任何信息。|1536872|只有这两种基本方法。GET和POST。但这是它们的结构，这使得它们不同，而不是你在后端编写的代码。在后端，你可以使用接收到的数据编写任何你想要的代码。但是对于"POST"-request，你必须在正文中发送/检索数据，而不是在url-addressline中；而对于"GET“请求，你必须在url-addressline中发送/检索数据，而不是在正文中。就这样。|1536873|所有其他的方法，如"PUT“、"DELETE”等等，它们都与"POST“具有相同的结构。|1536874|POST方法主要用于，如果你想隐藏一些内容，因为无论你在url-addressline行中写什么，它都会被保存在缓存中，GET-Method与用数据写一个url-addressline行是一样的。因此，如果您想发送敏感数据，这些数据不一定是用户名和密码，但例如一些in或散列，您不希望它们显示在url-address-line中，那么您应该使用POST方法。|1536875|此外，URL-Addressline的长度限制为1024个符号，而"POST"-Method则不受限制。因此，如果您有更多的数据，您可能无法使用GET-Request发送它，但需要使用POST-Request。因此，这也是POST请求的另一个加分点。|1536876|但是，当您没有复杂的文本要发送时，处理GET-request要容易得多。否则，这是POST方法的另一个优点，即使用GET方法，您需要对文本进行url编码，以便能够在文本中甚至空格中发送一些符号。但是使用POST方法，您没有任何限制，并且您的内容不需要以任何方式进行更改或操作。|1536877|entityMap^0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|Y|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|Z|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|10|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|11|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|S|$]]

Actually there's no difference other than their title. There's actually a basic difference between GET and the others. With a "GET"-Request method, you send the data in the url-address-line, which are separated first by a question-mark, and then with a &amp; sign.

But with a "POST"-request method, you can't pass data through the url, but you have to pass the data as an object in the so called "body" of the request. On the server side, you have then to read out the body of the received content in order to get the sent data.
But there's on the other side no possibility to send content in the body, when you send a "GET"-Request.

The claim, that "GET" is only for getting data and "POST" is for posting data, is absolutely wrong. Noone can prevent you from creating new content, deleting existing content, editing existing content or do whatever in the backend, based on the data, that is sent by the "GET" request or by the "POST" request. And nobody can prevent you to code the backend in a way, that with a "POST"-Request, the client asks for some data.

With a request, no matter which method you use, you call a URL and send or don't send some data to specify, which information you want to pass to the server to deal with your request, and then the client gets an answer from the server. The data can contain whatever you want to send, the backend is allowed to do whatever it wants with the data and the response can contain any information, that you want to put in there.

There are only these two BASIC METHODS. GET and POST. But it's their structure, which makes them different and not what you code in the backend. In the backend you can code whatever you want to, with the received data. But with the "POST"-request you have to send/retrieve the data in the body and not in the url-addressline, and with a "GET" request, you have to send/retrieve data in the url-addressline and not in the body. That's all. 

All the other methods, like "PUT", "DELETE" and so on, they have the same structure as "POST". 

The POST Method is mainly used, if you want to hide the content somewhat, because whatever you write in the url-addressline, this will be saved in the cache and a GET-Method is the same as writing a url-addressline with data. So if you want to send sensitive data, which is not always necessarily username and password, but for example some ids or hashes, which you don't want to be shown in the url-address-line, then you should use the POST method.

Also the URL-Addressline's length is limited to 1024 symbols, whereas the "POST"-Method is not restricted. So if you have a bigger amount of data, you might not be able to send it with a GET-Request, but you'll need to use the POST-Request. So this is also another plus point for the POST-request.

But dealing with the GET-request is way easier, when you don't have complicated text to send.
Otherwise, and this is another plus point for the POST method, is, that with the GET-method you need to url-encode the text, in order to be able to send some symbols within the text or even spaces. But with a POST method you have no restrictions and your content doesn't need to be changed or manipulated in any way.

blocks|key|1536928|text|PUT和POST都是Rest方法。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1536929|PUT+-如果我们使用两次使用相同参数的PUT发出相同的请求两次，那么第二次请求将不会有任何效果。这就是为什么PUT通常用于Update场景，使用相同的参数多次调用Update不会比初始调用做更多的事情，因此PUT是幂等的。|1536930|POST不是幂等的，例如Create将在目标中创建两个单独的条目，因此它不是幂等的，因此create在POST中被广泛使用。|1536931|每次使用带有相同参数的POST进行相同的调用将导致两种不同的情况发生，因此POST通常用于Create场景|1536932|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

Both PUT and POST are Rest Methods .

PUT - If we make the same request twice using PUT using same parameters both times, the second request will not have any effect. This is why PUT is generally used for the Update scenario,calling Update more than once with the same parameters doesn't do anything more than the initial call hence PUT is idempotent. 

POST is not idempotent , for instance Create will create two separate entries into the target hence it is not idempotent so CREATE is used widely in POST.

Making the same call using POST with same parameters each time will cause two different things to happen, hence why POST is commonly used for the Create scenario

blocks|key|1537029|text|Post和Put主要用于post数据和其他更新数据。但是您可以仅对post请求执行相同的操作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1537030|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Post and Put are mainly used for post the data and other update the data. But you can do the same with post request only.

They both seem to be sending data to the server inside the body, so what makes them different?

What's the difference between a POST and a PUT HTTP REQUEST?

服务器

它们似乎都在向身体内的服务器发送数据，那么是什么使它们不同呢？

问POST和PUT HTTP请求有什么区别？
EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问POST和PUT HTTP请求有什么区别？EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问POST和PUT HTTP请求有什么区别？
EN