The Web Servers tab (under Web Applications) is where you can define backend servers (i.e origin servers) as a server pool. Add one or more servers to the server pool. Alternatively, if your web application resides on a docker (container), enable Docker platform to provide docker information. You can choose one web server profile per web application.
You can specify the docker image ID. This will create a pool of all containers spawned from the docker image.
Note that a single Web Server profile can be used to create a container pool or a server pool, but not a combination of both.
- all origin servers (containers) in pool must have one common port
- all origin servers (containers) in pool must have one common protocol
- all origin servers (containers) in pool must have one common healthcheck profile
You can use weights for WAF to distribute the request load to various servers in the Web Server Pool. Consider a pool consisting of four origin servers with the weights 1, 2, 3 and 3. The total weights assigned to all servers is 9. WAF distributes 1/9th of total load to sever 1, then 2/9th of total load to server 2, and so on.
To specify weights, while creating a server pool, simply add the weight (number) beside the server address. You can add weights to your existing pool as well. Default is 1. Maximum allowed value is 256.
roundrobin - (default) Each server (container) receives the connection in turns, according to their weights. Weights are dynamically adjusted for best performance.
leastconn - The server (container) with the lowest number of connections receives the connection.
first - The first server (container) with available connection slots receives the connection.
source - Only one designated server (container) receives the connection, based on the source IP address.
Active means the server (container) pool is assigned to a web application in your account. Inactive means the server (container) pool is not yet assigned to a web application.