Fixing Insecure Mixed Content (HTTP Assets) on HTTPS
Eliminate browser mixed content warnings by enabling Nimbica’s automated HTTPS asset rewriting pipeline.
Understanding Mixed Content Warnings
When your site loads over secure HTTPS, modern browsers block insecure http:// stylesheets, scripts, fonts, and images with a "Mixed Content" security warning in the console.
Automated HTTPS Asset Rewriting
Nimbica's AI compiler automatically parses all asset references during build time and rewrites insecure http:// URLs to secure https:// or root-relative paths, guaranteeing zero mixed content warnings.
📋 Verified Execution Steps (3 Total Steps)
In Nimbica Dashboard ➔ Site Settings ➔ Security, verify "Force HTTPS Asset Rewriting" is enabled.
In WP-Admin ➔ Settings ➔ General, ensure WordPress Address (URL) and Site Address (URL) start with https://.
Trigger a new AI build to allow Nimbica to rewrite legacy database URLs in the output.