-
-
Notifications
You must be signed in to change notification settings - Fork 115
Retry request in interceptors response #170
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
Labels
Comments
@nkovacic does this help at all? |
It could work this way, but currently opted for the client side check for token expiration, because currently its the only ways to do this in one place. |
I will try to get this implemented as soon as I can! |
This feature is coming very soon! See this PR |
Great, thank you for your effort 👍 |
27 tasks
@nkovacic This feature is implemented in |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Usually servers handles token expiration and then with 401 response tells the client to refresh token.
In the examples this is handled in request interceptor, but is there a way to handle it response and retry all failed requests?
The text was updated successfully, but these errors were encountered: