Misplaced Pages

Revision as of 18:59, 8 July 2024

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 feature of HTTP/1.1, which allows multiple HTTP requests to be sent over a single TCP connection without waiting for the corresponding responses. HTTP/1.1 requires servers to respond to pipelined requests correctly, with 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.

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

In HTTP/3, multiplexing is accomplished via QUIC which replaces TCP. This further reduces loading time, as there is no head-of-line blocking even if some packets are lost.

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 operations of HTTP/2 and SPDY are solution for this. By 2017 most browsers supported HTTP/2 by default which uses multiplexing instead.

Non-idempotent requests such as POST should not be pipelined. Read requests like GET and HEAD 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 produce valid responses to pipelined requests, but may not actually process requests concurrently.

Most pipelining problems happen in HTTP intermediate nodes (hop-by-hop), i.e. in proxy servers, especially in transparent proxy servers (if one of them along the HTTP chain does not handle pipelined requests properly then nothing works as it should).

Using pipelining with HTTP proxy servers is usually not recommended also because the HOL blocking problem may really slow down proxy server responses (as the server responses must be in the same order of the received requests).

Example: if a client sends 4 pipelined GET requests to a proxy through a single connection and the first one is not in its cache then the proxy has to forward that request to the destination web server; if the following three requests are instead found in its cache, the proxy has to wait for the web server response, then it has to send it to the client and only then it can send the three cached responses too.

If instead a client opens 4 connections to a proxy and sends 1 GET request per connection (without using pipelining) the proxy can send the three cached responses to client in parallel before the response from server is received, decreasing the overall completion time (because requests are served in parallel with no head-of-line blocking problem). The same advantage exists in HTTP/2 multiplexed streams.

Implementation status

Pipelining was introduced in HTTP/1.1 and was not present in HTTP/1.0.

There have always been complaints about browsers, proxy servers, etc. not working well when using pipelined requests / responses, up to the point that for many years (at least till 2011) software developers, engineers, web experts, etc. tried to summarize the various kind of problems they noted, to fix things and to give advices about how to deal with pipelining on the Open Web.

Implementation in web browsers

Of all the major browsers, only Opera had a fully working implementation that was enabled by default. In other browsers HTTP pipelining was disabled or not implemented.

• Internet Explorer 8 does not support 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) used to support pipelining; however, it was removed in Firefox 54. When it was supported, pipelining was disabled by default to avoid issues with misbehaving servers. If pipelining was enabled by the user, Mozilla browsers used some heuristics, mostly to turn pipelining off for older Microsoft IIS servers. The removal was eventually backported to SeaMonkey.
• Konqueror 2.0 supports pipelining, but it is 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 proxy servers

Most HTTP proxies do not pipeline outgoing requests.

Some HTTP proxies, including transparent HTTP proxies, may manage pipelined requests very badly (e.g. by mixing up the order of pipelined responses).

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:

• httperf

See also

• HTTP persistent connection
• WebSocket
• SPDY

References

1. ^ Fielding, R.; Reschke, J. (2014). Fielding, R.; Reschke, J. (eds.). "Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing: Pipelining". ietf.org. doi:10.17487/RFC7230. Retrieved 2014-07-24. {{cite journal}}: Cite journal requires |journal= (help)
2. ^ "Revision 1330814 | Connection management in HTTP/1.x | MDN". MDN Web Docs. Archived from the original on 2018-03-19. 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. ^ Mark Nottingham (March 14, 2011). "Making HTTP Pipelining Usable on the Open Web". Retrieved October 16, 2021.
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. Fielding, R.; Reschke, J. (2014). Fielding, R.; Reschke, J. (eds.). "Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing: Concurrency". ietf.org. doi:10.17487/RFC7230. Retrieved 2014-07-24. {{cite journal}}: Cite journal requires |journal= (help)
11. "Key Differences between HTTP/1.0 and HTTP/1.1". Archived from the original on 2016-04-24. Retrieved 2016-04-16.
12. "Internet Explorer and Connection Limits". IEBlog. Retrieved 2016-11-14.
13. Firefox 54 Release Notes
14. "Bug 264354: Enable HTTP pipelining by default". Mozilla. Retrieved September 16, 2011.
15. "Source code – nsHttpConnection.cpp". Firefox source code. Mozilla. May 7, 2010. Retrieved December 5, 2010.
16. Emir Arian. Internet Communication: Protocols and related subjects. Retrieved 2021-10-16.
17. HTTP Pipelining - The Chromium Projects
18. "HTTP/1 Pipelining support has been removed in Firefox 54 - Pale Moon forum". forum.palemoon.org. Retrieved 2018-06-07.
19. Mark Nottingham (June 20, 2007). "The State of Proxy Caching". Retrieved May 16, 2009.
20. Mark Nottingham (July 11, 2011). "What proxies must do". Retrieved October 16, 2021.
21. "squid : pipeline_prefetch configuration directive". Squid. November 9, 2009. Retrieved December 1, 2009.
22. "Polipo — a caching web proxy". Juliusz Chroboczek. September 18, 2009. Retrieved November 12, 2009.
23. "Tempesta FW — a Linux Application Delivery Controller". GitHub. Retrieved March 29, 2018.
24. "Servers: Tempesta's side - tempesta-tech/tempesta Wiki". Tempesta Technologies INC. August 1, 2017. Retrieved March 29, 2018.
25. Kahan, José (June 7, 2002). "Change History of libwww". World Wide Web Consortium. Retrieved August 3, 2010.
26. "Using HTTP::Async for Parallel HTTP Requests (Colin Bradford)" (PDF). Archived from the original (PDF) on 2012-03-10. Retrieved 2010-08-03.
27. System.Net.HttpWebRequest & pipelining
28. QNetworkRequest Class Reference Archived 2009-12-22 at the Wayback Machine, Nokia QT documentation
29. Pipelined HTTP GET utility
30. Curl pipelining explanation Archived 2012-06-27 at the Wayback Machine, Curl developer documentation
31. Curl pipelining removal announcementArchived 2021-02-05 at the Wayback Machine
32. C. Michael Pilato; Ben Collins-Sussman; Brian W. Fitzpatrick (2008). Version Control with Subversion. O'Reilly Media. p. 238. ISBN 978-0-596-51033-6.
33. Justin R. Erenkrantz (2007). "Subversion: Powerful New Toys" (PDF).
34. "HTTP/HTTPS messages". Microsoft TechNet. January 21, 2005.
35. How CICS Web support handles pipelining
36. "HTTP Website". Archived from the original on 2012-06-08. Retrieved 2010-10-01.

External links

• RFC 7230 Fielding, R.; Reschke, J. (2014). Fielding, R; Reschke, J (eds.). "Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing". ietf.org. doi:10.17487/RFC7230. Retrieved 2014-07-24. {{cite journal}}: Cite journal requires |journal= (help)
• 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
• serf C library

• Hypertext Transfer Protocol