SSL

Really Simple SSL 2.5.14, minor update

2.5.14 was released today, with two adjustments:

  • A bug was discovered in the mixed content fixer, where a match was found on http links across html elements when newlines were removed by optimization plugins. If a link element was found, but the href was https, it would match the first href=”http, which could be an external hyperlink.
    It didn’t come up before, as it only causes an issue in a very specific set of conditions.
  • The wp_rest_api was not forced over SSL yet with PHP. Although the .htaccess redirect should redirect any requests to https, NGINX servers won’t be able to use this. This has now been adjusted.

 

Related Articles

  • Certificate expiration check in Really Simple SSL pro

    There’s something strange with uptime robots: they don’t detect expired certificates. So even though you don’t get any messages that your site is down, it might be if your SSL...
  • 2.3.5 Released

    Versino 2.3.5 was released today. A 2.3.4 version was released earlier today, but contained a small bug: the javascript redirect was not added correctly anymore. As the javascript should be...
  • Over 500.000 active installations of Really Simple SSL!

    This week I noticed Really Simple SSL has passed half a million active websites, and is download over 2 million times! Pretty cool! So I have to thank you, for...
  • Easy Digital Downloads Gravity Forms license integration

    As we use Easy Digital Downloads software licensing for plugin upgrade handling in combination with Gravity Forms to handle support requests, I missed a simple automatic license check in Gravity...

2 Comments

  • ao

    It was redirecting my homepage to the login page. I hope this update will take care of that issue. Nice plugin by the way. Thanks

    • Rogier Lankhorst

      Yes, the wp_safe_redirect had me confused: it can’t be used on the front-end, as it redirects to the login page instead of a similar but safe url. It also kicks in when the www version of the site is used for example. This is fixed as of 2.5.15. Sorry for any problems this might have caused. Somehow this didn’t pop up in the tests. Tests are being improved to prevent this in the future.