Does HTTP/2 multiplexing prevent TCP head-of-line blocking?
No. HTTP/2 interleaves independent streams at the application layer, but one TCP connection still delivers an ordered byte stream. Lost bytes can delay delivery of later bytes from that connection.
Answered in
HTTP/2 vs HTTP/3 Under Packet Loss: What QUIC Changes—and What It CannotCompare HTTP/2 over TCP with HTTP/3 over QUIC: how loss affects streams, and which flow-control or congestion limits both still face.
Read the full analysisOther questions this article answers
More network protocols questions
- Did HTTP/1.0 always open a new TCP connection for every resource?
- Does HTTP/2 eliminate every form of head-of-line blocking?
- Does HTTP/3 make packet loss irrelevant?
- Does one lost QUIC packet stop every HTTP/3 stream?
- Is HTTP/3 always faster than HTTP/2?
- Does DNS happen before every HTTP request?
- Is UDP an unreliable protocol with no congestion control?
- Is QUIC just UDP with encryption?
Every answer on Crashtech is written by the editor of the article it comes from — never auto-summarised. Browse all answers or the Network Protocols beat.