Health Check Question

Hi Greg,

 

 

Most webservers will respond to a request with an HTTP host header and no value. The Connection: close header tells the server that the client won't try to re-use the TCP connection, so the server can close the connection after responding to the request.

 

 

Rather than worrying about the monitor configuration, I'd focus first on finding a page you can make a request to where the server doesn't generate a session. If that's possible, you could use a standard HTTP monitor with a customized send string. If that's not possible, then you could figure out how to make a request which tells the server to kill the session. That would probably take two requests and require using an external monitor which references a shell script using curl. There are examples of using curl from a shell script for an external monitor in the monitoring Codeshare (Click here).

 

 

Aaron