Misplaced Pages

HTTP pipelining: Difference between revisions

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.
Browse history interactively← Previous editNext edit →Content deleted Content addedVisualWikitext
Revision as of 04:26, 1 September 2007 editChris-martin (talk | contribs)Extended confirmed users, Rollbackers8,343 editsm remove unnecessary parens and a contraction← Previous edit Revision as of 21:55, 15 September 2007 edit undo76.212.139.79 (talk) →Implementation statusNext edit →
Line 10: Line 10:
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. 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.


pipelining is the lining of pipes
== Implementation status ==
=== 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 just fine.

Exceptions include IIS 4 and reportedly 5.

=== Implementation in web browsers ===
] as of version 7 doesn't support pipelining.

] 2.0 supports pipelining, but it's disabled by default. It uses some ]s, especially to turn pipelining off for ] ]s. Instructions for enabling pipelining can be found here .

] 2.0 supports pipelining, but it's disabled by default. Instructions for enabling it can be found here .

] has pipelining enabled by default. It uses ]s to control the level of pipelining employed depending on the connected ].

=== Implementation in web proxies ===
Most HTTP proxies do not pipeline outgoing requests, as demonstrated by .

Some versions of the Squid web proxy will pipeline up to two outgoing requests. This functionality has been disabled in the latest versions.

The proxy pipelines outgoing requests.

=== Other implementations ===
Some other applications currently exploiting pipelining are from ] (a minimalist pipelined HTTP client), ] (a ] ] distribution system) and ] (a sophisticated file transfer program).


== External links == == External links ==

Revision as of 21:55, 15 September 2007

Schema of non-pipelined vs. pipelined connection.

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.

Only idempotent requests should be pipelined, such as GET and HEAD requests. POST requests should not be pipelined. Requests on a new connection should not be pipelined either, since it has not yet been determined if the origin server (or proxy server) supports HTTP/1.1. Hence, pipelining can only be done when reusing an existing (keepalive) persistent connection.

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.

pipelining is the lining of pipes

External links

Category: