standard
HTTP/2 is a major revision of the HTTP protocol that multiplexes many requests over a single TCP connection, succeeding HTTP/1.1.
No evidence-backed relationships are recorded.
A single-file Python agent taps the interface with the same filter tcpdump prints for tcp, and it reconstructs method, path, status and p95 latency for HTTP/1.x while gRPC inside TLS stays an opaque byte count.
Reality
A dev.to guide walks Laravel apps from HTTP/1.1 to HTTP/3 on nginx, and the part worth reading twice is its admission that the middle step can hurt, because one connection carrying 40 streams stalls on one lost packet.
Reality
Turbopack decides which chunks to merge by looking only at chunks a page already loads together, which bounds the worst case but leaves the returning visitor re-downloading shared code the merged file no longer fits.
Reality
Unity 6.5 shipped a protocol pin whose enum tops out at HTTP/2, which tells you where the engine puts the risk. QUIC only pays for concurrent, small-object traffic, and only if your CDN negotiates it.
Reality
A practitioner who builds an automation browser argues bot detection fires in a fixed order, starting at the TLS handshake. The Bamberg crawl he cites found 75% of blocks on headless Chromium needed only HTTP headers.
Reality
gRPC got the announcement slot, but underneath it is a raw inbound socket that a Worker can route in JavaScript. Full duplex only shows up once that socket gets passed down to a Durable Object and a Container.
Reality
Unit 42 says the Android TV box botnet now floods over HTTP/2 with full Chrome fingerprints and resolves its command server through the Ethereum Name Service, with Tor as a fallback.
Reality