azurit
azurit
Ready to review (again)!
Ready to review again.
> I agree it can happen, but any functionality test of the WAF will fail afterwards anyways. It depends, most of the exclusion rules looks like this: ``` SecRule REQUEST_FILENAME...
See: [#1](https://www.google.com/search?q="ctl%3AruleRemoveById%3D949110") [#2](https://github.com/coreruleset/coreruleset/issues?q=is%3Aissue+%22ctl%3AruleRemoveById%3D949110%22)
This one is real fun. :) [#3](https://www.google.com/search?q="SecRuleRemoveById+949110")
Few are also here: [#4](https://github.com/coreruleset/coreruleset/issues?q=is%3Aissue+%22SecRuleRemoveById+949110%22)
I assume we don't want this. Closing.
@Xhoenix You are doing double URL decode using `t:urlDecodeUni` action: First one in the first rule and second one in the last rule. All rules are using the same data...
Also, i don't think we need such a complex rule for this. According to RFC 9110, `Referer` header cannot include a fragment (`#`). We should create a simple rule which...