-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Access Nominatim via HTTPS for location search #2960
Comments
kepta
added a commit
to kepta/iD
that referenced
this issue
Feb 3, 2016
change of all http:// URIs in js/id folder to //. (closes openstreetmap#2960)
Merged
kepta
added a commit
to kepta/iD
that referenced
this issue
Feb 3, 2016
change of all http:// URIs in js/id folder to //. (closes openstreetmap#2960)
kepta
added a commit
to kepta/iD
that referenced
this issue
Feb 3, 2016
change of all http:// URIs in js/id folder to https://. (closes openstreetmap#2960)
kepta
added a commit
to kepta/iD
that referenced
this issue
Feb 3, 2016
change of all http:// URIs in js/id folder to https://. (closes openstreetmap#2960)
kepta
added a commit
to kepta/iD
that referenced
this issue
Feb 4, 2016
(closes openstreetmap#2960) Interim
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When trying to do a location search using the "Search worldwide" button, my browser is blocking the request because I loaded osm.org via HTTPS but iD is trying to contact Nominatim via HTTP. I am using Chromium but I think all browsers have become more strict about this in the last year or two.
I see for reverse geocoding Nominatim's URL was changed in 16a2449 but the search feature is still pointing at HTTP. I believe the simplest fix might be to just change line 248 in feature_list.js to point at https://
The text was updated successfully, but these errors were encountered: