-
-
Notifications
You must be signed in to change notification settings - Fork 231
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
Expired token sends wrong http status code 500 #268
Comments
Hi, is there a specific router where this occurs, in general Fusio should return a |
The reply from the server for an expired token is 500: { |
ok, I see this is a valid point, we should add a try catch around the JWT decode to return the fitting status code. |
I have just commited a fix for this issue s.: apioo/fusio-impl@a0be884 |
Thank you, glad it was an easy one for once! Have a great day |
When my application attempts to use the rest service with an expired token, the reply from fusio is http status 500(internal server error), when it should be 401 (unauthorized)
Edit, not that it should make a difference, but I do have development enabled instead of production
The text was updated successfully, but these errors were encountered: