-
Notifications
You must be signed in to change notification settings - Fork 443
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
Catch expired token throwing error #198
Comments
Same here. |
To catch errors in a specific middleware like
|
@hobofan this may be a dumb question, but how do you error out from there? Basically I was to say if unauthorized return a 403. If I'm not in the callback I can just throw an HttpException but as soon as I'm in my secondary middleware it doesn't work - it throws for the application but is not handled and the request is simply canceled. Edit: scratch that! It was as simple as |
Running into the issue where expired token (using credentialsRequired false) is throwing error, and I want to redirect instead. What is the current correct way to handle this?
The text was updated successfully, but these errors were encountered: