Repository navigation
Replies: 2 comments 1 reply
|
Check this configuration in Admin project: |
1 reply
|
Done in 3.2.0 release. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
The frontend application's index page uses absolute paths when referencing dynamically generated/static assets (JavaScript, CSS, etc.).
This causes issues when the application is deployed under a subpath rather than at the root of the domain.
For example, asset references are generated as:
/assets/...
/assets/...
This is real code from index:
<title>Skoruba Duende IdentityServer Admin</title> <script type="module" crossorigin src="/assets/index-C2RZ8P2e.js"></script>instead of using paths relative to the application's configured base path.
As a result, when the application is hosted behind a reverse proxy or Kubernetes Ingress using a path prefix, the browser tries to load these resources from the domain root instead of the application's base path.
It would be helpful if asset URLs respected the configured base path or used relative paths, allowing the frontend to be deployed correctly under a subpath.
All reactions