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

   ### Bug description
   
   Hi, I have a little issue using superset app root parameter.
   
   I'm using superset inside a container and it is available behind an nginx 
reverse proxy. My configuration seems ok because all resources are loaded 
except one, the main superset logo "superset-logo-horiz.png" is not resolved 
because the prefix is missing.
   
   I think there is the only resource with that, I compared with favicon and it 
was correctly loaded : 
   
   <img width="676" height="315" alt="Image" 
src="https://github.com/user-attachments/assets/c8942e0f-a455-400d-a467-a1166b8d2454";
 />
   
   <img width="655" height="286" alt="Image" 
src="https://github.com/user-attachments/assets/92fe2b16-058e-4b94-ad47-264a2e099540";
 />
   
   On the network tab in firefox I have juste an error on this resource, so I 
think it is bug, am I wrong ?
   
   Thanks.
   
   ### Screenshots/recordings
   
   _No response_
   
   ### Superset version
   
   master / latest-dev
   
   ### Python version
   
   3.9
   
   ### Node version
   
   18 or greater
   
   ### Browser
   
   Firefox
   
   ### 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