HTTP Headers
The following HTTP headers are parsed and understood by redirect.li.
Specify what client hints should be included in subsequent requests.
What partial content range types this server supports via byte serving.
access-control-allow-credentials
Allow credentials to be sent in CORS requests.
Indicate whether the response can be shared with the given origin.
The age the object has been in a proxy cache in seconds.
Indicate a resource should be loaded from a different server while still appearing to be loaded from this server.
Platform for Privacy Preferences Project, now obsolete.
Inform all caching mechanisms from server to client whether they may cache this object.
Encoded information about your request from Cloudflare.
Encoded information about your request from Cloudflare.
Cloudflare request ID
Control options for the current connection and list of hop-by-hop response fields.
Determine whether the response should be displayed inline or downloaded.
Encodings used in the message, and the order they appear.
The natural language or languages of the intended audience for the enclosed content.
The length of the response body in octets (8-bit bytes).
The content security policy allows the server to determine what resources the user is allowed to load.
content-security-policy-report-only
The content security policy, reporting only.
The MIME type of this content.
Isolate the document from cross-origin windows.
The cross-origin policy.
The date and time that the message was sent.
Do not track.
An identifier for a specific version of a resource.
Used by a server to indicate that UAs should evaluate connections to the host emitting the header field for CT compliance.
The time at which the response is considered stale.
Enable and disable browser features.
Host name of requested site.
The last modified date for the requested object.
Used to express a typed relationship with another resource.
New location of requested resource.
MIME version.
Configure network request logging.
P3P policy.
Enable and disable browser features.
HTTP/1.0 backwards compatible cache handling.
Send or receive a partial part of the resource.
Controls what referrer information is sent with requests.
Report to.
A name for the server.
Server metrics for the request.
A cookie sent from the server to be set on the client
A HSTS Policy informing the HTTP client how long to cache the HTTPS only policy and whether this applies to subdomains.
Indicates that different content may be provided to different clients, depending on the vary header.
Added by proxies to track a request through proxies and to avoid loops.
Authentication method used to access the resource.
Indicates whether a cache was used to server this response.
Used by the Google Cloud platform to identify requests.
Use x-content-type-options.
Prevents Internet Explorer from MIME-sniffing a response away from the declared content-type.
Clickjacking protection.
Tags for Magento.
x-permitted-cross-domain-policies
Specifies if a cross-domain policy is allowed.
Where to send WordPress pings.
The software powering this site.
WordPress redirect agent. A value of "WordPress" indicates that WordPress itself redirected the resource.
URL is being redirected with the WordPress plugin Redirection.
Specify how the resource is shown in search results.
Recommends the preferred rendering engine (often a backward-compatibility mode) to use to display the content.
Details about the Vercel cache
Cross-site scripting (XSS) filter.