Systems and protocols · Intermediate

HTTP/3: mapping HTTP onto QUIC streams

Explain stream independence, QPACK dependencies and shared congestion control without claiming that HTTP/3 eliminates all waiting.

Ask Logeia about this articleTry the three questionsReview your answers

Updated

On this page
  1. Separate HTTP semantics from transport
  2. Work a loss example
  3. Compression can introduce another wait
  4. Shared resources and deployment conditions
  5. Ask Logeia about this articleCheck your understanding

Separate HTTP semantics from transport

HTTP/3 maps HTTP semantics onto QUIC. Methods and status codes retain their application meaning, while bidirectional request streams and additional control streams carry the protocol’s messages and settings. This is not simply HTTP/2 frames sent unchanged as UDP datagrams. QUIC provides secure stream transport, and HTTP/3 builds request-response behavior on that foundation. Application responsibilities such as authorization and validation remain. Understanding the division helps distinguish a protocol-format problem from transport loss, a compression dependency, or an application that has not yet produced its response.

Work a loss example

Suppose requests A and B use different QUIC streams. A packet carrying bytes required by A is lost, but the bytes B needs arrive. Unlike one ordered TCP byte stream, delivery of B’s stream need not wait solely for A’s missing bytes. A still has to recover its own missing data. If a lost packet contains data from both streams, both can be affected. Stream independence changes the scope of transport ordering dependencies; it does not abolish packet loss, retransmission, or the time required for the server to compute a result.

Compression can introduce another wait

QPACK compresses HTTP field sections and can refer to dynamic-table entries. A field section that depends on an update not yet received can be blocked until the necessary compression state becomes available. Therefore, independent transport streams do not imply that every HTTP message can always be decoded independently. Inspect the control and encoder-decoder streams as well as response-body data. Compression savings and dependency limits are a trade-off. When explaining a stalled request, identify the missing prerequisite instead of labeling every wait as transport head-of-line blocking.

Shared resources and deployment conditions

Streams on a connection still share network capacity and congestion-control consequences. A congestion response can reduce transmission opportunities across several requests even when their ordering is independent. Deployment also depends on UDP reachability and compatible endpoints. The version label alone cannot guarantee lower latency than HTTP/2 under every workload. Compare loss, round-trip time, connection reuse and response sizes under stated conditions. Separate handshake behavior from steady-state throughput, and distinguish the absence of one cross-stream ordering dependency from the much stronger and incorrect claim that requests never wait on each other.

Reading and practice are recorded separately in this browser, for each language.

Learn this in order

Understand the systems behind the web · STEP 10

Choose a learning path