|
I have contributed to OSM for seven years. Now, for the first time, North America shows upon opening as here: http://www.openstreetmap.org/#map=5/38.007/-95.844. I receive messages such as below when I choose 'Show my location': Geolocation error: Network location provider at 'https://www.googleapis.com/' : Returned error code 403.. Geolocation error: Only secure origins are allowed (see: https://goo.gl/Y0ZkNV).. I am unaware of any action on my part to deny my location. I use a version of Chrome on my Windows desktop. I have read to go to Settings>Content Settings...>Website Settings>openstreetmap.org. Website Settings does not exist so far as I can see. |
|
There are two issues here: One is the display that you see when you first open the OSM website. In a new window with no cookies etc., I get a map of Western Europe; I think that this is either based on IP address geolocation or just the default - see here for an explanation of that. The other issue is what happens when you click the "show my location" button. That has the web site ask your web browser where it thinks it is. As the link indicates, recent versions of Chrome and Chromium won't send your location to a website unless it's over an https connection. Also Firefox 55+. There's an issue for this one here, and the decision to not send your location to OSM is your browser's, not OSM's. There's been discussion about whether it's a good idea for OSM to only support https, and there are arguments both for and against that that have been discussed ad nauseum in github and on mailing lists etc. As nevw has said, if you browse to https://www.openstreetmap.org/ the "show my location button" will work, which will probably result in another prompt from your browser asking whether you want to share your location with OpenStreetMap.org. I thank you both for your responses. I have opened OSM using the link above. Clicking 'Show my location' resulted in Geolocation error: Network location provider at 'https://www.googleapis.com/' : Returned error code 403.. this time, so still no success, unfortunately. Typing 'Binfield Heath' into the search bar gets me to where I need to be very quickly, so I might find the situation resolves itself as unexpectedly as it appeared a few days ago. I have no such issue on my Android 'phone, using the same browser and search engine.
(12 Sep '17, 20:50)
silver mapper
|
|
I had this error message and followed the explanatory link, which was mostly incomprehensible to an "ordinary" user of OSM. Such gems as "a service worker script that had been tampered with because they got it over a MITM’d or spoofed cafe wifi connection" are all well and good, but it would have been more useful to put, simply, "Check you are using https" or something similar. KISS :) The page you're refering to is part of Chrome's documentation. It is an open source project so in theory you could contribute to making that page more helpful, though I'm not sure which part of "recent versions of Chrome and Chromium won't send your location to a website unless it's over an https connection" was unclear :)
(01 Apr '18, 10:41)
SomeoneElse ♦
|
It could be that you need to use https instead of http
I also first noticed this error in Chrome, and wrote a blog post about it here: http://harrywood.co.uk/blog/2016/07/21/leaflet-geolocation-error/ but I see nowadays firefox and safari have followed, locking it down so you can only geolocate if you're on a secure connection.