The ArgoCD UI replaces the browser history to navigate to /login?return_url=... without reloading the page. This behaviour is causing issues for us since we want to rewrite the /login location to /auth/login in our ingress controller. It would help immensely if the history.push was replaced by a window.location.href here: https://github.com/argoproj/argo-cd/blob/master/ui/src/app/app.tsx#L270
Not sure if this should be a feature request or a bug.
To Reproduce
Navigate to the / location of the ArgoCD UI and notice that the browser location has been updated to /login?return_url=... without a page reload. Checking the ingress controller logs shows that no calls were made to argocd-server.
Expected behavior
Ideally this should trigger a page reload to /login?return_url=... instead of just manipulating the browser history.
Checklist:
argocd version
.Describe the bug
The ArgoCD UI replaces the browser history to navigate to
/login?return_url=...
without reloading the page. This behaviour is causing issues for us since we want to rewrite the/login
location to/auth/login
in our ingress controller. It would help immensely if thehistory.push
was replaced by awindow.location.href
here: https://github.com/argoproj/argo-cd/blob/master/ui/src/app/app.tsx#L270Not sure if this should be a feature request or a bug.
To Reproduce
Navigate to the
/
location of the ArgoCD UI and notice that the browser location has been updated to/login?return_url=...
without a page reload. Checking the ingress controller logs shows that no calls were made to argocd-server.Expected behavior
Ideally this should trigger a page reload to
/login?return_url=...
instead of just manipulating the browser history.Screenshots
N/A
Version
N/A