Recap and Practice
Key takeaways
- The web is one simple dance repeated endlessly: a client (usually a browser) sends a request, and a server sends back a response. Everything else is detail on top of that.
- A is labeled parts stitched together — scheme, host, path, query. The method is the verb: GET reads, POST creates, PUT updates, DELETE removes.
- Status codes are the server's one-glance verdict. The 4xx/5xx split tells you where to look: 4xx means the request was wrong (bad URL), 5xx means the server's own code broke.
- (the padlock) seals the conversation so nobody in the middle can read it — real apps use it always. Cookies are how a site remembers you're logged in across requests.
- Your is the client (runs in the browser); your is the server (runs your logic and talks to the ). Every feature you build lives on one side of the dance.
Try it
Open any website, then open your browser's developer tools (right-click → "Inspect", then the "Network" tab) and reload the page. Watch the list of requests fill up — you'll see one page request followed by dozens more for images, fonts, and styles, exactly as described. Click one and look at its method (GET), its (hopefully 200), and its headers. You're now seeing the request/response dance happen in real time, with the vocabulary to read it.
of the chapter
I'm learning how the web works as a beginner. Using my own app as the example:
<describe your app, or paste a URL or an error you're seeing>
- Walk me through the request/response cycle for one specific action
(like loading a page or submitting a form), step by step.
- Tell me which part is the client (frontend) and which is the server (backend).
- If I'm seeing a status code or error, explain whether it's a 4xx (my
request was wrong) or a 5xx (the server broke), and where to look.
- Keep it concrete and beginner-friendly — no assumed knowledge.