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

Ricardo_77091's avatar
Ricardo_77091
Icon for Nimbostratus rankNimbostratus
Mar 26, 2009

HTTP Monitor that follows redirects

We are trying to configure an HTTP monitor to monitor a .NET application and mark the member as down if it does not receive the response it expects. The problem is that the first response is a 401 Una...
management
monitoring
STP_88362's avatar
STP_88362
Icon for Nimbostratus rankNimbostratus
Jun 10, 2009
I'm having a similar problem with an external monitor using the script and NTLM. From an SSH login to the LTM I'm able to input my command and watch the "200 OK" response come up after the initial "401 Unauthorized" happens -- the LTM just tries a second time and is successful.

 

My command is like this:

 

curl --ntlm -k -v -u 'MYDOMAIN\USER:' http://SERVER-FQDN/pages/default.aspx -H "Host: SERVER"

 

I had to put the "--ntlm" as just "-ntlm" would keep trying to send the authentication in basic instead.

 

When I used the script, I modified the "HTTP Monitor_c URL_ GET With Host Specific Headers" script with the IP and host name in my situation, and subbed in the curl NTLM command but left the grep portion as written. I added the URI portion and RECV portion to the monitor via the GUI. As soon as I have the RECV portion filled in, the node is marked as down. I end up with the same result no matter if I use the IP of the site or the FQDN.

 

I feel like I'm close to having things work, but would love any input! This is my first stab at an external monitor with NTLM, so it's been a learning experience.

 

Thanks much --

 

Sam