Editing HTTP pipelining (section)

{{Short description|Computer communication technique}}
[[File:HTTP pipelining2.svg|thumb|right|300px|Time diagram of non-pipelined vs. pipelined connection]]
{{HTTP}}
'''HTTP pipelining''' is a feature of '''HTTP/1.1''', which allows multiple [[HTTP]] requests to be sent over a single [[Transmission Control Protocol|TCP]] connection without waiting for the corresponding responses.<ref name="HTTP/1.1-pipelining">{{cite journal|url=http://tools.ietf.org/html/rfc7230#section-6.3.2|title=Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing: Pipelining|year=2014 |publisher=ietf.org|doi=10.17487/RFC7230 |accessdate=2014-07-24|editor-last1=Fielding |editor-last2=Reschke |editor-first1=R. |editor-first2=J. |last1=Fielding |first1=R. |last2=Reschke |first2=J. |doi-access=free |url-access=subscription }}</ref> HTTP/1.1 requires servers to respond to pipelined requests correctly, with non-pipelined but valid responses even if server does not support HTTP pipelining. Despite this requirement, many legacy HTTP/1.1 servers do not support pipelining correctly, forcing most HTTP clients to not use HTTP pipelining.

The technique was superseded by '''[[multiplexing]]''' via [[HTTP/2]],<ref name=":0">{{Cite web|url=https://developer.mozilla.org/en-US/docs/Web/HTTP/Connection_management_in_HTTP_1.x$revision/1330814|title=Revision 1330814 {{!}} Connection management in HTTP/1.x {{!}} MDN|website=MDN Web Docs|language=en-US|access-date=2018-03-19|archive-date=2018-03-19|archive-url=https://web.archive.org/web/20180319213834/https://developer.mozilla.org/en-US/docs/Web/HTTP/Connection_management_in_HTTP_1.x$revision/1330814|url-status=dead}}</ref> which is supported by most modern [[Web browser|browsers]].<ref name="browser_support">{{cite web|url=http://caniuse.com/#search=http2|title=HTTP2 browser support|accessdate=March 9, 2017}}</ref>

In [[HTTP/3]], multiplexing is accomplished via [[QUIC]] which replaces [[Transmission Control Protocol|TCP]]. This further reduces loading time, as there is no [[head-of-line blocking]] even if some packets are lost.