Open holandes22 opened 9 years ago
Apparently this is related to the token expiration time being too low. default is 5.
We can, for simplicity just disable the token refresh. Or live it, and the client needs to be clever enough to request a new token after expiration
After closing the tab, the session remains authenticated (meaning still stores the token), but opening a new tab (which uses that session) and browsing to something that sends a request to the backend, will produce a loading state that doesn't finish. We need to catch the server error in case of expired token