We created a new URL request test (we already have some others working properly but to IIS web servers) for an Apache web server and we get consistently bad while the site is accessible from the HostMonitor's computer IE7 browser.
We tried using the IP of the site instead of the name.
We tried using other RMA agents in the network to do the test and it is the same.
We tried different configurations and even modified the registry with HTTP 1.1 support as per a thread recommendation here.
We also tried to generate an HTTP test and it doesn't work either.
We really don't know what could be happening.
Which would be the steps to diagnose why this is happening?
We're using Host Monitor 8.72 running on Windows Server 2003 x64
Tests to IIS 6 servers are working properly but this new test is not.
URL test
"Bad" status means HTTP server provides some answer that indicates error, e.g. HTTP code 404 (page not found) or HTTP code (internal server error).
You may use %HTTPCode% and %HttpHeader% variables to check answer returned by the server. E.g. you may use these variables in "Send e-mail" action assigned to the test or use "Tune up Reply" test property to display HTTP code in Reply field of the test
Regards
Alex
You may use %HTTPCode% and %HttpHeader% variables to check answer returned by the server. E.g. you may use these variables in "Send e-mail" action assigned to the test or use "Tune up Reply" test property to display HTTP code in Reply field of the test
Regards
Alex
HostMonitor uses the same standard HTTP HEADER, GET or POST requests like any web browser.
I think "Directory index forbidden" can be related to virtual host options... server may redirect requests depending on IP address of client (web browser/HostMonitor) or hostname used in URL request.
Regards
Alex
I think "Directory index forbidden" can be related to virtual host options... server may redirect requests depending on IP address of client (web browser/HostMonitor) or hostname used in URL request.
Regards
Alex