因为get是纯粹的url，它们可以被web浏览器缓存，并且可能更好地用于一致生成的图像之类的事情。(设置过期时间)

一个来自gravatar页面的例子:http://www.gravatar.com/avatar/4c3be63a4c2f539b013787725dfce802?d=monsterid

GET可能会产生稍微更好的性能，一些web服务器在调用处理程序之前将POST内容写入临时文件。

另一件需要考虑的事情是尺寸限制。get的上限是URL的大小，标准是1024字节，不过浏览器可能支持更多。

传输更多的数据应该使用POST来获得更好的浏览器兼容性。

即使小于这个限制也是一个问题，正如另一个帖子所写的，URL中的任何内容都可能最终出现在浏览器UI的其他部分，比如历史记录。

我的一般经验法则是，当您向服务器发出不打算改变状态的请求时使用Get。post是为更改状态的服务器请求保留的。

短的版本

GET:通常用于已提交的搜索请求，或者任何您希望用户能够再次调出确切页面的请求。

GET的优点:

url可以安全地添加书签。 页面可以安全地重新加载。

GET的缺点:

变量作为名称-值对通过url传递。(安全风险) 可以传递的变量数量有限。(基于浏览器。例如，Internet Explorer被限制为2048个字符。)

POST:用于更高安全性的请求，其中数据可能用于更改数据库，或者您不希望别人添加书签的页面。

POST的优点:

url中不显示名称-值对。(安全+= 1) 可以通过POST传递无限数量的名称-值对。参考。

POST的缺点:

使用POST数据的页面不能被书签。(如果你愿意的话。)

完整版

直接来自超文本传输协议——HTTP/1.1:

9.3 GET The GET method means retrieve whatever information (in the form of an entity) is identified by the Request-URI. If the Request-URI refers to a data-producing process, it is the produced data which shall be returned as the entity in the response and not the source text of the process, unless that text happens to be the output of the process. The semantics of the GET method change to a "conditional GET" if the request message includes an If-Modified-Since, If-Unmodified-Since, If-Match, If-None-Match, or If-Range header field. A conditional GET method requests that the entity be transferred only under the circumstances described by the conditional header field(s). The conditional GET method is intended to reduce unnecessary network usage by allowing cached entities to be refreshed without requiring multiple requests or transferring data already held by the client. The semantics of the GET method change to a "partial GET" if the request message includes a Range header field. A partial GET requests that only part of the entity be transferred, as described in section 14.35. The partial GET method is intended to reduce unnecessary network usage by allowing partially-retrieved entities to be completed without transferring data already held by the client. The response to a GET request is cacheable if and only if it meets the requirements for HTTP caching described in section 13. See section 15.1.3 for security considerations when used for forms. 9.5 POST The POST method is used to request that the origin server accept the entity enclosed in the request as a new subordinate of the resource identified by the Request-URI in the Request-Line. POST is designed to allow a uniform method to cover the following functions: Annotation of existing resources; Posting a message to a bulletin board, newsgroup, mailing list, or similar group of articles; Providing a block of data, such as the result of submitting a form, to a data-handling process; Extending a database through an append operation. The actual function performed by the POST method is determined by the server and is usually dependent on the Request-URI. The posted entity is subordinate to that URI in the same way that a file is subordinate to a directory containing it, a news article is subordinate to a newsgroup to which it is posted, or a record is subordinate to a database. The action performed by the POST method might not result in a resource that can be identified by a URI. In this case, either 200 (OK) or 204 (No Content) is the appropriate response status, depending on whether or not the response includes an entity that describes the result.

从w3schools.com:

What is HTTP? The Hypertext Transfer Protocol (HTTP) is designed to enable communications between clients and servers. HTTP works as a request-response protocol between a client and server. A web browser may be the client, and an application on a computer that hosts a web site may be the server. Example: A client (browser) submits an HTTP request to the server; then the server returns a response to the client. The response contains status information about the request and may also contain the requested content. Two HTTP Request Methods: GET and POST Two commonly used methods for a request-response between a client and server are: GET and POST. GET – Requests data from a specified resource POST – Submits data to be processed to a specified resource

在这里我们区分主要的区别:

第一个重要的事情是GET和POST的含义:

GET应该用来…得到……一些来自服务器的信息， 而POST应该用来向服务器发送一些信息。

在那之后，有几件事可以注意:

使用GET，用户可以在浏览器中使用“后退”按钮，并且可以将页面添加为书签 你可以作为GET传递的参数的大小是有限制的(如果我没记错的话，某些版本的Internet Explorer是2KB);POST的限制更多，通常取决于服务器的配置。

无论如何，我不认为我们可以“生活”没有GET:想想你每天在查询字符串中使用多少带有参数的url——没有GET，所有这些都不能工作;-)

最初的目的是GET用于获取数据，而POST用于任何用途。我使用的经验法则是，如果我要向服务器发送任何东西，我就使用POST。如果我只是调用一个URL来获取数据，我会使用get。