Google has made changes lately to Google Maps API related to Geo Location on Chrome, Firefox and Safari and more browsers in the future due to security concern. Your server will require HTTPS in order to use geo location.

Chrome has public intent to deprecate powerful features like geolocation on non-secure origins, and we hope that others will follow.

Starting with Chrome 50, Chrome no longer supports obtaining the user’s location using the HTML5 Geolocation API from pages delivered by non-secure connections. This means that the page that’s making the Geolocation API call must be served from a secure context such as HTTPS.

It is an important issue as it will directly impact any site that requires use of the geolocation API and is not served over https, but it is a change that we do believe is beneficial to all users on the web. This post should help you understand the reasoning and how to proceed.

Read full article available at https://developers.google.com/web/updates/2016/04/geolocation-on-secure-contexts-only

Users who have LIKED this post: