HTTP Response Headers
A server can respond with a variety of headers in its response to your web browser. Here you can learn what each one means.
Indicates that the server can handle partial requests and resume interrupted downloads.
Number of seconds that the page has been in a proxy cache.
Tells the browser to load the content from another server, without doing a redirect.
Used to control how the response can be cached by any mechanism along the response chain.
A header used by Cloudflare to indicate whether a resource was cached or not.
An ID used by Cloudflare to track requests.
Tells the web browser how to decode the data being sent. This is usually used to compress data for more efficient transfer.
Specifies the language that the intended audience should be able to speak.
Contains the size, in bytes, of the body of the response.
Used to protect users from Cross Site Scripting and Data Injection attacks.
Indicates the media type of the response that is being sent.
Indicates the date and time when the server response was generated.
A unique identifier for a resource to let web caches work more efficiently.
Contains a date and time after which the current response is stale and should be refetched.
Controls which features of the web browser are allowed to work for this website.
This header includes a date which references the day and time when this resource was last updated.
The NEL header is used to configure Network Error Logging.
Controls which features of the web browser are allowed to work for this website.
Protects data from being leaked to 3rd party or insecure origins.
Specifies how the web browser should report certain types of issues that it encounters.
Provides information about the software used by the server.
Instructs the browser to store some information and then send it back to the server on subsequent requests.
Tells web browsers that they should only use HTTPS connections to view this website.
Specifies the encoding used to transfer the response to the client.
Indicates to caching layers how to handle responses based on different request headers.
Tells the web browser that the Content-Type headers are deliberately set and should be followed.
Prevents sites from being displayed inside an iframe.
Provides information about the software running on your server that was used to generate the webpage.
Provides protection against reflected cross-site scripting attacks.