HTTP Monitor in 10.2

In 10.2, F5 has nicely gone back to not appending CRLF's to the send string, so you'd want to include the \r\n's yourself. It's always good to specify a connection: close header so the server knows LTM isn't planning on trying to reuse the TCP connection. You could try something like this to start with:

 

 

GET /monitor.html HTTP/1.1\r\nHost: \r\nConnection: Close\r\n\r\n

 

 

For the receive string, ideally you check for a string found only in the first 5120 bytes of a successful response. Or you could look for any HTTP 2xx or HTTP 3xx response:

 

 

HTTP/1\.(0|1) (2|3)

 

 

 

https://support.f5.com/kb/en-us/products/big-ip_ltm/releasenotes/product/relnote_10_2_0_ltm.html

 

 

LTM http, https, tcp monitors with non-empty send string need \r\n specified (CR135548-1)

 

When you create a new TCP, HTTP, or HTTPS monitor in version 10.2.0, you must include \r\n at the end of a non-empty Send String, for example GET /\r\n instead of GET /. If you do not include \r\n at the end of the Send String, the TCP, HTTP, or HTTPS monitor fails.

 

 

 

Aaron