Skip to Content

The author


If you needed another excuse to run your websites over HTTPS, then you'll be pleased to know that W3C has put in draft recommendations (that both Chrome and Firefox have taken on already) to require HTTPS for some of the more powerful HTML5 features, starting with those most likely to contain personally identifiable information.

Features include:

  • Geolocation
  • Fullscreen
  • Device orientation/motion
  • Video and microphone

These will now require that the website is running over HTTPS. For example, making sure that a user’s location isn’t broadcast unencrypted makes perfect sense, when you think about it.

This change is in Chrome Canary (version 50) and Firefox Nightly (47) at the moment. As you may  know with browser’s rapid releases, this isn't far away (April 19th 2016 for Chrome)

Once those are released, requests for these features will just return an error:

So if you have any upcoming websites that make use of these features, or any existing sites that you’d still like to work for the foreseeable future, then now is the time to take the plunge and move to HTTPS!

If you'd like to know more about switching across to HTTPS, get in touch to speak with one of our technical advisers.


At the end of January, Google updated its webmaster guidelines with a specific mention to HTTPS. 

"If possible, secure your site's connections with HTTPS. Encrypting interactions between the user and your website is a good practice for communication on the web."

It's a rare event that Google updates its guidelines and this entirely new addition clearly supports the need for websites to move to HTTPS.