Forum Discussion
Cirrocumulushttps health monitor configured with only send strings but no receive strings - what it will check ?
A content check monitor with no receive string is relatively powerless to assess application delivery health. In the case of your HTTPS monitor, for example, the system will establish a secure connection to the pool member, send the HTTP 0.9 GET request you provided in the Send String, and any response - including a 404 Not Found or other HTTP 500 error - is considered a successful response and the monitor will mark the pool member as available. As such, your monitor is not much more effective than a service check monitor and certainly not (necessarily) indicative of application delivery health.
Conventional wisdom is to use an appropriate receive string in a content check monitor.
Cirrocumulusok so in that case the default https monitor in the F5 also not having receive string.So it's of no use right ? it is same as using tcp-443 monitor ? is that right .
