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

Chris1269_13050's avatar
Chris1269_13050
Icon for Nimbostratus rankNimbostratus
Nov 18, 2013

HTTP Health Monitor Receive String issue

I am currently having an issue with the Receive string part or a HTTP health monitor. I am using a GET request like: GET /default.aspx HTTP/1.1\r\nHost: myurl.com\r\n   I am also using authenticat...
health monitoring
management
Chris1269_13050's avatar
Chris1269_13050
Icon for Nimbostratus rankNimbostratus
Nov 28, 2013

Thanks, this issue has now been resolved. I needed to add User-Agent to the request.

 

Gerlan_32355's avatar
Gerlan_32355
Icon for Altostratus rankAltostratus
Dec 09, 2015
I inserted the User-Agent on request and worked well, too! Thanks for help! Follow the example of request: GET /system1/ HTTP/1.1\r\nHost: host1.mydomain.com\r\nUser-Agent: Mozilla/4.0 (Compatible; MSIE 6.0; Windows NT 5.0; T312461)\r\nConnection: Close\r\n\r\n Receive string: SystemOK
  • Aaron_F's avatar
    Aaron_F
    Icon for Nimbostratus rankNimbostratus
    Jul 30, 2019

    Ran into new use for this information. New Tomcat server deployments are returning HTTP 200 responses when sending CURL requests from the F5, but when using a basic HTTP health monitor, it was getting HTTP 500 response, resulting in failed health check. Turns out that new Tomcat web server versions are requiring User-Agent: be defined in the health monitor call from the F5 to the tomcat web servers running new software.