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

UI fails to load when navigating directly to a page more than one directory deep #1081

Closed
wyattanderson opened this issue Jan 26, 2023 · 0 comments · Fixed by #1083
Closed
Labels
bug Something isn't working

Comments

@wyattanderson
Copy link
Contributor

Describe the bug

As far as I can tell, starting with 2.10.0, assets in the returned HTML are requested from ./_app instead of /_app. When a user navigates directly to a route that is more than one directory deep, the assets fail to load because the browser requests them relative to the page URL.

For instance, if a user clicks an external link like http://localhost:8080/namespaces/default/workflows or refreshes the browser while on this page, the browser tries to request assets from http://localhost:8080/namespaces/default/_app/immutable/start-ca935cf5.js instead of http://localhost:8080/_app/immutable/start-ca935cf5.js, and the page never loads.

To Reproduce
Steps to reproduce the behavior:

  1. Start a local cluster with docker-compose up
  2. Navigate to http://localhost:8080/, which the app will rewrite to http://localhost:8080/namespaces/default/workflows
  3. Refresh the page
  4. The page fails to load
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant