SUPERSET_APP_ROOT is not applied on some internal redirects after login and in Settings > User > Info

[parkjeyeong]

Bug description

Environment

• Superset version: 6.0.0
• Deployment: docker-compose
• Configuration:
  • SUPERSET_APP_ROOT set via environment variable

Describe the bug

I configured SUPERSET_APP_ROOT in docker-compose.yml to run Superset under a sub-path.

Most routes work correctly and include the configured app root,
but some internal navigations ignore SUPERSET_APP_ROOT and redirect to root (/) paths.

Specifically:

• Redirect right after login (/superset/welcome)
• Navigation to Settings > User > Info
  Both cases drop the configured app root.

Expected behavior

All redirects and internal navigations should respect SUPERSET_APP_ROOT.

Examples:

/my-prefix/superset/welcome/
/my-prefix/user_info/

Actual behavior

Some redirects ignore SUPERSET_APP_ROOT and navigate to root paths.

Examples:

/superset/welcome/
/user_info/

Could you please confirm whether this is an intended behavior or a bug?
Thank you.

Screenshots/recordings

No response

Superset version

6.0.0

Python version

I don't know

Node version

18 or greater

Browser

Chrome

[dosubot]

Hi @parkjeyeong! I'm Dosu and I’m helping the superset team.

This is a known bug in Superset 6.0.0—internal redirects like the post-login redirect and navigation to Settings > User > Info do not consistently respect SUPERSET_APP_ROOT. The frontend routes for these pages are hardcoded to root-relative paths (e.g., /superset/welcome/, /user_info/) and do not dynamically prepend the app root, which causes the behavior you described. This is not intended and breaks sub-path deployments.

A fix for the login redirect was merged after 6.0.0 (PR #34395), and there are ongoing efforts to address similar issues for other routes and authentication flows (PR #35296, PR #33508). However, these fixes are not included in 6.0.0, so the issue persists in that version.

If you need a workaround before upgrading, you would need to manually patch the affected routes in your deployment to ensure they use the app root, but this can be tricky and may require changes in both frontend and backend code. Upgrading to a version where these fixes are merged is the most reliable solution once available.

Let me know if you want more technical details or guidance on patching locally.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[iammuntazirali]

Hi there 👋
I’d like to work on this issue.
Please assign it to me. Thanks!

[parkjeyeong]

@dosubot

Hi Dosu, thanks for the detailed explanation.

Just to clarify, do you know whether the remaining fixes (e.g. for Settings > User > Info and other internal routes not respecting SUPERSET_APP_ROOT) are planned to be included in a specific upcoming release version?

We’re currently evaluating whether to upgrade or apply a temporary patch, so having a rough target version or timeline would be very helpful.

Thanks again for the pointers to the related PRs.

[dosubot]

The remaining fixes for internal routes like Settings > User > Info not respecting SUPERSET_APP_ROOT are actively being addressed. The specific fix for the user info/settings menu is in PR #36058, which was updated in late January 2026 and is likely to land in the next minor or patch release after that date. This PR directly addresses the missing app root in the user info link and other related UI issues.

Recent merged PRs (like #35098) have improved subdirectory deployment support for many URLs, but some routes and authentication flows are still being patched. Superset’s release process means these fixes will appear in the next release after their merge—there’s no fixed date, but you can track their inclusion via the changelog or by watching the PRs.

If you need these fixes immediately, you’d need to patch your deployment with the changes from the relevant PRs. Otherwise, upgrading to the next release after these PRs are merged will resolve the issues for you.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}