Service Response Monitor › Test Management › Create Tests › HTTPS Tests

HTTPS Tests

The HTTPS test monitors the amount of time required to log in and test a secure website. You can test sites directly or use a proxy. You can also search for regular expressions on a web page, and you can specify the number of nested levels you want the HTTPS test to traverse during the test.

SRM uses HTTP 1.1 by default for all HTTP requests. It can handle HTTP 1.0 responses.

Options and Arguments

HTTPS tests require the following specific options and arguments:

• URL To Test. The hostname of the secure website to test.

  Note: IPv6 addresses can be used, but they must be embedded in brackets, for example [0aff::230:6eff:fe4b:51db]:8080. For example, 0aff::230:6eff:fe4b:51db represents the IPv6 address and 8080 represents the port number.

• User Name. (Optional) A user name for the site you are testing if it requires web authentication.
• Password. (Optional) A password for the user name you specified if the site requires web authentication. SRM stores the password in encrypted form.
• Frame Depth. (Optional) The number of levels the test should traverse when downloading nested frames. (The HTTPS test downloads all frames, images, external scripts, and applets during the page download so that the measurement reflects the user's experience when downloading a web page.) The default value is 3.
• Text Match. (Optional) A regular expression or text string that you want SRM to match on the pages you test. The number of matches displays in the Results Field column on the Monitor page for the agent.
• Min Matches. (Optional) The minimum number of times that SRM must find the search expression (default is 1). If the search expression is not found at least as many times as you specify in this field, the test will fail (Availability=0). If this field is set to zero and the agent does not find the search expression, the Availability measurement is not affected.
• Download Content. Checking this box downloads all images, frames, scripts, and applets, with the core HTML code from the proxy site.
• Fail on Content Errors. Checking this box specifies that any errors encountered while downloading images, frames, scripts, and applets cause the test to fail.
• Use Proxy. Check this box to use a proxy server for the website being tested. If this box is not checked, the following proxy options do not appear on the screen.
• Proxy Server. The hostname (the name or IP address) of the proxy server to use if the system from which you are testing does not have direct Internet access
• Proxy Port. (Optional) The port to use on the proxy server. The default is 80.
• Proxy User Name. (Optional) A valid username to be authenticated on the specified proxy server.
• Proxy Password. (Optional) The password for the specified user name. SRM stores the password in encrypted form.

Specify these options and arguments when you create or modify tests.

Notes:

• You retype the password in the Verify Proxy Password field to verify that you have entered it correctly.
• HTTP Test only supports the HTTP Basic authentication scheme. For more information consult documentation on your web server.

Untrusted SSL Certificates

HTTPS websites display an SSL certificate when the certificate is invalid (untrusted) or the address by which the website is accessed does not match with the SSL certificate.

To allow untrusted SSL certificates you must uncomment (that is, remove '#') 'allow_untrusted_ssl_certificates' in the svcrsp.cf configuration file.

Example

Use this example to create a test that monitors the amount of time required to access the main web page at the secure website, https://chargeMycredit.com This example tests the server once every 60 seconds and waits up to 20 seconds for a successful response. It calculates response time and availability statistics over the last 300 seconds (5 minutes).

To create a new test in a policy

1. Click + (New) on the Test Monitors toolbar.

   The New test pane appears.

2. From the Test Type list, select HTTPS.
3. In the Description field, specify chargeMycredit web.
4. In the Test Name field, specify HTTPS Test.
5. In the Test Interval field, specify 60.
6. In the Test Timeout field, specify 20.
7. In the Samples Per Interval field, specify 1.
8. In the Statistics Window field, specify 300.
9. In the URL To Test field, specify https://chargeMycredit.com. You specify the full web address, including https://.
10. In the User Name field, specify creditAcct.
11. In the Password field, specify secret.
12. Accept defaults for all other fields.
13. Click Save Test.

When you commit your changes, SRM adds an entry similar to the following to the svcrsp.cf file:

{ 
index=27 
type=https
desc="Test secure Web response at https://chargeMycredit.com" 
dest="https://chargeMycredit.com" 
username="creditAcct" 
encoded=yes 
password="ibwc3m" 
args="max_depth=3&minmatch=1&content_dl=true&content_err=false" 
interval=60 
samples=1 
timeout=20 
window=300 
tos=0 
limit=0 
status=active 
name="HTTPS-Test"
class=""
context=""
flags="1"
loglevel=1
}

For information about errors you may encounter when running HTTPS tests, see HTTPS Test Error Codes.