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:
Public Cache-Control
Download List of All Websites using Public Cache-Control
Indicates that the response may be cached by any cache, even if the response would normally be non-cacheable (e.g. if the response does not contain a max-age directive or the Expires header).
Tags:
Post Cache-Control Header
Download List of All Websites using Post Cache-Control Header
this website is using post-heck Cache-Control Header.
Tags:
Precheck Cache-Control Header
Download List of All Websites using Precheck Cache-Control Header
this website is using precheck Cache-Control Header.
Tags:
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:
Cache-Control Header Max-Age
Download List of All Websites using Cache-Control Header Max-Age
Specifies the maximum amount of time a resource will be considered fresh. Contrary to Expires, this directive is relative to the time of the request. this website is having max-age=900 secs.
Tags:
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:
Block Content Sniffing
Download List of All Websites using Block Content Sniffing
The X-Content-Type-Options response HTTP header is a marker used by the server to indicate that the MIME types advertised in the Content-Type headers should not be changed and be followed. This allows to opt-out of MIME type sniffing, or, in other words, it is a way to say that the webmasters knew what they were doing.
Tags:
XSS-Protection Header
Download List of All Websites using XSS-Protection Header
The HTTP X-XSS-Protection response header is a feature of Internet Explorer, Chrome and Safari that stops pages from loading when they detect reflected cross-site scripting (XSS) attacks. Although these protections are largely unnecessary in modern browsers when sites implement a strong Content-Security-Policy that disables the use of inline JavaScript (`unsafe-inline`), they can still provide protections for users of older web browsers that don`t yet support CSP.
Tags: