APACHE & HTTPS

Starting in January 2017, Google Chrome will start flagging web sites which do not use HTTPS. At present about 50% of web sites use HTTPS.

Google is aware of incremental cost of a web site obtaining a certificate etc. This means its likely that page ranks of non-HTTPS sites will be reduced severely.

The net effect of this change will mean may websites will close as the costs exceed revenue. Already many sites, including this one, have seen revenue declines.

Azure offers *.azurewebsites.net a HTTPS cerficate so that any site using Azure can use HTTPS now. This means sites like this will not be harmed by the Google change.

HEARTBLEED

Some SSL problems were found with openssl so it had to be patched.

openssl version -a

if its below than 1.0.1g then update your system

ENABLE HTTPS

Adding this generic JavaScript to the header of a web page will change it to HTTPS.

<script type=”text/javascript”>
    if (window.location.protocol != “https:”) window.location.href = “https:” + window.location.href.substring(window.location.protocol.length);
</script>

WORDPRESS

There are broken link checkers to find any problematic images or hrefs that are broken. Larger blogs with lots of images could be exposed to thousands of man hours of work to fix links.