NetwNETW
Curriculum
CHAPTER 10

End-to-End Lifecycle

From typing a URL to pixels on screen

18 min read4 sections
In this chapter
The full journeyStep by stepWhat can go wrongTools

01The full journey

Every page load traverses every layer and every device. Understanding this single flow unifies the whole subject.

02Step by step

URL parse → cache check → DNS resolve → TCP connect → TLS handshake → HTTP request → routing → server processing → response → render.

  • ▸Browser cache check (memory/disk)
  • ▸DNS (recursive → root → TLD → authoritative)
  • ▸TCP 3-way handshake (1 RTT)
  • ▸TLS 1.3 handshake (1 RTT)
  • ▸HTTP/2 request over multiplexed stream
  • ▸Each packet routed hop-by-hop
  • ▸ACKs, retransmits, congestion control
  • ▸TLS decrypt → HTTP parse → HTML/CSS/JS → render

03What can go wrong

DNS failure, TCP timeout, TLS cert error, HTTP 4xx/5xx, packet loss, congestion, render blocking. Each maps to a layer and a diagnostic tool.

04Tools

curl, dig, traceroute, ping, tcpdump, wireshark, browser DevTools (Network tab), openssl s_client. Learn these and you can debug any network issue.