This will simply return the user to the login page and display a message once he gets an unauthorized response regardless of context.
The drawback here is that if there is a minor bug and the user gets an unauthorized response, he/she can be logged out even if the token is still valid.
I suggest we use http 440 for this. both on the backend for notification and the frontend for case distinction.
Fixes #92
This will simply return the user to the login page and display a message once he gets an unauthorized response regardless of context.
The drawback here is that if there is a minor bug and the user gets an unauthorized response, he/she can be logged out even if the token is still valid.
I suggest we use http 440 for this. both on the backend for notification and the frontend for case distinction.