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.

HTTP Upgrade Header - HTTP/2

Download List of All Websites using HTTP Upgrade Header - HTTP/2

   The HTTP Upgrade mechanism is used to establish HTTP/2 starting from plain HTTP. The client starts an HTTP/1.1 connection and sends an Upgrade: h2c header. If the server supports HTTP/2, it replies with HTTP 101 Switching Protocol status code. The HTTP Upgrade mechanism is used only for cleartext HTTP2 (h2c). In the case of HTTP2 over TLS (h2), the ALPN TLS protocol extension is used instead.

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.

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.

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.

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=0 secs.

Vary Header check for User-Agent

Download List of All Websites using Vary Header check for User-Agent

   When using the Vary: User-Agent header, caching servers should consider the user agent when deciding whether to serve the page from cache

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.