https_url possible also if built-in web server is not used?

[IzzySoft]

Could we have an equivalent to the built-in web server's https_url keyword for use without the built-in server? Could be a simple yes/no switch like "force_ssl_links" – or something more sophisticated like "force_ssl_links_proxies" (accepting a list of remote IPs to enable this for).

Background: Monitorix running on a firewalled server. HTTP access is given via Squid from the DMZ host. Squid is addressed via HTTPS, but pulls from the "unexposed server" via HTTP. Result: Mixed content, as Monitorix thinks it's an HTTP access – while the client (browser) expects HTTPS content.

[mikaku]

@IzzySoft,

I'm unable to reproduce your scenario here, so I'm afraid you'll have to test it on your own.

So, can you please, add the global option https_url = y and then change the line https://github.com/mikaku/Monitorix/blob/master/monitorix.cgi#L262 by:

$config{url} = ($ENV{HTTPS} || ($config{https_url} || "n") eq "y") ? "https://" . $ENV{HTTP_HOST} : "http://" . $ENV{HTTP_HOST};

and see if it works for you (without breaking any other configurations)? Thanks.

[IzzySoft]

I'll have to postpone this a little due to lack of time for proper testing, sorry. Currently running 25h days …