HTTPS & Geolocation

Posted by James Watson on 30 Jul, 2016

I've added a Blog to the site (courtesy of Goutham Balaraman's Flask-Blogging extension) as a means of providing notification of updates and details of new features as they're added...

In response to an increase in the general awareness of web privacy concerns, Google recently announced that Chrome would stop supporting Geolocation API calls served from insecure contexts (e.g. HTTP). In order to maintain the ability to set the transmit / receive site locations using the location buttons in the site entry panel header bars the site now supports HTTPS, using certificates issued by the Let's Encrypt project.

It's recommended that users access the site using the secure https protocol;


 Share on: Twitter / Facebook / Google+ / Email