For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Brian_Kenworthy's avatar
Brian_Kenworthy
Icon for Nimbostratus rankNimbostratus
Oct 11, 2007

HTTPS Monitor Help

Hi all.     I have a web application listening on for SSL connections on a high port, 8000. I would like to setup a health monitor to send a GET request to a uri /webservices/mylistener, so I h...
management
monitoring
wuench_99164's avatar
wuench_99164
Icon for Altocumulus rankAltocumulus
Aug 29, 2013

I have run into similar issues with Mule, it seems to have extensive logging on by default, and is therefore very picky about the transactions it looks for. I tried a generic TCP monitor and generic HTTPS montior. While they may work for the F5 they fill the mule logs. You will need to setup a URL to hit (/testmule below) as Mule doesn't like a GET to root. And we also added accept and user agent headers. Not sure if both are required. I didn't add a host header as I wanted to keep the monitor standard for all of our Mule deployments. The connection close may also be a good idea, but I didn't test it.

Here is the monitor I used:

monitor https_Mule {
   defaults from https
   send "GET /TestMule HTTP/1.1\r\nUser-Agent: F5LTM\r\nAccept: */*\r\n\r\n"
}