View Single Post
  #1  
Old 02-14-2017, 06:25 PM
Toby's Avatar
Toby Toby is offline
Senior Member
 
Join Date: Oct 2007
Location: Houston, we have a problem!
Posts: 601
Default To SSL or Not to SSL

Google is getting more aggressive about sites being encrypted, and a Google Security Blog post from last Fall was brought to my attention by a sponsor program earlier this month due to the need for changing link codes as the result of implementing SSL.

https://security.googleblog.com/2016...ecure-web.html

The part that got my attention... Beginning in January 2017 (Chrome 56), we’ll mark HTTP pages that collect passwords or credit cards as non-secure, as part of a long-term plan to mark all HTTP sites as non-secure.

That makes it pretty clear that Google intends to eventually flag all HTTP sites as insecure. That can't be good for surfer confidence and traffic. I've just implemented SSL across my entire network. I'm still in the process of tweeking a few things to get all my scripts to play nice with SSL. But overall, it has been far less painful than anticipated.

Last edited by Toby : 02-14-2017 at 11:49 PM.
Reply With Quote