blocks|key|343928|text|GET用于从服务器获取数据。POST+(以及鲜为人知的PUT和DELETE)是为修改服务器上的数据而设计的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|343929|GET请求不应导致从应用程序中删除数据。如果你有一个链接，你可以点击GET来删除数据，那么Google爬虫你的网站就可以点击你所有的"Delete“链接。|343930|标准答案可以在here中找到，它引用了HTML2.0规范：|offset|length|343931|343932|如果表单的处理是幂等的(即，它对世界的状态没有持久的可观察到的影响)，那么form方法应该是GET。许多数据库搜索没有明显的副作用，使查询表单成为理想的应用程序。|blockquote|343933|343934|如果与表单处理关联的服务有副作用(例如，修改数据库或订阅服务)，则该方法应为POST。|343935|343936|在AJAX调用中，您需要使用服务器支持的任何方法。您应该始终设计您的服务器，以便POST/PUT/DELETE调用修改数据的操作。其他评论有指向REST的链接，REST通常将C/R/U/D映射到"POST或PUT"(Create)/GET(Read)/PUT(Update)/DELETE(Delete).|343937|entityMap|0|LINK|mutability|MUTABLE|url|http://www.cs.tut.fi/~jkorpela/forms/methods.html^0|0|0|7|4|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|10|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|11|8|@]|9|@$F|12|G|13|1|14]]|A|$]]|$1|H|3|-4|5|6|7|15|8|@]|9|@]|A|$]]|$1|I|3|J|5|K|7|16|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|17|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|18|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|19|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1A|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]]|S|$T|$5|U|V|W|A|$X|Y]]]]

GET is designed for getting data from the server. POST (and lesser-known friends PUT and DELETE) are designed for modifying data on the server.

A GET request should never cause data to be removed from an application. If you have a link you can click on with a GET to remove data, then Google spidering your site could click on all your "Delete" links.

The canonical answer can be found <a href="http://www.cs.tut.fi/~jkorpela/forms/methods.html" rel="noreferrer">here</a>, which quotes the HTML 2.0 spec:

<blockquote>
 If the processing of a form is idempotent (i.e. it has no lasting
 observable effect on the state of the
 world), then the form method should be
 GET. Many database searches have no
 visible side-effects and make ideal
 applications of query forms.
 
 If the service associated with the processing of a form has side effects
 (for example, modification of a
 database or subscription to a
 service), the method should be POST.
</blockquote>

In your AJAX call, you need to use whatever method your server supports. You should always design your server so that operations that modify data are called by POST/PUT/DELETE. Other comments have links to REST, which generally maps C/R/U/D to "POST or PUT"(Create)/GET(Read)/PUT(Update)/DELETE(Delete).

blocks|key|345246|text|如果要通过HTTPS发送大量数据或敏感数据，则需要使用POST。如果它只是一个简单的参数，我会使用GET。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|345247|GET请求对可以发送的数据量有限制。我忘记了确切的数字，但这可能会导致问题，如果你正在发送任何实质性的东西。|345248|基本上，GET和POST之间的区别在于，在GET请求中，参数在URL中传递，而在POST中，参数包含在消息体中。|345249|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

If you're sending large amounts of data, or sensitive data over HTTPS, you will want to use POST. If it's just a simple parameter, I would use GET.

GET requests have a limit to the amount of data that can be sent. I forget the exact number, but this can cause issues if you're sending anything substantial.

Basically the difference between GET and POST is that in a GET request, the parameters are passed in the URL where as in a POST, the parameters are included in the message body.

blocks|key|346243|text|不管是不是它的AJAX都无关紧要。这是关于你正在采取的行动。我建议遵循REST的原则。对更新、删除等有进一步的规定。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|346244|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/REST^0|Z|4|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Whether its AJAX or not is irrelevant. Its about the action that you're taking. I'd recommend following the principles of <a href="http://en.wikipedia.org/wiki/REST" rel="noreferrer">REST</a>. Which have further provisions for updating, deleting, etc...

blocks|key|3121118|text|GET请求在CSRF+(跨站点请求伪造)攻击中更容易受到攻击。也就是说，伪造的POST请求需要在用户端启用Javascript，而伪造的GET请求仍然可以使用img，script标签。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3121119|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|$]]

GET requests are easier to exploit in CSRF (cross site request forgery) attacks. Namely fake POST requests require Javascript to be enabled on the user side, while fake GET requests are still possible just with img, script tags.

blocks|key|345338|text|许多web服务器限制了可作为URL的一部分传递的数据的长度，因此GET请求可能会以难以调试的奇怪方式中断。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|345339|此外，大多数服务器软件将URL记录在访问日志中，因此，如果您在GET请求中传递敏感信息(如密码)，则这些信息很可能会以明文形式写入磁盘。|345340|从REST的角度来看，GET请求不应该有副作用--它们不应该修改数据。因此，如果您只是通过ID更新资源，这是有意义的，但是如果您要提交对资源的更改，则应该对GETting谓词使用PUT、POST或UPDATE。|345341|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Many web servers limit the length of the data that can be passed as part of the URL, so the GET request may break in odd ways that are hard to debug.

