Misplaced Pages

HTTP pipelining

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.

This is an old revision of this page, as edited by Ade56facc (talk | contribs) at 21:48, 16 October 2021 (→Implementation in web proxies: Added a sentence + reference about bad behavior of some HTTP proxies + changed a few URLs from http to https). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Revision as of 21:48, 16 October 2021 by Ade56facc (talk | contribs) (→Implementation in web proxies: Added a sentence + reference about bad behavior of some HTTP proxies + changed a few URLs from http to https)(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff)
Time diagram of non-pipelined vs. pipelined connection
HTTP
Request methods
Header fields
Response status codes
Security access control methods
Security vulnerabilities

HTTP pipelining is a feature of HTTP/1.1 which allows multiple HTTP requests to be sent over a single TCP (transmission control protocol) connection without waiting for the corresponding responses. HTTP/1.1 specification requires servers to respond to pipelined requests correctly, sending back non-pipelined but valid responses even if server does not support HTTP pipelining. Despite this requirement, many legacy HTTP/1.1 servers do not support pipelining correctly, forcing most HTTP clients to not use HTTP pipelining in practice.

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

In HTTP/3, the multiplexing is accomplished through the new underlying QUIC transport protocol, which replaces TCP. This further reduces loading time, as there is no head-of-line blocking anymore.

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 HTTP proxies, including transparent HTTP proxies, may manage pipelined requests very badly (i.e. by mixing up the order of pipelined responses, etc.).

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.
  • 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 previously had limited support for pipelining using the CURLMOPT_PIPELINING option, but this support was removed in version 7.65.0
  • portsnap (a FreeBSD ports tree distribution system)
  • Advanced Packaging Tool (APT) supports 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.

Testing tools which support HTTP pipelining include:

See also

References

  1. ^ "Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing". ietf.org. Retrieved 2014-07-24.
  2. ^ "Revision 1330814 | Connection management in HTTP/1.x | MDN". MDN Web Docs. Retrieved 2018-03-19.
  3. "HTTP2 browser support". Retrieved March 9, 2017.
  4. 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 14 January 2010.
  5. ^ Willis, Nathan (18 November 2009). "Reducing HTTP latency with SPDY". LWN.net.
  6. "Connections". w3.org.
  7. "HTTP/1.1 Pipelining FAQ'".
  8. "Archived copy". Archived from the original on 2016-04-24. Retrieved 2016-04-16.{{cite web}}: CS1 maint: archived copy as title (link)
  9. "Wayback link of 'Windows Internet Explorer 8 Expert Zone Chat (August 14, 2008)'". Microsoft. August 14, 2008. Archived from the original on December 4, 2010. Retrieved May 10, 2012.
  10. "Internet Explorer and Connection Limits". IEBlog. Retrieved 2016-11-14.
  11. Pipelining Network MozillaZine
  12. Cheah Chu Yeow. Firefox secrets. p. 180. ISBN 0-9752402-4-2.
  13. "Bug 264354: Enable HTTP pipelining by default". Mozilla. Retrieved September 16, 2011.
  14. "Source code – nsHttpConnection.cpp". Firefox source code. Mozilla. May 7, 2010. Retrieved December 5, 2010.
  15. "Bug 1340655: Remove H1 Pipeline Support". Mozilla. Retrieved March 22, 2017.
  16. HTTP Pipelining - The Chromium Projects
  17. "HTTP/1 Pipelining support has been removed in Firefox 54 - Pale Moon forum". forum.palemoon.org. Retrieved 2018-06-07.
  18. Mark Nottingham (June 20, 2007). "The State of Proxy Caching". Retrieved May 16, 2009.
  19. Mark Nottingham (July 11, 2011). "What proxies must do". Retrieved October 16, 2021.
  20. "squid : pipeline_prefetch configuration directive". Squid. November 9, 2009. Retrieved December 1, 2009.
  21. "Polipo — a caching web proxy". Juliusz Chroboczek. September 18, 2009. Retrieved November 12, 2009.
  22. "Tempesta FW — a Linux Application Delivery Controller". GitHub. Retrieved March 29, 2018.
  23. "Servers: Tempesta's side - tempesta-tech/tempesta Wiki". Tempesta Technologies INC. August 1, 2017. Retrieved March 29, 2018.
  24. Kahan, José (June 7, 2002). "Change History of libwww". World Wide Web Consortium. Retrieved August 3, 2010.
  25. "Using HTTP::Async for Parallel HTTP Requests (Colin Bradford)" (PDF). Archived from the original (PDF) on 2012-03-10. Retrieved 2010-08-03.
  26. System.Net.HttpWebRequest & pipelining
  27. QNetworkRequest Class Reference Archived 2009-12-22 at the Wayback Machine, Nokia QT documentation
  28. Pipelined HTTP GET utility
  29. Curl pipelining explanation Archived 2012-06-27 at the Wayback Machine, Curl developer documentation
  30. Curl pipelining removal announcementArchived 2021-02-05 at the Wayback Machine
  31. C. Michael Pilato; Ben Collins-Sussman; Brian W. Fitzpatrick (2008). Version Control with Subversion. O'Reilly Media. p. 238. ISBN 0-596-51033-0.
  32. Justin R. Erenkrantz (2007). "Subversion: Powerful New Toys" (PDF).
  33. "HTTP/HTTPS messages". Microsoft TechNet. January 21, 2005.
  34. How CICS Web support handles pipelining
  35. "HTTP Website". Archived from the original on 2012-06-08. Retrieved 2010-10-01.

External links

Category: