List of HTTP header fields

HTTP header fields are a list of strings sent and received by both the client program and server on every HTTP request and response. These headers are usually invisible to the end-user and are only processed or logged by the server and client applications. They define how information sent/received through the connection are encoded (as in Content-Encoding), the session verification and identification of the client (as in browser cookies, IP address, user-agent) or their anonymity thereof (VPN or proxy masking, user-agent spoofing), how the server should handle data (as in Do-Not-Track), the age (the time it has resided in a shared cache) of the document being downloaded, amongst others.

General format

In HTTP version 1.x, header fields are transmitted after the request line (in case of a request HTTP message) or the response line (in case of a response HTTP message), which is the first line of a message. Header fields are colon-separated key-value pairs in clear-text string format, terminated by a carriage return (CR) and line feed (LF) character sequence. The end of the header section is indicated by an empty field line, resulting in the transmission of two consecutive CR-LF pairs. In the past, long lines could be folded into multiple lines; continuation lines are indicated by the presence of a space (SP) or horizontal tab (HT) as the first character on the next line. This folding was deprecated in RFC 7230.^[1]

HTTP/2^[2] and HTTP/3 instead use a binary protocol, where headers are encoded in a single HEADERS and zero or more CONTINUATION frames using HPACK^[3] (HTTP/2) or QPACK (HTTP/3), which both provide efficient header compression. The request or response line from HTTP/1 has also been replaced by several pseudo-header fields, each beginning with a colon (:).

Field names

A core set of fields is standardized by the Internet Engineering Task Force (IETF) in RFC 9110 and 9111. The Field Names, Header Fields and Repository of Provisional Registrations are maintained by the IANA. Additional field names and permissible values may be defined by each application.

Header field names are case-insensitive.^[4] This is in contrast to HTTP method names (GET, POST, etc.), which are case-sensitive.^[5]

HTTP/2 makes some restrictions on specific header fields (see below).

Non-standard header fields were conventionally marked by prefixing the field name with X- but this convention was deprecated in June 2012 because of the inconveniences it caused when non-standard fields became standard.^[6] An earlier restriction on use of Downgraded- was lifted in March 2013.^[7]

Field values

A few fields can contain comments (i.e. in User-Agent, Server, Via fields), which can be ignored by software.^[8]

Many field values may contain a quality (q) key-value pair separated by equals sign, specifying a weight to use in content negotiation.^[9] For example, a browser may indicate that it accepts information in German or English, with German as preferred by setting the q value for de higher than that of en, as follows:

Accept-Language: de; q=1.0, en; q=0.5

Size limits

The standard imposes no limits to the size of each header field name or value, or to the number of fields. However, most servers, clients, and proxy software impose some limits for practical and security reasons. For example, the Apache 2.3 server by default limits the size of each field to 8,190 bytes, and there can be at most 100 header fields in a single request.^[10]

Request fields

Standard request fields

Name	Description	Example	Status	Standard
A-IM	Acceptable instance-manipulations for the request.^[11]	A-IM: feed	Permanent	RFC 3229
Accept	Media type(s) that is/are acceptable for the response. See Content negotiation.	Accept: text/html	Permanent	RFC 9110
Accept-Charset	Character sets that are acceptable.	Accept-Charset: utf-8	Permanent	RFC 9110
Accept-Datetime	Acceptable version in time.	Accept-Datetime: Thu, 31 May 2007 20:35:00 GMT	Provisional	RFC 7089
Accept-Encoding	List of acceptable encodings. See HTTP compression.	Accept-Encoding: gzip, deflate	Permanent	RFC 9110
Accept-Language	List of acceptable human languages for response. See Content negotiation.	Accept-Language: en-US	Permanent	RFC 9110
Access-Control-Request-Method, Access-Control-Request-Headers^[12]	Initiates a request for cross-origin resource sharing with Origin (below).	Access-Control-Request-Method: GET	Permanent: standard
Authorization	Authentication credentials for HTTP authentication.	Authorization: Basic QWxhZGRpbjpvcGVuIHNlc2FtZQ==	Permanent	RFC 9110
Cache-Control	Used to specify directives that must be obeyed by all caching mechanisms along the request-response chain.	Cache-Control: no-cache	Permanent	RFC 9111
Connection	Control options for the current connection and list of hop-by-hop request fields.^[13] Must not be used with HTTP/2.^[14]	Connection: keep-alive Connection: Upgrade	Permanent	RFC 9110
Content-Encoding	The type of encoding used on the data. See HTTP compression.	Content-Encoding: gzip	Permanent	RFC 9110
Content-Length	The length of the request body in octets (8-bit bytes).	Content-Length: 348	Permanent	RFC 9110
Content-MD5	A Base64-encoded binary MD5 sum of the content of the request body.	Content-MD5: Q2hlY2sgSW50ZWdyaXR5IQ==	Obsolete^[15]	RFC 1544, 1864, 4021
Content-Type	The Media type of the body of the request (used with POST and PUT requests).	Content-Type: application/x-www-form-urlencoded	Permanent	RFC 9110
Cookie	An HTTP cookie previously sent by the server with Set-Cookie (below).	Cookie: $Version=1; Skin=new;	Permanent: standard	RFC 2965, 6265
Date	The date and time at which the message was originated (in "HTTP-date" format as defined by RFC 9110: HTTP Semantics, section 5.6.7 "Date/Time Formats").	Date: Tue, 15 Nov 1994 08:12:31 GMT	Permanent	RFC 9110
Expect	Indicates that particular server behaviors are required by the client.	Expect: 100-continue	Permanent	RFC 9110
Forwarded	Disclose original information of a client connecting to a web server through an HTTP proxy.^[16]	Forwarded: for=192.0.2.60;proto=http;by=203.0.113.43 Forwarded: for=192.0.2.43, for=198.51.100.17	Permanent	RFC 7239
From	The email address of the user making the request.	From: [e-mail]	Permanent	RFC 9110
Host	The domain name of the server (for virtual hosting), and the TCP port number on which the server is listening. The port number may be omitted if the port is the standard port for the service requested. Mandatory since HTTP/1.1.^[17] If the request is generated directly in HTTP/2, it should not be used.^[18]	Host: en.wikipedia.org:8080 Host: en.wikipedia.org
HTTP2-Settings	A request that upgrades from HTTP/1.1 to HTTP/2 MUST include exactly one HTTP2-Setting header field. The HTTP2-Settings header field is a connection-specific header field that includes parameters that govern the HTTP/2 connection, provided in anticipation of the server accepting the request to upgrade.^[19]^[20]	HTTP2-Settings: token64	Permanent: standard
If-Match	Only perform the action if the client supplied entity matches the same entity on the server. This is mainly for methods like PUT to only update a resource if it has not been modified since the user last updated it.	If-Match: "737060cd8c284d8af7ad3082f209582d"	Permanent	RFC 9110
If-Modified-Since	Allows a 304 Not Modified to be returned if content is unchanged.	If-Modified-Since: Sat, 29 Oct 1994 19:43:31 GMT	Permanent	RFC 9110
If-None-Match	Allows a 304 Not Modified to be returned if content is unchanged, see HTTP ETag.	If-None-Match: "737060cd8c284d8af7ad3082f209582d"	Permanent	RFC 9110
If-Range	If the entity is unchanged, send me the part(s) that I am missing; otherwise, send me the entire new entity.	If-Range: "737060cd8c284d8af7ad3082f209582d"	Permanent	RFC 9110
If-Unmodified-Since	Only send the response if the entity has not been modified since a specific time.	If-Unmodified-Since: Sat, 29 Oct 1994 19:43:31 GMT	Permanent	RFC 9110
Max-Forwards	Limit the number of times the message can be forwarded through proxies or gateways.	Max-Forwards: 10	Permanent	RFC 9110
Origin^[12]	Initiates a request for cross-origin resource sharing (asks server for Access-Control-* response fields).	Origin: http://www.example-social-network.com	Permanent: standard	RFC 6454
Pragma	Implementation-specific fields that may have various effects anywhere along the request-response chain.	Pragma: no-cache	Permanent	RFC 9111
Prefer	Allows client to request that certain behaviors be employed by a server while processing a request.	Prefer: return=representation	Permanent	RFC 7240
Proxy-Authorization	Authorization credentials for connecting to a proxy.	Proxy-Authorization: Basic QWxhZGRpbjpvcGVuIHNlc2FtZQ==	Permanent	RFC 9110
Range	Request only part of an entity. Bytes are numbered from 0. See Byte serving.	Range: bytes=500-999	Permanent	RFC 9110
Referer [sic]	This is the address of the previous web page from which a link to the currently requested page was followed. (The word "referrer" has been misspelled in the RFC as well as in most implementations to the point that it has become standard usage and is considered correct terminology)	Referer: http://en.wikipedia.org/wiki/Main_Page	Permanent	RFC 9110
TE	The transfer encodings the user agent is willing to accept: the same values as for the response header field Transfer-Encoding can be used, plus the "trailers" value (related to the "chunked" transfer method) to notify the server it expects to receive additional fields in the trailer after the last, zero-sized, chunk. Only trailers is supported in HTTP/2.^[14]	TE: trailers, deflate	Permanent	RFC 9110
Trailer	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.	Trailer: Max-Forwards	Permanent	RFC 9110
Transfer-Encoding	The form of encoding used to safely transfer the entity to the user. Currently defined methods are: chunked, compress, deflate, gzip, identity. Must not be used with HTTP/2.^[14]	Transfer-Encoding: chunked	Permanent	RFC 9110
User-Agent	The user agent string of the user agent.	User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20100101 Firefox/12.0	Permanent	RFC 9110
Upgrade	Ask the server to upgrade to another protocol. Must not be used in HTTP/2.^[14]	Upgrade: h2c, HTTPS/1.3, IRC/6.9, RTA/x11, websocket	Permanent	RFC 9110
Via	Informs the server of proxies through which the request was sent.	Via: 1.0 fred, 1.1 example.com (Apache/1.1)	Permanent	RFC 9110
Warning	A general warning about possible problems with the entity body.	Warning: 199 Miscellaneous warning	Obsolete^[21]	RFC 7234, 9111

Common non-standard request fields

Field name	Description	Example
Upgrade-Insecure-Requests^[22]	Tells a server which (presumably in the middle of a HTTP -> HTTPS migration) hosts mixed content that the client would prefer redirection to HTTPS and can handle Content-Security-Policy: upgrade-insecure-requests Must not be used with HTTP/2^[14]	Upgrade-Insecure-Requests: 1
X-Requested-With	Mainly used to identify Ajax requests (most JavaScript frameworks send this field with value of XMLHttpRequest); also identifies Android apps using WebView^[23]	X-Requested-With: XMLHttpRequest
DNT^[24]	Requests a web application to disable their tracking of a user. This is Mozilla's version of the X-Do-Not-Track header field (since Firefox 4.0 Beta 11). Safari and IE9 also have support for this field.^[25] On March 7, 2011, a draft proposal was submitted to IETF.^[26] The W3C Tracking Protection Working Group is producing a specification.^[27]	DNT: 1 (Do Not Track Enabled) DNT: 0 (Do Not Track Disabled)
X-Forwarded-For^[28]	A de facto standard for identifying the originating IP address of a client connecting to a web server through an HTTP proxy or load balancer. Superseded by Forwarded header.	X-Forwarded-For: client1, proxy1, proxy2 X-Forwarded-For: 129.78.138.66, 129.78.64.103
X-Forwarded-Host^[29]	A de facto standard for identifying the original host requested by the client in the Host HTTP request header, since the host name and/or port of the reverse proxy (load balancer) may differ from the origin server handling the request. Superseded by Forwarded header.	X-Forwarded-Host: en.wikipedia.org:8080 X-Forwarded-Host: en.wikipedia.org
X-Forwarded-Proto^[30]	A de facto standard for identifying the originating protocol of an HTTP request, since a reverse proxy (or a load balancer) may communicate with a web server using HTTP even if the request to the reverse proxy is HTTPS. An alternative form of the header (X-ProxyUser-Ip) is used by Google clients talking to Google servers. Superseded by Forwarded header.	X-Forwarded-Proto: https
Front-End-Https^[31]	Non-standard header field used by Microsoft applications and load-balancers	Front-End-Https: on
X-Http-Method-Override^[32]	Requests a web application to override the method specified in the request (typically POST) with the method given in the header field (typically PUT or DELETE). This can be used when a user agent or firewall prevents PUT or DELETE methods from being sent directly (note that this is either a bug in the software component, which ought to be fixed, or an intentional configuration, in which case bypassing it may be the wrong thing to do).	X-HTTP-Method-Override: DELETE
X-ATT-DeviceId^[33]	Allows easier parsing of the MakeModel/Firmware that is usually found in the User-Agent String of AT&T Devices	X-Att-Deviceid: GT-P7320/P7320XXLPG
X-Wap-Profile^[34]	Links to an XML file on the Internet with a full description and details about the device currently connecting. In the example to the right is an XML file for an AT&T Samsung Galaxy S2.	x-wap-profile: http://wap.samsungmobile.com/uaprof/SGH-I777.xml
Proxy-Connection^[35]	Implemented as a misunderstanding of the HTTP specifications. Common because of mistakes in implementations of early HTTP versions. Has exactly the same functionality as standard Connection field. Must not be used with HTTP/2.^[14]	Proxy-Connection: keep-alive
X-UIDH^[36]^[37]^[38]	Server-side deep packet insertion of a unique ID identifying customers of Verizon Wireless; also known as "perma-cookie" or "supercookie"	X-UIDH: ...
X-Csrf-Token^[39]	Used to prevent cross-site request forgery. Alternative header names are: X-CSRFToken^[40] and X-XSRF-TOKEN^[41]	X-Csrf-Token: i8XNjC4b8KVok4uw5RftR38Wgp2BFwql
X-Request-ID,^[stackoverflow2 1]^[42] X-Correlation-ID,^[43] Correlation-ID^[44]	Correlates HTTP requests between a client and server.	X-Request-ID: f058ebd6-02f7-4d3f-942e-904344e8cde5
Save-Data^[45]	The Save-Data client hint request header available in Chrome, Opera, and Yandex browsers lets developers deliver lighter, faster applications to users who opt-in to data saving mode in their browser.	Save-Data: on

Response fields

Standard response fields

Field name	Description	Example	Status	Standard
Accept-CH	Requests HTTP Client Hints	Accept-CH: UA, Platform	Experimental	RFC 8942
Access-Control-Allow-Origin, Access-Control-Allow-Credentials, Access-Control-Expose-Headers, Access-Control-Max-Age, Access-Control-Allow-Methods, Access-Control-Allow-Headers^[12]	Specifying which web sites can participate in cross-origin resource sharing	Access-Control-Allow-Origin: *	Permanent: standard	RFC 7480
Accept-Patch^[46]	Specifies which patch document formats this server supports	Accept-Patch: text/example;charset=utf-8	Permanent	RFC 5789
Accept-Ranges	What partial content range types this server supports via byte serving	Accept-Ranges: bytes	Permanent	RFC 9110
Age	The age the object has been in a proxy cache in seconds	Age: 12	Permanent	RFC 9111
Allow	Valid methods for a specified resource. To be used for a 405 Method not allowed	Allow: GET, HEAD	Permanent	RFC 9110
Alt-Svc^[47]	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. ^[48]	Alt-Svc: http/1.1="http2.example.com:8001"; ma=7200	Permanent
Cache-Control	Tells all caching mechanisms from server to client whether they may cache this object. It is measured in seconds	Cache-Control: max-age=3600	Permanent	RFC 9111
Connection	Control options for the current connection and list of hop-by-hop response fields.^[13] Must not be used with HTTP/2.^[14]	Connection: close	Permanent	RFC 9110
Content-Disposition^[49]	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-Disposition: attachment; filename="fname.ext"	Permanent	RFC 2616, 4021, 6266
Content-Encoding	The type of encoding used on the data. See HTTP compression.	Content-Encoding: gzip	Permanent	RFC 9110
Content-Language	The natural language or languages of the intended audience for the enclosed content^[50]	Content-Language: da	Permanent	RFC 9110
Content-Length	The length of the response body in octets (8-bit bytes)	Content-Length: 348	Permanent	RFC 9110
Content-Location	An alternate location for the returned data	Content-Location: /index.htm	Permanent	RFC 9110
Content-MD5	A Base64-encoded binary MD5 sum of the content of the response	Content-MD5: Q2hlY2sgSW50ZWdyaXR5IQ==	Obsolete^[15]	RFC 1544, 1864, 4021
Content-Range	Where in a full body message this partial message belongs	Content-Range: bytes 21010-47021/47022	Permanent	RFC 9110
Content-Type	The MIME type of this content	Content-Type: text/html; charset=utf-8	Permanent	RFC 9110
Date	The date and time that the message was sent (in "HTTP-date" format as defined by RFC 9110)	Date: Tue, 15 Nov 1994 08:12:31 GMT	Permanent	RFC 9110
Delta-Base	Specifies the delta-encoding entity tag of the response.^[11]	Delta-Base: "abc"	Permanent	RFC 3229
ETag	An identifier for a specific version of a resource, often a message digest	ETag: "737060cd8c284d8af7ad3082f209582d"	Permanent	RFC 9110
Expires	Gives the date/time after which the response is considered stale (in "HTTP-date" format as defined by RFC 9110)	Expires: Thu, 01 Dec 1994 16:00:00 GMT	Permanent: standard	RFC 9111
IM	Instance-manipulations applied to the response.^[11]	IM: feed	Permanent	RFC 3229
Last-Modified	The last modified date for the requested object (in "HTTP-date" format as defined by RFC 9110)	Last-Modified: Tue, 15 Nov 1994 12:45:26 GMT	Permanent	RFC 9110
Link	Used to express a typed relationship with another resource, where the relation type is defined by RFC 5988	Link: </feed>; rel="alternate"^[51]	Permanent	RFC 5988
Location	Used in redirection, or when a new resource has been created.	Example 1: Location: http://www.w3.org/pub/WWW/People.html Example 2: Location: /pub/WWW/People.html	Permanent	RFC 9110
P3P	This field is supposed to set P3P policy, in the form of P3P:CP="your_compact_policy". However, P3P did not take off,^[52] most browsers have never fully implemented it, a lot of websites set this field with fake policy text, that was enough to fool browsers the existence of P3P policy and grant permissions for third party cookies.	P3P: CP="This is not a P3P policy! See https://en.wikipedia.org/wiki/Special:CentralAutoLogin/P3P for more info."	Permanent
Pragma	Implementation-specific fields that may have various effects anywhere along the request-response chain.	Pragma: no-cache	Permanent	RFC 9111
Preference-Applied	Indicates which Prefer tokens were honored by the server and applied to the processing of the request.	Preference-Applied: return=representation	Permanent	RFC 7240
Proxy-Authenticate	Request authentication to access the proxy.	Proxy-Authenticate: Basic	Permanent	RFC 9110
Public-Key-Pins^[53]	HTTP Public Key Pinning, announces hash of website's authentic TLS certificate	Public-Key-Pins: max-age=2592000; pin-sha256="E9CZ9INDbd+2eRQozYqqbQ2yXLVKB9+xcprMF+44U1g=";	Permanent	RFC 7469
Retry-After	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.^[54]	Example 1: Retry-After: 120 Example 2: Retry-After: Fri, 07 Nov 2014 23:59:59 GMT	Permanent	RFC 9110
Server	A name for the server	Server: Apache/2.4.1 (Unix)	Permanent	RFC 9110
Set-Cookie	An HTTP cookie	Set-Cookie: UserID=JohnDoe; Max-Age=3600; Version=1	Permanent: standard	RFC 6265
Strict-Transport-Security	A HSTS Policy informing the HTTP client how long to cache the HTTPS only policy and whether this applies to subdomains.	Strict-Transport-Security: max-age=16070400; includeSubDomains	Permanent: standard
Trailer	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.	Trailer: Max-Forwards	Permanent	RFC 9110
Transfer-Encoding	The form of encoding used to safely transfer the entity to the user. Currently defined methods are: chunked, compress, deflate, gzip, identity. Must not be used with HTTP/2.^[14]	Transfer-Encoding: chunked	Permanent	RFC 9110
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	Tk: ?	Permanent
Upgrade	Ask the client to upgrade to another protocol. Must not be used in HTTP/2^[14]	Upgrade: h2c, HTTPS/1.3, IRC/6.9, RTA/x11, websocket	Permanent	RFC 9110
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.	Example 1: Vary: * Example 2: Vary: Accept-Language	Permanent	RFC 9110
Via	Informs the client of proxies through which the response was sent.	Via: 1.0 fred, 1.1 example.com (Apache/1.1)	Permanent	RFC 9110
Warning	A general warning about possible problems with the entity body.	Warning: 199 Miscellaneous warning	Obsolete^[21]	RFC 7234, 9111
WWW-Authenticate	Indicates the authentication scheme that should be used to access the requested entity.	WWW-Authenticate: Basic	Permanent	RFC 9110
X-Frame-Options^[55]	Clickjacking protection: deny - no rendering within a frame, sameorigin - no rendering if origin mismatch, allow-from - allow from specified location, allowall - non-standard, allow from any location	X-Frame-Options: deny	Obsolete^[56]

Common non-standard response fields

Field name	Description	Example
Content-Security-Policy, X-Content-Security-Policy, X-WebKit-CSP^[57]	Content Security Policy definition.	X-WebKit-CSP: default-src 'self'
Expect-CT^[58]	Notify to prefer to enforce Certificate Transparency.	Expect-CT: max-age=604800, enforce, report-uri="https://example.example/report"
NEL^[59]	Used to configure network request logging.	NEL: { "report_to": "name_of_reporting_group", "max_age": 12345, "include_subdomains": false, "success_fraction": 0.0, "failure_fraction": 1.0 }
Permissions-Policy^[60]	To allow or disable different features or APIs of the browser.	Permissions-Policy: fullscreen=(), camera=(), microphone=(), geolocation=(), interest-cohort=()^[61]
Refresh	Used in redirection, or when a new resource has been created. This refresh redirects after 5 seconds. Header extension introduced by Netscape and supported by most web browsers. Defined by HTML Standard^[62]	Refresh: 5; url=http://www.w3.org/pub/WWW/People.html
Report-To^[63]	Instructs the user agent to store reporting endpoints for an origin.	Report-To: { "group": "csp-endpoint", "max_age": 10886400, "endpoints": [ { "url": "https-url-of-site-which-collects-reports" } ] }
Status	CGI header field specifying the status of the HTTP response. Normal HTTP responses use a separate "Status-Line" instead, defined by RFC 9110.^[64]	Status: 200 OK
Timing-Allow-Origin	The Timing-Allow-Origin response header specifies origins that are allowed to see values of attributes retrieved via features of the Resource Timing API, which would otherwise be reported as zero due to cross-origin restrictions.^[65]	Timing-Allow-Origin: * Timing-Allow-Origin: <origin>[, <origin>]*
X-Content-Duration^[66]	Provide the duration of the audio or video in seconds; only supported by Gecko browsers	X-Content-Duration: 42.666
X-Content-Type-Options^[67]	The only defined value, "nosniff", prevents Internet Explorer from MIME-sniffing a response away from the declared content-type. This also applies to Google Chrome, when downloading extensions.^[68]	X-Content-Type-Options: nosniff^[69]
X-Powered-By^[stackoverflow1 1]	Specifies the technology (e.g. ASP.NET, PHP, JBoss) supporting the web application (version details are often in X-Runtime, X-Version, or X-AspNet-Version)	X-Powered-By: PHP/5.4.0
X-Redirect-By^[70]	Specifies the component that is responsible for a particular redirect.	X-Redirect-By: WordPress X-Redirect-By: Polylang
X-Request-ID, X-Correlation-ID^[stackoverflow2 1]	Correlates HTTP requests between a client and server.	X-Request-ID: f058ebd6-02f7-4d3f-942e-904344e8cde5
X-UA-Compatible^[71]	Recommends the preferred rendering engine (often a backward-compatibility mode) to use to display the content. Also used to activate Chrome Frame in Internet Explorer. In HTML Standard, only the IE=edge value is defined.^[72]	X-UA-Compatible: IE=edge X-UA-Compatible: IE=EmulateIE7 X-UA-Compatible: Chrome=1
X-XSS-Protection^[73]	Cross-site scripting (XSS) filter	X-XSS-Protection: 1; mode=block

Effects of selected fields

Avoiding caching

If a web server responds with Cache-Control: no-cache then a web browser or other caching system (intermediate proxies) must not use the response to satisfy subsequent requests without first checking with the originating server (this process is called validation). This header field is part of HTTP version 1.1, and is ignored by some caches and browsers. It may be simulated by setting the Expires HTTP version 1.0 header field value to a time earlier than the response time. Notice that no-cache is not instructing the browser or proxies about whether or not to cache the content. It just tells the browser and proxies to validate the cache content with the server before using it (this is done by using If-Modified-Since, If-Unmodified-Since, If-Match, If-None-Match attributes mentioned above). Sending a no-cache value thus instructs a browser or proxy to not use the cache contents merely based on "freshness criteria" of the cache content. Another common way to prevent old content from being shown to the user without validation is Cache-Control: max-age=0. This instructs the user agent that the content is stale and should be validated before use.

The header field Cache-Control: no-store is intended to instruct a browser application to make a best effort not to write it to disk (i.e not to cache it).

The request that a resource should not be cached is no guarantee that it will not be written to disk. In particular, the HTTP/1.1 definition draws a distinction between history stores and caches. If the user navigates back to a previous page a browser may still show you a page that has been stored on disk in the history store. This is correct behavior according to the specification. Many user agents show different behavior in loading pages from the history store or cache depending on whether the protocol is HTTP or HTTPS.

The Cache-Control: no-cache HTTP/1.1 header field is also intended for use in requests made by the client. It is a means for the browser to tell the server and any intermediate caches that it wants a fresh version of the resource. The Pragma: no-cache header field, defined in the HTTP/1.0 spec, has the same purpose. It, however, is only defined for the request header. Its meaning in a response header is not specified.^[74] The behavior of Pragma: no-cache in a response is implementation specific. While some user agents do pay attention to this field in responses,^[75] the HTTP/1.1 RFC specifically warns against relying on this behavior.

See also

• HTTP header injection
• HTTP ETag
• List of HTTP status codes

References

