Forum Discussion

Brian_Mayer_841's avatar
Brian_Mayer_841
Icon for Nimbostratus rankNimbostratus
Jan 20, 2012

Having some trouble creating a health monitor for our OWA through ISA site

I have tried all sorts of combinations of GET requests and HTTP header fields, but I flat out cannot get a health monitor to successfully run against our OWA webmail servers. I should note that only tcp/443 is active, and that all traffic is proxied through two separate ISA servers. Each ISA server is a pool member (IP:443), and so I'm just sending an HTTPS monitor with Basic authentication details in the monitor.

 

 

Have any of you every successfully setup one of these types of monitors (essentially OWA though ISA over SSL)?

 

 

 

Thank you!

 

B

 

microsoft
partner

11 Replies

Sort By
Show More
  • Daniel_55334's avatar
    Daniel_55334
    Icon for Altostratus rankAltostratus
    Feb 24, 2012
    I hit the exact same problem recently. The curl command successfully get legitimate response after basic authentication. However the monitor just failed. F5 support sees in the debug that the server just replies 400 bad request. It turns out to have the send string configured as below and it works.

     

    "GET /owa/ HTTP/1.1\r\nUser-Agent: curl/7.15.5 (i686-redhat-linux-gnu) libcurl/7.15.5 OpenSSL/0.9.8b zlib/1.2.3 libidn/0.6.5\r\nHost: 10.1.1.1\r\nAccept: */*"