upgrade-insecure-requests
A Content Security Policy directive that makes the browser fetch a page's http:// sub-resources over https:// instead. It clears mixed-content warnings on older pages without editing every link.
What upgrade-insecure-requests does not show
Covered in CrawlCheck's guide to rolling out a Content Security Policy from report-only to enforced. It only works where the HTTPS version of each file exists, and it does not redirect the page itself or replace HSTS.
Terms this definition uses
Related terms in Security and privacy
Where an agent, a tool or a page can be turned against its operator, and the controls that limit the damage without proving safety.
Cookie prefix · Partitioned cookie · SameSite · Public suffix · Schemeful same-site · Subresource Integrity · Integrity metadata · CSP report-only · CSP hash · strict-dynamic · form-action · base-uri · object-src · Referrer leakage · Dangling CNAME · Subdomain takeover · SPF lookup limit · TLS downgrade · Certificate Transparency · X-Frame-Options · frame-ancestors · Referrer-Policy · Permissions-Policy · Encrypted Client Hello · lookalike domain · homoglyph · incident switch · high-risk field · Indirect prompt injection · Direct prompt injection · Jailbreak · Data exfiltration · Sensitive information disclosure · Secret leakage · Insecure output handling · Excessive agency · Least privilege · Trust boundary · Input validation · Output validation · Allowlist · Denylist · SSRF · RCE · Credential scope · OAuth scope · API key · Bearer token · mTLS · Rate-limit policy · Audit log · PII · Data minimization · Purpose limitation · Retention period · Data residency · Tenant isolation · Threat model · DMARC · DMARC alignment · SPF · DKIM · MTA-STS · TLS-RPT · CAA record · DNSSEC · hard bounce
Questions about upgrade-insecure-requests
What is upgrade-insecure-requests?
A Content Security Policy directive that makes the browser fetch a page's http:// sub-resources over https:// instead. It clears mixed-content warnings on older pages without editing every link.
What does upgrade-insecure-requests not show or guarantee?
It clears mixed-content warnings on older pages without editing every link. Covered in CrawlCheck's guide to rolling out a Content Security Policy from report-only to enforced. It only works where the HTTPS version of each file exists, and it does not redirect the page itself or replace HSTS.
Which area of the glossary does upgrade-insecure-requests belong to?
Security and privacy: Where an agent, a tool or a page can be turned against its operator, and the controls that limit the damage without proving safety.
← form-action · base-uri →
See it in the full glossary · 792 terms across 19 areas.
Free browser extension
See this on any site you visit, in one click.
CrawlCheck for Chrome grades every site you visit A–F and shows, from your own browser, what search engines and AI assistants are actually served. Free, no account.