Lists media types the client can receive.
Accept: application/jsonRFC 9110 | RFC 9111 | RFC 6265 | Fetch
Search HTTP request and response headers, RFC references, syntax examples, browser notes, and common implementation mistakes.
10
Request
10
Response
7
Content
8
Cache
7
Security
8
CORS
2
Cookie
4
Authentication
Enter a header name, RFC, category, or keyword.
Looking up header reference...
Search a header name, category, keyword, or RFC reference.
Filter the server-rendered list by category, status, direction, or keyword.
Click a card name to load it into the lookup form.
Lists media types the client can receive.
Accept: application/jsonLists content codings the client can decode.
Accept-Encoding: gzip, br, zstdLists preferred natural languages.
Accept-Language: en-US, en;q=0.9Legacy header for acceptable character sets.
Accept-Charset: utf-8Carries credentials for the target resource.
Authorization: Bearer eyJhbGciOi...Challenges the client to authenticate.
WWW-Authenticate: Bearer realm="api"Carries credentials for an intermediary proxy.
Proxy-Authorization: Basic dXNlcjpwYXNzChallenges the client to authenticate to a proxy.
Proxy-Authenticate: Basic realm="proxy"Identifies the media type of the message body.
Content-Type: application/json; charset=utf-8States the body length in octets.
Content-Length: 348Identifies content codings applied to the body.
Content-Encoding: gzipIdentifies the intended language of the representation.
Content-Language: en-USIdentifies a URI for the representation in the response body.
Content-Location: /reports/current.jsonSuggests inline display or download handling for a body.
Content-Disposition: attachment; filename="report.pdf"Identifies transfer codings for HTTP/1.1 message framing.
Transfer-Encoding: chunkedIdentifies the authority of the target URI.
Host: api.example.comIdentifies software making the request.
User-Agent: Mozilla/5.0 ...Identifies the referring resource URL when available.
Referer: https://example.com/docsIdentifies the origin that initiated a request.
Origin: https://app.example.comProvides a target URI for redirects or newly created resources.
Location: https://example.com/new-pathRequests part of a representation.
Range: bytes=0-1023Describes the byte range carried in a partial response.
Content-Range: bytes 0-1023/4096Advertises whether range requests are supported.
Accept-Ranges: bytesExpresses typed links related to the current resource.
Link: <https://api.example.com/page/2>; rel="next"Tells clients when to retry after rate limiting or temporary unavailability.
Retry-After: 120Controls caching, freshness, revalidation, and storage behavior.
Cache-Control: public, max-age=3600Provides an entity tag for cache validation and concurrency checks.
ETag: "v3-report"Sends ETags the client already has for conditional requests.
If-None-Match: "v3-report"States when the representation was last changed.
Last-Modified: Tue, 15 Nov 1994 12:45:26 GMTAsks for the resource only if modified after a date.
If-Modified-Since: Tue, 15 Nov 1994 12:45:26 GMTGives an absolute expiration time for cached content.
Expires: Tue, 15 Nov 1994 12:45:26 GMTLists request headers that affect the selected representation.
Vary: Accept-Language, Accept-EncodingIndicates how long a cached response has been stored.
Age: 42Legacy cache-related header retained for old clients.
Pragma: no-cacheSends stored cookies to the server.
Cookie: session=abc123; theme=darkAsks the user agent to store a cookie.
Set-Cookie: session=abc123; Path=/; Secure; HttpOnly; SameSite=LaxTells browsers which origin may read a cross-origin response.
Access-Control-Allow-Origin: https://app.example.comLists methods allowed by a CORS preflight response.
Access-Control-Allow-Methods: GET, POST, OPTIONSLists request headers allowed by CORS preflight.
Access-Control-Allow-Headers: Authorization, Content-TypeAllows browsers to expose credentialed CORS responses.
Access-Control-Allow-Credentials: trueLists response headers visible to browser JavaScript.
Access-Control-Expose-Headers: X-Request-ID, RateLimit-RemainingControls how long browsers may cache a CORS preflight result.
Access-Control-Max-Age: 600Names the method for an upcoming CORS request.
Access-Control-Request-Method: PATCHNames headers for an upcoming CORS request.
Access-Control-Request-Headers: authorization, content-typeControls which content sources the browser may load or execute.
Content-Security-Policy: default-src 'self'; script-src 'self'Reports CSP violations without enforcing the policy.
Content-Security-Policy-Report-Only: default-src 'self'; report-to cspTells browsers to use HTTPS for future requests to the host.
Strict-Transport-Security: max-age=31536000; includeSubDomainsPrevents some browser MIME sniffing when set to nosniff.
X-Content-Type-Options: nosniffLegacy clickjacking protection header.
X-Frame-Options: DENYControls how much referrer information browsers send.
Referrer-Policy: strict-origin-when-cross-originControls access to browser features in documents and frames.
Permissions-Policy: geolocation=(), camera=()Defines reporting endpoints for browser-generated reports.
Report-To: {"group":"csp","max_age":10886400,"endpoints":[{"url":"https://reports.example.com/csp"}]}Provides browser brand client hints.
Sec-CH-UA: "Chromium";v="124", "Not:A-Brand";v="99"Indicates when the response was generated.
Date: Tue, 15 Nov 1994 12:45:26 GMTIdentifies server software in a response.
Server: nginxStandard proxy header for original client and protocol information.
Forwarded: for=203.0.113.43;proto=https;host=example.comCommunicates the maximum request quota in a rate-limit window.
RateLimit-Limit: 100Communicates remaining requests in the current rate-limit window.
RateLimit-Remaining: 42Communicates when rate-limit quota resets.
RateLimit-Reset: 60These headers are commonly seen in proxies, servers, and platforms, but they are not standards-track HTTP headers.
Lists client and proxy IP addresses added by intermediaries.
X-Forwarded-For: 203.0.113.43, 198.51.100.17Communicates the original protocol used by the client.
X-Forwarded-Proto: httpsCarries one client IP address from a proxy to an upstream app.
X-Real-IP: 203.0.113.43Carries a request identifier for tracing and logs.
X-Request-ID: req_01HZ...Carries a correlation identifier across systems.
X-Correlation-ID: 8f2d6a2c0dHTTP headers are name-value fields that describe requests, responses, caching, authentication, cookies, content negotiation, browser security, and proxy behavior. This reference is built for fast lookup: search a header, read the syntax, copy an example, and follow the official RFC or standards link when you need the full details.
HTTP header field names are case-insensitive. `Content-Type`, `content-type`, and `CONTENT-TYPE` identify the same field name. Header values are different: value syntax and case-sensitivity depend on the specific header.
Request headers are sent by clients to describe what they want or what credentials they present. Response headers are sent by servers to describe what they returned, how it can be cached, and how browsers should handle it. Some headers, such as `Content-Type`, can appear in both directions.
Security headers such as `Content-Security-Policy`, `Strict-Transport-Security`, `X-Content-Type-Options`, `Referrer-Policy`, and `Permissions-Policy` help browsers enforce safer defaults. They reduce common risks, but they do not replace secure application code, safe authentication, or input validation.
CORS headers control whether browsers expose cross-origin responses to frontend JavaScript. CORS is a browser security model, not a server-to-server access-control system. A server can return `200 OK` and still fail in the browser if preflight or credential rules are wrong.
`Cache-Control`, `ETag`, `Last-Modified`, `Vary`, `Age`, and `Expires` shape browser, proxy, and CDN cache behavior. Use `no-store` for highly sensitive responses, and use validators such as `ETag` when cached content should be revalidated instead of downloaded again.
`Cookie` and `Set-Cookie` handle browser state. Sensitive session cookies should usually include `Secure`, `HttpOnly`, and a deliberate `SameSite` policy. `Authorization` and `WWW-Authenticate` handle authentication schemes such as Bearer and Basic credentials.
Modern HTTP semantics are centered on RFC 9110, while HTTP caching is covered by RFC 9111. Cookies are specified in RFC 6265, and Structured Field Values are defined by RFC 8941. Browser-specific behavior such as CORS is primarily specified by the WHATWG Fetch Standard.
Header names are case-insensitive. Header values depend on the individual header's grammar and semantics.
Status codes summarize the result of a request. Headers carry metadata about the request, response, body, caching, authentication, security policy, and browser behavior.
Common security headers include `Content-Security-Policy`, `Strict-Transport-Security`, `X-Content-Type-Options`, `Referrer-Policy`, and `Permissions-Policy`.
The network request can succeed while the browser blocks JavaScript from reading the response because the CORS headers do not permit that origin, method, header, or credential mode.
No. Browsers control or forbid some headers, including many connection, host, cookie, origin, and CORS preflight headers.