Skip to content

Possible Authorization header bug in v2.16.4 #959

Closed
@danversjflett

Description

@danversjflett

Hi. I've just updated Resty in my project to v2.16.4.

We use bearer token authorization headers in our project.
We set up the Resty client using:
SetAuthScheme("Bearer").SetAuthToken(token)

This has worked for us up to v2.16.3.

Now we are getting Status Code 401 Unauthorized from the API. I can set a breakpoint and debug the code after the response is received - I see that the Resty client has the "Token" field set to the token we give it, but in the request the "Authorization" Header is not set at all.

In previous versions, the "Authorization" Header in a request made by the client is set to "Bearer [token]".

Metadata

Metadata

Assignees

Labels

bugv2For resty v2

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions