Load Balancing Algorithms

Description

Origin server IP hash: Requests from the same IP address are routed to the same backend server.
Weighted round robin: All requests are distributed to origin servers in turn based on their weights. A larger weight indicates that more traffic will be forwarded to the corresponding server.
Session Hash: Requests identified by the same session ID are directed to the same origin server. Ensure that a session tag in Traffic Identifier is configured after the domain name is added to WAF, or the session hash configuration does not take effect. For details, see How Do I Configure a Traffic Identifier for a Known Attack Source?

FAQs

Which Editions Support Load Balancing Algorithms?

Only the professional and enterprise editions in cloud mode support configuring load balancing algorithms.

How Do I Configure a Traffic Identifier for a Known Attack Source?

In the navigation pane on the left, choose Website Settings.
In the Domain Name column, click the website domain name to go to its basic information page.

In the Traffic Identifier area, click

next to IP Tag, Session Tag, or User Tag to configure a traffic identifier.

**Table 1** Traffic identifier parameters
Identifier	Description	Example Value
IP Tag	HTTP request header field of the original client IP address. Ensure that the protected website has a layer-7 proxy configured in front of WAF and that Use Layer-7 Proxy under the website basic information settings is set to Yes for this parameter to take effect. This field is used to store the real IP address of the client. You can customize the field name and configure multiple fields (separated by commas). After the configuration, WAF preferentially reads the configured field to obtain the real IP address of the client. If multiple fields are configured, WAF reads the IP address from left to right. NOTICE: If you want to use a TCP connection IP address as the client IP address, set IP Tag to $remote_addr. If the TCP Option Address (TOA) kernel module is configured for packets, but you do not want to identify TOA as the client IP address, set the IP address identifier to $remote_sockaddr and upgrade the dedicated engine version to the one later than May 2024. After doing this, layer-3 source IP addresses of packets will be identified as client IP addresses. If WAF does not obtain the real IP address of a client from fields you configure, WAF reads the cdn-src-ip, x-real-ip, x-forwarded-for, and $remote_addr fields in sequence to read the client IP address.	X-Forwarded-For
Session Tag	This tag is used to block possibly malicious requests based on the cookie attributes of an attack source. Configure this parameter to block requests based on cookie attributes.	jssessionid
User Tag	This tag is used to block possibly malicious requests based on the Params attribute of an attack source. Configure this parameter to block requests based on the Params attributes.	name