Web Server Pool settings

This wizard lets you define backend servers (i.e origin servers) as a server pool.

Want to create a new server pool? Go to Web Applications > Web Servers and click the New Web Servers button.

Name of the server pool profile

Enter the name and description for the server pool. Initially the user who creates the server pool is the owner. When editing a server pool, you can choose another owner.


Select tags to apply to the server pool. Users with the applied tags in their scope will have access to it. Click Create to add a new tag.

Server port and protocol

The port number automatically changes to the appropriate one when you toggle Protocol HTTPS. You can provide a different port number other than the one added by the toggle switch.

Click to toggle between http:// and https:// for the server. The port number changes as per your selection.

Docker platform

Enable Docker platform to load balance traffic between web applications installed on containers. Docker image ID is required. This will create a pool of all containers spawned from the docker image.

Optionally, you can provide the docker name.

Web Servers

You can add one server or multiple servers to load balance traffic between several original URLs. All URLs must use the same protocol and port. For each server provide the IP address or a Fully Qualified Domain Name, and the corresponding weight between 0 to 256. WAF uses weights to distribute the request load to various servers in the Web Server Pool. Default weight is 1.

Server load balancing

Choose the method to load balance traffic between the servers. Your choices are:

roundrobin - Each server receives the connection in turns, according to their weights. Weights are dynamically adjusted for best performance.

leastconn - The server with the lowest number of connections receives the connection. Use of this algorithm is recommended where very long sessions are expected, such as LDAP, SQL, TSE, etc.

first - The first server with available connection slots receives the connection. The servers are chosen from the lowest numeric identifier to the highest, which defaults to the server's position in the farm.

source - Only one designated server receives the connection, based on the source IP address. The source IP address is hashed and divided by the total weight of the running servers to designate which server will receive the request. This ensures that the same client IP address will always reach the same server as long as no server goes down or up.