You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be great if we able correctly use Supervisord web interface behind proxy with HTTPS scheme. Currently Supervisord controls return Location header with HTTP scheme (which can be easily redirected to HTTPS). But if it resides inside iframe it's blocked by modern browsers (mixed content error).
Apparent solution seems to give more power to user for control of Location header through configuration settings (url parameter?) or use "X-Forwarded-Proto" or "X-Forwarded-Protocol" header as @fengsisuggested.
The text was updated successfully, but these errors were encountered:
It would be great if we able correctly use Supervisord web interface behind proxy with HTTPS scheme. Currently Supervisord controls return Location header with HTTP scheme (which can be easily redirected to HTTPS). But if it resides inside iframe it's blocked by modern browsers (mixed content error).
Apparent solution seems to give more power to user for control of Location header through configuration settings (url parameter?) or use "X-Forwarded-Proto" or "X-Forwarded-Protocol" header as @fengsi suggested.
The text was updated successfully, but these errors were encountered: