CDNetworks Documentation Flood Shield 2.0 User Guide Define traffic that does not require client-based detection

Define traffic that does not require client-based detection

Last update:2025-09-15 18:15:29

Explanation of Ajax request exceptions:
The JavaScript files distributed to clients for Web Bot Detection will continuously verify Ajax requests by dynamically adding URI Tokens. Since Ajax requests are not cached by default, this may lead to repeated requests and increased network bandwidth usage. Therefore, the system exempts such requests by default. This decision balances security and cost. If you wish to enhance the security of such requests, you may remove the Ajax request exemption. However, if your website enforces strict validation on URL parameters, it is not recommended to remove the Ajax request exemption.

For other application requests that you do not wish to be handled by Web Risk Detection, you can customize and configure exception rules.

Note: If your website receives requests from the following clients, please configure exceptions in the application request whitelist based on request characteristics before enabling Web Risk Detection to prevent false positives that may affect normal business operations.

  • Native APP
  • Native Mini Program
  • Third-party Application API Calls

Steps

  1. Log in to the Wangsu Console, locate your activated product, find the security product currently in use, and click to enter.
  2. Go to the Protection Configuration > Security Policy page.
  3. Find the Domain for which you need to configure the security policy. Click [ Product Maintenance ] Cloud Security Product Maintenance Announcement to enter the Security Policy editing page.
  4. Select the Bot Management tab. If Bot Management is currently disabled, please enable it first.
  5. Configure exceptions under Web Bot Detection > Bypass Traffic from Specific Clients(Exceptional Scenarios).

Custom exception configuration item description

  • Name: Enter the name of the exception rule.
  • Rule Description (Optional): Provide a description for the rule.
  • Matching Conditions: Specify matching conditions according to application requirements. Multiple matching conditions can be configured, and the relationship between them is AND. Within a single matching condition, multiple matching items can be entered using a separator, and the relationship between the items is OR.
Is the content of this document helpful to you?
Yes
I have suggestion
Submitted successfully! Thank you very much for your feedback, we will continue to strive to do better!