Talk:HTTP pipelining

Safari and popelining?
Hi, all modern browsers are listed. But what is with Safari? -- cu AssetBurned (talk) 15:16, 22 May 2008 (UTC)

HTTP Server support
I understand that all HTTP/1.1 servers have to be able to accept pipelined requests, but are there any servers which fully support pipelining, and send pipelined responses? Apache maybe? -- Lee Carré 19:27, 22 November 2006 (UTC)


 * Methinks you might be confused. What's a pipelined response?  A response that you send before you receive the request?--Jec 20:51, 23 November 2006 (UTC)


 * An HTTP Response. A pipelined response would be a response that's pipelined; sent in the same manor as pipelined HTTP requests. This is from the server's point of view, not the client's, the only response a client sends is a TCP ACK. -- Lee Carré 06:23, 24 November 2006 (UTC)


 * A pipelined HTTP request is a request that has been sent before the reply for the previous request has been received. Think about it -- there's no such thing as a pipelined reply.
 * What you are thinking of is sending multiple replies in a single IP packet. Most servers will do that either if they use a buffer for replies (as Apache does), or if they enable Nagle's algorithm (most do). --Jec 01:23, 2 July 2007 (UTC)

Google Chrome supports pipelining http (but not https) in the stable release (from version 18) as a non-default option. as default.[10]

really?

Where is this actually defined?
A quick search of RFC 2068 for pipeline finds no hits. Plugwash 01:44, 7 October 2007 (UTC)
 * sorry my mistake the copy of the RFC I was looking at was split into sections causing my search to not find stuff that was in fact in the RFC. Plugwash —Preceding signed but undated comment was added at 01:47, 7 October 2007 (UTC)

Konqueror support can be "enabled"?
Is it just me, or saying that Konqueror supports it but needs to be "enabled" is like saying that firefox supports tor and just needs to be enabled? The "trick" listed in the page makes you use an external software (a proxy) that implements pipelining... —Preceding unsigned comment added by Flameeyes (talk • contribs) 16:36, 27 February 2008 (UTC)


 * I agree. That pipeline "support" involves using a 3rd party web proxy (Polipo), clearly that's not the same thing as the browser actually having in-built support for pipelining.  I'd edit it myself but I don't have any references to whether Konqueror actually supports pipelining or not.  Maybe if someone actually has a reference they can do the edit.. PUnkX22 (talk) 17:10, 24 July 2008 (UTC)

Severs Supporting pipelining Is there any way to know whether a particular server supports pipelining beforehand?? —Preceding unsigned comment added by Lance.cse (talk • contribs) 12:40, 2 February 2009 (UTC)

LFTP support
I don't see any indication that lftp supports HTTP pipelining; the man page only mentions FTP pipelining. Pimlottc (talk) 13:43, 20 October 2009 (UTC)

Link Rot!
Link for Firefox FAQ rotted! Pls halp! Kingsocarso (talk) 16:57, 1 March 2012 (UTC)

What Internet Explorer 9 & 10
This is incredibly outdated, please include all modern browsers. Leica0000 (talk) 09:11, 28 August 2014 (UTC)

External links modified
Hello fellow Wikipedians,

I have just modified 2 external links on HTTP pipelining. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added archive https://web.archive.org/web/20091222054207/http://doc.qt.nokia.com/4.6/qnetworkrequest.html to http://doc.qt.nokia.com/4.6/qnetworkrequest.html
 * Added archive https://web.archive.org/web/20120627181619/http://curl.haxx.se/dev/readme-pipelining.html to http://curl.haxx.se/dev/readme-pipelining.html

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

Cheers.— InternetArchiveBot  (Report bug) 15:14, 27 October 2017 (UTC)

pipelining vs multiplexing
Hello. The image in the article clearly is incorrect. The pipelining in HTTP/1.1 only allows the second request after the first request is finished. Initiating multiple requests at once can either be done through multiple (TCP) connections, through HTTP/2 multiplexing (with HOL-blocking), or through HTTP/3 multiplexing (over QUIC). As "HTTP pipelining" as it is described in the article is barely if at all used anymore, and "HTTP multiplexing" is now with QUIC used even more, I think this article should be renamed to HTTP pipelining. Then we can properly seperate: --BlauerBaum (talk) 22:26, 18 June 2021 (UTC)
 * multiple (TCP) connections (multiplexing)
 * HTTP/1.1 pipelining (pipelining)
 * HTTP/2 multiplexing (multiplexing)
 * HTTP/3 over QUIC (multiplexing)