Skip to content

The HTTP Response Headers List

New Course Coming Soon:

Get Really Good at Git

Every HTTP response has a set of headers. This post aims to list all those headers, and describe them

Every HTTP response can have a set of headers.

This post aims to list all those headers, and describe them.

Standard headers


Accept-Patch: text/example;charset=utf-8

Specifies which patch document formats this server supports


Accept-Ranges: bytes

What partial content range types this server supports via byte serving


Age: 12

The age the object has been in a proxy cache in seconds


Allow: GET, HEAD

Valid methods for a specified resource. To be used for a 405 Method not allowed


Alt-Svc: http/1.1= ""; ma=7200

A server uses “Alt-Svc” header (meaning Alternative Services) to indicate that its resources can also be accessed at a different network location (host or port) or using a different protocol. When using HTTP/2, servers should instead send an ALTSVC frame


Cache-Control: max-age=3600 Cache-Control: no-cache, no-store, max-age=0, must-revalidate

If no-cache is used, the Cache-Control header can tell the browser to never use a cached version of a resource without first checking the ETag value.

max-age is measured in seconds

The more restrictive no-store option tells the browser (and all the intermediary network devices) the not even store the resource in its cache:

Cache-Control: no-store


Connection: close

Control options for the current connection and list of hop-by-hop response fields. Deprecated in HTTP/2


Content-Disposition: attachment; filename="file.txt"

An opportunity to raise a “File Download” dialogue box for a known MIME type with binary format or suggest a filename for dynamic content. Quotes are necessary with special characters


Content-Encoding: gzip

The type of encoding used on the data. See HTTP compression


Content-Language: en

The natural language or languages of the intended audience for the enclosed content


Content-Length: 348

The length of the response body expressed in 8-bit bytes


Content-Location: /index.htm

An alternate location for the returned data


Content-Range: bytes 21010-47021/47022

Where in a full body message this partial message belongs


Content-Type: text/html; charset=utf-8

The MIME type of this content


Date: Tue, 15 Nov 1994 08:12:31 GMT

The date and time that the message was sent (in “HTTP-date” format as defined by RFC 7231)


Delta-Base: "abc"

Specifies the delta-encoding entity tag of the response


ETag: "737060cd8c284d8a[...]"

An identifier for a specific version of a resource, often a message digest


Expires: Sat, 01 Dec 2018 16:00:00 GMT

Gives the date/time after which the response is considered stale (in “HTTP-date” format as defined by RFC 7231)


IM: feed

Instance-manipulations applied to the response


Last-Modified: Mon, 15 Nov 2017 12:00:00 GMT

The last modified date for the requested object (in “HTTP-date” format as defined by RFC 7231)

Link: </feed>; rel="alternate"

Used to express a typed relationship with another resource, where the relation type is defined by RFC 5988


Location: /pub/WWW/People.html

Used in redirection, or when a new resource has been created


Pragma: no-cache

Implementation-specific fields that may have various effects anywhere along the request-response chain.


Proxy-Authenticate: Basic

Request authentication to access the proxy


HTTP Public Key Pinning, announces hash of website’s authentic TLS certificate


Retry-After: 120 Retry-After: Fri, 07 Nov 2014 23:59:59 GMT

If an entity is temporarily unavailable, this instructs the client to try again later. Value could be a specified period of time (in seconds) or a HTTP-date


Server: Apache/2.4.1 (Unix)

A name for the server

Set-Cookie: UserID=JohnDoe; Max-Age=3600; Version=1

An HTTP cookie


Strict-Transport-Security: max-age=16070400; includeSubDomains

A HSTS Policy informing the HTTP client how long to cache the HTTPS only policy and whether this applies to subdomains


Trailer: Max-Forwards

The Trailer general field value indicates that the given set of header fields is present in the trailer of a message encoded with chunked transfer coding


Transfer-Encoding: chunked

The form of encoding used to safely transfer the entity to the user. Currently defined methods are: chunked, compress, deflate, gzip, identity. Deprecated in HTTP/2


Tk: ?

Tracking Status header, value suggested to be sent in response to a DNT(do-not-track), possible values: ”!” — under construction ”?” — dynamic “G” — gateway to multiple parties “N” — not tracking “T” — tracking “C” — tracking with consent “P” — tracking only if consented “D” — disregarding DNT “U” — updated


Upgrade: h2c, HTTPS/1.3, IRC/6.9, RTA/x11, websocket

Ask the client to upgrade to another protocol. Deprecated in HTTP/2


Vary: Accept-Language Vary: *

Tells downstream proxies how to match future request headers to decide whether the cached response can be used rather than requesting a fresh one from the origin server


Via: 1.0 fred, 1.1 (Apache/1.1)

Informs the client of proxies through which the response was sent


Warning: 199 Miscellaneous warning

A general warning about possible problems with the entity body


WWW-Authenticate: Basic

Indicates the authentication scheme that should be used to access the requested entity

CORS headers

Non-standard headers:


Helps to protect against XSS attacks. See MDN for more details


Refresh: 10;

Redirect to a URL after an arbitrary delay expressed in seconds


X-Powered-By: Brain/0.6b

Can be used by servers to send their name and version


Allows the server to pass a request ID that clients can send back to let the server correlate the request


Sets which version of Internet Explorer compatibility layer should be used. Only used if you need to support IE8 or IE9. See StackOverflow


Now replaced by the Content-Security-Policy header, used in older browsers to stop pages load when an XSS attack is detected

Are you intimidated by Git? Can’t figure out merge vs rebase? Are you afraid of screwing up something any time you have to do something in Git? Do you rely on ChatGPT or random people’s answer on StackOverflow to fix your problems? Your coworkers are tired of explaining Git to you all the time? Git is something we all need to use, but few of us really master it. I created this course to improve your Git (and GitHub) knowledge at a radical level. A course that helps you feel less frustrated with Git. Launching Summer 2024. Join the waiting list!

Here is how can I help you: