New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OAuth1Authenticator does not encode ConsumerKey in the authorization header #1654
Comments
If you made it work, please submit a PR to fix it. |
The way I got it working is a bit of a hack. I don't have the time right now to dive into the source code and submit a proper fix. Maybe during the Christmas break, but I can't promise anything. |
Please note that |
I think v107 latest preview should work. I added encoding to the consumer key, which wasn't there before. |
I am now not even sure it's a valid issue. Header values normally aren't encoded. When I started to encode header values by default, lots of things got broken. Nevertheless, it doesn't seem to be important enough as there's no follow up. |
Read this first!
Important
invalid
and closed in three days.Expected Behavior
Actual Behavior
Steps to Reproduce the Problem
I have been able to get around this problem by doing the following:
Specifications
StackTrace
The text was updated successfully, but these errors were encountered: