Must Revalidate HTTP Cache-Control
Download List of All Websites using Must Revalidate HTTP Cache-Control
Indicates that once a resource has become stale (e.g. max-age has expired), a cache must not use the response to satisfy subsequent requests for this resource without successful validation on the origin server.
Tags:
NO Store HTTP Cache-Control
Download List of All Websites using NO Store HTTP Cache-Control
The cache should not store anything about the client request or server response.
Tags:
No Cache Content
Download List of All Websites using No Cache Content
Forces caches to submit the request to the origin server for validation before releasing a cached copy.
Tags:
X-Frame-Options Header
Download List of All Websites using X-Frame-Options Header
The X-Frame-Options HTTP response header can be used to indicate whether or not a browser should be allowed to render a page in a <frame>, <iframe>, <embed> or <object>. Sites can use this to avoid clickjacking attacks, by ensuring that their content is not embedded into other sites.
Pragma Header - backwards compatibility with HTTP/1.0
Download List of All Websites using Pragma Header - backwards compatibility with HTTP/1.0
The Pragma HTTP/1.0 general header is an implementation-specific header that may have various effects along the request-response chain. It is used for backwards compatibility with HTTP/1.0 caches where the Cache-Control HTTP/1.1 header is not yet present.
Tags:
HSTS - Browser HTTPS Only for domain and subdomains
Download List of All Websites using HSTS - Browser HTTPS Only for domain and subdomains
The HTTP Strict-Transport-Security response header (often abbreviated as HSTS) lets a web site tell browsers that it should only be accessed using HTTPS, instead of using HTTP for domain and subdomains browsers will never connect to your domain using an insecure connection. While the service is hosted by Googlefor 31536000 seconds
Vary Header Accept-Encoding
Download List of All Websites using Vary Header Accept-Encoding
The Accept-Encoding request HTTP header advertises which content encoding, usually a compression algorithm, the client is able to understand. Using content negotiation, the server selects one of the proposals, uses it and informs the client of its choice with the Content-Encoding response header.
Tags: