Topzle Topzle

List of HTTP header fields

Updated: Wikipedia source

List of HTTP header fields

An HTTP header field is a name-value pair in an HTTP request or response message that represents metadata about the message. Generally, the information of a header field is used by software and not shown to the user. Header fields represent information about many aspects including how message content is encoded (via 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 or Global Privacy Control), the age (the time it has resided in a shared cache) of the document being downloaded, and much more.

Tables

· Request fields › Standard request fields
A-IM
A-IM
Name
A-IM
Description
Acceptable instance-manipulations for the request.
Example
A-IM: feed
Status
Permanent
Standard
RFC 3229
Accept
Accept
Name
Accept
Description
Media type(s) that is/are acceptable for the response. See Content negotiation.
Example
Accept: text/html
Status
Permanent
Standard
RFC 9110
Accept-Charset
Accept-Charset
Name
Accept-Charset
Description
Character sets that are acceptable.
Example
Accept-Charset: utf-8
Status
Permanent
Standard
RFC 9110
Accept-Datetime
Accept-Datetime
Name
Accept-Datetime
Description
Acceptable version in time.
Example
Accept-Datetime: Thu, 31 May 2007 20:35:00 GMT
Status
Provisional
Standard
RFC 7089
Accept-Encoding
Accept-Encoding
Name
Accept-Encoding
Description
List of acceptable encodings. See HTTP compression.
Example
Accept-Encoding: gzip, deflate
Status
Permanent
Standard
RFC 9110
Accept-Language
Accept-Language
Name
Accept-Language
Description
List of acceptable human languages for response. See Content negotiation.
Example
Accept-Language: en-US
Status
Permanent
Standard
RFC 9110
Access-Control-Request-Method,Access-Control-Request-Headers
Access-Control-Request-Method,Access-Control-Request-Headers
Name
Access-Control-Request-Method,Access-Control-Request-Headers
Description
Initiates a request for cross-origin resource sharing with Origin (below).
Example
Access-Control-Request-Method: GET
Status
Permanent: standard
Authorization
Authorization
Name
Authorization
Description
Authentication credentials for HTTP authentication.
Example
Authorization: Basic QWxhZGRpbjpvcGVuIHNlc2FtZQ==
Status
Permanent
Standard
RFC 9110
Cache-Control
Cache-Control
Name
Cache-Control
Description
Used to specify directives that must be obeyed by all caching mechanisms along the request-response chain.
Example
Cache-Control: no-cache
Status
Permanent
Standard
RFC 9111
Connection
Connection
Name
Connection
Description
Control options for the current connection and list of hop-by-hop request fields. Must not be used with HTTP/2.
Example
Connection: keep-alive Connection: Upgrade
Status
Permanent
Standard
RFC 9110
Content-Encoding
Content-Encoding
Name
Content-Encoding
Description
The type of encoding used on the data. See HTTP compression.
Example
Content-Encoding: gzip
Status
Permanent
Standard
RFC 9110
Content-Length
Content-Length
Name
Content-Length
Description
The length of the request body in octets (8-bit bytes).
Example
Content-Length: 348
Status
Permanent
Standard
RFC 9110
Content-MD5
Content-MD5
Name
Content-MD5
Description
A Base64-encoded binary MD5 sum of the content of the request body.
Example
Content-MD5: Q2hlY2sgSW50ZWdyaXR5IQ==
Status
Obsolete
Standard
RFC 1544, 1864, 4021
Content-Type
Content-Type
Name
Content-Type
Description
The Media type of the body of the request (used with POST and PUT requests).
Example
Content-Type: application/x-www-form-urlencoded
Status
Permanent
Standard
RFC 9110
Cookie
Cookie
Name
Cookie
Description
An HTTP cookie previously sent by the server with Set-Cookie (below).
Example
Cookie: $Version=1; Skin=new;
Status
Permanent: standard
Standard
RFC 2965, 6265
Date
Date
Name
Date
Description
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").
Example
Date: Tue, 15 Nov 1994 08:12:31 GMT
Status
Permanent
Standard
RFC 9110
Expect
Expect
Name
Expect
Description
Indicates that particular server behaviors are required by the client.
Example
Expect: 100-continue
Status
Permanent
Standard
RFC 9110
Forwarded
Forwarded
Name
Forwarded
Description
Disclose original information of a client connecting to a web server through an HTTP proxy.
Example
Forwarded: for=192.0.2.60;proto=http;by=203.0.113.43 Forwarded: for=192.0.2.43, for=198.51.100.17
Status
Permanent
Standard
RFC 7239
From
From
Name
From
Description
The email address of the user making the request.
Example
Status
Permanent
Standard
RFC 9110
Host
Host
Name
Host
Description
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. If the request is generated directly in HTTP/2, it should not be used.
Example
Host: en.wikipedia.org:8080 Host: en.wikipedia.org
Status
Permanent
Standard
RFC 9110, 9113
HTTP2-Settings
HTTP2-Settings
Name
HTTP2-Settings
Description
A request that upgrades from HTTP/1.1 to HTTP/2 MUST include exactly one HTTP2-Settings 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.
Example
HTTP2-Settings: token64
Status
Obsolete
Standard
RFC 7540, 9113
If-Match
If-Match
Name
If-Match
Description
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.
Example
If-Match: "737060cd8c284d8af7ad3082f209582d"
Status
Permanent
Standard
RFC 9110
If-Modified-Since
If-Modified-Since
Name
If-Modified-Since
Description
Allows a 304 Not Modified to be returned if content is unchanged.
Example
If-Modified-Since: Sat, 29 Oct 1994 19:43:31 GMT
Status
Permanent
Standard
RFC 9110
If-None-Match
If-None-Match
Name
If-None-Match
Description
Allows a 304 Not Modified to be returned if content is unchanged, see HTTP ETag.
Example
If-None-Match: "737060cd8c284d8af7ad3082f209582d"
Status
Permanent
Standard
RFC 9110
If-Range
If-Range
Name
If-Range
Description
If the entity is unchanged, send me the part(s) that I am missing; otherwise, send me the entire new entity.
Example
If-Range: "737060cd8c284d8af7ad3082f209582d"
Status
Permanent
Standard
RFC 9110
If-Unmodified-Since
If-Unmodified-Since
Name
If-Unmodified-Since
Description
Only send the response if the entity has not been modified since a specific time.
Example
If-Unmodified-Since: Sat, 29 Oct 1994 19:43:31 GMT
Status
Permanent
Standard
RFC 9110
Max-Forwards
Max-Forwards
Name
Max-Forwards
Description
Limit the number of times the message can be forwarded through proxies or gateways.
Example
Max-Forwards: 10
Status
Permanent
Standard
RFC 9110
Origin
Origin
Name
Origin
Description
Initiates a request for cross-origin resource sharing (asks server for Access-Control-* response fields).
Example
Origin: http://www.example-social-network.com
Status
Permanent: standard
Standard
RFC 6454
Pragma
Pragma
Name
Pragma
Description
Implementation-specific fields that may have various effects anywhere along the request-response chain.
Example
Pragma: no-cache
Status
Outdated
Standard
RFC 9111
Prefer
Prefer
Name
Prefer
Description
Allows client to request that certain behaviors be employed by a server while processing a request.
Example
Prefer: return=representation
Status
Permanent
Standard
RFC 7240
Proxy-Authorization
Proxy-Authorization
Name
Proxy-Authorization
Description
Authorization credentials for connecting to a proxy.
Example
Proxy-Authorization: Basic QWxhZGRpbjpvcGVuIHNlc2FtZQ==
Status
Permanent
Standard
RFC 9110
Range
Range
Name
Range
Description
Request only part of an entity. Bytes are numbered from 0. See Byte serving.
Example
Range: bytes=500-999
Status
Permanent
Standard
RFC 9110
Referer [sic]
Referer [sic]
Name
Referer [sic]
Description
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.)
Example
Referer: http://en.wikipedia.org/wiki/Main_Page
Status
Permanent
Standard
RFC 9110
TE
TE
Name
TE
Description
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.
Example
TE: trailers, deflate
Status
Permanent
Standard
RFC 9110
Trailer
Trailer
Name
Trailer
Description
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.
Example
Trailer: Max-Forwards
Status
Permanent
Standard
RFC 9110
Transfer-Encoding
Transfer-Encoding
Name
Transfer-Encoding
Description
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.
Example
Transfer-Encoding: chunked
Status
Permanent
Standard
RFC 9110
User-Agent
User-Agent
Name
User-Agent
Description
The user agent string of the user agent.
Example
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20100101 Firefox/12.0
Status
Permanent
Standard
RFC 9110
Upgrade
Upgrade
Name
Upgrade
Description
Ask the server to upgrade to another protocol. Must not be used in HTTP/2.
Example
Upgrade: h2c, HTTPS/1.3, IRC/6.9, RTA/x11, websocket
Status
Permanent
Standard
RFC 9110
Via
Via
Name
Via
Description
Informs the server of proxies through which the request was sent.
Example
Via: 1.0 fred, 1.1 example.com (Apache/1.1)
Status
Permanent
Standard
RFC 9110
Warning
Warning
Name
Warning
Description
A general warning about possible problems with the entity body.
Example
Warning: 199 Miscellaneous warning
Status
Obsolete
Standard
RFC 7234, 9111
Name
Description
Example
Status
Standard
A-IM
Acceptable instance-manipulations for the request.
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
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. Must not be used with HTTP/2.
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
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.
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.
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. If the request is generated directly in HTTP/2, it should not be used.
Host: en.wikipedia.org:8080 Host: en.wikipedia.org
Permanent
RFC 9110, 9113
HTTP2-Settings
A request that upgrades from HTTP/1.1 to HTTP/2 MUST include exactly one HTTP2-Settings 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.
HTTP2-Settings: token64
Obsolete
RFC 7540, 9113
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
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
Outdated
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.
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.
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.
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
RFC 7234, 9111
· Request fields › Common non-standard request fields
Upgrade-Insecure-Requests
Upgrade-Insecure-Requests
Field name
Upgrade-Insecure-Requests
Description
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
Example
Upgrade-Insecure-Requests: 1
X-Requested-With
X-Requested-With
Field name
X-Requested-With
Description
Mainly used to identify Ajax requests (most JavaScript frameworks send this field with value of XMLHttpRequest); also identifies Android apps using WebView
Example
X-Requested-With: XMLHttpRequest
DNT
DNT
Field name
DNT
Description
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. On March 7, 2011, a draft proposal was submitted to IETF. The W3C Tracking Protection Working Group is producing a specification.
Example
DNT: 1 (Do Not Track Enabled) DNT: 0 (Do Not Track Disabled)
X-Forwarded-For
X-Forwarded-For
Field name
X-Forwarded-For
Description
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.
Example
X-Forwarded-For: client1, proxy1, proxy2 X-Forwarded-For: 129.78.138.66, 129.78.64.103
X-Forwarded-Host
X-Forwarded-Host
Field name
X-Forwarded-Host
Description
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.
Example
X-Forwarded-Host: en.wikipedia.org:8080 X-Forwarded-Host: en.wikipedia.org
X-Forwarded-Proto
X-Forwarded-Proto
Field name
X-Forwarded-Proto
Description
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.
Example
X-Forwarded-Proto: https
Front-End-Https
Front-End-Https
Field name
Front-End-Https
Description
Non-standard header field used by Microsoft applications and load-balancers
Example
Front-End-Https: on
X-Http-Method-Override
X-Http-Method-Override
Field name
X-Http-Method-Override
Description
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 (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).
Example
X-HTTP-Method-Override: DELETE
X-ATT-DeviceId
X-ATT-DeviceId
Field name
X-ATT-DeviceId
Description
Allows easier parsing of the MakeModel/Firmware that is usually found in the User-Agent String of AT&T Devices
Example
X-Att-Deviceid: GT-P7320/P7320XXLPG
X-Wap-Profile
X-Wap-Profile
Field name
X-Wap-Profile
Description
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.
Example
x-wap-profile: http://wap.samsungmobile.com/uaprof/SGH-I777.xml
Proxy-Connection
Proxy-Connection
Field name
Proxy-Connection
Description
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.
Example
Proxy-Connection: keep-alive
X-UIDH
X-UIDH
Field name
X-UIDH
Description
Server-side deep packet inspection of a unique ID identifying customers of Verizon Wireless; also known as "perma-cookie" or "supercookie"
Example
X-UIDH: ...
X-Csrf-Token
X-Csrf-Token
Field name
X-Csrf-Token
Description
Used to prevent cross-site request forgery. Alternative header names are: X-CSRFToken and X-XSRF-TOKEN
Example
X-Csrf-Token: i8XNjC4b8KVok4uw5RftR38Wgp2BFwql
X-Request-ID, X-Correlation-ID, Correlation-ID
X-Request-ID, X-Correlation-ID, Correlation-ID
Field name
X-Request-ID, X-Correlation-ID, Correlation-ID
Description
Correlates HTTP requests between a client and server. Superseded by the traceparent header
Example
X-Request-ID: f058ebd6-02f7-4d3f-942e-904344e8cde5
Save-Data
Save-Data
Field name
Save-Data
Description
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.
Example
Save-Data: on
Sec-GPC
Sec-GPC
Field name
Sec-GPC
Description
The Sec-GPC (Global Privacy Control[broken anchor]) request header indicates whether the user consents to a website or service selling or sharing their personal information with third parties.
Example
Sec-GPC: 1
Field name
Description
Example
Upgrade-Insecure-Requests
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
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
X-Requested-With: XMLHttpRequest
DNT
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. On March 7, 2011, a draft proposal was submitted to IETF. The W3C Tracking Protection Working Group is producing a specification.
DNT: 1 (Do Not Track Enabled) DNT: 0 (Do Not Track Disabled)
X-Forwarded-For
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
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
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
Non-standard header field used by Microsoft applications and load-balancers
Front-End-Https: on
X-Http-Method-Override
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 (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
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
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
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.
Proxy-Connection: keep-alive
X-UIDH
Server-side deep packet inspection of a unique ID identifying customers of Verizon Wireless; also known as "perma-cookie" or "supercookie"
X-UIDH: ...
X-Csrf-Token
Used to prevent cross-site request forgery. Alternative header names are: X-CSRFToken and X-XSRF-TOKEN
X-Csrf-Token: i8XNjC4b8KVok4uw5RftR38Wgp2BFwql
X-Request-ID, X-Correlation-ID, Correlation-ID
Correlates HTTP requests between a client and server. Superseded by the traceparent header
X-Request-ID: f058ebd6-02f7-4d3f-942e-904344e8cde5
Save-Data
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
Sec-GPC
The Sec-GPC (Global Privacy Control[broken anchor]) request header indicates whether the user consents to a website or service selling or sharing their personal information with third parties.
Sec-GPC: 1
· Response fields › Standard response fields
Accept-CH
Accept-CH
Field name
Accept-CH
Description
Requests HTTP Client Hints
Example
Accept-CH: UA, Platform
Status
Experimental
Standard
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
Access-Control-Allow-Origin,Access-Control-Allow-Credentials,Access-Control-Expose-Headers,Access-Control-Max-Age,Access-Control-Allow-Methods,Access-Control-Allow-Headers
Field name
Access-Control-Allow-Origin,Access-Control-Allow-Credentials,Access-Control-Expose-Headers,Access-Control-Max-Age,Access-Control-Allow-Methods,Access-Control-Allow-Headers
Description
Specifying which web sites can participate in cross-origin resource sharing
Example
Access-Control-Allow-Origin: *
Status
Permanent: standard
Standard
RFC 7480
Accept-Patch
Accept-Patch
Field name
Accept-Patch
Description
Specifies which patch document formats this server supports
Example
Accept-Patch: text/example;charset=utf-8
Status
Permanent
Standard
RFC 5789
Accept-Ranges
Accept-Ranges
Field name
Accept-Ranges
Description
What partial content range types this server supports via byte serving
Example
Accept-Ranges: bytes
Status
Permanent
Standard
RFC 9110
Age
Age
Field name
Age
Description
The age the object has been in a proxy cache in seconds
Example
Age: 12
Status
Permanent
Standard
RFC 9111
Allow
Allow
Field name
Allow
Description
Valid methods for a specified resource. To be used for a 405 Method not allowed
Example
Allow: GET, HEAD
Status
Permanent
Standard
RFC 9110
Alt-Svc
Alt-Svc
Field name
Alt-Svc
Description
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.
Example
Alt-Svc: http/1.1="http2.example.com:8001"; ma=7200
Status
Permanent
Cache-Control
Cache-Control
Field name
Cache-Control
Description
Tells all caching mechanisms from server to client whether they may cache this object. It is measured in seconds
Example
Cache-Control: max-age=3600
Status
Permanent
Standard
RFC 9111
Connection
Connection
Field name
Connection
Description
Control options for the current connection and list of hop-by-hop response fields. Must not be used with HTTP/2.
Example
Connection: close
Status
Permanent
Standard
RFC 9110
Content-Disposition
Content-Disposition
Field name
Content-Disposition
Description
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.
Example
Content-Disposition: attachment; filename="fname.ext"
Status
Permanent
Standard
RFC 2616, 4021, 6266
Content-Encoding
Content-Encoding
Field name
Content-Encoding
Description
The type of encoding used on the data. See HTTP compression.
Example
Content-Encoding: gzip
Status
Permanent
Standard
RFC 9110
Content-Language
Content-Language
Field name
Content-Language
Description
The natural language or languages of the intended audience for the enclosed content
Example
Content-Language: da
Status
Permanent
Standard
RFC 9110
Content-Length
Content-Length
Field name
Content-Length
Description
The length of the response body in octets (8-bit bytes)
Example
Content-Length: 348
Status
Permanent
Standard
RFC 9110
Content-Location
Content-Location
Field name
Content-Location
Description
An alternate location for the returned data
Example
Content-Location: /index.htm
Status
Permanent
Standard
RFC 9110
Content-MD5
Content-MD5
Field name
Content-MD5
Description
A Base64-encoded binary MD5 sum of the content of the response
Example
Content-MD5: Q2hlY2sgSW50ZWdyaXR5IQ==
Status
Obsolete
Standard
RFC 1544, 1864, 4021
Content-Range
Content-Range
Field name
Content-Range
Description
Where in a full body message this partial message belongs
Example
Content-Range: bytes 21010-47021/47022
Status
Permanent
Standard
RFC 9110
Content-Type
Content-Type
Field name
Content-Type
Description
The MIME type of this content
Example
Content-Type: text/html; charset=utf-8
Status
Permanent
Standard
RFC 9110
Date
Date
Field name
Date
Description
The date and time that the message was sent (in "HTTP-date" format as defined by RFC 9110)
Example
Date: Tue, 15 Nov 1994 08:12:31 GMT
Status
Permanent
Standard
RFC 9110
Delta-Base
Delta-Base
Field name
Delta-Base
Description
Specifies the delta-encoding entity tag of the response.
Example
Delta-Base: "abc"
Status
Permanent
Standard
RFC 3229
ETag
ETag
Field name
ETag
Description
An identifier for a specific version of a resource, often a message digest
Example
ETag: "737060cd8c284d8af7ad3082f209582d"
Status
Permanent
Standard
RFC 9110
Expires
Expires
Field name
Expires
Description
Gives the date/time after which the response is considered stale (in "HTTP-date" format as defined by RFC 9110)
Example
Expires: Thu, 01 Dec 1994 16:00:00 GMT
Status
Permanent: standard
Standard
RFC 9111
IM
IM
Field name
IM
Description
Instance-manipulations applied to the response.
Example
IM: feed
Status
Permanent
Standard
RFC 3229
Last-Modified
Last-Modified
Field name
Last-Modified
Description
The last modified date for the requested object (in "HTTP-date" format as defined by RFC 9110)
Example
Last-Modified: Tue, 15 Nov 1994 12:45:26 GMT
Status
Permanent
Standard
RFC 9110
Link
Link
Field name
Link
Description
Used to express a typed relationship with another resource, where the relation type is defined by RFC 8288
Example
Link: ; rel="alternate"
Status
Permanent
Standard
RFC 8288
Location
Location
Field name
Location
Description
Used in redirection, or when a new resource has been created.
Example
Example 1: Location: http://www.w3.org/pub/WWW/People.html Example 2: Location: /pub/WWW/People.html
Status
Permanent
Standard
RFC 9110
P3P
P3P
Field name
P3P
Description
This field is supposed to set P3P policy, in the form of P3P:CP="your_compact_policy". However, P3P did not take off, 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.
Example
P3P: CP="This is not a P3P policy! See https://en.wikipedia.org/wiki/Special:CentralAutoLogin/P3P for more info."
Status
Permanent
Pragma
Pragma
Field name
Pragma
Description
Implementation-specific fields that may have various effects anywhere along the request-response chain.
Example
Pragma: no-cache
Status
Permanent
Standard
RFC 9111
Preference-Applied
Preference-Applied
Field name
Preference-Applied
Description
Indicates which Prefer tokens were honored by the server and applied to the processing of the request.
Example
Preference-Applied: return=representation
Status
Permanent
Standard
RFC 7240
Proxy-Authenticate
Proxy-Authenticate
Field name
Proxy-Authenticate
Description
Request authentication to access the proxy.
Example
Proxy-Authenticate: Basic
Status
Permanent
Standard
RFC 9110
Public-Key-Pins
Public-Key-Pins
Field name
Public-Key-Pins
Description
HTTP Public Key Pinning, announces hash of website's authentic TLS certificate
Example
Public-Key-Pins: max-age=2592000; pin-sha256="E9CZ9INDbd+2eRQozYqqbQ2yXLVKB9+xcprMF+44U1g=";
Status
Permanent
Standard
RFC 7469
Retry-After
Retry-After
Field name
Retry-After
Description
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.
Example
Example 1: Retry-After: 120 Example 2: Retry-After: Fri, 07 Nov 2014 23:59:59 GMT
Status
Permanent
Standard
RFC 9110
Server
Server
Field name
Server
Description
A name for the server
Example
Server: Apache/2.4.1 (Unix)
Status
Permanent
Standard
RFC 9110
Set-Cookie
Set-Cookie
Field name
Set-Cookie
Description
An HTTP cookie
Example
Set-Cookie: CookieName=CookieValue; Max-Age=3600; Version=1
Status
Permanent: standard
Standard
RFC 6265
Strict-Transport-Security
Strict-Transport-Security
Field name
Strict-Transport-Security
Description
A HSTS Policy informing the HTTP client how long to cache the HTTPS only policy and whether this applies to subdomains.
Example
Strict-Transport-Security: max-age=16070400; includeSubDomains
Status
Permanent: standard
Trailer
Trailer
Field name
Trailer
Description
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.
Example
Trailer: Max-Forwards
Status
Permanent
Standard
RFC 9110
Transfer-Encoding
Transfer-Encoding
Field name
Transfer-Encoding
Description
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.
Example
Transfer-Encoding: chunked
Status
Permanent
Standard
RFC 9110
Tk
Tk
Field name
Tk
Description
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
Example
Tk: ?
Status
Permanent
Upgrade
Upgrade
Field name
Upgrade
Description
Ask the client to upgrade to another protocol. Must not be used in HTTP/2
Example
Upgrade: h2c, HTTPS/1.3, IRC/6.9, RTA/x11, websocket
Status
Permanent
Standard
RFC 9110
Vary
Vary
Field name
Vary
Description
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
Example 1: Vary: * Example 2: Vary: Accept-Language
Status
Permanent
Standard
RFC 9110
Via
Via
Field name
Via
Description
Informs the client of proxies through which the response was sent.
Example
Via: 1.0 fred, 1.1 example.com (Apache/1.1)
Status
Permanent
Standard
RFC 9110
Warning
Warning
Field name
Warning
Description
A general warning about possible problems with the entity body.
Example
Warning: 199 Miscellaneous warning
Status
Obsolete
Standard
RFC 7234, 9111
WWW-Authenticate
WWW-Authenticate
Field name
WWW-Authenticate
Description
Indicates the authentication scheme that should be used to access the requested entity.
Example
WWW-Authenticate: Basic
Status
Permanent
Standard
RFC 9110
X-Frame-Options
X-Frame-Options
Field name
X-Frame-Options
Description
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
Example
X-Frame-Options: deny
Status
Obsolete
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
Specifying which web sites can participate in cross-origin resource sharing
Access-Control-Allow-Origin: *
Permanent: standard
RFC 7480
Accept-Patch
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
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.
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. Must not be used with HTTP/2.
Connection: close
Permanent
RFC 9110
Content-Disposition
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
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
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.
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.
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 8288
Link: ; rel="alternate"
Permanent
RFC 8288
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, 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
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.
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: CookieName=CookieValue; 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.
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
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
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
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
· Response fields › Common non-standard response fields
Content-Security-Policy,X-Content-Security-Policy,X-WebKit-CSP
Content-Security-Policy,X-Content-Security-Policy,X-WebKit-CSP
Field name
Content-Security-Policy,X-Content-Security-Policy,X-WebKit-CSP
Description
Content Security Policy definition.
Example
X-WebKit-CSP: default-src 'self'
Expect-CT
Expect-CT
Field name
Expect-CT
Description
Notify to prefer to enforce Certificate Transparency.
Example
Expect-CT: max-age=604800, enforce, report-uri="https://example.example/report"
NEL
NEL
Field name
NEL
Description
Used to configure network request logging.
Example
NEL: { "report_to": "name_of_reporting_group", "max_age": 12345, "include_subdomains": false, "success_fraction": 0.0, "failure_fraction": 1.0 }
Permissions-Policy
Permissions-Policy
Field name
Permissions-Policy
Description
To allow or disable different features or APIs of the browser.
Example
Permissions-Policy: fullscreen=(), camera=(), microphone=(), geolocation=(), interest-cohort=()
Refresh
Refresh
Field name
Refresh
Description
Tells the browser to refresh the page or redirect to a different URL, after a given number of seconds (0 meaning immediately); or when a new resource has been created[clarification needed]. Header introduced by Netscape in 1995 and became a de facto standard supported by most web browsers. Eventually standardized in the HTML Living Standard in 2017.
Example
Refresh: 5; url=http://www.w3.org/pub/WWW/People.html
Report-To
Report-To
Field name
Report-To
Description
Instructs the user agent to store reporting endpoints for an origin.
Example
Report-To: { "group": "csp-endpoint", "max_age": 10886400, "endpoints": [ { "url": "https-url-of-site-which-collects-reports" } ] }
Status
Status
Field name
Status
Description
CGI header field specifying the status of the HTTP response. Normal HTTP responses use a separate "Status-Line" instead, defined by RFC 9110.
Example
Status: 200 OK
Timing-Allow-Origin
Timing-Allow-Origin
Field name
Timing-Allow-Origin
Description
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.
Example
Timing-Allow-Origin: * Timing-Allow-Origin: [, ]*
X-Content-Duration
X-Content-Duration
Field name
X-Content-Duration
Description
Provide the duration of the audio or video in seconds. Not supported by current browsers – the header was only supported by Gecko browsers, from which support was removed in 2015.
Example
X-Content-Duration: 42.666
X-Content-Type-Options
X-Content-Type-Options
Field name
X-Content-Type-Options
Description
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.
Example
X-Content-Type-Options: nosniff
X-Powered-By
X-Powered-By
Field name
X-Powered-By
Description
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)
Example
X-Powered-By: PHP/5.4.0
X-Redirect-By
X-Redirect-By
Field name
X-Redirect-By
Description
Specifies the component that is responsible for a particular redirect.
Example
X-Redirect-By: WordPressX-Redirect-By: Polylang
X-Request-ID, X-Correlation-ID
X-Request-ID, X-Correlation-ID
Field name
X-Request-ID, X-Correlation-ID
Description
Correlates HTTP requests between a client and server.
Example
X-Request-ID: f058ebd6-02f7-4d3f-942e-904344e8cde5
X-UA-Compatible
X-UA-Compatible
Field name
X-UA-Compatible
Description
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.
Example
X-UA-Compatible: IE=edgeX-UA-Compatible: IE=EmulateIE7X-UA-Compatible: Chrome=1
X-XSS-Protection
X-XSS-Protection
Field name
X-XSS-Protection
Description
Cross-site scripting (XSS) filter
Example
X-XSS-Protection: 1; mode=block
Field name
Description
Example
Content-Security-Policy,X-Content-Security-Policy,X-WebKit-CSP
Content Security Policy definition.
X-WebKit-CSP: default-src 'self'
Expect-CT
Notify to prefer to enforce Certificate Transparency.
Expect-CT: max-age=604800, enforce, report-uri="https://example.example/report"
NEL
Used to configure network request logging.
Permissions-Policy
To allow or disable different features or APIs of the browser.
Permissions-Policy: fullscreen=(), camera=(), microphone=(), geolocation=(), interest-cohort=()
Refresh
Tells the browser to refresh the page or redirect to a different URL, after a given number of seconds (0 meaning immediately); or when a new resource has been created[clarification needed]. Header introduced by Netscape in 1995 and became a de facto standard supported by most web browsers. Eventually standardized in the HTML Living Standard in 2017.
Refresh: 5; url=http://www.w3.org/pub/WWW/People.html
Report-To
Instructs the user agent to store reporting endpoints for an origin.
] }
Status
CGI header field specifying the status of the HTTP response. Normal HTTP responses use a separate "Status-Line" instead, defined by RFC 9110.
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.
Timing-Allow-Origin: * Timing-Allow-Origin: [, ]*
X-Content-Duration
Provide the duration of the audio or video in seconds. Not supported by current browsers – the header was only supported by Gecko browsers, from which support was removed in 2015.
X-Content-Duration: 42.666
X-Content-Type-Options
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.
X-Content-Type-Options: nosniff
X-Powered-By
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
Specifies the component that is responsible for a particular redirect.
X-Redirect-By: WordPressX-Redirect-By: Polylang
X-Request-ID, X-Correlation-ID
Correlates HTTP requests between a client and server.
X-Request-ID: f058ebd6-02f7-4d3f-942e-904344e8cde5
X-UA-Compatible
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.
X-UA-Compatible: IE=edgeX-UA-Compatible: IE=EmulateIE7X-UA-Compatible: Chrome=1
X-XSS-Protection
Cross-site scripting (XSS) filter
X-XSS-Protection: 1; mode=block

References

  1. Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing
    https://datatracker.ietf.org/doc/html/rfc7230#section-3.2.4
  2. HTTP/2
    https://www.rfc-editor.org/rfc/rfc9113
  3. HPACK: Header Compression for HTTP/2
    https://www.rfc-editor.org/rfc/rfc7541
  4. "core - Apache HTTP Server"
    https://web.archive.org/web/20120509104709/https://httpd.apache.org/docs/2.3/mod/core.html#limitrequestfieldsize
  5. HTTP Semantics
    https://datatracker.ietf.org/doc/html/rfc9110#section-5.1
  6. HTTP Semantics
    https://datatracker.ietf.org/doc/html/rfc9110#section-9.1
  7. Deprecating the "X-" Prefix and Similar Constructs in Application Protocols
    https://www.rfc-editor.org/rfc/rfc6648
  8. "Message Headers"
    https://www.iana.org/assignments/message-headers/message-headers.xml
  9. HTTP Semantics
    https://datatracker.ietf.org/doc/html/rfc9110#section-5.6.5
  10. HTTP Semantics
    https://datatracker.ietf.org/doc/html/rfc9110#section-12.4.2
  11. RFC 3229
    https://www.rfc-editor.org/rfc/rfc3229
  12. "Cross-Origin Resource Sharing"
    https://www.w3.org/TR/cors/
  13. HTTP Semantics
    https://datatracker.ietf.org/doc/html/rfc9110#section-7.6.1
  14. HTTP/2
    https://datatracker.ietf.org/doc/html/rfc9113#section-8.2.2
  15. Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content
    https://datatracker.ietf.org/doc/html/rfc7231#appendix-B
  16. Forwarded HTTP Extension: Introduction
    http://tools.ietf.org/html/rfc7239#section-1
  17. HTTP Semantics
    https://datatracker.ietf.org/doc/html/rfc9110#section-7.2
  18. HTTP/2
    https://datatracker.ietf.org/doc/html/rfc9113#section-8.3.1
  19. www.iana.org
    https://www.iana.org/assignments/message-headers/message-headers.xml
  20. Hypertext Transfer Protocol Version 2 (HTTP/2)
    https://datatracker.ietf.org/doc/html/rfc7540#section-3.2.1
  21. HTTP Caching
    https://datatracker.ietf.org/doc/html/rfc9111#section-5.5
  22. W3C
    https://www.w3.org/TR/upgrade-insecure-requests/#preference
  23. "The "X-Requested-With" Header – Stoutner"
    https://www.stoutner.com/the-x-requested-with-header/
  24. "Try out the "Do Not Track" HTTP header"
    http://blog.sidstamm.com/2011/01/try-out-do-not-track-http-header.html
  25. "Web Tracking Protection: Minimum Standards and Opportunities to Innovate"
    http://blogs.msdn.com/b/ie/archive/2011/03/14/web-tracking-protection-minimum-standards-and-opportunities-to-innovate.aspx
  26. IETF Do Not Track: A Universal Third-Party Web Tracking Opt Out March 7, 2011
    http://tools.ietf.org/html/draft-mayer-do-not-track-00
  27. W3C Tracking Preference Expression (DNT), January 26, 2012
    http://www.w3.org/2011/tracking-protection/drafts/tracking-dnt.html
  28. "SquidFaq/ConfiguringSquid - Squid Web Proxy Wiki"
    http://wiki.squid-cache.org/SquidFaq/ConfiguringSquid#head-3518b69c63e221cc3cd7885415e365ffaf3dd27f
  29. "mod_proxy - Apache HTTP Server Version 2.2"
    https://httpd.apache.org/docs/2.2/mod/mod_proxy.html#x-headers
  30. "How do I adjust my SSL site to work with GeekISP's loadbalancer?"
    http://www.geekisp.com/faq/6_65_en.html
  31. "Helping to Secure Communication: Client to Front-End Server"
    https://technet.microsoft.com/en-us/library/aa997519(v=exchg.65).aspx
  32. "OpenSocial Core API Server Specification 2.5.1"
    https://opensocial.github.io/spec/2.5.1/Core-API-Server.xml#rfc.section.2.1.1.1
  33. "ATT Device ID"
    https://web.archive.org/web/20120216021736/http://developer.att.com/developer/forward.jsp?passedItemId=5300270
  34. "WAP Profile"
    http://www.developershome.com/wap/detection/detection.asp?page=profileHeader
  35. "The Proxy-Connection: header is a mistake in how some web browsers use HTTP"
    https://web.archive.org/web/20161023162007/https://jdebp.eu/FGA/web-proxy-connection-header.html
  36. "Verizon Injecting Perma-Cookies to Track Mobile Customers, Bypassing Privacy Controls"
    https://www.eff.org/deeplinks/2014/11/verizon-x-uidh
  37. "Checking known AT&T, Verizon, Sprint, Bell Canada & Vodacom Unique Identifier beacons"
    http://lessonslearned.org/sniff
  38. The Washington Post
    https://www.washingtonpost.com/business/technology/verizon-atandt-tracking-their-users-with-super-cookies/2014/11/03/7bbbf382-6395-11e4-bb14-4cfea1e742d5_story.html
  39. "SAP Cross-Site Request Forgery Protection"
    https://help.sap.com/saphelp_nw74/helpdata/en/b3/5c22518bc72214e10000000a44176d/content.htm
  40. "Django Cross Site Request Forgery protection"
    https://web.archive.org/web/20150120134602/https://docs.djangoproject.com/en/1.7/ref/contrib/csrf/
  41. "Angular Cross Site Request Forgery (XSRF) Protection"
    https://docs.angularjs.org/api/ng/service/$http#cross-site-request-forgery-xsrf-protection
  42. devcenter.heroku.com
    https://devcenter.heroku.com/articles/http-request-id
  43. Rapid7 Blog
    https://blog.rapid7.com/2016/12/23/the-value-of-correlation-ids/
  44. hilton.org.uk
    http://hilton.org.uk/blog/microservices-correlation-id
  45. w3c.org
    https://www.w3.org/TR/trace-context/
  46. Web Platform Incubator Community Group
    https://wicg.github.io/savedata/#save-data-request-header-field
  47. MDN Web Docs
    https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-GPC
  48. PATCH Method for HTTP
    http://tools.ietf.org/html/rfc5789#section-3.1
  49. HTTP Alternative Services
    https://www.rfc-editor.org/rfc/rfc7838
  50. HTTP Alternative Services, section 3
    https://tools.ietf.org/html/rfc7838#section-3
  51. Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)
    https://www.rfc-editor.org/rfc/rfc6266
  52. HTTP Semantics
    https://datatracker.ietf.org/doc/html/rfc9110#section-8.5
  53. Indicate the canonical version of a URL by responding with the Link rel="canonical" HTTP header Retrieved: 2012-02-09
    https://support.google.com/webmasters/bin/answer.py?hl=en&answer=139394
  54. W3C P3P Work Suspended
    http://www.w3.org/P3P
  55. "Public Key Pinning Extension for HTTP"
    http://www.rfc-editor.org/rfc/rfc7469.txt
  56. HTTP Semantics
    https://datatracker.ietf.org/doc/html/rfc9110#section-10.2.3
  57. HTTP Header Field X-Frame-Options
    https://www.rfc-editor.org/rfc/rfc7034
  58. "Content Security Policy Level 2"
    http://www.w3.org/TR/CSP11/#frame-ancestors-and-frame-options
  59. "Content Security Policy"
    http://www.w3.org/TR/CSP/
  60. Mozilla Developer Network
    https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Expect-CT
  61. Mozilla Developer Network
    https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/NEL/
  62. "Permissions Policy"
    https://www.w3.org/TR/permissions-policy/
  63. "Am I FLoCed?"
    https://amifloced.org/
  64. GitHub
    https://github.com/whatwg/html/pull/2892
  65. Mozilla Developer Network
    https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/report-to
  66. RFC 9110: HTTP Semantics
    https://www.rfc-editor.org/rfc/rfc9110
  67. Mozilla Developer Network
    https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Timing-Allow-Origin
  68. "Configuring servers for Ogg media"
    https://developer.mozilla.org/en-US/docs/Web/HTTP/Configuring_servers_for_Ogg_media#Serve_X-Content-Duration_headers
  69. Bugzilla@Mozilla
    https://bugzilla.mozilla.org/show_bug.cgi?id=1160695
  70. "IE8 Security Part VI: Beta 2 Update"
    http://blogs.msdn.com/b/ie/archive/2008/09/02/ie8-security-part-vi-beta-2-update.aspx
  71. "Hosting - Google Chrome Extensions - Google Code"
    https://code.google.com/chrome/extensions/hosting.html
  72. WHATWG
    https://fetch.spec.whatwg.org/#x-content-type-options-header
  73. "X-Redirect-By HTTP response header"
    https://webtechsurvey.com/response-header/x-redirect-by
  74. "Defining Document Compatibility: Specifying Document Compatibility Modes"
    http://msdn.microsoft.com/en-us/library/ie/cc288325%28v=vs.85%29.aspx#SetMode
  75. WHATWG
    https://html.spec.whatwg.org/multipage/semantics.html#attr-meta-http-equiv-x-ua-compatible
  76. "IE8 Security Part IV: The XSS Filter"
    http://blogs.msdn.com/b/ie/archive/2008/07/02/ie8-security-part-iv-the-xss-filter.aspx
  77. HTTP Caching
    https://datatracker.ietf.org/doc/html/rfc9111#section-5.4
  78. "How to prevent caching in Internet Explorer"
    https://support.microsoft.com/en-us/kb/234067/
  79. "What is the X-REQUEST-ID http header?"
    https://stackoverflow.com/questions/25433258/what-is-the-x-request-id-http-header
  80. "Why does ASP.NET framework add the 'X-Powered-By:ASP.NET' HTTP Header in responses? - Stack Overflow"
    https://stackoverflow.com/questions/1288338/why-does-asp-net-framework-add-the-x-powered-byasp-net-http-header-in-response
Image
Source:
Tip: Wheel or +/− to zoom, drag to pan, Esc to close.