HTTP pipelining

HTTP pipelining is a technique in which multiple HTTP requests are written out to a single socket without waiting for the corresponding responses. Pipelining is only supported in HTTP/1.1, not in 1.0.

The pipelining of requests results in a dramatic improvement in page loading times, especially over high latency connections such as satellite Internet connections.

Since it is usually possible to fit several HTTP requests in the same TCP packet, HTTP pipelining allows fewer TCP packets to be sent over the network, reducing network load.

Non-idempotent methods like POST should not be pipelined. Sequences of GET and HEAD requests can be always 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.

Contents

  • 1 Implementation status
    • 1.1 Implementation in web servers
    • 1.2 Implementation in web browsers
    • 1.3 Implementation in web proxies
    • 1.4 Other implementations
  • 2 See also
  • 3 References
  • 4 External links

Schema of non-pipelined vs. pipelined connection.

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.

Exceptions include IIS 4.

Implementation in web browsers

HTTP pipelining is disabled in most browsers.

Opera has pipelining enabled by default. It uses heuristics to control the level of pipelining employed depending on the connected server.

Internet Explorer 8 does not pipeline requests, due to concerns regarding buggy proxies and head-of-line blocking.

Mozilla browsers (such as Mozilla Firefox, SeaMonkey and Camino), support pipelining however it is disabled by default.It uses some heuristics, especially to turn pipelining off for IIS servers. does the same thing as Firefox.

Konqueror 2.0 supports pipelining, but it's disabled by default.

Google Chrome does not support pipelining.

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.

Other implementations

The libwww library made by the World Wide Web Consortium, 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.
  • Python module httplib2 provides http pipelining support.
  • 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, supports HTTP Pipelining.

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:

posted @ 2010-11-26 00:08  dzqabc  阅读(1513)  评论(0)  编辑  收藏  举报