WAF allows you to configure traffic identifiers by IP address, session, or user tag to block possibly malicious requests from known attack sources based on IP address, Cookie, or Params.
If you have enabled enterprise projects, ensure that you have all operation permissions for the project where your WAF instance locates. Then, you can select the project from the Enterprise Project drop-down list and configure known attack source traffic identifiers for the domain names.
The website to be protected has been added to WAF.
If the IP address tag is not configured, WAF identifies the client IP address by default.
Tag |
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 Proxy Configured under the website basic information settings is set to Yes for this parameter to take effect. If there are multiple field names separated by commas (,), WAF reads the fields from left to right to obtain the client IP address. For example, for X-Forwarded-For,CDN-Src-IP,X-real-IP, WAF obtains the client IP address from the X-Forwarded-For field first. If this field has no value, WAF then obtains the value from other fields in sequence. If there is no field configured by the customer, WAF obtains the source IP address in the TCP connection by default. |
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 |