remove Authorization header from the redirect call #5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This workaround fixes the flacking error 400 on API is observed last weeks: 'Authentication information is not given in the correct format. Check the value of Authorization header.'
I've discovered with Fiddler it is getting the correct 302 response to the 1st call when the token is validated but on the 2nd call it fails with the error mentioned above.
There are a few of the mentions of this bug last days:
I found the difference between performing the calls from different HTTP client like Postman and CURL. Some of them are not propagating the headers on redirect.
So, the idea of the fix is to disable auto-redirect and on the second call to remove the Authorization header explicitly.
The similar problem and solution is described here: