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.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.