1. "Field Parsing". Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing. June 2014. sec. 3.2.4. doi:10.17487/RFC7230. RFC 7230.
2. HTTP/2. June 2022. doi:10.17487/RFC9113. RFC 9113.
3. "HPACK: Header Compression for HTTP/2". IETF. May 2015. Retrieved December 13, 2021.
4. "Field Names". HTTP Semantics. June 2022. sec. 5.1. doi:10.17487/RFC9110. RFC 9110.
5. "Methods: Overview". HTTP Semantics. June 2022. sec. 9.1. doi:10.17487/RFC9110. RFC 9110.
6. Internet Engineering Task Force (June 1, 2012). "RFC 6648". Retrieved November 12, 2012.
7. "Message Headers". Iana.org. June 11, 2014. Retrieved June 12, 2014.
8. "Comments". HTTP Semantics. June 2022. sec. 5.6.5. doi:10.17487/RFC9110. RFC 9110.
9. "Quality Values". HTTP Semantics. June 2022. sec. 12.4.2. doi:10.17487/RFC9110. RFC 9110.
10. . Httpd.apache.org. Archived from the original on May 9, 2012. Retrieved March 13, 2012.
11. RFC 3229. doi:10.17487/RFC3229.
12. "Cross-Origin Resource Sharing". Retrieved July 24, 2017.
13. "Connection header". HTTP Semantics. June 2022. sec. 7.6.1. doi:10.17487/RFC9110. RFC 9110.
14. "Connection-Specific Header Fields". HTTP/2. June 2022. sec. 8.2.2. doi:10.17487/RFC9113. RFC 9113.
15. "Changes from RFC 2616". Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content. June 2014. sec. B. doi:10.17487/RFC7231. RFC 7231.
16. "Forwarded HTTP Extension: Introduction". IETF. June 2014. Retrieved January 7, 2016.
17. "Host and :authority". HTTP Semantics. June 2022. sec. 7.2. doi:10.17487/RFC9110. RFC 9110.
18. "Request Pseudo-Header Fields". HTTP/2. June 2022. sec. 8.3.1. doi:10.17487/RFC9113. RFC 9113.
19. "Message Headers". www.iana.org. Retrieved November 26, 2018.
20. "HTTP2-Settings Header Field". Hypertext Transfer Protocol Version 2 (HTTP/2). sec. 3.2.1. doi:10.17487/RFC7540. RFC 7540.
21. "Warning header". HTTP Caching. June 2022. sec. 5.5. doi:10.17487/RFC9111. RFC 9111.
22. "Upgrade Insecure Requests - W3C Candidate Recommendation". W3C. October 8, 2015. Retrieved January 14, 2016.
23. "The "X-Requested-With" Header – Stoutner".
24. "Try out the "Do Not Track" HTTP header". Retrieved January 31, 2011.
25. "Web Tracking Protection: Minimum Standards and Opportunities to Innovate". Retrieved March 24, 2011.
26. IETF Do Not Track: A Universal Third-Party Web Tracking Opt Out March 7, 2011
27. W3C Tracking Preference Expression (DNT), January 26, 2012
28. Amos Jeffries (July 2, 2010). "SquidFaq/ConfiguringSquid - Squid Web Proxy Wiki". Retrieved September 10, 2009.
29. The Apache Software Foundation. "mod_proxy - Apache HTTP Server Version 2.2". Retrieved November 12, 2014.
30. Dave Steinberg (April 10, 2007). "How do I adjust my SSL site to work with GeekISP's loadbalancer?". Retrieved September 30, 2010.
31. "Helping to Secure Communication: Client to Front-End Server". July 27, 2006. Retrieved April 23, 2012.
32. "OpenSocial Core API Server Specification 2.5.1". Retrieved October 8, 2014.
33. . Archived from the original on February 16, 2012. Retrieved January 14, 2012.
34. "WAP Profile". Retrieved January 14, 2012.
35. de Boyne Pollard, Jonathan (2007). "The Proxy-Connection: header is a mistake in how some web browsers use HTTP". Retrieved January 16, 2018.
36. "Verizon Injecting Perma-Cookies to Track Mobile Customers, Bypassing Privacy Controls". Electronic Frontier Foundation. Retrieved January 19, 2014.
37. "Checking known AT&T, Verizon, Sprint, Bell Canada & Vodacom Unique Identifier beacons". Retrieved January 19, 2014.
38. Craig Timberg. "Verizon, AT&T tracking their users with 'supercookies'". The Washington Post. Retrieved January 19, 2014.
39. "SAP Cross-Site Request Forgery Protection". SAP SE. Retrieved January 20, 2015.
40. . Django (web framework). Archived from the original on January 20, 2015. Retrieved January 20, 2015.
41. "Angular Cross Site Request Forgery (XSRF) Protection". AngularJS. Retrieved January 20, 2015.
42. "HTTP Request IDs". devcenter.heroku.com. Retrieved March 22, 2022.
43. "The Value of Correlation IDs". Rapid7 Blog. December 23, 2016. Retrieved April 13, 2018.
44. Hilton, Peter. "Correlation IDs for microservices architectures - Peter Hilton". hilton.org.uk. Retrieved April 13, 2018.
45. "Save Data API Living Document Draft Community Group Report 2.1.1. Save-Data Request Header Field". Web Platform Incubator Community Group. June 30, 2020. Retrieved March 5, 2021.
46. "RFC 5789". Retrieved December 24, 2014.
47. "HTTP Alternative Services". IETF. April 2016. Retrieved April 19, 2016.
48. "HTTP Alternative Services, section 3". IETF. April 2016. Retrieved June 8, 2017.
49. "RFC 6266". Retrieved March 13, 2015.
50. "Content-Language". HTTP Semantics. June 2022. sec. 8.5. doi:10.17487/RFC9110. RFC 9110.
51. Indicate the canonical version of a URL by responding with the Link rel="canonical" HTTP header Retrieved: 2012-02-09
52. W3C P3P Work Suspended
53. "Public Key Pinning Extension for HTTP". IETF. Retrieved April 17, 2015.
54. "Retry-After". HTTP Semantics. June 2022. sec. 10.2.3. doi:10.17487/RFC9110. RFC 9110.
55. "HTTP Header Field X-Frame-Options". IETF. 2013. Retrieved June 12, 2014.
56. "Content Security Policy Level 2". Retrieved August 2, 2014.
57. "Content Security Policy". W3C. 2012. Retrieved April 28, 2017.
58. "Expect-CT". Mozilla Developer Network. Retrieved July 23, 2021.
59. "NEL". Mozilla Developer Network. 2021. Retrieved May 18, 2021.
60. "Permissions Policy". W3C. 2020. Retrieved May 1, 2021.
61. "Am I FLoCed?". EFF. 2021. Retrieved May 1, 2021.
62. "Define the HTTP Refresh header by annevk · Pull Request #2892 · whatwg/html". GitHub. August 9, 2017. Retrieved April 17, 2021.
63. "CSP: report-to". Mozilla Developer Network. 2021. Retrieved May 18, 2021.
64. RFC 9110: HTTP Semantics
65. "Timing-Allow-Origin". Mozilla Developer Network. Retrieved January 25, 2018.
66. "Configuring servers for Ogg media". May 26, 2014. Retrieved January 3, 2015.
67. Eric Lawrence (September 3, 2008). "IE8 Security Part VI: Beta 2 Update". Retrieved September 28, 2010.
68. "Hosting - Google Chrome Extensions - Google Code". Retrieved June 14, 2012.
69. van Kesteren, Anne (August 26, 2016). "Fetch standard". WHATWG. from the original on August 26, 2016. Retrieved August 26, 2016.
70. "X-Redirect-By HTTP response header". Retrieved May 29, 2021.
71. "Defining Document Compatibility: Specifying Document Compatibility Modes". April 1, 2011. Retrieved January 24, 2012.
72. "HTML Living Standard 4.2.5.3 Pragma directives, X-UA-Compatible state". WHATWG. March 12, 2021. Retrieved March 14, 2021. For meta elements with an http-equiv attribute in the X-UA-Compatible state, the content attribute must have a value that is an ASCII case-insensitive match for the string"IE=edge".
73. Eric Lawrence (July 2, 2008). "IE8 Security Part IV: The XSS Filter". Retrieved September 30, 2010.
74. "Pragme". HTTP Caching. June 2022. sec. 5.4. doi:10.17487/RFC9111. RFC 9111.
75. "How to prevent caching in Internet Explorer". Microsoft. September 22, 2011. Retrieved April 15, 2015.

