Forum Discussion
Brian_Mayer_841
Nimbostratus
Jan 20, 2012Having 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 ...
hoolio
Cirrostratus
Jan 31, 2012I'm not sure why you're getting a 401. One thing to note that I forgot is that if you're using the username and password fields on the monitor, you should terminate the send string with one \r\n as the monitoring daemon appends the Authorization header after the send string along with two \r\n's to terminate the request.
I just tested on 10.2.1 with our OWA server. This example worked:
GET /owa/auth/logon.aspx HTTP/1.1\r\nAuthorization: Basic dXNlcm5hbWU6cGFzc3dvcmQ=\r\nUser-Agent: LTM-Monitor\r\nHost: owa.example.com\r\nAccept: */*\r\n\r\n
Instead of setting the user/pass in the monitor fields, I just base64 encoded them manually and set that in the Authorization header. Can you give something like this a try?
Aaron
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects