Can a Path Containing # Be Matched in a Precise Protection Rule?

The path added to a precise protection rule cannot contain special characters ('"<>&*# %\?).

The number sign (#) is a client parameter. Parameters following the number sign (#) are not transferred to the server for web page location. WAF and browsers do not consider the content following the number sign (#) as URL parameters. Therefore, the parameters cannot be obtained.

Click to enlarge

Parent topic: Precise Protection rules

Precise Protection rules FAQs

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

more