Fixing HTTPS Redirects and Mixed Content on Masterhost

Moving an Evolution CMS site to HTTPS should be routine, but on shared hosting the redirect layer, manager asset paths, and inherited .htaccess rules can combine into frustrating mixed-content issues.

The typical symptom

• the site redirects to HTTPS
• some CSS, JS, or editor assets still load over HTTP
• the manager may partially break
• the browser lock never becomes fully secure

Why this happens

A redirect rule alone does not guarantee that generated asset URLs, manager configuration, and editor integrations also switch to HTTPS. On older Evolution CMS projects, one hard-coded HTTP path is enough to keep the problem alive.

What to verify

• the site URL and manager URL settings
• hard-coded protocol references in templates and chunks
• editor and file-manager asset paths
• exceptions in .htaccess that bypass HTTPS unexpectedly

Deployment advice

Start with a clean redirect rule set from a current distribution, then test assets in the network inspector. Fix the URLs that are still generated as HTTP instead of trying to solve everything with rewrite exceptions alone.

Mixed-content fixes are usually a configuration audit, not just a redirect task.