dosubot[bot] commented on issue #37518:
URL: https://github.com/apache/superset/issues/37518#issuecomment-3809977079

   <!-- Greeting -->
   Hi @parkjeyeong! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the 
superset team.
   
   <!-- Answer -->
   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](https://github.com/apache/superset/pull/34395)), and there are ongoing 
efforts to address similar issues for other routes and authentication flows 
([PR #35296](https://github.com/apache/superset/pull/35296), [PR 
#33508](https://github.com/apache/superset/pull/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.
   
   
   <!-- Dosu Comment Footer -->
   *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).*
   
   ---
   <sup>How did I do? 
[Good](https://app.dosu.dev/response-feedback/53692480-deba-4ab9-b9d2-ee433324981b?feedback_type=great_response)
 | 
[Irrelevant](https://app.dosu.dev/response-feedback/53692480-deba-4ab9-b9d2-ee433324981b?feedback_type=irrelevant_answer)
 | 
[Incorrect](https://app.dosu.dev/response-feedback/53692480-deba-4ab9-b9d2-ee433324981b?feedback_type=incorrect_sources)
 | 
[Verbose](https://app.dosu.dev/response-feedback/53692480-deba-4ab9-b9d2-ee433324981b?feedback_type=too_verbose)
 | 
[Hallucination](https://app.dosu.dev/response-feedback/53692480-deba-4ab9-b9d2-ee433324981b?feedback_type=hallucination)
 | [Report 
🐛](https://app.dosu.dev/response-feedback/53692480-deba-4ab9-b9d2-ee433324981b?feedback_type=bug_report)
 | 
[Other](https://app.dosu.dev/response-feedback/53692480-deba-4ab9-b9d2-ee433324981b?feedback_type=other)</sup>
   
   [![Chat with 
Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github)&nbsp;[![Open
 in 
Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=This%20is%20a%20known%20bug%20in%20Superset%206.0.0%E2%80%94internal%20redirects%20like%20the%20post-login%20redirect%20and%20navigation%20to%20Settings%20%3E%20User%20%3E%20Info%20do%20not%20consistently%20respect%20SUPERSET_APP_ROOT.%20The%20frontend%20routes%20for%20these%20pages%20are%20hardcoded%20to%20root-relative%20paths%20%28e.g.%2C%20/superset/welcome/%2C%20/user_info/%29%20and%20do%20not%20dynamically%20prepend%20the%20app%20root%2C%20which%20causes%20the%20behavior%20you%20described.%20This%20is%20not%20intended%20and%20breaks%20sub-path%20deployments.%0A%0AA%20fix%20for%20the%20login%20redirect%20was%20merged%20after%206.0.0%20%28%5BPR%20%2334395%5D%28https%3A//github.com/apache/superset/pull/34395%29%29%2C%20and%20there%20are%20ongoin
 
g%20efforts%20to%20address%20similar%20issues%20for%20other%20routes%20and%20authentication%20flows%20%28%5BPR%20%2335296%5D%28https%3A//github.com/apache/superset/pull/35296%29%2C%20%5BPR%20%2333508%5D%28https%3A//github.com/apache/superset/pull/33508%29%29.%20However%2C%20these%20fixes%20are%20not%20included%20in%206.0.0%2C%20so%20the%20issue%20persists%20in%20that%20version.%0A%0AIf%20you%20need%20a%20workaround%20before%20upgrading%2C%20you%20would%20need%20to%20manually%20patch%20the%20affected%20routes%20in%20your%20deployment%20to%20ensure%20they%20use%20the%20app%20root%2C%20but%20this%20can%20be%20tricky%20and%20may%20require%20changes%20in%20both%20frontend%20and%20backend%20code.%20Upgrading%20to%20a%20version%20where%20these%20fixes%20are%20merged%20is%20the%20most%20reliable%20solution%20once%20available.%0A%0ALet%20me%20know%20if%20you%20want%20more%20technical%20details%20or%20guidance%20on%20patching%20locally.)&nbsp;[![Join
 Discord](https://img.shields.io/badge/join
 
-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share
 on 
X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/issues/37518)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to