SSL Insecure Content Fixer v2.5.0 has just been released. This release adds support for https detection on KeyCDN; an option to only fix content resource links for the current website; and the .htaccess rules file for the non-WP test script now supports Apache v2.4.
Thanks to Luke Driscoll for his contribution via GitHub, there is a new option for ignoring resources on external websites when fixing content blocks. This applies to the fixer modes of Content and above, and means that all your images from your own website will be fixed, but external ones won’t.
Thanks to Andreas Schneider for his contribution via GitHub, the test script that runs outside of WordPress in its own folder now has Apache rules that suit both v2.2 and v2.4 of Apache.
KeyCDN sends the header X-Forwarded-Scheme to tell websites what protocol their visitors connected with, and none of the standard headers. X-Forwarded-Scheme is now supported and will be automatically detected when you are using KeyCDN or similar reverse proxy systems.
You can update to the latest version from your WordPress plugin admin page. Here’s the full changelog for SSL Insecure Content Fixer.Posted on