Forum Discussion
Daniel_55334
Feb 24, 2012Altostratus
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: */*"