-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
When apikey is missing or it's wrong 500 returned instead of 401 in 0.10.1 #2385
Comments
what's in the logs? |
Sorry, here are the logs, I just removed the key itself and the host name we are using: 2017/04/13 10:10:11 [error] 30754#0: *297 lua entry thread aborted: runtime error: /usr/local/share/lua/5.1/kong/tools/database_cache.lua:223: attempt to conca |
Sounds like this was handled in #2313? Unfortunately that fix hasn't been published yet, and likely won't for a while... :( |
The same is happening in my environment when the oauth2 authorization token is expired or missing: |
this has been fixed, released on 0.11 |
Summary
After upgrading to 0.10.1, when the apikey is missing (we are using key-auth plugin) or it's wrong, 500 is returned with plain/text message body: "An unexpected error occurred" instead of 401 with json:
{
"message": "No API key found in headers or querystring"
}
Steps To Reproduce
Additional Details & Logs
The text was updated successfully, but these errors were encountered: