J'ai regardé attentivement la configuration ( pour Apache) donné par le dev pour M/monit.
Another option is to use a sub-domain rather than a sub-path. In this case, access to M/Monit will go via an URL that looks like,
https://mmonit.proxy.address/ In this example, the HTTP proxy server will also be using https, but M/Monit will continue to use http.
This setup requires that the proxyScheme attribute in M/Monit’s Connector is set to https even though the Connector itself is using
http. The reason is that redirects from M/Monit must use the https scheme to match the proxy server’s scheme.
<Connector port="8080" proxyScheme=”https” ... />
Apache configuration for https://mmonit.proxy.address rather than https://proxy.address/mmonit/ will be something like:
<VirtualHost *:443>
ServerName mmonit.proxy.address:443
ProxyPass / http://192.168.1.10:8080/
ProxyPassReverse / http://192.168.1.10:8080/
SSL & other config..
</VirtualHost>
You may also prefer the hostname and port number to reflect that specified in the original request, not the one on which M/Monit itself
is listening. This can be achieved by using the proxyName and proxyPort attributes in the <Connector> element. Please note that
these proxy attributes should not be used when setting up a sub-path proxy. In practice, when using a sub-domain, you should
configure the <Connector> element in server.xml, with the following proxy settings:
<Connector port="8080" proxyScheme=”https” proxyName="proxy.address" proxyPort="443" ... />
This will cause M/Monit to pretend that all proxied requests were directed to https://mmonit.proxy.address on port 443. This is
particularly useful when M/Monit performs redirects from the login page or other pages inside its web-app. Otherwise these redirects
will contain the hostname and port number of M/Monit. It is valid to omit the proxyName attribute from the <Connector> element. If
you do so, the value used in URLs emitted by M/Monit will be the host name on which M/Monit is running. In the example above, it
would be localhost.
