HTTP and the web
Read a request and a response, and know which part of them you can trust.
For anyone who has opened the network tab and wanted to know what they were looking at. No server experience needed; the examples are the ones you meet in a browser.
Start: Requests, responses and what a status code means- Requests, responses and what a status code meansEvery exchange is a method, a path and headers one way, and a status and headers back.2 min
- URLs, and why encoding is not optionalA URL has parts with rules, and the same character means different things in different parts.2 min
- The headers you will actually meetContent type, caching and CORS explain most of what looks mysterious in a network tab.3 min
- Tokens, cookies, and what is actually secretBase64 is not encryption and a JWT is signed, not hidden — both are readable by anyone holding them.3 min