You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "sfirke (via GitHub)" <gi...@apache.org> on 2023/07/07 16:47:50 UTC
[GitHub] [superset] sfirke commented on issue #24512: Superset on 443 port
sfirke commented on issue #24512:
URL: https://github.com/apache/superset/issues/24512#issuecomment-1625680176
Most people use an application gateway, load balancer, or reverse proxy to implement SSL / HTTPS and route traffic in via port 443. You could try asking this in the Superset Slack chat, but it seems like more of a general Docker question than a Superset bug or issue that needs the project's attention.
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org