Interactive Session: How HTTP / HTTPS Works
Step through the packet exchange sequence between nodes.
Interactive Execution Sandbox
Interact with a live or clearly-labelled simulated instance of HTTP / HTTPS.
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.
HTTP request smuggling
InjectionConflicting Content-Length and Transfer-Encoding headers make a proxy and origin disagree about where one request ends.
Send ambiguous framing
A single request contains both length signals, interpreted differently by each hop.
Requests rejected by one hop but accepted by another.
Access control bypass, cache poisoning or response splitting.
Defences that matter
- Reject ambiguous message framing
- Normalise headers at the edge
- Use HTTP/2 end-to-end where possible
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
- Stateless client-server request/response model
- Standardized HTTP verbs (GET, POST, PUT, DELETE, PATCH, OPTIONS)
- Rich header semantics (caching, content negotiation, authentication)
- TLS encryption via HTTPS (Port 443)
Real-World Use Cases
- Serving web pages and SPA assets
- RESTful web APIs
- Microservice webhooks
- CDN content distribution
Advantages & Strengths
- Universal platform support across all operating systems
- Human-readable header text (HTTP/1.1)
Limitations & Vulnerabilities
- Stateless nature requires cookies/tokens for sessions
- HTTP/1.1 text header redundancy