Health monitors

suthomas1,

You should know that http Get happens after a successful 3 way handshake. So why would one simply add tcp monitor again, which is again a 3way handshake...

Well it depends on how you are assigning both the monitors to the pool. If you use

http or tcp

together, it could be because you are sure that tcp would work always and not sure of the content check monitor, whether the server team has built the path or not, often these happens during the migration works. You just don't want the pool to go down because the service is Up, but not the content check path, so you put tcp monitor, but along with that you also add http/https monitor to know if it really passes content check. In long run, you would be removing tcp and keeping http alone.

But if you do

http and tcp

it's really of no use.