Guides
Secure Access Help Center

View Synthetic Test Results for HTTP Server

The Endpoint Test Results page displays response time and response code as well as error types and details for failed tests.

Procedure

  1. From the left menu, go to: Experience Insights > Insights Management > Endpoint tests.
  2. On the Endpoint Tests page, click an HTTP server test.
  1. View the results.
  • Response code—Denotes the interaction between the client and the server. A successful response code falls within the 200-299 range.
  • Response time—The amount of time it takes for a request sent by the testing agent to receive a response from the target application server.
  • Error types
    • HTTP Server Test Error "dh Key Too Small"—Indicates that the web server that performed TLS negotiation with the endpoint agent was configured with a Diffie-Hellman group that is cryptographically weak. Because of the insecure nature of weak Diffie-Hellman groups, many endpoint agents will refuse to communicate via HTTPS with the server. Web servers that have been in service for years without recent updates or that have compatibility requirements with old clients that cannot support newer encryption are most likely to generate this error.
    • HTTP Server Test Fails with SSL error
      • If the error occurs when the test is run from cloud agents or enterprise agents, the cause is typically a misconfigured web server that fails to send all required intermediate digital certificates in the certificate chain. Alternatively, if the web server's SSL server certificate was issued by a non-trusted certification authority (such as with private/internal PKI), the error is due to the agents missing the certification authority's root certificate.
      • If the error occurs only from enterprise agents that use an SSL-decrypting proxy, the error is due to the agents missing the proxy's signing certificate.
    • DNS error—Occurs when there's a problem with the process of converting a domain name (for example: www.example.com) into its corresponding IP address (for example: 192.0.2.1).

Create Synthetic Network Tests > View Synthetic Test Results for HTTP Server > View Synthetic Test Results for Network

Updated 2 months ago