| Revision as of 04:24, 1 May 2005 editAsqueella (talk | contribs)477 edits formatting + reasonable values for "maxrequests". (Check out faq at moz.org to see that 20-40 figure was nonsense)← Previous edit | Revision as of 04:24, 1 May 2005 edit undoAsqueella (talk | contribs)477 editsm →External linksNext edit → | ||
| Line 12: | Line 12: | ||
| == External links == | == External links == | ||
| * , courtesy of mozilla.org |
* , courtesy of mozilla.org. | ||
| * measuring the benefits of pipelining, along with modern design technologies (] and ]) | * measuring the benefits of pipelining, along with modern design technologies (] and ]) | ||
Revision as of 04:24, 1 May 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 image/Javascript file etc.
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. A server is required to support it in order to be HTTP/1.1 compliant. Recent versions of the Apache HTTP Server support it.
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 4) and click OK.
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)