-
Notifications
You must be signed in to change notification settings - Fork 26
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
Switch to api.openstreetmap.org API host #123
Conversation
Looking into this today.. When I try it, I get a "301 Moved Permanently" redirect, which triggers a CORS error. There is some discussion on openstreetmap/operations#951 about it. |
Yes, this is the reason I personally made this a draft as mentioned above. |
I ended up just copying what @tyrasd did in openstreetmap/iD@c4d1390 by making separate |
Since this PR is being linked from all over the place, I'll copy what I said in westnordost/osmapi#33 (comment) . Realistically the RFC 8414 compliant endpoints should be used. Those would be https://www.openstreetmap.org/.well-known/oauth-authorization-server and https://api.openstreetmap.org/.well-known/oauth-authorization-server (which redirects to www). The JOSM code does look for that on non-OSM endpoints, but that will probably change so that we don't have URL endpoints hardcoded into the application [for OSM]. |
Use
api.openstreetmap.org/api/
-and HTTPS- instead ofwww.openstreetmap.org/api/*
.(Is: openstreetmap/operations#951)
Except for regular link in README.md and index.html.
PR will initially be marked as a draft, as there seem to be unresolved issues upstream.
cc: @bhousel