Forum Discussion

Luca_55898's avatar
Luca_55898
Icon for Nimbostratus rankNimbostratus
Jan 31, 2012

Can't get custom HTTP monitor to work

I have a website which runs on a URL similar to the one below:

 

 

https://mydomain.com/support/display/SPT/Home

 

 

So i have i custom HTTP monitor configured like this:

 

 

GET /support/display/SPT/Home HTTP/1.1\r\nHost: mydomain.com\r\nConnection: Close\r\n\r\n

 

 

And i have the return string configured to be a single word which is displayed multiple times on the page.

 

 

When i have the return string entered the monitor marks the page down. When there is no return string entered the monitor marks it up.

 

 

Any thoughts on why it can't seem to identify the return string?

 

  • are you able to see the return string when using telnet to pool member from bigip?

     

     

    e.g.

     

    telnet x.x.x.x 80

     

    GET /support/display/SPT/Home HTTP/1.1

     

    Host: mydomain.com

     

    Connection: Close

     

     

    additionally, there is content length limit in http/https health monitor.

     

     

    sol3451: Content length limits for HTTP and HTTPS health monitors

     

    http://support.f5.com/kb/en-us/solutions/public/3000/400/sol3451.html
  • Yes i can i can see the return string when i telnet straight to the pool member.

     

    Its in the pool on port 8080 though. Do i need to modify the monitor to use 8080?

     

     

    Im just checking for a single word, which is 'cloud' (no quotes)

     

  • Do i need to modify the monitor to use 8080?i do not think so since health monitor will connect to pool member port.

     

     

    have you tried bigd debug and tcpdump?

     

     

    Troubleshooting Ltm Monitors by Aaron

     

    http://devcentral.f5.com/wiki/AdvDesignConfig.TroubleshootingLtmMonitors.ashx
  • additionally, there is content length limit in http/https health monitor.

     

     

    sol3451: Content length limits for HTTP and HTTPS health monitors

     

    http://support.f5.com/kb/en-us/solutions/public/3000/400/sol3451.html

     

    Ah it was this. I changed the return string to something right at the top of the page and it worked.

     

     

    Cheers.