ProxyReversePass配置引发混合内容警告问题求助

Alright, let's tackle this mixed content warning issue you're facing after the server update. I've dealt with similar Apache reverse proxy + Magento/WordPress setups before, so here's what's likely going on and how to fix it:

When you use ProxyReversePass to serve WordPress content through your Magento HTTPS domain, the problem usually boils down to one thing: WordPress is still generating HTTP links for its resources (images, scripts, styles) even though the parent page loads over HTTPS. Browsers flag this as unsafe mixed content because they expect all resources on an HTTPS page to also use HTTPS.

This often happens after server updates because Apache might have reset some proxy-related headers, or the backend WordPress instance isn't aware it's being accessed through an HTTPS reverse proxy.

1. Update Apache Reverse Proxy Config to Pass HTTPS Context #

First, make sure your Apache virtual host for the Magento domain is properly telling WordPress that the incoming request is over HTTPS. Add these headers to your proxy configuration:

<VirtualHost *:443>
    ServerName your-magento-domain.com

    # Existing SSL config (SSLCertificateFile, SSLCertificateKeyFile, etc.)

    # Proxy rule for WordPress content (adjust paths to match your setup)
    ProxyPass /wordpress-content http://your-wordpress-domain.com/wordpress-content
    ProxyPassReverse /wordpress-content http://your-wordpress-domain.com/wordpress-content

    # Critical: Pass HTTPS info to the backend WordPress server
    RequestHeader set X-Forwarded-Proto "https"
    RequestHeader set X-Forwarded-Port "443"
</VirtualHost>

Don't forget to enable required Apache modules if they aren't already:

a2enmod headers proxy proxy_http
systemctl restart apache2

2. Configure WordPress to Recognize HTTPS via Proxy #

WordPress needs to know it's being accessed over HTTPS even if the direct connection from Apache is HTTP. Add this to your wp-config.php file:

// Force WordPress to use HTTPS when behind the reverse proxy
if (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && $_SERVER['HTTP_X_FORWARDED_PROTO'] === 'https') {
    $_SERVER['HTTPS'] = 'on';
    $_SERVER['SERVER_PORT'] = 443;
}

// Also update your site URL and home URL to use the Magento HTTPS path
define('WP_SITEURL', 'https://your-magento-domain.com/wordpress-content');
define('WP_HOME', 'https://your-magento-domain.com/wordpress-content');

3. Fix Existing HTTP Links in WordPress #

Even after updating the config, old HTTP links might still be stored in your WordPress database. Use one of these methods to replace them:

Option 1: WP-CLI (Recommended if you have it installed) #

wp search-replace 'http://your-wordpress-domain.com' 'https://your-magento-domain.com/wordpress-content' --skip-columns=guid

Option 2: Database Query (Backup first!) #

Run these SQL commands on your WordPress database (replace wp_ with your table prefix):

UPDATE wp_posts SET post_content = REPLACE(post_content, 'http://your-wordpress-domain.com', 'https://your-magento-domain.com/wordpress-content');
UPDATE wp_postmeta SET meta_value = REPLACE(meta_value, 'http://your-wordpress-domain.com', 'https://your-magento-domain.com/wordpress-content');

4. Verify Magento's References to WordPress Content #

Double-check any places in Magento where you're embedding WordPress content (like widgets or custom blocks) to ensure they're using the HTTPS URL from your Magento domain, not the old WordPress HTTP domain.

After making these changes:

• Clear your Magento and WordPress caches completely
• Open the page in a browser, hit F12 to open DevTools, and check the Console tab for remaining mixed content errors (it will show exactly which resources are still using HTTP)
• Test across different browsers to ensure the warning is gone

内容的提问来源于stack exchange，提问作者Pablo Marti Cordero