-
Notifications
You must be signed in to change notification settings - Fork 19
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
Unauthorized (401) response not processed correctly #188
Comments
This is related to Nakadi's zalando/nakadi#645 - the server returns the wrong structure and the wrong response code for certain auth failures (the line you referenced is a client workaround). Do you have an example request of a bad response structure returned with a 401? |
There's a workaround in 0.8.6. It's be great if you could go upstream and comment on or like zalando/nakadi#645. Having to patch around what should be a simple server fix in api clients is unfortunate. |
Actually, it suffices for me to not provide an access token and I get a 401 response. |
Did you solve this problem?? |
The
Problem
created for the response below doesn't contain enough information to understandPerhaps the line
should accommodate for 401 as well
The text was updated successfully, but these errors were encountered: