# HTTP Server Tests

The Connected Devices HTTP server tests work exactly like the Content Delivery Network test suite, only the HTTP server test measures against one target that can be any custom HTTP server while the CDN test suite measures all or as many of the pre-configured CDNs we monitor as you like. The HTTP server test is configurable, as outlined below.

For information about how the test works, and to see which CDNs you can test to, see [Content Delivery Network (CDN) Test Suite](https://docs.thousandeyes.com/product-documentation/connected-devices/connected-devices-tests/dynamic-application-test-suites/cdn-test-suite).

## HTTP Server Test Configuration Options

Configure your HTTP server test via the following tabs and fields.

### Basic Settings

The basic settings tab contains only the settings detailed within [Configuring Common Test Settings](https://docs.thousandeyes.com/product-documentation/connected-devices/test-management/test-settings/configuring-connected-devices-tests#configuring-common-test-settings).

* For the **Target** setting, enter the URL to test to. Do not include URL queries or fragments. Defaults to an empty string field; enter a valid domain name or IP address.

### Advanced Settings

**IP Version**

* Defaults to “Prefer IPv6 (auto-detect)”. Choose also “IPv4 only” or “IPv6 only”.

**HTTP Server Timeout**

* Defaults to 5 s. Choose also from 5-15 s.

**Agent Testing Thresholds**

* **Cross-traffic, downlink/uplink**: Defaults to 25,000 bytes per second down/up.
* **CPU usage**: Defaults to 30%. Range is from 1-100%.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.thousandeyes.com/product-documentation/connected-devices/connected-devices-tests/web/http-server-tests.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.