SSL

Chrome 62: all text inputs without SSL showing not secure warning

Yesterday Sucuri posted a blog that might cause some worries for a regular small business owner: as of the coming version of Chrome, version 62, all input text fields on websites will result in “not secure” warnings in the browser. This might scare your customers away for no reason, so once more this is evidence that Google is forcing the web over https. First they started by giving ranking benefits, now they are starting to hand out penalties for not being on SSL.

I think this is a good thing, as it will make the web more secure. Furthermore, as SSL certificates or not expensive, or even free, there aren’t many arguments to stay on http.

Related Articles

  • Complianz GDPR 1.2: Cookie notification with A/B testing and categories

    Today Complianz GDPR premium 1.2.0 and Complianz GDPR 1.2.0 have been released! Both free and premium versions now have the option to use categories in the cookie warning. If you...
  • 2.3.10 release

    As WordPress 4.6 was due to release today, I was planning to release the new version of Really Simple SSL as well. No really big changes, but ‘ll list them...
  • Really Simple SSL 2.5.21 ready for betatesting

    Today 2.5.21 was released for beta testing on https://github.com/rlankhorst/really-simple-ssl. We welcome any input on this new release! This release is already extensively tested without any issues, but we love to get...
  • Really Simple SSL 2.4 released

    Today the 2.4 version is released. The mixed content fixer has been rebuilt, which should make it work in almost all situations. The marker which makes it possible for the...