NETWORKING / A CONCEPT NOTE
HTTP Request Lifecycle
what happens when you hit Enter
Overview · mechanism
pitfall · examples
01 / THE SHORT VERSION
The idea in a few sentences.
From typing a URL to rendering the page: DNS lookup, TCP/TLS handshake, sending the HTTP request, backend routing, receiving the response, and browser rendering.
02 / FOLLOW THE MECHANISM
How the lifecycle flows
DNS Resolution
browser converts the hostname to an IP address.
Handshake
browser establishes TCP connection and completes TLS handshake.
HTTP Exchange
browser sends the HTTP request; server processes it and replies with HTML.
Render
browser parses HTML, fetches static assets, and builds the page.
04 / COMMAND NOTES
Read the command, then the result.
Inspect the flags and arguments before trying an example. Snippets can need local setup, replacement values, or resources in your own environment.
print timing breakdown for DNS, TCP, TLS
curl -w '@curl-format.txt' -o /dev/null -s https://supraj.devtrace DNS path
dig +trace supraj.dev05 / CHECK YOURSELF
Could you explain HTTP Request Lifecycle to a teammate?
Try it out loud in two sentences: what it is, and the one detail that changes the picture. If you stall, the gap is the part to reread.
Up next in NetworkingPorts & Socketshow one machine runs many services