Dries Buytaert

Explanation

The date and time at which the request was made. A browser uses it for age calculations rather than using its own internal date and time; e.g. when comparing against Max-Age or Expires.

The type of the message body, specified as a MIME type.

The Vary header specifies a list of headers that must be considered when caching responses. For a cached response to be used, these headers must match between the cached response and the new request. This ensures that the appropriate version of a resource is served based on factors like language, encoding, or device type.

A cookie that was sent from the server to the browser.
expires= sets the maximum lifetime of the cookie using a specific date.
max-age= sets the maximum lifetime of the cookie in seconds.
path= indicates the path that must exist in the requested URL for the browser to send the cookie.

A cookie that was sent from the server to the browser.
expires= sets the maximum lifetime of the cookie using a specific date.
max-age= sets the maximum lifetime of the cookie in seconds.
path= indicates the path that must exist in the requested URL for the browser to send the cookie.

A cookie that was sent from the server to the browser.
expires= sets the maximum lifetime of the cookie using a specific date.
max-age= sets the maximum lifetime of the cookie in seconds.
path= indicates the path that must exist in the requested URL for the browser to send the cookie.

A cookie that was sent from the server to the browser.
expires= sets the maximum lifetime of the cookie using a specific date.
max-age= sets the maximum lifetime of the cookie in seconds.
path= indicates the path that must exist in the requested URL for the browser to send the cookie.

A cookie that was sent from the server to the browser.
expires= sets the maximum lifetime of the cookie using a specific date.
max-age= sets the maximum lifetime of the cookie in seconds.
path= indicates the path that must exist in the requested URL for the browser to send the cookie.

missing Add a Strict-Transport-Security header. The Strict-Transport-Security header or HSTS header is used to instruct browsers to only use HTTPS, instead of using HTTP. It helps enforce secure communication.

missing Add a Content-Security-Policy header. The Content-Security-Policy header helps browsers prevent cross site scripting (XSS) and data injection attacks.

missing Add a Referrer-Policy header. When a visitor navigates from one page to another, browsers often pass along referrer information. The Referrer-Policy header controls how much referrer information a browser can share. This is important to configure when private information is embedded in the path or query string and passed onto an external destination.

missing Add a Permissions-Policy header. Restrict access to device features like the camera, microphone, location, accelerometer and much more.

missing Add a Cross-Origin-Embedder-Policy to specify how this page can be loaded by cross-origin resources.

missing Add a Cross-Origin-Opener-Policy header to opt-in into better browser isolation.

missing Add a Cross-Origin-Resource-Policy header to specify who can load this page.

missing Add a X-Frame-Options header. The X-Frame-Options header prevents this URL from being embedded in an iframe. This protects against clickjacking attacks. Alternatively, set a Content-Security-Policy header with a frame-ancestor directive.

missing Add a X-Permitted-Cross-Domain-Policies header to prevent Flash, Adobe Reader and other clients from sharing data across domains.