HTTP - Pipelining & Multiplexing

HTTP/1.1 Without Pipelining

Each HTTP request over the TCP connection must be responded to before the next request can be made.

HTTP/1.1 With Pipelining

Each HTTP request over the TCP connection may be made immediately without waiting for the previous request’s response to return. The responses will come back in the same order.

HTTP/2 Multiplexing

Each HTTP request over the TCP connection may be made immediately without waiting for the previous response to come back. The responses may come back in any order. Also allows the requests responses to be split into chunks and be returned in an intermingled fashion so avoiding head of line blocking