parkjeyeong opened a new issue, #37518:
URL: https://github.com/apache/superset/issues/37518

   ### 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
   
   ### Additional context
   
   _No response_
   
   ### Checklist
   
   - [x] I have searched Superset docs and Slack and didn't find a solution to 
my problem.
   - [x] I have searched the GitHub issue tracker and didn't find a similar bug 
report.
   - [x] I have checked Superset's logs for errors and if I found a relevant 
Python stacktrace, I included it here as text in the "additional context" 
section.


-- 
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