TOKEN EXPIRED : 401 response code instead of 500 about cakephp-jwt-auth HOT 7 CLOSED

With debug on the 500 is expected since I am directly throwing the exception generated by Jwt::decode() for easy debugging. With debug off you will get a 401.

from cakephp-jwt-auth.

Are you checking with debug on or off? With debug off you should get a 401 response code.

from cakephp-jwt-auth.

the debug is on

from cakephp-jwt-auth.

Up to me 500 was not expected, and the message passed to the 401 was enough.
we may pass some more information about the original exception to the auth exception for debug issues

from cakephp-jwt-auth.

I now understand the reason that made you directly throwing the exception generated by Jwt::decode() when debug is on.
it is needed when you build this plugin and test it but not when someone using it in his project.

from cakephp-jwt-auth.

No it was not for plugin development, it's to make debugging easier for the app developer as Jwt::decode() can throw multiple types of exceptions. This behavior is similar to how for e.g. you would get a MissingController exception with debug on but that would be turned in into a NotFoundException with debug off.

I am not keen on changing this behavior. As I stated earlier with debug off you will always get an UnauthorizedException with 401 status code if authentication fails for any reason.

from cakephp-jwt-auth.

Ok
Then I will do it in my project :)

from cakephp-jwt-auth.