You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the logout page, the code is trying the change the url by using window.location.replace THEN window.location.href 250ms later.
The issue is when the url Hydra is redirecting to is a http 302 that redirects to another url, the window.location.href call makes the browser come back once again to the original redirect url, making the call 2 times (when the loading takes more than 250ms).
Reproducing the bug
Reproducing with hydra needs a lot of configuration, but I can demonstrate the bug in the code snippet:
functionredirect(){window.location.replace(redir);// In case replace failed try hrefsetTimeout(function(){window.location.href=redir;},250);// Show message after http-equiv="refresh"}
Go back to the network console, you'll notice the call to https://tinyurl.com/codingame-test-redirect has been done twice, will the first one has been cancelled
Relevant log output
No response
Relevant configuration
No response
Version
2.0.1
On which operating system are you observing this issue?
Linux
In which environment are you deploying?
Kubernetes with Helm
Additional Context
This behavior can be observed at least with latest Chrome and latest Firefox
The text was updated successfully, but these errors were encountered:
Preflight checklist
Describe the bug
In the logout page, the code is trying the change the url by using
window.location.replace
THENwindow.location.href
250ms later.The issue is when the url Hydra is redirecting to is a http 302 that redirects to another url, the
window.location.href
call makes the browser come back once again to the original redirect url, making the call 2 times (when the loading takes more than 250ms).Reproducing the bug
Reproducing with hydra needs a lot of configuration, but I can demonstrate the bug in the code snippet:
https://tinyurl.com/codingame-test-redirect
has been done twice, will the first one has been cancelledRelevant log output
No response
Relevant configuration
No response
Version
2.0.1
On which operating system are you observing this issue?
Linux
In which environment are you deploying?
Kubernetes with Helm
Additional Context
This behavior can be observed at least with latest Chrome and latest Firefox
The text was updated successfully, but these errors were encountered: