DevKits
47 headers

HTTP Headers Reference

Every HTTP header developers meet in production — from Content-Type and Cache-Control to the whole CORS family and modern security headers — with examples and the pitfalls that trip most people up.

Each entry explains what a header does, when to set it, and one thing that will bite you if you set it wrong — like why Cache-Control: no-cache does not actually mean “don’t cache”, or why Access-Control-Allow-Origin: * cannot be combined with credentials.

Content

Declaring and describing the message body — type, size, encoding, disposition.

Caching

Directives that tell browsers and CDNs how long and how to store a response.

Conditional

Send the resource only if it changed — the mechanics behind 304 Not Modified.

Authentication

Credentials and auth-scheme negotiation.

CORS

Cross-origin resource sharing headers — the whole `Access-Control-*` family.

Security

Headers that harden the browser against XSS, framing, MIME sniffing, and cleartext.

Cookies

Setting and reading HTTP cookies.

Ranges

Partial content requests and responses.

Request negotiation

Client hints about accepted media types, encodings, and languages.

Response

Response-only headers about servers, timing, and redirects.

Miscellaneous

Proxy propagation, protocol upgrades, and other utility headers.