---
title: "Test Level Proxy"
slug: "test-level-proxy"
updated: 2026-04-28T16:57:42Z
published: 2026-04-28T16:57:42Z
canonical: "docs.catchpoint.com/test-level-proxy"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.catchpoint.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Test Level Proxy

## Test Level Proxy

**Test-Level Proxy** configuration allows you to specify proxy behavior on a per-test basis. This provides greater flexibility than enterprise agent–level proxy configuration, enabling different tests to run with different proxy settings - even when executed on the same node.

### Proxy Concepts

The following proxy types are supported for Test-Level Proxy:

- **Direct** No proxy is used. The test connects directly to the target endpoint.
- **Enterprise Agent Proxy** Uses the proxy configuration defined on the Enterprise Agent node. This is the default behavior if no custom proxy is selected.
- **Custom Proxy (Static)** A specific proxy host and port are configured for the test. This proxy applies only to the selected test (or inherited scope).

**Not currently supported** We plan to introduce support for Proxy Auto-Config (PAC) in a future release

The following proxy authentication methods are supported:

- **None**
- **Basic authentication**

Proxy credentials are sourced from the **Credential Library**. Credentials are not entered directly in the test configuration.

### Where Test-Level Proxy Can Be Configured

![web_test_properties.png](https://cdn.document360.io/cb4af8f9-6751-4fd2-b39c-07aae832badb/Images/Documentation/web_test_properties.png)

Proxies can be configured at the Product, Folder or Test level.

When configuring proxy settings for a product, folder, or test, you explicitly select which proxy method to use:

- Direct (no proxy)
- Enterprise Agent Proxy
- Custom Proxy

Proxy settings do not automatically fail over to other options in the event that a connection cannot be established. The proxy option applied to a particular test determines the behavior for that test.

### Configuring a Custom Test-Level Proxy

#### Step 1: Create a Proxy Configuration

![create_proxy.png](https://cdn.document360.io/cb4af8f9-6751-4fd2-b39c-07aae832badb/Images/Documentation/create_proxy.png)

Custom proxies are defined in the **Proxy Configuration Library**.

A proxy configuration includes:

- Proxy type: **Static**
- Host and port (for example: `proxy.example.com:8080`)
- Optional credentials (selected from the Credential Library)
- Optional bypass list (comma-separated hosts or addresses that should not use the proxy)

Once created, proxy configurations can be reused across multiple tests.

#### Step 2: Assign the Proxy to a Product, Folder, or Test

![assign_proxy.png](https://cdn.document360.io/cb4af8f9-6751-4fd2-b39c-07aae832badb/Images/Documentation/assign_proxy.png)

1. Open the test configuration.
2. Navigate to the **Request / Proxies** section.
3. Select one of the following options:
  - **Direct** – do not use a proxy
  - **Enterprise Agent Proxy** – use the proxy configured on the agent node
  - **Custom Proxy** – select a proxy configuration from the library
4. Save the test.

The selected proxy configuration will be applied to all executions of the test.

### Enterprise Agent Proxy vs Test-Level Proxy

Both proxy approaches are supported:

- **Enterprise Agent Proxy** Proxy configuration is defined on the agent node and applies by default.
- **Test-Level Proxy** Proxy behavior is determined by the test configuration (or inherited from the parent folder or product), overriding node-level proxy usage when selected. Each test explicitly controls which option is used.

For details on configuring Enterprise Agent proxy settings, see: [Proxy Setup for Enterprise Nodes](https://docs.catchpoint.com/docs/proxy-setup-for-enterprise-nodes)

## Credentials and Security

- Proxy credentials are managed centrally in the **Credential Library**.
- Multiple tests can reference the same credentials.
- Credentials are never stored directly in test definitions.

This approach ensures secure credential reuse and centralized management.