Explain, in order, the major systems involved between pressing Enter and a
page appearing on screen — DNS, TCP/QUIC, TLS, HTTP, routing, proxies, load
balancing, caching, and rendering.
Read a raw HTTP request or response and know what every header actually
does, not just its name.
Explain the TLS 1.3 handshake, why forward secrecy matters, and how a
certificate chain of trust actually establishes identity.
Trace a packet's exact path from your laptop to a server on the other
side of the world — NAT, BGP, anycast, and VRRP included.
Explain why a CDN and a load balancer both exist, and what job each does
that the other genuinely cannot.
Walk through the browser's rendering pipeline and diagnose why a real
page feels janky or shifts around while loading.
Name the specific attack (XSS, CSRF, SSRF, clickjacking...) each security
header and cookie flag in this lifecycle actually defends against.
Talk about SLI/SLO, 95th-percentile billing, and traffic engineering the
way a network engineer operating a real datacenter actually does, and
set SRE-style SLOs, error budgets, and burn-rate alerts for a service.
Build the server side in Go: a hardened HTTPS server, a reverse proxy, a
caching edge, retries with idempotency, SSRF-safe clients, and streaming
endpoints. Thirteen labs, each tested against real sites, ending with one
request traced through every guide in the series (Chapter 25).
