This article needs to be updated. (March 2015)
Time diagram of non-pipelined vs. pipelined connection.
HTTP pipelining is a technique in which multiple HTTP requests are sent on a single TCP connection without waiting for the corresponding responses.
The pipelining of requests results in a dramatic improvement in the loading times of HTML pages, especially over high latency connections such as satellite Internet connections. The speedup is less apparent on broadband connections, as the limitation of HTTP 1.1 still applies: the server must send its responses in the same order that the requests were received -- so the entire connection remains first-in-first-out and HOL blocking can occur. The asynchronous operation of the upcoming HTTP/2 or SPDY could be a solution for this.
Non-idempotent requests, like those using POST, should not be pipelined. Sequences of GET and HEAD requests can always be pipelined. A sequence of other idempotent requests like PUT and DELETE can be pipelined or not depending on whether requests in the sequence depend on the effect of others.
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 not to fail if a client chooses to pipeline requests.
Pipelining was introduced in HTTP/1.1 and was not present in HTTP/1.0.
Implementation in web servers
Implementing pipelining in web servers is a relatively simple matter of making sure that network buffers are not discarded between requests. For that reason, most modern web servers handle pipelining without any problem.
Implementation in web browsers
Of all the major browsers, only Opera based on Presto layout engine had a fully working implementation that was enabled by default. In all other browsers HTTP pipelining is disabled or not implemented.
- Internet Explorer 8 does not pipeline requests, due to concerns regarding buggy proxies and head-of-line blocking.
- Internet Explorer 11 does not support pipelining. 
- Mozilla browsers (such as Mozilla Firefox, SeaMonkey and Camino) support pipelining; however, it is disabled by default. Pipelining is disabled by default to avoid issues with misbehaving servers. When pipelining is enabled, Mozilla browsers use some heuristics, especially to turn pipelining off for older IIS servers. Support for H1 Pipeline was removed from Mozilla Firefox in Version 54.
- Konqueror 2.0 supports pipelining, but it's disabled by default.
- Google Chrome previously supported pipelining, but it has been disabled due to bugs and problems with poorly behaving servers.
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 by default and needs to be manually enabled for "bandwidth management and access logging reasons." Squid supports multiple requests from clients.
The Polipo proxy pipelines outgoing requests.
The libwww library made by the World Wide Web Consortium (W3C), supports pipelining since version 5.1 released at 18 February 1997.
Other application development libraries that support HTTP pipelining include:
- Perl modules providing client support for HTTP pipelining are HTTP::Async and the LWPng (libwww-perl New Generation) library.
- Apache Foundation project HttpComponents provides pipelining support in the HttpCore NIO extensions.
- The Microsoft .NET Framework 3.5 supports HTTP pipelining in the module
- Qt class
QNetworkRequest, introduced in 4.4.
Some other applications currently exploiting pipelining are:
Testing tools which support HTTP pipelining include:
- ^ a b c "Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing". ietf.org. Retrieved .
- ^ Nielsen, Henrik Frystyk; Gettys, Jim; Baird-Smith, Anselm; Prud'hommeaux, Eric; Lie, Håkon Wium; Lilley, Chris (24 June 1997). "Network Performance Effects of HTTP/1.1, CSS1, and PNG". World Wide Web Consortium. Retrieved 2010.
- ^ a b Willis, Nathan (18 November 2009). "Reducing HTTP latency with SPDY". LWN.net.
- ^ "Connections". w3.org.
- ^ "HTTP/1.1 Pipelining FAQ'".
- ^ http://www8.org/w8-papers/5c-protocols/key/key.html
- ^ "Wayback link of 'Windows Internet Explorer 8 Expert Zone Chat (August 14, 2008)'". Microsoft. August 14, 2008. Retrieved 2012.
- ^ "Internet Explorer and Connection Limits". IEBlog. Retrieved .
- ^ Pipelining Network MozillaZine
- ^ Cheah Chu Yeow. Firefox secrets. p. 180. ISBN 0-9752402-4-2.
- ^ "Bug 264354: Enable HTTP pipelining by default". Mozilla. Retrieved 2011.
- ^ "Source code - nsHttpConnection.cpp". Firefox source code. Mozilla. May 7, 2010. Retrieved 2010.
- ^ "Bug 1340655: Remove H1 Pipeline Support". Mozilla. Retrieved 2017.
- ^ HTTP Pipelining - The Chromium Projects
- ^ Mark Nottingham (June 20, 2007). "The State of Proxy Caching". Retrieved 2009.
- ^ "squid : pipeline_prefetch configuration directive". Squid. November 9, 2009. Retrieved 2009.
- ^ "Polipo -- a caching web proxy". Juliusz Chroboczek. September 18, 2009. Retrieved 2009.
- ^ Kahan, José (June 7, 2002). "Change History of libwww". World Wide Web Consortium. Retrieved 2010.
- ^ Using HTTP::Async for Parallel HTTP Requests (Colin Bradford)
- ^ System.Net.HttpWebRequest & pipelining
- ^ QNetworkRequest Class Reference Archived 2009-12-22 at the Wayback Machine., Nokia QT documentation
- ^ Pipelined HTTP GET utility
- ^ Curl pipelining explanation Archived 2012-06-27 at the Wayback Machine., Curl developer documentation
- ^ C. Michael Pilato; Ben Collins-Sussman; Brian W. Fitzpatrick (2008). Version Control with Subversion. O'Reilly Media. p. 238. ISBN 0-596-51033-0.
- ^ Justin R. Erenkrantz (2007). "Subversion: Powerful New Toys" (PDF).
- ^ "HTTP/HTTPS messages". Microsoft TechNet. January 21, 2005.
- ^ How CICS Web support handles pipelining
- ^ HTTP Website