HTTP/2
The second major version of the HTTP protocol, standardized in 2015. It introduces multiplexing, binary framing, header compression (HPACK), and server push, and serves as the underlying transport protocol for gRPC.
Core Facts
Compared to WebSocket, SSE is lighter to implement, natively supports automatic reconnection, and is the superior engineering choice for unidirectional scenarios where only server-side push is needed.
HTTP/2 uses multiplexing technology to allow concurrent transmission of multiple requests over a single TCP connection, while HTTP/3 switches the transport layer from TCP to the QUIC protocol.
Timeline (last 90 days)
Claude once objected to implementing HTTP/2 for jpm, but the author insisted; measurements showed HTTP/2 was about 17% faster on home connections, but flat or worse on GitHub runners, with cold-start nuxt installs up to 2 times slower, 8% to 15% more CPU consumed on large tarballs, and a 60KB increase in binary size, so the 3671 lines of HTTP/2 code were ultimately deleted.
SSE runs on top of standard HTTP/1.1 chunked transfer encoding or HTTP/2 and HTTP/3 multiplexed streams.
CVE-2026-92392 is a use-after-free vulnerability originating from curl mishandling an HTTP/2 RST_STREAM sent by the server; when the reason is HTTP_1_1_REQUIRED or REFUSED_STREAM, it causes a use-after-free of struct Curl_easy.
HTTPX supports the HTTP/2 protocol, whereas requests only supports HTTP/1.1.
Compared to WebSocket, SSE is lighter to implement, natively supports automatic reconnection, and is the superior engineering choice for unidirectional scenarios where only server-side push is needed.
HTTP/2 is the HTTP protocol (RFC 7540) published by the IETF in 2015; its core innovations are binary framing and multiplexing, which resolve the head-of-line blocking problem of HTTP/1.1.
All Facts (7)
Compared to WebSocket, SSE is lighter to implement, natively supports automatic reconnection, and is the superior engineering choice for unidirectional scenarios where only server-side push is needed.
75%VerifiedHTTP/2 uses multiplexing technology to allow concurrent transmission of multiple requests over a single TCP connection, while HTTP/3 switches the transport layer from TCP to the QUIC protocol.
75%UnverifiedHTTP/2 is the HTTP protocol (RFC 7540) published by the IETF in 2015; its core innovations are binary framing and multiplexing, which resolve the head-of-line blocking problem of HTTP/1.1.
60%UnverifiedClaude once objected to implementing HTTP/2 for jpm, but the author insisted; measurements showed HTTP/2 was about 17% faster on home connections, but flat or worse on GitHub runners, with cold-start nuxt installs up to 2 times slower, 8% to 15% more CPU consumed on large tarballs, and a 60KB increase in binary size, so the 3671 lines of HTTP/2 code were ultimately deleted.
50%UnverifiedSSE runs on top of standard HTTP/1.1 chunked transfer encoding or HTTP/2 and HTTP/3 multiplexed streams.
50%UnverifiedCVE-2026-92392 is a use-after-free vulnerability originating from curl mishandling an HTTP/2 RST_STREAM sent by the server; when the reason is HTTP_1_1_REQUIRED or REFUSED_STREAM, it causes a use-after-free of struct Curl_easy.
50%UnverifiedHTTPX supports the HTTP/2 protocol, whereas requests only supports HTTP/1.1.
50%