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
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.
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 fromhttp://localhost:8080/namespaces/default/_app/immutable/start-ca935cf5.js
instead ofhttp://localhost:8080/_app/immutable/start-ca935cf5.js
, and the page never loads.To Reproduce
Steps to reproduce the behavior:
docker-compose up
The text was updated successfully, but these errors were encountered: