Jump to content

HTTP pipelining: Difference between revisions

From Wikipedia, the free encyclopedia
Browse history interactively
← Previous editNext edit →
Content deleted Content added
VisualWikitext
FuzzyBSc (talk | contribs)
82 edits
Replace rfc2616 references with httpbis documents
FuzzyBSc (talk | contribs)
82 edits
m Fix rfc link
Line 64: Line 64:


==External links==
==External links==
*[http://tools.ietf.org/html/rfc7230 RFC 7230 <ref name="pipeline">{{cite web|url=http://tools.ietf.org/html/rfc7230#section-6.3.2|title=Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing|publisher=ietf.org|accessdate=2014-07-24}}]
* RFC 7230 <ref name="pipeline">{{cite web|url=http://tools.ietf.org/html/rfc7230#section-6.3.2|title=Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing|publisher=ietf.org|accessdate=2014-07-24}}]
*[http://www.mozilla.org/projects/netlib/http/pipelining-faq.html HTTP/1.1 Pipelining FAQ at mozilla.org]
*[http://www.mozilla.org/projects/netlib/http/pipelining-faq.html HTTP/1.1 Pipelining FAQ at mozilla.org]
*[http://www.w3.org/Protocols/HTTP/Performance/Pipeline.html "Network Performance Effects of HTTP/1.1, CSS1, and PNG" at w3.org]
*[http://www.w3.org/Protocols/HTTP/Performance/Pipeline.html "Network Performance Effects of HTTP/1.1, CSS1, and PNG" at w3.org]

Revision as of 15:15, 23 July 2014

Schema of non-pipelined vs. pipelined connection.
HTTP
Request methods
Header fields
Response status codes
Security access control methods
Security vulnerabilities

HTTP pipelining is a technique in which multiple HTTP requests are sent on a single TCP connection without waiting for the corresponding responses.[1]

The pipelining of requests results in a dramatic improvement[2] 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[1] and HOL blocking can occur. The asynchronous operation of the upcoming HTTP 2.0 or SPDY could be a solution for this.[3]

Non-idempotent methods like POST should not be pipelined. Sequences of GET and HEAD requests can always be pipelined. A sequence of other idempotent requests like GET, HEAD, PUT and DELETE can be pipelined or not depending on whether requests in the sequence depend on the effect of others.[1]

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.[4]

Implementation status

Pipelining is only supported in HTTP/1.1, not in 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

Out 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.[3]

  • Internet Explorer 8 does not pipeline requests, due to concerns regarding buggy proxies and head-of-line blocking.[5]
  • Mozilla browsers (such as Mozilla Firefox, SeaMonkey and Camino) support pipelining, however it is disabled by default.[6][7] Pipelining is disabled by default to avoid issues with misbehaving servers.[8] When pipelining is enabled, Mozilla browsers use some heuristics, especially to turn pipelining off for older IIS servers.[9]
  • Konqueror 2.0 supports pipelining, but it's disabled by default.[citation needed]
  • Google Chrome supports pipelining for HTTP in the stable release as a non-default option (starting with version 18). There is no support for pipelining HTTPS yet.[10] As of version 26, the flag to enable HTTP pipelining in Chrome has been disabled.

Implementation in web proxies

Most HTTP proxies do not pipeline outgoing requests.[11]

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."[12] Squid supports multiple requests from clients.

The Polipo proxy pipelines outgoing requests.[13]

Other implementations

The libwww library made by the World Wide Web Consortium (W3C), supports pipelining since version 5.1 released at 18 February 1997.[14]

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.[15]
  • 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.[16]
  • Qt class QNetworkRequest, introduced in 4.4.[17]

Some other applications currently exploiting pipelining are:

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

Testing tools which support HTTP pipelining include:

See also

References

  1. ^ a b c "Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing". ietf.org. Retrieved 2014-07-24.
  2. ^ 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.
  3. ^ a b Willis, Nathan (18 November 2009). "Reducing HTTP latency with SPDY". LWN.net.
  4. ^ "HTTP/1.1 Pipelining FAQ'".
  5. ^ "Wayback link of 'Windows Internet Explorer 8 Expert Zone Chat (August 14, 2008)'". Microsoft. August 14, 2008. Retrieved May 10, 2012.
  6. ^ Pipelining Network MozillaZine
  7. ^ Cheah Chu Yeow. Firefox secrets. p. 180. ISBN 0-9752402-4-2.
  8. ^ "https://bugzilla.mozilla.org/show_bug.cgi?id=264354". Mozilla. Retrieved September 16, 2011. {{cite web}}: External link in |title= (help)
  9. ^ "Source code – nsHttpConnection.cpp". Firefox source code. Mozilla. May 7, 2010. Retrieved December 5, 2010.
  10. ^ HTTP Pipelining - The Chromium Projects
  11. ^ Mark Nottingham (June 20, 2007). "The State of Proxy Caching". Retrieved May 16, 2009.
  12. ^ "squid : pipeline_prefetch configuration directive". Squid. November 9, 2009. Retrieved December 1, 2009.
  13. ^ "Polipo — a caching web proxy". Juliusz Chroboczek. September 18, 2009. Retrieved November 12, 2009.
  14. ^ Kahan, José (June 7, 2002). "Change History of libwww". World Wide Web Consortium. Retrieved August 3, 2010.
  15. ^ Using HTTP::Async for Parallel HTTP Requests (Colin Bradford)
  16. ^ System.Net.HttpWebRequest & pipelining
  17. ^ QNetworkRequest Class Reference, Nokia QT documentation
  18. ^ Pipelined HTTP GET utility
  19. ^ Curl pipelining explanation, Curl developer documentation
  20. ^ C. Michael Pilato, Ben Collins-Sussman, Brian W. Fitzpatrick (2008). Version Control with Subversion. O'Reilly Media. p. 238. ISBN 0-596-51033-0.{{cite book}}: CS1 maint: multiple names: authors list (link)
  21. ^ Justin R. Erenkrantz (2007). "Subversion: Powerful New Toys" (PDF).
  22. ^ "HTTP/HTTPS messages". Microsoft TechNet. January 21, 2005.
  23. ^ How CICS Web support handles pipelining
  24. ^ "Pipelined HTTP Client".
  25. ^ HTTP Website
Retrieved from "https://en.wikipedia.org/w/index.php?title=HTTP_pipelining&oldid=618134161"