Help with External HTTP Monitor (cURL) - Requires http authentication

It might be an interesting exercise to troubleshoot the external monitor issues, but for basic auth monitoring, it is more efficient to use a standard HTTP monitor with a customized send string which includes the Authorization header. If the page you want to check the response content for is /whatsup.aspx, you should try using that in the send string:

 

 

GET /whatsup.aspx HTTP/1.1\r\nHost: members.acc.org\r\nConnection: close\r\nAuthorization: Basic ZGRlbmJvdzpiYWJ5cmVuMQ==\r\n

 

 

If that doesn't work, can you reply with the applications response? It might actually be necessary to make a request to the intermediate page with an external monitor, but it makes sense from a resource perspective to try to do it first with an standard HTTP(S) monitor.

 

 

Aaron