Hi,
I have a URL request test.
The URL becomes unavailble from time to time for a few minutes.
The problem is that when the url is live again, the status of test is still Bad.
There is no reverse alert, no content checking.
In addition, in the test status I see the reply time.
How can I find why the test status is Bad?
Thanks
URL request satus is bad even thought the website is live
-
- Posts: 2832
- Joined: Tue May 16, 2006 4:41 am
- Contact:
URL request test returns Bad status, when HTTP server returns some HTTP error code (E.g. Error code 403 - Forbidden).
You may check HTTP error code, returned by the server, using %HTTPCode% macro-variable.
Also, you may use %HTTPHeader% variable to get complete HTTP header received from the server.
Please check the manual or visit our web site for more information at:
%HTTPCode%, %HTTPHeader% macro-variables: http://www.ks-soft.net/hostmon.eng/mfra ... .htm#macro
You may check HTTP error code, returned by the server, using %HTTPCode% macro-variable.
Also, you may use %HTTPHeader% variable to get complete HTTP header received from the server.
Please check the manual or visit our web site for more information at:
%HTTPCode%, %HTTPHeader% macro-variables: http://www.ks-soft.net/hostmon.eng/mfra ... .htm#macro
-
- Posts: 2832
- Joined: Tue May 16, 2006 4:41 am
- Contact:
HTTP code 500 means "internal server error".
If server always returns HTTP code 500, than may be server cannot process correctly some flags used by HostMonitor in HTTP header ?
E.g. HostMonitor always uses "no-cache" flag, or default user-agent Mozilla/4.0 (compatible; MSIE 6.0) is rejected by the webserver.
On the other hand, if server returns HTTP code 500 from time to time, or for some period of time - it's definitely server-side problem.
You should check web server logs for errors.
If server always returns HTTP code 500, than may be server cannot process correctly some flags used by HostMonitor in HTTP header ?
E.g. HostMonitor always uses "no-cache" flag, or default user-agent Mozilla/4.0 (compatible; MSIE 6.0) is rejected by the webserver.
On the other hand, if server returns HTTP code 500 from time to time, or for some period of time - it's definitely server-side problem.
You should check web server logs for errors.
-
- Posts: 2832
- Joined: Tue May 16, 2006 4:41 am
- Contact: