HTTP pipelining - Misplaced Pages

This is an old revision of this page, as edited by Tom.Reding (talk | contribs) at 20:04, 19 December 2020 (Enum 1 author/editor WL; WP:GenFixes on). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Revision as of 20:04, 19 December 2020 by Tom.Reding (talk | contribs) (Enum 1 author/editor WL; WP:GenFixes on)(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff)

HTTP

Persistence Compression HTTPS QUIC
Request methods
OPTIONS GET HEAD POST PUT DELETE TRACE CONNECT PATCH
Header fields
Cookie ETag Location HTTP referer DNT X-Forwarded-For
Response status codes
301 Moved Permanently 302 Found 303 See Other 403 Forbidden 404 Not Found 451 Unavailable for Legal Reasons
Security access control methods
Basic access authentication Digest access authentication
Security vulnerabilities
HTTP header injection HTTP request smuggling HTTP response splitting HTTP parameter pollution
v t e

HTTP pipelining is a technique in which multiple HTTP requests are sent on a single TCP (transmission control protocol) connection without waiting for the corresponding responses.

The technique was superseded by multiplexing via HTTP/2, which is supported by most modern browsers.

As of 2018, HTTP pipelining is not enabled by default in modern browsers, due to several issues including buggy proxy servers and HOL blocking.

Motivation and limitations

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 HTTP/2 and SPDY are solutions for this. Browsers ultimately did not enable pipelining by default, and by 2017 most browsers supported HTTP/2 by default which used multiplexing instead.

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.

Implementation status

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 disabled by default.
Google Chrome previously supported pipelining, but it has been disabled due to bugs and problems with poorly behaving servers.
Pale Moon (web browser) supports pipelining, and is enabled by default

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.

Tempesta FW, an open source application delivery controller, also pipelines requests to backend servers.

Other implementations

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 System.Net.HttpWebRequest.
Qt class QNetworkRequest, introduced in 4.4.

Some other applications currently exploiting pipelining are:

IceBreak application server since BUILD389
phttpget from FreeBSD (a minimalist pipelined HTTP client)
libcurl has limited support for pipelining using the CURLMOPT_PIPELINING option.
portsnap (a FreeBSD ports tree distribution system)
Advanced Packaging Tool (APT) support pipelining.
Subversion (SVN) has optional support for HTTP pipelining with the serf WebDAV access module (the default module, neon does not have pipelining support).
Microsoft Message Queuing on Windows Server 2003 utilises pipelining on HTTP by default, and can be configured to use it on HTTPS.
IBM CICS 3.1 supports HTTP pipelining within its client.

Multipart XHR is implementation of pipelining (without any browser or web server support) done purely in JavaScript in combination with server-side scripting.

Testing tools which support HTTP pipelining include: