Simon Marechal
Simon Marechal
Should be fixed in #1111
This is the expected behavior, the first "block" stops the filtering. This is especially important for violations that could lead to denial of service of the filter, such as maximum...
not exactly, things that are about the arguments will block at once, but things that are about signatures will all be applied at the same time and you'll get all...
When you use curl this way, it adds the `Content-Type: application/x-www-form-urlencoded` header. Raw spaces are indeed invalid, as they should be encoded as `%20`. Sadly, it might be the case...
The entries are sorted by descending length of the regular expression, it is not that arbitrary anymore. If two REs have the same length, then it's arbitrary.
There is indeed a bug where it would display in rate limits the statistics for global filters. cf. #1091
Should be fixed by PR
@yanushg can you give me more details about the problem with the waf report?
@yanushg I cannot reproduce this problem. This can however happen when the content filter is inactive. Can you confirm the content filter was active at that point?
(should be fixed in the attached PR)