For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

astokes_6920's avatar
astokes_6920
Icon for Nimbostratus rankNimbostratus
Nov 10, 2009

HTTP monitor with HEAD, not GET

While using the following monitor, I'm finding that the web servers are keeping TCP sessions in the TIME_WAIT state, rather than closing them outright.     GET /serverin.html HTTP/1.1\r\nCo...
management
monitoring
astokes_6920's avatar
astokes_6920
Icon for Nimbostratus rankNimbostratus
Nov 13, 2009
I did get output from an ethereal packet capture.

 

 

The "close\r\n" is included in both the HTTP header request from the LTM and the response from the IIS server. It's obvious however that the IIS box isn't doing what it "agreed" to do and closing the connection outright. Still leaving over 3000 connections in time_wait.

 

 

Does anyone else have this issue using the built in http monitor template? I'm inclined to ask for help with an advanced monitor, but don't really see where that would help as I believe I have evidence in hand that it's an IIS issue.

 

 

But I certainly can't be the only one experiencing this? Or, are hundreds, if not thousands, of time_wait connections to be expected between LTM and IIS?