Add a liveness test to an existing domain

When you configure a Global Traffic Management domain, you can configure liveness tests to perform validation tests on each server. Add a liveness test on an existing property type in a domain.

Before you begin

Before you can add a liveness test to a property type, verify that the property type supports liveness tests. For example, you can perform liveness tests on the Mirror Failover property type and the Weight Random Load Balancing property types.

How to

  1. On the Traffic Management Domains page, select the domain for which you want to add a liveness test. The Edit Domain Settings page appears.
  2. On the Properties tab, select the property to which you want to add a liveness test. The review page for the selected property opens.
  3. On the Liveness Tests tab, click the Add New Liveness Test button to access the fields.

    Click the right caret icon to expand the Liveness Tests field if it is not open.

  4. In the Liveness Test Details section of the page, enter the following information to create a liveness test. This example uses the HTTP protocol. Other protocols have different or fewer fields to fill out. See Liveness Test for more information about these fields.
    • Enabled-- click the checkbox to allow (enable) the liveness test for the selected property. Uncheck the box to disable the liveness test for the selected property.
    • Test Name (required)
    • Test Interval
    • Test Timeout
    • Port: specify the port number for requesting the test object
    • Protocol: select a protocol type from the menu (for example, DNS, HTTP, FTP, TCP)
      Note: If you select one of the secure protocols for a liveness test (HTTPS, POPS, SMTPS, and TCPS), you can upload an SSL certificate for that test. See Upload an SSL certificate for a liveness test for more information.
      Note: If you select the HTTPS protocol, the Certificate Verification checkbox, which is enabled by default, appears below the Protocol field. Use this checkbox to verify the validity of an SSL certificate. This prevents the delivery of traffic to an origin that is operational but has an invalid or bad certificate, which can cause failure on the clients if they are sent to the origin.

      If you select the HTTP protocol and the Certificate Verification checkbox is enabled (checked), you must specify a Host HTTP header.

    • HTTP Method: Select the following HTTP methods in the drop-down menu:GET, HEAD, POST, PUT, PATCH, DELETE, OPTIONS, TRACE.

      This drop-down menu is visible only when you specify HTTP or HTTPS in the Protocols pull-down menu.

      When you specify HTTP or HTTPS as the test object protocol in the Protocol drop-down menu and you select POST, PUT, or PATCH in the HTTP Method drop-down menu, the HTTP Request Body field displays below the HTTP Headers section of the Liveness Test page.

      You can select two different views when you add or edit HTTP request body content in the HTTP Request Body field: Text View and Base64 View. And you can toggle between these two views. For more information, see Liveness Test.

    • Test Object Path (optional): only enter the local part of the URL for the test object (for example, /data/results/test.html)
    • HTTP Headers (optional). Akamai strongly recommends that you set the host header correctly for all HTTP/HTTPs tests. If you do not specify an HTTP header, the property's fully qualified domain name will be used.

      Choose one or more HTTP headers and their values from a standard list of HTTP headers. In the Name field pull-down menu, choose an HTTP header and specify its value. Click the green plus sign (+) next to a header row to see a new row from which you can choose additional HTTP headers.

      Note: The HTTP headers option is available only when you select HTTP and HTTPs protocols.

      Optionally, you can choose Other …, which allows you to specify one or more customized HTTP headers. The customized header name must contain only letters, digits, hyphens, underscores, and dots. Blank spaces causes an error when you try to submit and validate the changes. To return to the Name field pull-down menu, click the left arrow located to the left of the header text field.

      In addition, you can test the validity of the selected HTTP headers by clicking the Validate HTTP Headers button. A message appears only if HTTP header errors are detected.

      If the same server is being tested for more than one property, the liveness tests will be coalesced and a host header will be chosen from among them, unless different host headers are explicitly specified for each test.

      If you are using Cloud Server Targeting for a data center, you can enable Cloud Server Host Header Override. Akamai's liveness test agents populate the Host header with the host header value configured in the liveness test. For more information, see Configuring GTM with cloud-based services

      For detailed descriptions of standard HTTP headers, see

    • HTTP/FTP Errors: Select the responses you want to consider for server failures.
    • Authentication: If you are using password authentication, provide a username and password.
  5. Click Save Liveness Test to save your changes. The test's name appears in the Test Name column.
  6. Click Add to Change List.
    The review Change List Dialog opens.
  7. Click the Review Change List button. The Review Change List Dialog opens. Verify your changes, validate them, add a required comment, and click Activate Domain to save them. The Traffic Management Domains page opens.
    For more information about the Review Change List Detail Dialog, see Change List Detail Dialog.