What happens when you type a URL in the browser?
The definitive end-to-end walkthrough — DNS to render.
Question
Walk me through what happens between typing a URL and seeing the page.
Answer
1) Browser checks its cache, then OS cache, then hits the resolver — recursive DNS returns the A/AAAA record. 2) TCP three-way handshake to the resolved IP on port 443. 3) TLS handshake — client hello, server hello + cert, key exchange, finished. 4) HTTP request (usually HTTP/2 or HTTP/3) with cookies, headers. 5) Server processes, possibly hits app server + DB, returns response. 6) Browser parses HTML, builds DOM. 7) It fetches subresources (CSS, JS, images) — often over the same connection. 8) CSSOM built, JS executes, layout + paint + composite. Modern browsers overlap steps aggressively via preload/prefetch and speculative parsing.
See question and answer above.
Keep reading
You may also like
interview
AWS: When would you pick S3 over EBS?
The right answer shows you understand *access patterns*, not just storage products.
interview
How does Terraform know what already exists?
The most missed Terraform interview follow-up. Explain state files and how they work.
interview
Explain the CAP Theorem in one paragraph
A distributed-systems classic that trips senior engineers as often as juniors.
Discussion (0)
No comments yet. Be the first to weigh in.