Practical references for web work.
Short explanations focused on what a real HTTP client or browser actually observes.
Status codes in context
Why 200, 304, 401, 403, 404 and 503 mean different things to clients.
Open →02 / HTTPUseful response headers
Content types, cache behaviour, validators and the limits of headers.
Open →03 / HTTPChoose the right Content-Type
A browser-oriented guide to MIME types, JSON responses and accidental content interpretation.
Open →04 / HTTPUnderstand validators before long cache lifetimes
Practical HTTP caching rules for HTML, assets, revalidation and unexpected stale responses.
Open →05 / HTTPRedirects are changes to request flow
An HTTP guide to 301, 302, 303, 307 and 308 with practical methods for testing chains.
Open →Keep examples reproducible
The examples use conventional HTTP semantics rather than an invented private API. You can examine responses from a server you control with curl -I and curl -v.
Always test real applications as well as static responses: reverse proxies can change which headers and status codes reach clients.
Begin with the response you can actually observe. Status codes answer one question, media types answer another and redirect headers may move a request to a different resource. Inspect those elements separately before changing a configuration. The additional chapters cover caching, representations and location changes. Each guide includes a method for testing the behaviour on a service you control.