GUIDES / HTTP / DOCUMENTATION
Practical references for web work.
Short explanations focused on what a real HTTP client or browser actually observes.
01 / HTTP
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 →REFERENCE / METHOD
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.