How a Web Page Reaches Your Screen
The path from typing an address to seeing a page: the name looked up as an address, a request sent to a server, a reply of files the browser assembles.
What a learner can do afterwards
- Put the steps in order from pressing enter to a finished page
- Explain what the name lookup is for and what breaks without it
- Tell apart what the browser does from what the server does
1 · Read
Pressing enter starts a chain: your browser looks up the address, asks the server, receives page files, then builds the page. Request out, reply back, page up.
Computers knock with numbers, not names, so DNS works like a phone book. Type wikipedia.org and DNS returns the matching address to knock on. If DNS fails, names lead nowhere, though the site itself runs fine.
The jobs split cleanly. The server stores the files and hands them over: HTML for words and structure, CSS for colours and layout, JavaScript for motion and clicks. Your browser asks, then assembles those pieces for your screen.
Each link can snap. A slow server leaves your browser hanging until it quits with a 504. A request with no path dies as unreachable. No reply, no page.
Look up the name, request the files, and let the browser build what the server stores.
2 · Watch
Take it off screen
Where it sits
8 questions wait behind this lesson, each with its answer explained. Every answer feeds the sky: stars light as they are learned, and dim when it is time to come back.