Opened 7 years ago
Closed 7 years ago
#15147 closed defect (fixed)
Overpass request contains OAuth Authorization header
Reported by: | mmd | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | 17.08 |
Component: | Core | Version: | |
Keywords: | overpass api oauth http | Cc: |
Description
I noticed that JOSM's Overpass download sends an OAuth Authorization HTTP header field along with each request to Overpass API, although Overpass API does not require such a header and has no idea what to do with it.
I guess this is somehow a left over of communicating with api.openstreetmap.org? Would it make sense to only send this header to an API server, rather than an Overpass API instance?
Example header:
Authorization: OAuth oauth_consumer_key="...", oauth_nonce="...", oauth_signature="...", oauth_signature_method="HMAC-SHA1", oauth_timestamp="...", oauth_token="...", oauth_version="1.0"
Attachments (0)
Change History (2)
comment:1 by , 7 years ago
Keywords: | overpass api oauth http added |
---|---|
Milestone: | → 17.08 |
comment:2 by , 7 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
In 12598/josm: