Configuring Anti-Crawler Rules¶
You can configure website anti-crawler protection rules to protect against search engines, scanners, script tools, and other crawlers, and use JavaScript to create custom anti-crawler protection rules.
Note
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 protection policies for the domain names in the project.
Prerequisites¶
A website has been added to WAF.
Constraints¶
Cookies must be enabled and JavaScript supported by any browser used to access a website protected by anti-crawler protection rules.
If your service is connected to CDN, exercise caution when using the JS anti-crawler function.
CDN caching may impact JS anti-crawler performance and page accessibility.
JS anti-crawler protection is not supported if you use the ELB access mode.
WAF only logs JavaScript challenge and JavaScript authentication events. No other protective actions can be configured for JavaScript challenge and authentication.
WAF JavaScript-based anti-crawler rules only check GET requests and do not check POST requests.
How JavaScript Anti-Crawler Protection Works¶
Figure 1 shows how JavaScript anti-crawler detection works, which includes JavaScript challenges (step 1 and step 2) and JavaScript authentication (step 3).
Figure 1 JavaScript Anti-Crawler protection process¶
If JavaScript anti-crawler is enabled when a client sends a request, WAF returns a piece of JavaScript code to the client.
If the client sends a normal request to the website, triggered by the received JavaScript code, the client will automatically send the request to WAF again. WAF then forwards the request to the origin server. This process is called JavaScript verification.
If the client is a crawler, it cannot be triggered by the received JavaScript code and will not send a request to WAF again. The client fails JavaScript authentication.
If a client crawler fabricates a WAF authentication request and sends the request to WAF, the WAF will block the request. The client fails JavaScript authentication.
By collecting statistics on the number of JavaScript challenges and authentication responses, the system calculates how many requests the JavaScript anti-crawler defends. In Figure 2, the JavaScript anti-crawler has logged 18 events, 16 of which are JavaScript challenge responses, and 2 of which are JavaScript authentication responses. Others indicates the number of WAF authentication requests fabricated by the crawler.
Figure 2 Parameters of a JavaScript anti-crawler protection rule¶
Important
WAF only logs JavaScript challenge and JavaScript authentication events. No other protective actions can be configured for JavaScript challenge and authentication.
Configuring an Anti-Crawler Rule¶
Log in to the management console.
Click
in the upper left corner of the management console and select a region or project.Click
in the upper left corner and choose Web Application Firewall (Dedicated) under Security.In the navigation pane on the left, choose Policies.
Click the name of the target policy to go to the protection configuration page.
In the Anti-Crawler configuration area, toggle on the function if needed. Then, click Configure Anti-Crawler.
Figure 3 Anti-Crawler configuration area¶
Select the Feature Library tab and enable the protection by referring to Table 1.
A feature-based anti-crawler rule has two protective actions:
Block
WAF blocks and logs detected attacks.
Caution
Enabling this feature may have the following impacts:
Blocking requests of search engines may affect your website SEO.
Blocking scripts may block some applications because those applications may trigger anti-crawler rules if their user-agent field is not modified.
Log only
Detected attacks are logged only. This is the default protective action.
Scanner is enabled by default, but you can enable other protection types if needed.
Figure 4 Feature Library¶
Table 1 Anti-crawler detection features¶ Type
Description
Remarks
Search Engine
This rule is used to block web crawlers, such as Googlebot and Baiduspider, from collecting content from your site.
If you enable this rule, WAF detects and blocks search engine crawlers.
Note
If Search Engine is not enabled, WAF does not block POST requests from Googlebot or Baiduspider. If you want to block POST requests from Baiduspider, use the configuration described in Configuration Example - Search Engine.
Scanner
This rule is used to block scanners, such as OpenVAS and Nmap. A scanner scans for vulnerabilities, viruses, and other jobs.
After you enable this rule, WAF detects and blocks scanner crawlers.
Script Tool
This rule is used to block script tools. A script tool is often used to execute automatic tasks and program scripts, such as HttpClient, OkHttp, and Python programs.
If you enable this rule, WAF detects and blocks the execution of automatic tasks and program scripts.
Note
If your application uses scripts such as HttpClient, OkHttp, and Python, disable Script Tool. Otherwise, WAF will identify such script tools as crawlers and block the application.
Other
This rule is used to block crawlers used for other purposes, such as site monitoring, using access proxies, and web page analysis.
Note
To avoid being blocked by WAF, crawlers may use a large number of IP address proxies.
If you enable this rule, WAF detects and blocks crawlers that are used for various purposes.
Select the JavaScript tab and change Status if needed.
JavaScript anti-crawler is disabled by default. To enable it, click
and then click OK in the displayed dialog box to toggle on 
.
Figure 5 JavaScript¶
Important
Cookies must be enabled and JavaScript supported by any browser used to access a website protected by anti-crawler protection rules.
If your service is connected to CDN, exercise caution when using the JS anti-crawler function.
CDN caching may impact JS anti-crawler performance and page accessibility.
Configure a JavaScript-based anti-crawler rule by referring to Table 2.
Two protective actions are provided: Protect all requests and Protect specified requests.
To protect all paths except a specified path
Set Protection Mode to Protect all paths. Then, click Exclude Path, configure protected paths, and click Confirm.
Figure 6 Exclude Rule¶
To protect a specified path only
Set Protection Mode to Protect specified requests, click Add Rule, configure the request rule, and click Confirm.
Figure 7 Add Rule¶
Table 2 Parameters of a JavaScript-based anti-crawler protection rule¶ Parameter
Description
Example Value
Rule Name
Name of the rule
wafjs
Path
A part of the URL, not including the domain name
A URL is used to define the address of a web page. The basic URL format is as follows:
Protocol name://Domain name or IP address[:Port]/[Path/.../File name].
For example, if the URL is http://www.example.com/admin, set Path to /admin.
Note
The path does not support regular expressions.
The path cannot contain two or more consecutive slashes. For example, ///admin. If you enter ///admin, WAF converts /// to /.
/admin
Logic
Select a logical relationship from the drop-down list.
Include
Rule Description
A brief description of the rule.
None
Effective Date
Immediate
Immediate
Configuration Example - Logging Script Crawlers Only¶
To verify that WAF is protecting domain name www.example.com against an anti-crawler rule:
Execute a JavaScript tool to crawl web page content.
On the Feature Library tab, enable Script Tool and select Log only for Protective Action. (If WAF detects an attack, it logs the attack only.)
Figure 8 Enabling Script Tool¶
Enable anti-crawler protection.
Figure 9 Anti-Crawler configuration area¶
In the navigation pane on the left, choose Events to go to the Events page.
Configuration Example - Search Engine¶
To allow the search engine of Baidu or Google and block the POST request of Baidu:
Set Status of Search Engine to
by referring to the instructions in Step 6.Configure a precise protection rule by referring to Configuring Custom Precise Protection Rules.
Figure 10 Blocking POST requests¶