| Revision as of 15:58, 31 October 2006 edit12.106.100.66 (talk) →External links← Previous edit | Revision as of 17:27, 31 October 2006 edit undoHelix84 (talk | contribs)1,720 edits Pipelined HTTP content merged. added section Use in web browsersNext edit → | ||
| Line 1: | Line 1: | ||
| '''HTTP pipelining''' |
'''HTTP pipelining''' is a transfer method of HTTP/1.1 for improving performance, when multiple HTTP requests are written out to a socket together without waiting for the corresponding responses. Responses are then expected in order they were requested. Servers can also send multiple answers without closing their socket. This results in fewer ''roundtrips'' and faster load times. | ||
| The act of pipelining the requests can result in a dramatic improvement in page loading times, especially over high ] connections (such as ]). | |||
| Since it is usually possible to fit several HTTP requests in the same ] packet, HTTP pipelining allows fewer TCP packets to be sent over the network, reducing network load. | Since it is usually possible to fit several HTTP requests in the same ] packet, HTTP pipelining allows fewer TCP packets to be sent over the network, reducing network load. | ||
| Only idempotent requests can be pipelined, such as GET and HEAD requests. POST and PUT requests should not be pipelined. Requests on a new connection shouldn't be pipelined either, since it has not yet been determined if the origin server (or ]) supports HTTP/1.1. Hence, pipelining can only be done when reusing an existing ] (persistent) connection. | |||
| ⚫ | HTTP pipelining requires both the client and the server to support it. |
||
| ⚫ | 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 to not fail if a client chooses to pipeline requests. | ||
| Some of current applications exploiting pipelining are phttpget from ] (a minimalist pipelined HTTP client) and ] (a ports tree distribution system). | |||
| == Use in web browsers == | |||
| ] as of version 7 doesn't support pipelining. | |||
| ] 2.0 supports pipelining, but it's off by default. It uses some heuristics, especially to turn pipelining off for ] servers. | |||
| ] supports pipelining by default. It uses heuristics to control the level of pipelining employed depending on the server it's connected to. | |||
| == External links == | == External links == | ||
Revision as of 17:27, 31 October 2006
HTTP pipelining is a transfer method of HTTP/1.1 for improving performance, when multiple HTTP requests are written out to a socket together without waiting for the corresponding responses. Responses are then expected in order they were requested. Servers can also send multiple answers without closing their socket. This results in fewer roundtrips and faster load times.
The act of pipelining the requests can result 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 can be pipelined, such as GET and HEAD requests. POST and PUT requests should not be pipelined. Requests on a new connection shouldn't be pipelined either, since it has not yet been determined if the origin server (or proxy) supports HTTP/1.1. Hence, pipelining can only be done when reusing an existing keep-alive (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 to not fail if a client chooses to pipeline requests.
Some of current applications exploiting pipelining are phttpget from FreeBSD (a minimalist pipelined HTTP client) and portsnap (a ports tree distribution system).
Use in web browsers
Internet Explorer as of version 7 doesn't support pipelining.
Mozilla Firefox 2.0 supports pipelining, but it's off by default. It uses some heuristics, especially to turn pipelining off for IIS servers.
Opera supports pipelining by default. It uses heuristics to control the level of pipelining employed depending on the server it's connected to.
External links
- A FAQ on pipelining, courtesy of mozilla.org.
- A W3C page measuring the benefits of pipelining, along with modern design technologies (CSS and PNG)
- Optimizing Page Load Times
 | This computer networking article is a stub. You can help Misplaced Pages by expanding it. |