HTTP monitor with HEAD, not GET

This really isn't a monitor issue, and I always recommend that you add a connection: close, which will notify your web server to close this socket down and be prepared to accept another client request as opposed to maintaining a keep-alive connection (and occupying a socket that could happily service requests) to the LTM even though it won't be re-used.

 

 

TIME_WAIT status is an artifact of the web server's TCP/IP stack and is common. For single-purposed systems - i.e. a web or app server that does a single task, serving HTTP/S pages - it's common to tune the TIME_WAIT_REUSE and TIME_WAIT_RECYCLE timers on the server's OS to help minimize sockets sitting in this state. I don't know how to do this in Windows, but I'm sure some of the good folks out there will be able to chime in...

 

 

-Matt