HTTP/2
— Hypertext Transfer Protocol Version 2HTTP/2 keeps the same request and response semantics as HTTP/1.1 but replaces the text protocol with a binary framing layer. One TCP connection carries concurrent streams identified by stream IDs, and the HPACK algorithm compresses header fields that HTTP/1.1 repeated in full on every request.
Interactive Session: How HTTP/2 Works
Step through the packet exchange sequence between nodes.
Interactive Execution Sandbox
Interact with a live or clearly-labelled simulated instance of HTTP/2.
Threat Model & Attack Simulation
How this protocol is attacked in practice, what defenders can see, and which control stops it.
Threat model & attack simulation
SimulatedDefensive education. Every step runs in this page; no traffic is generated or sent.
HPACK bomb
Denial of serviceHighly compressed header blocks expand into enormous header tables, consuming server memory.
Build a compression bomb
The attacker sends a small compressed block that expands to a huge header set.
Header decompression memory spikes per connection.
Memory exhaustion and connection resets.
Defences that matter
- Cap decoded header size
- Limit concurrent streams and header table size
- Terminate abusive connections at the edge
This is a conceptual model for defenders, not an exploit toolkit. It contains no payloads, tooling or instructions for attacking systems you do not own.
Protocol Specification & Architecture
Key characteristics, real-world deployment patterns, and trade-offs.
Core Technical Features
- Binary framing layer with typed frames (HEADERS, DATA, SETTINGS, WINDOW_UPDATE)
- Stream multiplexing over a single TCP connection
- HPACK header compression with a dynamic table (RFC 7541)
- Per-stream and connection-level flow control
- Stream prioritisation and PING for keepalive and RTT probing
Real-World Use Cases
- Modern web browsing over HTTPS
- REST and gRPC style API traffic
- Asset-heavy sites that issue dozens of parallel requests
Advantages & Strengths
- Removes HTTP/1.1 head-of-line blocking at the request level
- Far fewer TCP connections and less header overhead per request
Limitations & Vulnerabilities
- A single lost TCP segment still stalls every multiplexed stream
- HPACK state makes implementations more complex to debug