| Revision as of 20:50, 23 November 2006 editJec (talk | contribs)Extended confirmed users1,130 editsm →Implementation status← Previous edit | Revision as of 07:04, 15 December 2006 edit undoGoarany (talk | contribs)239 editsm minor rewrite to keep it clearNext edit → | ||
| Line 2: | Line 2: | ||
| '''] pipelining''' is a technique in which multiple ] requests are written out to a single ] without waiting for the corresponding responses. Pipelining is only supported in HTTP/1.1, not in 1.0. | '''] pipelining''' is a technique in which multiple ] requests are written out to a single ] without waiting for the corresponding responses. Pipelining is only supported in HTTP/1.1, not in 1.0. | ||
| The |
The pipelining of requests results in a dramatic improvement in page loading times, especially over high ] connections (such as ]s). | ||
| Since it is usually possible to fit several HTTP requests in the same ] packet, HTTP pipelining allows fewer TCP ]s to be sent over the ], reducing ]. | Since it is usually possible to fit several HTTP requests in the same ] packet, HTTP pipelining allows fewer TCP ]s to be sent over the ], reducing ]. | ||
Revision as of 07:04, 15 December 2006
HTTP pipelining is a technique in which multiple HTTP requests are written out to a single socket without waiting for the corresponding responses. Pipelining is only supported in HTTP/1.1, not in 1.0.
The pipelining of requests results in a dramatic improvement in page loading times, especially over high latency connections (such as satellite Internet connections).
Since it is usually possible to fit several HTTP requests in the same TCP packet, HTTP pipelining allows fewer TCP packets to be sent over the network, reducing network load.
Only idempotent requests can be pipelined, such as GET and HEAD requests. POST and PUT requests should not be pipelined. Requests on a new connection shouldn't be pipelined either, since it has not yet been determined if the origin server (or proxy server) supports HTTP/1.1. Hence, pipelining can only be done when reusing an existing (keepalive) persistent connection.
HTTP pipelining requires both the client and the server to support it. HTTP/1.1 conforming servers are required to support pipelining. This does not mean that servers are required to pipeline responses, but that they are required to not fail if a client chooses to pipeline requests.
Implementation status
Implementation in web servers
Implementing pipelining in web servers is easy: it is enough to make sure that network buffers are not discarded between requests. For that reason, most modern web servers handle pipelining just fine.
Exceptions include IIS 4 and reportedly 5.
Implementation in web browsers
Internet Explorer as of version 7 doesn't support pipelining.
Mozilla Firefox 2.0 supports pipelining, but it's disabled by default. It uses some heuristics, especially to turn pipelining off for IIS servers.
Opera has pipelining enabled by default. It uses heuristics to control the level of pipelining employed depending on the connected server.
Implementation in web proxies
Most HTTP proxies do not pipeline outgoing requests.
Some versions of the Squid web proxy will pipeline up to two outgoing requests. This functionality has been disabled in the latest versions.
The Polipo proxy pipelines outgoing requests.
Other implementations
Some other applications currently exploiting pipelining are phttpget from FreeBSD (a minimalist pipelined HTTP client) and portsnap (a FreeBSD ports tree distribution system).
External links
- HTTP/1.1 Pipelining FAQ at mozilla.org
- "Network Performance Effects of HTTP/1.1, CSS1, and PNG" at w3.org
- "Optimizing Page Load Times" article
- phttpget
 | This computer networking article is a stub. You can help Misplaced Pages by expanding it. |