HTTP monitor with HEAD, not GET

FWIW I consider this to be a best practice: tuning your server stack for a specific workload.

 

 

There's no work-around to TIME_WAIT from the BigIP standpoint really; the server's stack is going to do what it's configured to do. Most of the time they're setup in a general way to try and accommodate the majority of use cases. If you've got a specific task a farm of servers will be performing, tune your stack in the optimal way for this workload.

 

 

To me, it's sort of the same the same as tuning BigIP's tcp profiles for a specific virtual server. It just happens to be a little more difficult to do, and it locks you into a set of server-wide behaviors TCP/IP wise.

 

 

From the workload standpoint, in the case of web servers, TIME_WAIT is a prime candidate for tuning (downward, in almost every case). Thanks for sharing the information above; as a *NIX ish type guy I had no clue how to do this on windows. This will be of great value.

 

 

-Matt