If anyone else wants a bit of history on pipelining wrt Netscape&#x2F;Firefox etc:<p><a href="http:&#x2F;&#x2F;kb.mozillazine.org&#x2F;Network.http.pipelining" rel="nofollow">http:&#x2F;&#x2F;kb.mozillazine.org&#x2F;Network.http.pipelining</a><p>And in particular (from links in the above):<p>&quot;Bug 264354 - Enable HTTP pipelining by default
Status: RESOLVED WONTFIX&quot; - in particular one of the last comments in the thread:
<a href="https:&#x2F;&#x2F;bugzilla.mozilla.org&#x2F;show_bug.cgi?id=264354#c65" rel="nofollow">https:&#x2F;&#x2F;bugzilla.mozilla.org&#x2F;show_bug.cgi?id=264354#c65</a><p>And:<p>&quot;Bug 395838 - Remove HTTP pipelining pref from release builds
Status: RESOLVED WONTFIX&quot;:
<a href="https:&#x2F;&#x2F;bugzilla.mozilla.org&#x2F;show_bug.cgi?id=395838" rel="nofollow">https:&#x2F;&#x2F;bugzilla.mozilla.org&#x2F;show_bug.cgi?id=395838</a><p>My general impression is that there were a few issues on Windows, in particular with &quot;anti-virus software&quot;, and some problems with broken proxies -- as well as a handful of issues with hopelessly broken servers.<p>Additionally, it appears SSL&#x2F;TLS latency was never really considered (not explicitly stated, but there appear to be implications that on &quot;fast networks&quot; http is &quot;fast enough&quot; that pipelining makes little difference) -- in other words it does indeed appear that just enabling piplining as the web moved from plain http to TLS, would&#x27;ve sidestepped most of the need for HTTP&#x2F;2...