How does HTTP/2 multiplex multiple requests over a single TCP connection?
u01 ·
grounded ·
HTTP 200 ·
index 0fc1763d6701
eval/questions.yaml annotates this question as
partial, and the gate holds the service
to agreeing with that annotation across the set.
What survived the check — each claim with the passage that supports it
HTTP/2 introduced a multiplexed session layer on top of the existing TLS and TCP protocols for exchanging concurrent HTTP messages with efficient field compression and server push.
rfc9110#1.2 — 100% of
this claim's content words appear in that passage.
What was retrieved — the passages the drafter saw, and nothing else
| rank | section | score |
|---|---|---|
| 1 | RFC 9110 Section 1.2: History and Evolution |
0.5479 |
| 2 | RFC 9112 Section 9: Connection Management |
0.5221 |
| 4 | RFC 9112 Section 9.4: Concurrency |
0.5065 |
| 5 | RFC 9112 Section 9.3.2: Pipelining |
0.5005 |
| 6 | RFC 9110 Section 3.3: Connections, Clients, and Servers |
0.4815 |
| 7 | RFC 9112 Section 9.7: TLS Connection Initiation |
0.4500 |
| 8 | RFC 9112 Section 9.1: Establishment |
0.4472 |
| 9 | RFC 9110 Section 1.1: Purpose |
0.4443 |
| 10 | RFC 9112 Section 9.3: Persistence |
0.4388 |