R3166-R3206-HP High-End Firewalls Attack Protection Configuration Guide-6PW101

60
• A filtering keyword with ^ at the beginning or $ at the end indicates an exact match. For example,
filtering keyword ^webfilter matches website addresses starting with webfilter (such as
webfilter.com.cn) or containing webfilter at the beginning of a string after a dot (such as
cmm.webfilter-any.com). Filtering keyword ^webfilter$ matches website addresses containing
standalone word webfilter like www.webfilter.com; it does not match website addresses like
www.webfilter-china.com.
• A filtering keyword with neither ^ at the beginning nor $ at the end indicates a fuzzy match, and
matches website addresses containing the keyword.
• If * is present at the beginning of a filtering keyword, it must be present in the format like *.xxx,
where xxx represents a keyword, for example, *.com or *.webfilter.com.
• A filtering keyword with only numerals is invalid. To filter a website address like www.123.com, you
can define a filtering keyword like ^123$, www.123.com, or 123.com , instead of 123 . In other
words, you are recommended to use exact match to filter numeral website addresses.
2. When configuring a URL parameter filtering keyword, follow the principles of wildcards:
• ^ matches parameters starting with the keyword and can be present once at the beginning of a
filtering keyword.
• $ matches parameters ending with the keyword and can be present once at the end of a filtering
keyword.
• & stands for one valid character and can be present multiple times at any position of a filtering
keyword, consecutively or non-consecutively, and cannot be used next to *. If it is present at the
beginning or end of a filtering keyword, it must be next to ^ or $.
• * stands for up to 4 valid characters including spaces and can be present once in the middle of a
filtering keyword.
Troubleshooting web filtering
Failed to add filtering entry or suffix keyword due to upper limit
Symptom
• When you try to add a URL address filtering entry or URL parameter filtering entry, the system
prompts you that no more entry can be added.
• When you add a Java blocking or ActiveX blocking suffix keyword, the system prompts you that no
more keyword can be added.
Analysis
The number of URL address filtering entries, URL parameter filtering entries, Java blocking suffix keywords,
or ActiveX blocking suffix keywords has reached the upper limit.
Solution
If necessary, remove some configured entries or keywords before adding new ones.
Invalid characters are present in the configured parameter
Symptom
When you configure a URL address filtering entry or URL parameter filtering entry, the system prompts
you that there are invalid characters in the configured parameter.