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

J_W__Koebel_442's avatar
J_W__Koebel_442
Icon for Nimbostratus rankNimbostratus
Dec 09, 2009

Monitors Won't Check HTTP Status Code

Hi everyone,     I'm trying to revise our currently lacking health monitors to keep better track of the status of each node. We run JBoss servlets on top of Tomcat to serve up a web app...
management
monitoring
hoolio's avatar
hoolio
Icon for Cirrostratus rankCirrostratus
Dec 10, 2009
I'd also guess it's the \r\n's on the end of the send string causing the app to send a 400 response back to the client. You could confirm this by checking the web server logs or running a tcpdump on LTM filtering for the static self IP and pool member IP.

 

 

You can use a receive string like this to check for an HTTP 1.0 or HTTP 1.1 200 OK response:

 

 

HTTP/1\.(0|1) 200 OK

 

 

Or more simply, '200 OK' will usually do fine. 200 on its own will match the year in the Date header (or the Last-Modified header.

 

 

Aaron