HH

HTTP Headers Reference

Complete reference of common HTTP request and response headers with descriptions

39 headers
AcceptRequest

Informs the server about the types of data that can be sent back. It is MIME-type information.

Accept-EncodingRequest

Indicates the content-encoding (usually a compression algorithm) that the client can understand.

Accept-LanguageRequest

Indicates the natural language and locale that the client prefers.

Accept-RangesResponse

Indicates if the server supports range requests, and if so in which unit the range can be expressed.

Access-Control-Allow-OriginResponse

Indicates whether the response can be shared with requesting code from the given origin (CORS).

AgeResponse

The time in seconds the object has been in a proxy cache.

AuthorizationRequest

Contains the credentials to authenticate a user agent with a server, usually after the server has responded with 401.

Cache-ControlBoth

Directives for caching mechanisms in both requests and responses. Caching directives are unidirectional.

ConnectionBoth

Controls whether the network connection stays open after the current transaction finishes.

Content-DispositionResponse

Indicates if the content is expected to be displayed inline or downloaded as an attachment.

Content-EncodingBoth

Lists the encodings that have been applied to the entity-body, and the order in which they have been applied.

Content-LengthBoth

The length of the request/response body in octets (8-bit bytes).

Content-Security-PolicyResponse

Controls resources the user agent is allowed to load for a given page. Helps prevent XSS attacks.

Content-TypeBoth

Indicates the media type of the resource. In requests, the client tells the server what type of data is sent.

CookieRequest

Contains stored HTTP cookies previously sent by the server with the Set-Cookie header.

ETagResponse

An identifier for a specific version of a resource. Allows caches to be more efficient and saves bandwidth.

ExpiresResponse

The date/time after which the response is considered stale.

ForwardedRequest

Contains information from the client-facing side of proxy servers that is altered or lost when a proxy is involved.

HostRequest

Specifies the host and port number of the server to which the request is being sent.

If-Modified-SinceRequest

Makes the request conditional: the server sends back the requested resource only if it has been modified after the given date.

If-None-MatchRequest

Makes the request conditional: returns 304 Not Modified if the ETag matches, allowing conditional GET requests.

Last-ModifiedResponse

The last modification date of the resource, used to compare several versions of the same resource.

LocationResponse

Indicates the URL to redirect a page to. It only provides a meaning when served with a 3xx or 201 status response.

OriginRequest

Indicates where a fetch originates from. It includes the scheme, the hostname and port. Sent with CORS requests.

RefererRequest

Contains the address of the previous web page from which a link to the currently requested page was followed.

Retry-AfterResponse

Indicates how long the user agent should wait before making a follow-up request (used with 429 or 503).

ServerResponse

Contains information about the software used by the origin server to handle the request.

Set-CookieResponse

Send cookies from the server to the user-agent so the user-agent can send them back later.

Strict-Transport-SecurityResponse

Lets a website tell browsers that it should only be accessed using HTTPS, instead of using HTTP (HSTS).

Transfer-EncodingBoth

Specifies the form of encoding used to safely transfer the payload body to the user.

User-AgentRequest

Contains a characteristic string that allows the network protocol peers to identify the application type, OS, and software vendor/version.

VaryResponse

Determines how to match future request headers to decide whether a cached response can be used or a fresh one must be requested.

WWW-AuthenticateResponse

Defines the authentication method that should be used to gain access to a resource (sent with 401 Unauthorized).

X-Content-Type-OptionsResponse

Indicates that the MIME types advertised in the Content-Type headers should be followed and not be changed.

X-Forwarded-ForRequest

Identifies the originating IP addresses of a client connecting through an HTTP proxy or a load balancer.

X-Frame-OptionsResponse

Indicates whether or not a browser should be allowed to render a page in a frame, iframe, embed or object. Used to prevent clickjacking.

X-RateLimit-LimitResponse

The maximum number of requests that the consumer is permitted to make per rate limit window.

X-Request-IDBoth

A unique identifier attached to each request for tracing and debugging purposes across distributed systems.

X-XSS-ProtectionResponse

Deprecated: controlled the old XSS filter in IE, Chrome and Safari, which current browsers have removed (Firefox never had it). Use Content-Security-Policy instead; if sent, use "0".

Opens your print window: choose "Save as PDF". The file is named "HTTP Headers Reference - MondayTool".
About this tool

Last updated:

Look up common HTTP headers

This HTTP headers reference lists 39 headers you meet most often when building or debugging web requests. Each entry shows the header name, whether it belongs to requests, responses or both, and a short description of its purpose.

How to use it

  1. Type a word into the search box, for example cache, cors or a header name such as ETag.
  2. Use the tabs All, Request, Response or Both to narrow the list.
  3. Read the description under each header name. The counter shows how many headers match.

How it works

The list is built into the page, so searching is instant and needs no network call. Search checks the header name, the description and the type label. The Request and Response tabs also include headers marked Both, because those can appear in either direction. The Both tab shows only that group.

What you see

FieldMeaning
NameThe header as it is written on the wire, such as Content-Type
TypeRequest, Response or Both
DescriptionWhat the header tells the client, server or cache

The list covers content negotiation, caching, CORS, cookies, redirects, authentication, proxies and a few security headers such as Content-Security-Policy and Strict-Transport-Security.

Assumptions and limits

  • It is a short reference of common headers, not the full IANA registry.
  • Descriptions are brief. They do not list every directive or syntax rule for a header.
  • The tool does not send requests or read the headers of any live site.

Frequently asked questions

What is the difference between request and response headers?

Request headers are sent by the client, such as Accept or Authorization. Response headers come back from the server, such as Set-Cookie or ETag. Some, like Cache-Control, are used in both directions.

Why do Both headers show under the Request tab?

A header marked Both can be sent in a request as well, so it is included when you filter by Request or Response.

Can I see the headers a website actually returns?

Not here. This page only explains headers. Use your browser's network panel or an HTTP client to see real ones.

More to explore

Related Network & API

Browse all tools from the same category.

Showing 1-2 of 7