HTTP/2
Embed This Widget
Add the script tag and a data attribute to embed this widget.
Embed via iframe for maximum compatibility.
<iframe src="https://ipfyi.com/iframe/entity//" width="420" height="400" frameborder="0" style="border:0;border-radius:10px;max-width:100%" loading="lazy"></iframe>Paste this URL in WordPress, Medium, or any oEmbed-compatible platform.
https://ipfyi.com/entity//Add a dynamic SVG badge to your README or docs.
[](https://ipfyi.com/entity//)Use the native HTML custom element.
M. Thomson, C. Benfield · 2022-06
Abstract
RFC 9113 defines HTTP/2, the second major version of the Hypertext Transfer Protocol. HTTP/2 uses a binary framing layer over TCP that enables multiplexing of multiple requests and responses over a single TCP connection, server push, header compression via HPACK (RFC 7541), and stream prioritization. HTTP/2 is negotiated using the TLS ALPN extension (h2) or via an HTTP/1.1 Upgrade header (h2c for cleartext).
Why This RFC Matters
HTTP/2 addressed the performance limitations of HTTP/1.1, particularly the head-of-line blocking problem where a slow response blocks subsequent responses on the same connection. By multiplexing streams over a single TCP connection, HTTP/2 dramatically reduced the need for domain sharding and connection pooling tricks used to work around HTTP/1.1 limitations. HPACK header compression reduced overhead from repetitive headers on every request. RFC 9113 updated the original RFC 7540 with fixes and alignment with the RFC 9110 semantics document. HTTP/2 is now used by the majority of web servers and browsers for HTTPS connections.