Upgrade-Insecure-Requests request header sends a signal to the server expressing the client’s preference for an encrypted and authenticated response, and that it can successfully handle the
upgrade-insecure-requests CSP directive.
|Header type||Request header|
|Forbidden header name||no|
A client requests signals to the server that it supports the upgrade mechanisms of
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
|Upgrade Insecure Requests
The definition of 'upgrade-insecure-requests' in that specification.
|Candidate Recommendation||Initial definition.|
The compatibility table in this page is generated from structured data. If you'd like to contribute to the data, please check out https://github.com/mdn/browser-compat-data and send us a pull request.
|Feature||Android webview||Chrome for Android||Edge mobile||Firefox for Android||Opera Android||iOS Safari||Samsung Internet|
1. Under consideration for future release.