Skip to content
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

Do not clear redirect state if no actual redirect #689

Merged
merged 1 commit into from
Jun 10, 2022

Conversation

zorn-v
Copy link
Contributor

@zorn-v zorn-v commented Jun 10, 2022

If you open/refresh protected page with expired token (server return 401 on refresh user) there will be two redirects to auth page - one from http interceptor _processLogout (with default invalidToken method) and another from _processTransitionEach 401 handler.
Because of this redirect state will be cleared on second redirect and you can not return to protected page after login.

If you open/refresh protected page with expired token (server return 401 on refresh user) there will be two redirects to auth page - one from http interceptor `_processLogout` (with default `invalidToken` method) and another from `_processTransitionEach` 401 handler. 
Because of this redirect state will be cleared on second redirect and you can not return to protected page after login.
@websanova websanova merged commit fbd7a6f into websanova:master Jun 10, 2022
@websanova
Copy link
Owner

Alright, this is up on 4.1.13, thx!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants