The Full Lifecycle of an HTTP Request
The Full Lifecycle of an HTTP Request
The companion film to the featured article. We trace one real request end to end using
curl, tcpdump, and a local cluster — showing each protocol hop as it actually happens,
including the handshakes most people have only read about.
Topics covered:
- DNS resolution, caches, and
SERVFAIL - The TCP handshake and slow start
- TLS 1.3's single-round-trip handshake
- Where connection reuse saves the most time
- The database phase: planning, buffer pool, and the log
Related articles
What Happens When You Call an API?
One request, traced end to end: DNS, TCP, TLS, HTTP, load balancing, server logic, and the database — with the real cost of every hop.
How TLS Actually Secures a Connection
From the ClientHello to the session ticket: what every message in a TLS handshake does, why certificates are the center of the trust model, and how TLS 1.3 changed the game.
How HTTP/2 and HTTP/3 Change Everything
Multiplexing, server push, and QUIC — why keep-alive is the old answer and what the new protocols actually fix.
More in Networking
Depth, delivered weekly
One technical dispatch a week — articles and episode notes before they go public.
One technical dispatch per week. No noise.