Use alternate backends

Routes requests to alternate backends defined by a Cluster, server IPs, or hostnames. Supports URL mapping.

This action routes a matching request to backend servers other than the application’s default. You must specify a cluster, a list of servers, or a hostname.

Configuration

  • Cluster: A cluster to which traffic is sent.
  • Servers: A list of server IP addresses to which traffic is sent.
  • Hostname: A fully qualified domain name (FQDN) whose addresses are used as the backend servers to which traffic is sent.
  • Direct: When enabled, requests bypass the configured application proxies and connect directly to the destination.
  • Remote URL: A URL that modifies attributes of the request sent to the backend, including the request URI, the use of HTTPS, the Host header, SNI, and the port used.
  • Relative to: A path prefix removed from the beginning of the request URI before the Remote URL is processed. This is useful for routing requests to backend services that do not expect the prefix.

Behavior

When the conditions of the web control are met, the request is routed to the specified cluster, servers, or hostname. The Remote URL can further modify the scheme, host, SNI, port, and path used for the backend request, and Relative to removes a path prefix before that processing occurs. This is a final action, so it terminates the evaluation of the remaining web controls.

Have questions not answered here? Contact Support to get more help.

Last modified on November 18, 2026