| Revision as of 09:47, 14 July 2005 editRedxelaSinnak (talk | contribs)137 editsm Grammar.← Previous edit | Revision as of 00:30, 17 August 2005 edit undo71.130.254.196 (talk) →How to enable HTTP pipelining in the Firefox web browser: deleted section. this isn't a HOWTONext edit → | ||
| Line 5: | Line 5: | ||
| HTTP pipelining requires both the client and the server to support it. Servers are required to support it in order to be HTTP/1.1 compliant. Although these servers are required to allow pipelined requests, they are not required to pipeline responses. Recent versions of the ] support pipelining. | HTTP pipelining requires both the client and the server to support it. Servers are required to support it in order to be HTTP/1.1 compliant. Although these servers are required to allow pipelined requests, they are not required to pipeline responses. Recent versions of the ] support pipelining. | ||
| == How to enable HTTP pipelining in the Firefox web browser == | |||
| # Type ''about:config'' in the Location Bar. | |||
| # Scroll down to ''network.http.pipelining''. | |||
| # Double click it so its value is set to ''true''. | |||
| # Double click ''network.http.pipelining.maxrequests'' and enter a value into the box (2 to 8) and click OK. | |||
| == External links == | == External links == | ||
Revision as of 00:30, 17 August 2005
HTTP pipelining appeared in HTTP/1.1. It allows clients to send multiple requests at once, without waiting for an answer. Servers can send multiple answers without closing their socket too. This results in fewer roundtrips and faster load times. This is particularly useful for Satellite Internet connections and other connections with high latency as separate requests need not be made for each file.
Since it is possible to cram several HTTP requests in the same TCP packet (the average MSS, or maximum segment size, being 512 bytes), fewer TCP packets are sent over the network, so pipelining benefits network load too.
HTTP pipelining requires both the client and the server to support it. Servers are required to support it in order to be HTTP/1.1 compliant. Although these servers are required to allow pipelined requests, they are not required to pipeline responses. Recent versions of the Apache HTTP Server support pipelining.
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)