HTTP persistent connection: Difference between revisions
Add reference to refereed performance paper |
|||
| Line 9: | Line 9: | ||
* Errors can be reported without the penalty of closing the TCP connection |
* Errors can be reported without the penalty of closing the TCP connection |
||
According to RFC 2616 (page 47), a single-user client should not maintain more than 2 connections with any server or proxy. A [[proxy server|proxy]] should use up to 2×<var>N</var> connections to another server or proxy, where <var>N</var> is the number of simultaneously active users. These guidelines are intended to improve HTTP response times |
According to RFC 2616 (page 47), a single-user client should not maintain more than 2 connections with any server or proxy. A [[proxy server|proxy]] should use up to 2×<var>N</var> connections to another server or proxy, where <var>N</var> is the number of simultaneously active users. These guidelines are intended to improve HTTP response times, avoid congestion. There is no HTTP performance benefit of additional connections, if HTTP pipelining over the TCP connection is correctly implemented, while significant issues with causing congestion, to the user or others. |
||
== Use in web browsers == |
== Use in web browsers == |
||
Revision as of 15:03, 5 August 2010
| HTTP |
|---|
 |
| Request methods |
| Header fields |
| Response status codes |
| Security access control methods |
| Security vulnerabilities |
HTTP persistent connection, also called HTTP keep-alive, or HTTP connection reuse, is the idea of using the same TCP connection to send and receive multiple HTTP requests/responses, as opposed to opening a new connection for every single request/response pair.
Advantages
- Less CPU and memory usage (because fewer connections are open simultaneously)
- Enables HTTP pipelining of requests and responses
- Reduced network congestion (fewer TCP connections)
- Reduced latency in subsequent requests (no handshaking)
- Errors can be reported without the penalty of closing the TCP connection
According to RFC 2616 (page 47), a single-user client should not maintain more than 2 connections with any server or proxy. A proxy should use up to 2×N connections to another server or proxy, where N is the number of simultaneously active users. These guidelines are intended to improve HTTP response times, avoid congestion. There is no HTTP performance benefit of additional connections, if HTTP pipelining over the TCP connection is correctly implemented, while significant issues with causing congestion, to the user or others.
Use in web browsers
Netscape Navigator (since at least 4.05) and Internet Explorer (since at least 4.01) support persistent connections to Web servers and proxies.
Netscape doesn't close persistent connections using timeout. All idling persistent connections are queued. When there is a need to open new persistent connections while connecting to a different server, the idle connections are killed by the browser using some form of LRU algorithm.[1]
Internet Explorer supports persistent connections. By default, versions 6 and 7 use 2 persistent connections while version 8 uses 6.[2] Persistent connections time out after 60 seconds of inactivity which is changeable via the Windows Registry.[3]
Mozilla Firefox supports persistent connections. The number of simultaneous connections can be customized (per-server, per-proxy, total). Persistent connections time out after 300 seconds (5 minutes) of inactivity which is changeable via the configuration.[4]
Opera supports persistent connections since 4.0.[5] The number of simultaneous connections can be customized (per-server, total).
References
- ^ Zhe Wang and Pei Cao (1998-12-09). "Persistent Connection Behavior of Popular Browsers". University of Wisconsin-Madison. Retrieved 2009-07-08.
- ^ "IE8 speeds things up". stevesouders.com. 2008-03-10. Retrieved 2009-07-17.
- ^ "How to change the default keep-alive time-out value in Internet Explorer". Microsoft. 2007-10-27. Retrieved 2009-07-17.
- ^ "Network.http.keep-alive.timeout". mozillazine.org. Retrieved 2009-07-17.
- ^ "Opera 4.0 Upgrades File Exchange: Includes HTTP 1.1". Opera Software. 2000-03-28. Retrieved 2009-07-08.