Configuration Example - Learn More

Case 1: Blocking Specific Attack Requests

Analysis of a specific type of WordPress pingback attack shows that the User Agent field contains WordPress.

Figure 1 WordPress pingback attack

A precise protection rule as shown in the figure can block this type of attack.

Figure 2 User Agent configuration

Case 2: Blocking Specific URL Requests

If a large number of IP addresses are accessing a specific URL that does not exist, configure the following precise protection rule to block such requests to reduce resource usage on the origin server.

Figure 3 Blocking requests to a specific URL

Case 3: Blocking Requests with Empty Fields

You can configure precise protection rules to block requests having null fields.

Figure 4 Blocking request with empty referer value

Case 4: Blocking Specified File Types (ZIP, TAR, and DOCX)

You can configure file types that match the path field to block specific files of certain types. For example, if you want to block .zip files, you can configure a precise protection rule as shown in Figure 5 to block access requests of .zip files.

Figure 5 Blocking requests of specific file types

Case 5: Hotlink Protection

You can configure a protection rule based on the Referer field to enable WAF to block hotlinking from a specific website. If you find out that, for example, requests from "https://abc.blog.com" are stealing images from your site, you can configure a rule to block such requests.

Figure 6 Hotlink protection

Case 6: Allowing Specific URL Requests from a Specified IP Address

You can configure multiple conditions in the Condition List field. If an access request meets the conditions in the list, WAF will allow the request from a specific IP address to access a specified URL.

Figure 7 Allowing specific IP addresses to access specified URLs