You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The existing GHC Resource authorization supports both Basic Auth and Bearer Token.
The latter results in setting HTTP Header: Authorization: Bearer <token>.
Problem
In some ESRI ArcGIS server configurations the following HTTP Header is required: X-Esri-Authorization: Bearer <token>....
* update all translation files plus doc HOWTO translations
* #268 drop de_DE translations ('de' only now)
* #9 add auth headers for WMS OWSLib calls
* #277 support ESRI ArcGIS Server token auth
…es) Collections (#284)
* update all translation files plus doc HOWTO translations
* #268 drop de_DE translations ('de' only now)
* #9 add auth headers for WMS OWSLib calls
* #277 support ESRI ArcGIS Server token auth
* #283 change name to id for Collection identifier plus tests
Intro
The existing GHC Resource authorization supports both Basic Auth and Bearer Token.
The latter results in setting HTTP Header:
Authorization: Bearer <token>
.Problem
In some ESRI ArcGIS server configurations the following HTTP Header is required:
X-Esri-Authorization: Bearer <token>
....See details below and here
Possible Solution
Within the ESRI FS Probe, if the HTTP Header:
Authorization: Bearer <token>
is set, set alsoX-Esri-Authorization
with the same value.The text was updated successfully, but these errors were encountered: