Closed malenki closed 9 years ago
see http://wiki.openstreetmap.org/wiki/Talk:Overpass_turbo#in_doesn.27t_seem_to_work_in_wizard
Does it still fail in the master branch? edit: I see it does. Will investigate
Seems to be this bug: https://github.com/EFForg/https-everywhere/issues/49
OpenStreetMap.org ruleset does an automatic switch from http://nominatim.openstreetmap.org to https://nominatim.openstreetmap.org in the background. To verify that, you can manually deactivate that rule in HTTPS everywhere -> nominatim works as before.
One option could be to add a corresponding rule to HTTPS everywhere to do an automatic switch from http://overpass-turbo.eu to https://overpass-turbo.eu and all should be fine, at least when using overpass-turbo.eu/master.
BTW: Another error message needs to resolved here: "Blocked loading mixed display content "http://wiki.openstreetmap.org/w/images/b/b3/Powered_by_Overpass_API.png" "
Message on Javascript console:
http://nominatim.openstreetmap.org/search?X-Requested-With=overpass-turbo&format=json&q=Berlin
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://nominatim.openstreetmap.org/search?X-Requested-With=overpass-turbo&format=json&q=Berlin. (Reason: CORS header 'Access-Control-Allow-Origin' missing).
An error occured while contacting the osm search server nominatim.openstreetmap.org :(
turbo.m...5-04-23 (line 25)
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://nominatim.openstreetmap.org/search?X-Requested-With=overpass-turbo&format=json&q=Berlin. (Reason: CORS request failed).
Thanks for linking the ticket.
The only issue with adding overpass turbo to HTTPSeverywhere is that I don't have a signed certificate for https://overpass-turbo.eu/.
An alternative workaround would be to hardcode all nominatim queries to https
…
An alternative workaround would be to hardcode all nominatim queries to https…
this is now live on the main instance
Martin Raifer schrieb am Mon, 18 May 2015 13:16:41 -0700:
An alternative workaround would be to hardcode all nominatim queries to https…
this is now live on the main instance
Thanks for the quick fix, although I filed a quite incomplete issue. (Yes, I experienced it with FF and didn't test other browsers.)
You can get a certificate for free from Startssl.
When entering e.g.
and exectuing the query, overpass turbo immediately returns