Baseline Widely available
The HTTP Upgrade-Insecure-Requests request header sends a signal to the server indicating the client's preference for an encrypted and authenticated response, and that the client can successfully handle the upgrade-insecure-requests CSP directive.
Upgrade-Insecure-Requests: <boolean>
<boolean>
1 indicates 'true' and is the only valid value for this field.
A client's request signals to the server that it supports the upgrade mechanisms of upgrade-insecure-requests:
GET / HTTP/1.1
Host: example.com
Upgrade-Insecure-Requests: 1
The server can now redirect to a secure version of the site. A Vary header can be used so that the site isn't served by caches to clients that don't support the upgrade mechanism.
Location: https://example.com/
Vary: Upgrade-Insecure-Requests
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4