Reference category
Web & HTTP
HTTP is the layer where most client–server failures become visible. A status code says what the server decided, headers say how the message must be handled, and a media type says how the body must be read. These pages cover all three together because real debugging rarely needs only one of them.
Start with the status code when a request fails, then read the headers that control caching, authentication and body parsing. Every entry states the standard definition first, then the causes and fixes seen in logs, so the page is useful before you open the specification.
Reference sets in this category (3)
HTTP Status Codes — Meanings, Causes and Fixes
What each HTTP status code means, when a server should return it, what causes it in practice and how to fix it. Facts from RFC 9110, paired with free debugging tools.
30 entries →HTTP Header Reference
What the common HTTP request and response headers mean, how they are parsed, and which ones carry security consequences. Facts from RFC 9110, RFC 9111 and RFC 6265, paired with a header inspector.
15 entries →MIME Types and Content Types — Reference
What each common media type is for, which file extensions map to it, how browsers and servers treat it, and the mistakes that break uploads and APIs.
23 entries →