How to fix: HTTP resources loaded on HTTPS page (mixed content)
An HTTPS page loads scripts, images, or other resources over HTTP, triggering browser mixed content warnings.
Why it matters
Active mixed content (scripts, iframes, forms) is blocked by modern browsers. Passive mixed content (images) is loaded but can be intercepted by a network attacker, replacing images, injecting watermarks, or fingerprinting users via the unencrypted HTTP request.
All resources must be loaded over HTTPS when the page is served over HTTPS.
How to fix it
- 1Update all resource URLs from http:// to https://
- 2Add upgrade-insecure-requests to your CSP to auto-upgrade HTTP requests
- 3Use protocol-relative URLs (//example.com) or absolute HTTPS URLs
Code examples
CSP upgrade-insecure-requests
// next.config.mjs
export default {
async headers() {
return [{ source: "/(.*)", headers: [{ key: "Content-Security-Policy", value: "upgrade-insecure-requests; default-src https: 'self';" }] }];
},
};References
Detected automatically by VulnRadar. The check id is mixed-content, stable across every scan so you can filter or diff on it.
More headers checks
Questions
- How severe is HTTP resources loaded on HTTPS page (mixed content)?
- VulnRadar rates this high severity in the headers category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id mixed-content, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does HTTP resources loaded on HTTPS page (mixed content) map to?
- It maps to CWE-319. In the OWASP Top 10 it falls under A02:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.