http://my.oschina.net/leejun2005/blog/136820
刚看到群里又有同学在说 HTTP 协议下的 Get 请求参数长度是有大小限制的&＃xff0c;最大不能超过
XX&＃xff0c;而 Post 是无限制的&＃xff0c;看到这里&＃xff0c;我想他们定是看多了一些以讹传讹的博客或者书籍&＃xff0c;
导致一种理解上的误区&＃xff1a;
1、首先即使有长度限制&＃xff0c;也是限制的是整个 URI 长度&＃xff0c;而不仅仅是你的参数值数据长度。
2、HTTP 协议从未规定 GET/POST 的请求长度限制是多少。
The HTTP protocol does not place any a priori limit on the length of a URI. Servers MUST be able to handle the URI of any resource they serve, and SHOULD be able to handle URIs of unbounded length if they provide GET-based forms that could generate such URIs. A server SHOULD return 414 (Request-URI Too Long) status if a URI is longer than the server can handle (see section 10.4.15).
Note: Servers ought to be cautious about depending on URI lengths above 255 bytes, because some older client or proxy implementations might not properly support these lengths.
3、所谓的请求长度限制是由浏览器和 web 服务器决定和设置的&＃xff0c;各种浏览器和 web 服务器的设定
均不一样&＃xff0c;这依赖于各个浏览器厂家的规定或者可以根据 web 服务器的处理能力来设定。
The limit is in MSIE and Safari about 2KB, in Opera about 4KB and in Firefox about 8KB, (255 bytes if we count very old browsers) . We may thus assume that 8KB is the maximum possible length and that 2KB is a more affordable length to rely on at the server side and that 255 bytes is the safest length to assume that the entire URL will come in.
If the limit is exceeded in either the browser or the server, most will just truncate the characters outside the limit without any warning. Some servers however may send a HTTP 414 error. If you need to send large data, then better use POST instead of GET. Its limit is much higher, but more dependent on the server used than the client. Usually up to around 2GB is allowed by the average webserver. This is also configureable somewhere in the server settings. The average server will display a server-specific error/exception when the POST limit is exceeded, usually as HTTP 500 error.
HTTP 1.1 defines Status Code 414 Request-URI Too Long for the cases where a server-defined limit is reached. You can see further details on RFC 2616. For the case of client-defined limits, there is no sense on the server returning something, because the server won&＃39;t receive the request at all.
The server is refusing to service the request because the Request-URI is longer than the server is willing to interpret. This rare condition is only likely to occur when a client has improperly converted a POST request to a GET request with long query information, when the client has descended into a URI "black hole" of redirection (e.g., a redirected URI prefix that points to a suffix of itself), or when the server is under attack by a client attempting to exploit security holes present in some servers using fixed-length buffers for reading or manipulating the Request-URI.
附 GET VS POST&＃xff1a;
1、多数浏览器对于POST采用两阶段发送数据的&＃xff0c;先发送请求头&＃xff0c;再发送请求体&＃xff0c;即使参数再少再短&＃xff0c;也会被分成两个步骤来发送(相对于GET)&＃xff0c;也就是第一步发送header数据&＃xff0c;第二步再发送body部分。HTTP是应用层的协议&＃xff0c;而在传输层有些情况TCP会出现两次连结的过程&＃xff0c;HTTP协议本身不保存状态信息&＃xff0c;一次请求一次响应。对于TCP而言&＃xff0c;通信次数越多反而靠性越低&＃xff0c;能在一次连结中传输完需要的消息是最可靠的&＃xff0c;尽量使用GET请求来减少网络耗时。如果通信时间增加&＃xff0c;这段时间客户端与服务器端一直保持连接状态&＃xff0c;在服务器侧负载可能会增加&＃xff0c;可靠性会下降。
Tips&＃xff1a;关于这点你可以参考&＃xff1a;Yahoo网站性能优化指南之服务器篇
上面这篇文章介绍了 wireshark 抓包验证 post 两次发包&＃xff0c;get 一次发包的全过程&＃xff0c;推荐阅读。
2、GET请求能够被cache&＃xff0c;GET请求能够被保存在浏览器的浏览历史里面(密码等重要数据GET提交&＃xff0c;别人查看历史记录&＃xff0c;就可以直接看到这些私密数据)POST不进行缓存。
3、GET参数是带在URL后面&＃xff0c;传统IE中URL的最大可用长度为2048字符&＃xff0c;其他浏览器对URL长度限制实现上有所不同。POST请求无长度限制(目前理论上是这样的)。
4、GET提交的数据大小&＃xff0c;不同浏览器的限制不同&＃xff0c;一般在2k-8K之间&＃xff0c;POST提交数据比较大&＃xff0c;大小靠服务器的设定值限制&＃xff0c;而且某些数据只能用 POST 方法「携带」&＃xff0c;比如 file。
5、全部用POST不是十分合理&＃xff0c;最好先把请求按功能和场景分下类&＃xff0c;对数据请求频繁&＃xff0c;数据不敏感且数据量在普通浏览器最小限定的2k范围内&＃xff0c;这样的情况使用GET。其他地方使用POST。
6、GET 的本质是「得」&＃xff0c;而 POST 的本质是「给」。而且&＃xff0c;GET 是「幂等」的&＃xff0c;在这一点上&＃xff0c;GET 被认为是「安全的」。但实际上 server 端也可以用作资源更新&＃xff0c;但是这种用法违反了约定&＃xff0c;容易造成 CSRF(跨站请求伪造)。
REF&＃xff1a;
maximum length of HTTP GET request?
post方式相比get安全,携带数据更大&＃xff0c;我准备所有数据都用post方式获取&＃xff0c;这样好吗&＃xff1f;
京公网安备 11010802041100号