Describe the bugX-Esri-Authorization header is still sent after changing Authorization on ESRI:FS Resource from Bearer Token to Basic Auth. This leads to Invalid Token error.
First reported by @BenGunnewijk .
To Reproduce
Steps to reproduce the behavior, e.g.:
Add ESRI:FS Resource
In Edit screen add Bearer Token auth and Save
Now change Auth to Basic Auth (provide valid user/password) and Save
Klik Test button
Test result is False, in details see code=498 message=Invalid Token
Expected Behavior
Step 5 above should be True (success) as Basic Auth should be accepted.
Screenshots or Logfiles
N.A.
Context (please complete the following information):
OS: any
Browser: any
Browser Version [e.g. 22]
Python Version: 2.7
GeoHealthCheck Version [master from oct 18, 2019.]
If running with Docker:
Docker installed version: n.a.
GeoHealthCheck Docker Image version: n.a.
Additional context
Problem seems to be easily solved in esrifs.py#L38: remove possibly existing/dangling 'X-Esri-Authorization' header first.
justb4
commented
5 years ago
Describe the bug
X-Esri-Authorizationheader is still sent after changingAuthorizationonESRI:FSResource from Bearer Token to Basic Auth. This leads toInvalid Tokenerror. First reported by @BenGunnewijk .To Reproduce Steps to reproduce the behavior, e.g.:
Testbuttoncode=498 message=Invalid TokenExpected Behavior Step 5 above should be
True(success) as Basic Auth should be accepted.Screenshots or Logfiles N.A.
Context (please complete the following information):
masterfrom oct 18, 2019.]If running with Docker:
Additional context Problem seems to be easily solved in esrifs.py#L38: remove possibly existing/dangling
'X-Esri-Authorization'header first.