As of this edit, this article uses content from "What is the X-REQUEST-ID http header?", authored by Stefan Kögl at Stack Exchange, which is licensed in a way that permits reuse under the Creative Commons Attribution-ShareAlike 3.0 Unported License, but not under the GFDL. All relevant terms must be followed.

1. "What is the X-REQUEST-ID http header?". Retrieved March 20, 2022.

As of this edit, this article uses content from "Why does ASP.NET framework add the 'X-Powered-By:ASP.NET' HTTP Header in responses?", authored by Adrian Grigore at Stack Exchange, which is licensed in a way that permits reuse under the Creative Commons Attribution-ShareAlike 3.0 Unported License, but not under the GFDL. All relevant terms must be followed.

1. "Why does ASP.NET framework add the 'X-Powered-By:ASP.NET' HTTP Header in responses? - Stack Overflow". Retrieved March 20, 2022.

External links

• Headers: Permanent Message Header Field Names
• RFC 6265: IETF HTTP State Management Mechanism
• RFC 9110: HTTP Semantics
• RFC 9111: HTTP Caching
• RFC 9112: HTTP/1.1
• RFC 9113: HTTP/2
• RFC 9114: HTTP/3
• RFC 7239: Forwarded HTTP Extension
• RFC 7240: Prefer Header for HTTP
• HTTP/1.1 headers from a web server point of view
• Internet Explorer and Custom HTTP Headers - EricLaw's IEInternals - Site Home - MSDN Blogs