On Fri, Oct 31, 2014 at 01:38:11PM +0100, Sebastian Fohler wrote:
> This is the option I've set in my backend pool:
>
> option ssl-hello-chk HEAD /rmo/login.rmo HTTP/1.0
>
> and the configuration is:
>
> apache[proxy]:443 -> jboss:8080 and if that fails apache shows a service
> is not available site which is at least in the browser a 503 error.
OK so :
1) this is not a valid configuration, as explained in the documentation,
ssl-hello-chk just sends SSL hello checks. You need "option httpchk"
to check a URL, no "ssl-hello-chk". If you want to check in HTTPS,
it's http over SSL so you need to have the "ssl" keyword on your
server line, or maybe just "check-ssl" if only the check is made in
ssl and the traffic doesn't need to be encrypted.
2) this is totally unrelated to "monitor".
Willy