Also, most server software logs URLs in the access logs, so if you pass sensitive information (such as passwords) in a GET request, this will in all likelihood be written to disk in plaintext.

From a REST perspective, GET requests should have no side-effects -- they shouldn't modify data. So, if you're just GETting a resource by ID, this makes sense, but if you're committing changes to a resource, you should be using PUT, POST, or UPDATE for the http verb.

blocks|key|3121163|text|两者都用于发送一些数据，并使用这些数据接收一些响应。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3121164|GET:获取存储在服务器中的信息。即。搜索、推文、个人信息。如果你想发送信息，那么get请求使用process.php?name=subroto发送请求，所以它基本上是通过url发送信息。Url不能处理超过2083个字符。所以对于博客帖子，你能记住这是不可能的吗？|3121165|POST:+Post和get做同样的事情。用户注册，用户登录，大数据发送，博客帖子。如果你需要发送安全信息，那么使用post或大数据，因为它不通过url。|3121166|$.get()和$.post()包含的特性是$.ajax()的子集。它有很多配置。|3121167|$.get+()方法，它是$.Ajax+()的一种简写形式。在使用$.get+()时，不是传入对象，而是传入参数。至少，您需要前两个参数，这是您想要检索的文件的URL+(即‘test.txt’)和一个成功的回调。|3121168|摘要：|3121169|$.get(+url+[,+data+]+[,+success+]+[,+dataType+]+)
$.post(+url+[,+data+]+[,+success+]+[,+dataType+]+)+//+for+sending+secure+or+Large+information
$.ajax(+url+[,+settings+]+)++//+More+Configaration|code-block|syntax|javascript|3121170|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|U|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|V|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|W|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|X|8|@]|9|@]|A|$]]|$1|L|3|M|5|N|7|Y|8|@]|9|@]|A|$O|P]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

Both are used to send some data and receive some response using that data. 

GET: Get information store in server. Ie. Search, tweet, Person Information. If you want to send information then get request send request using process.php?name=subroto
So it basically send information through url. Url cannot handle more than 2083 char. So for blog post can you remember it is not possible?

POST: Post do same thing as get. User registration, User login, Big data send, Blog Post.
If you need to send secure information then use post or for big data as it not go through url.

AJAX: $.get() and $.post() contain features that are subsets of $.ajax(). It has much configuration.

$.get () method, which is a kind of shorthand for $.Ajax (). When using $.get (), instead of passing in an object, you pass in arguments. At minimum, you’ll need the first two arguments, which are the URL of the file you want to retrieve (i.e. ‘test.txt’) and a success callback.

Summary:

<pre><code>$.get( url [, data ] [, success ] [, dataType ] )
$.post( url [, data ] [, success ] [, dataType ] ) // for sending secure or Large information
$.ajax( url [, settings ] ) // More Configaration
</code></pre>

blocks|key|345540|text|首先，是一般信息。如果您只读取数据，请使用GET，如果您更改了数据库、txt文件等上的内容，请使用POST。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|345541|但问题是，一些浏览器会缓存GET结果。我在IE7中遇到了AJAX请求的问题，但最后我发现浏览器缓存了GET结果。我重新考虑了流程，并将我的请求更改为POST。|345542|因此，如果不想使用缓存，就不要使用GET。|345543|(当然，您可以在GET操作中禁用缓存。但我并不喜欢这样)|345544|entityMap^0|L|3|1D|4|0|D|3|S|4|1E|3|22|4|0|H|3|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]|$9|Q|A|R|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|S|8|@$9|T|A|U|B|C]|$9|V|A|W|B|C]|$9|X|A|Y|B|C]|$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|11|8|@$9|12|A|13|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|14|8|@]|D|@]|E|$]]|$1|L|3|-4|5|6|7|15|8|@]|D|@]|E|$]]]|M|$]]

First, general information. Use <code>GET</code> if you only read data, use <code>POST</code> if you change something on database, txt files etc.

But the problem is, some browsers cache <code>GET</code> results. I had problems with <code>AJAX</code> requests in IE7, but at last I found out that browser caches <code>GET</code> results. I rethought the flow and changes my request to <code>POST</code>.

So, don't use <code>GET</code> if you don't want caching.

(Of course you can disable caching in GET operations. But I didn't prefer it)

blocks|key|3120997|text|关于我，我更喜欢帖子。我保留get到我知道发送的值仅限于我拥有“控制”的数据的事件，例如，检索具有id的项。例如，"getitem?id=123"，"deleteImtem?id=123"，...对于其他情况，当我有一个用户可以填写的表单时，我更喜欢POST。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3120998|就像Ryan+Smith所说的，最好使用POST来发送大量数据，而在其他语言/特殊字符中使用时就不那么麻烦了(一般来说，所有主流的javascript框架都不会有任何问题，但我认为使用POST不太值得)。|3120999|对于REST视角，在我看来，您可以将其用于新项目(以保持与整个项目的一致性)。|3121000|最后，可能是在网络中使用的一些程序(URL日志程序(例如:查看员工是否在非自动网站上浪费时间，...)代理，...+)或者任何其他类型的工具可以截取该查询。有些人会在报告中显示您使用GET发送的参数，将其视为不同的网页。但在这种情况下，这可能不是你的问题，它是从一个项目更改到另一个项目！;)|3121001|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|$]]

About me, i prefer POST. I reserve get to the events i know the sent value is limited to data i have the "control", for example, to retreive an item with an id. Example, "getitem?id=123", "deleteImtem?id=123", ... For the other cases, when i have a form fillable by a user, i prefer POST.

Like Ryan Smith have said, it's better to use POST to send a large amount of data, and less wories in cases of the use in others language/special chars (generally all majors javascript framework should'nt have any problems to deal with that but i think is less wories to use POST).

For the REST perspective, in my opinion, you can use this with a new project (to keep a consistency with the entire project). 

Finally, maybee some programs used in a network (URL loguers (ie.: to see if the employees lost their time on non-autorised sites, ...) proxys, ... ) or any other kind of tool can intercept the query. Somes will show in the reports the params you have sent with GET, considering it like a different web page. But in this situation, is could be not your problem it's changes from a project to an other! ;)

blocks|key|345373|text|无论您使用的是Ajax、HTML+form还是curl，GET和POST之间的区别都是一样的。下面是相关的定义：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|345374|345375|GET|unordered-list-item|345376|POST|345377|345378|entityMap|0|LINK|mutability|MUTABLE|url|http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.3|1|http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.5^0|H|4|N|4|S|3|W|4|0|0|0|3|0|0|0|4|1|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]|$9|Z|A|10|B|C]|$9|11|A|12|B|C]|$9|13|A|14|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|15|8|@]|D|@]|E|$]]|$1|G|3|H|5|I|7|16|8|@]|D|@$9|17|A|18|1|19]]|E|$]]|$1|J|3|K|5|I|7|1A|8|@]|D|@$9|1B|A|1C|1|1D]]|E|$]]|$1|L|3|-4|5|6|7|1E|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|1F|8|@]|D|@]|E|$]]]|N|$O|$5|P|Q|R|E|$S|T]]|U|$5|P|Q|R|E|$S|V]]]]

The difference is the same between <code>GET</code> and <code>POST</code> whether you're using Ajax, HTML <code>form</code>s, or <code>curl</code>. Here are the relevant definitions:

<ul>
<li><a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.3" rel="nofollow noreferrer">GET</a></li>
<li><a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.5" rel="nofollow noreferrer">POST</a></li>
</ul>

blocks|key|345356|text|如果您传递的任何参数的字符可能会在URL中弄乱(例如空格)，则可以使用POST。否则，您可以使用GET。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|345357|一般来说，如果你只是传递一些小的参数，你可以使用GET。但对于传递用户提交的信息，如博客条目、文本等，使用POST是一个很好的做法。|345358|也有一些框架完全依赖于基于段的urls+(例如site.com/products/133而不是site.com/products.php?id=333+)，这些框架出于安全考虑取消了GET变量。在这种情况下，你可以一直使用POST。|offset|length|style|CODE|345359|entityMap^0|0|0|N|L|1B|S|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@$F|O|G|P|H|I]|$F|Q|G|R|H|I]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|K|$]]

If you are passing on any arguments with characters that can get messed up in the URL (such as spaces), you use POST. Otherwise you can use GET.

Generally, if you're just passing on a few tiny arguments you would use GET. But for passing on user submitted information such as blog entries, text, etc, its a good practice to use POST.

There are also certain frameworks that rely completely on segment based urls (such as <code>site.com/products/133</code> rather than <code>site.com/products.php?id=333</code> and these frameworks unset the GET variables for security. In such cases you would use POST allt the time.

What is the difference between GET and POST for Ajax requests?

I don't see any difference between those two, except that when I use GET, the parameters are send in URL, which for me don't really make any difference, since all requests are made on background and user doesn't find any difference.

edit:
What are PUT and DELETE methods used for?

GET vs POST in Ajax

数据库

大数据

服务器

GET和POST对于Ajax请求有什么不同？我看不出这两者之间有什么区别，除了当我使用GET时，参数是在URL中发送的，这对我来说并没有什么区别，因为所有的请求都是在后台发出的，用户找不到任何区别。编辑：PUT、和DELETE方法的用途是什么？

问Ajax中的GET vs POST
EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Ajax中的GET vs POSTEN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Ajax中的GET vs POST
EN