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 23:47, 25 April 2005 editAlistairMcMillan (talk | contribs)Administrators33,791 edits →How to enable HTTP pipelining in []: Take out heading in link and format list← Previous edit Revision as of 00:17, 1 May 2005 edit undoQuale (talk | contribs)Autopatrolled, Extended confirmed users24,871 editsm spNext edit →
Line 1: Line 1:
'''HTTP pipelining''' appeared in ]/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 ] connections and other connections with high latency as seperate requests need not be made for each image/] etc. '''HTTP pipelining''' appeared in ]/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 ] connections and other connections with high latency as separate requests need not be made for each image/] etc.


Since it is possible to cram several HTTP requests in the same ] packet (the average ], or maximum segment size, being 512 bytes), fewer TCP packets are sent over the network, so pipelining benefits network load too. Since it is possible to cram several HTTP requests in the same ] packet (the average ], or maximum segment size, being 512 bytes), fewer TCP packets are sent over the network, so pipelining benefits network load too.

Revision as of 00:17, 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

  1. Go to about:config
  2. Scroll down to network.http.pipelining
  3. Double click it so its value is set to "true"
  4. Double click network.http.pipelining.maxrequests & enter a value into the box (20 to 40) and click OK.

External links

Category: