Running Really Simple SSL pro multisite 4.1.9
HTTPS enable on a per-site basis, and turned on.
The mixed content fixer combined with the 301 redirects through .htaccess seem to be working except for one issue.
When a client does not have a favicon saved, firefox browsers request one anyways.
A 302 link is returned for the insecure ‘w-logo-blue-white-bg.png’
Subsequently a 301 is returned for secure ‘w-logo-blue-white-bg.png’
But it was enough to trip the HTTPS warning in Firefox.
This topic was modified 1 month, 2 weeks ago by Blake Mackey.
I’ve narrowed the issue down to concurrent use of a plugin called WP Ultimo v1.10.13.
I use this plugin to manage my multisites.
Ultimo has it’s own separate setting to turn on/off forcing HTTPS.
If I disable Ultimo, everything works perfectly.
If I enable Ultimo (but leave its ‘force https’ setting off), all links get redirected perfectly with the exception of the default favicon fallback issue I note initially.
If I enable Ultimo (AND turn its ‘force https’ setting on), everything works perfectly.
I would prefer to manage the HTTPS setting under one plugin completely, so what can I change to enable this in Really Simple SSL?
I don’t think there’s a downside of enabling the force https in Ultimo as well. If you want we can take a look at the favicon issue. To do so, please share your domain with us. You can do this by sending an email to support(at)really-simple-ssl.com