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:
- Source (Ad-hoc only, required): The Agent that will conduct the test.
- URL/Complete URL: The full URL of the web page to be tested.
- HTTP Get Interval (required): The number of seconds between two consecutive HTTP queries. By default, the interval is set to 30 seconds.
- 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.
- Skip Certificate Verification: This option is to verify the validity of SSL certificates in HTTP tests. It will trigger an alert if an HTTPS certificate has expired or fails the SSL check, allowing the user to quickly detect certificate issues.
- Proxy Server
- HTTP/HTTPS: Select the protocol to be used by the proxy server.
- Proxy Server Address: Specify the IP address or FQDN of the proxy server.
- Port: Specify the TCP/IP port used by the proxy server.
- Enable Proxy Authentication: Check if the proxy server requires authentication in order to be utilized.
- Username: Specify the username needed for the proxy server authentication.
- Password: Specify the password associated with the above username.
- Enable Authentication: Check if you'd like to perform HTTP authentication on the URL being tested.
- Authentication Type: Basic or NTLM
- Username: Specify the username
- 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.