| Revision as of 10:27, 12 January 2007 editAmosfolarin (talk | contribs)42 edits Configuring the Firefox browser for pipelining← Previous edit | Revision as of 10:28, 12 January 2007 edit undoAmosfolarin (talk | contribs)42 edits →Implementation in web browsersNext edit → | ||
| Line 21: | Line 21: | ||
| ] as of version 7 doesn't support pipelining. | ] as of version 7 doesn't support pipelining. | ||
| ] 2.0 supports pipelining, but it's disabled by default. It uses some ], especially to turn pipelining off for ] ]s. Instructions for enabling pipelining can be found here . | ] 2.0 supports pipelining, but it's disabled by default. It uses some ], especially to turn pipelining off for ] ]s. Instructions for enabling pipelining can be found here . | ||
| ] has pipelining enabled by default. It uses ] to control the level of pipelining employed depending on the connected ]. | ] has pipelining enabled by default. It uses ] to control the level of pipelining employed depending on the connected ]. | ||
Revision as of 10:28, 12 January 2007
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. Instructions for enabling pipelining can be found here "(Pipelining optimisations in Firefox 2.0 web browser)".
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
- "Pipelining optimisations in Firefox 2.0 web browser"
 | This computer networking article is a stub. You can help Misplaced Pages by expanding it. |