Optimize handling of occasional 401s #224
Replies: 4 comments 1 reply
-
It might be dangerous to cut the session invalidation completely. |
Beta Was this translation helpful? Give feedback.
-
@oliverrahner coming back to the token refresh topic. There is a strange behavior of the VW servers with the token refresh. Every hour we have to refresh the token and now it's done using the refresh token function. Here is an example...
First request after token refresh with the new token:
A second request with the new token (unauthorized):
And as the result, full relogin:
It's a persistent issue and easy to reproduce. Only need to wait one hour. :) Btw... one more interesting thing... the refreshed token and the token after an unauthorized error is the same token. |
Beta Was this translation helpful? Give feedback.
-
I guess we can close this for now |
Beta Was this translation helpful? Give feedback.
-
Currently, the reaction to any 401 error received from the API leads an invalidation of the current session, which in turns leads to a login.
In my own tests, I have seen 401s occasionally appear and disappear again, without re-login or even refreshing tokens.
Question: should we remove that session invalidation completely?
Beta Was this translation helpful? Give feedback.
All reactions