Hi,
Thank you, this resolved it. We upgraded all Volo.* packages (including LeptonX) to 10.6.1, moved UsePathBase to Program.cs before InitializeApplicationAsync as you advised, and removed our HTML URL rewrite and the middleware-order workaround.
Admin Console now works under a path base on both our dev and test environments (each environment is served under its own path base on a single origin): the shell loads with the correct base href, the SPA router and API base follow the path base, OIDC sign-in works with our existing RootUrl and redirect URIs, and the account pages (including /gdpr) open as expected. No extra Admin Console setting was needed.
Thanks also for pointing to the related question. Please feel free to close this ticket. If we notice anything else under a path base we will open a new one.
Best regards
Additional information:
Observed behaviour at https://example.com/dev/svc/admin-console: the page loads (assets are served after we fixed middleware order and rewrote root-relative HTML URLs), but the SPA redirects the browser to https://example.com/admin-console/dev/svc/admin-console and shows "404 Page not found". The sidebar Home link points to https://example.com/admin-console/. This matches the router basepath being hard-coded to '/admin-console' in main-*.js. Our OpenIddict client redirect URIs (seeded from AdminConsole RootUrl) are https://example.com/dev/svc/admin-console/ and .../silent-renew.html.
Thanks, Juari
Hi Team,
We host an ABP 10.6 (Modern Apps) host app behind a reverse proxy under a path base (e.g. https://example.com/test/svc, using UsePathBase). Volo.Abp.AdminConsole works at /admin-console without a path base, but under a path base the SPA's router has basepath hard-coded to '/admin-console' (main-*.js), and the HTML contains root-relative asset URLs (/admin-console/assets/..., /theme-override.css). We worked around the middleware order and the HTML URLs, but the SPA router still shows "Page not found" and redirects outside the path base. Is there an official, supported way to run Admin Console under a path base (a configuration option, a build-time base setting, or a recommended hosting model)? If not, what is the recommended approach for hosting several environments on one origin?
Thanks, Juari
