HTTP is an application-based test that enables an agent to verify the availability and response time of a web server, expressed in seconds. The test support HTTP and HTTPS protocols, as well as proxy, proxy authentication, and simple web authentication (Basic/NTLM). The test can also execute an HTTP query with GET parameters included in the URL.
HTTP tests are configured as part of a target, or can also run standalone as an ad-hoc test (please review ad-hoc testing).

How to create an HTTP/HTTPS test


Step 1 - HTTP tests are created as part of a target.
Step 2 - In the target setup form click on the HTTP button and input the following information:
  1. Source (Ad-hoc only, required): The Agent that will conduct the test.
  2. URL/Complete URL: The full URL of the web page to be tested.
  3. HTTP Get Interval (required): The number of seconds between two consecutive HTTP queries. By default, the interval is set to 30 seconds.
  4. HTTP GET Timeout (required): The number of seconds that the Agent will wait for a response from the HTTP server before declaring that the data point failed. The default value is 5 seconds.
  5. Proxy Server
    1. HTTP/HTTPS: Select the protocol to be used by the proxy server.
    2. Proxy Server Address: Specify the IP address or FQDN of the proxy server.
    3. Port: Specify the TCP/IP port used by the proxy server.
    4. Enable Proxy Authentication: Check if the proxy server requires authentication in order to be utilized.
      1. Username: Specify the username needed for the proxy server authentication.
      2. Password: Specify the password associated with the above username.
    5. Enable Authentication: Check if you'd like to perform HTTP authentication on the URL being tested.
      1. Authentication Type: Basic or NTLM
      2. Username: Specify the username
      3. Password: Specify the password


HTTP status codes and HTTP/S test outcome

  • Successful tests will return an HTTP 200 status code.
  • Unsuccessful tests will return an error HTTP status code such as 404 or 503.
  • Redirects won't be followed.
Have more questions? Submit a request


Article is closed for comments.