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

john4665f5's avatar
john4665f5
Icon for Nimbostratus rankNimbostratus
Apr 26, 2016

Default HTTP/HTTPS monitor acceptable HTTP status codes?

Hello,   I've been digging through F5's LTM documentation, but I am not able to find anything solid on the default acceptable HTTP/HTTPS monitor status codes. What is the LTM expecting back using ...
application delivery
LTM
Theo_12742's avatar
Theo_12742
Icon for Cirrus rankCirrus
Apr 26, 2016

While it's not well documented, the HTTP monitor will accept any response (including 302's). However, you can control this behavior by using RegEx in the Receive String. For example, I use the following (and use HTTP >= 1.0):

 

^HTTP.1\.[0|1]\s([2|3][0-9][0-9])

Which marks the monitor as up for any HTTP code 200-399.

 

john4665f5's avatar
john4665f5
Icon for Nimbostratus rankNimbostratus
Apr 26, 2016
Hello Theo, Thank you for the response. I've tested a 302 response and the node was marked down, but a 301 works just fine. I didn't get a chance to look further into like the bigd debugs, but I wonder if it was because the response was "302 Found" instead of a typical 302 temporary redirect. Just to clarify the reason for this question is not how to make the node available, I can modify the send/recv strings in a child monitor to pass the host header, 302, etc. and mark it up, but just curious as to what the default expected responses are. Thank you, John