-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[ML] Link to ml app goes through several redirects before getting to app #105254
Comments
Pinging @elastic/ml-ui (:ml) |
I've been unable to reproduce the first scenario in this issue. |
Thanks for checking @jgowdyelastic. If I can repro it I'll try to better capture the circumstances. As it stands, I can't repeat that behavior today 🤷♂️. Maybe scenario 2 will be the only real takeaway from this issue, which thankfully isn't too critical. |
Actually @jgowdyelastic wrt the 1st scenario, I got it again while running tests in Firefox. I tested it in parallel in Chrome and it worked fine even though I saw the error in Chrome before when I first reported this. It might be worth a local test in Firefox if you get a chance. I got the following output in Firefox's console:
So it gets stuck in a redirect loop going from Anyway, curious to see if you see it in Firefox. If not, we can just consider it logged and see if anyone else sees something similar down the road! |
@aaronjcaldwell thanks for the additional information, i'm still not able to reproduce on master or 7.14 when using Firefox. |
@jgowdyelastic Yes, can confirm I was using a basic license in all attempts. |
Unable to reproduce this on 7.15.0 (local install). Tried using basic and trial license, on Chrome and Firefox. Removing |
Closing this one, redirect issues were addressed in #139279 |
Kibana version:
7.14
Describe the bug:
Clicking on the ML app link sometimes goes through several redirects before landing on a blank page, but not always. Sometimes it gets the app correctly but a user still can't navigate back correctly (maybe a redirect that should replace instead of adding to history?). Seems like there might be a race condition (not entirely sure how to consistently trigger) but also minimally some router behavior that could be tweaked.
Steps to reproduce:
Screenshots (if relevant):
First scenario:
Second scenario:
The text was updated successfully, but these errors were encountered: