hcq/MaxScale
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Use matched instead of blocked

Browse Source 
As queries that match a rule aren't always blocked, it's more appropriate
to use `matched` instead of `blocked`.
This commit is contained in:
Markus Mäkelä
2017-04-03 12:40:06 +03:00
parent 108978fcd2
commit d32a2e410b
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
Documentation/Filters/Database-Firewall-Filter.md
View File

@ -139,13 +139,13 @@ This rule blocks all queries that use the wildcard character *.
#### `columns` #### `columns`
This rule expects a list of values after the `columns` keyword. These values are This rule expects a list of values after the `columns` keyword. These values are
interpreted as column names and if a query targets any of these, it is blocked. interpreted as column names and if a query targets any of these, it is matched.
#### `function` #### `function`
This rule expects a list of values after the `function` keyword. These values This rule expects a list of values after the `function` keyword. These values
are interpreted as function names and if a query uses any of these, it is are interpreted as function names and if a query uses any of these, it is
blocked. The symbolic comparison operators (`<`, `>`, `>=` etc.) are also matched. The symbolic comparison operators (`<`, `>`, `>=` etc.) are also
considered functions whereas the text versions (`NOT`, `IS`, `IS NOT` etc.) are considered functions whereas the text versions (`NOT`, `IS`, `IS NOT` etc.) are
not considered functions. not considered functions.
@ -220,9 +220,9 @@ list of users and networks the keyword match is expected.
After this either the keyword `any` `all` or `strict_all` is expected. This After this either the keyword `any` `all` or `strict_all` is expected. This
defined how the rules are matched. If `any` is used when the first rule is defined how the rules are matched. If `any` is used when the first rule is
matched the query is considered blocked and the rest of the rules are matched the query is considered as matched and the rest of the rules are
skipped. If instead the `all` keyword is used all rules must match for the query skipped. If instead the `all` keyword is used all rules must match for the query
to be blocked. The `strict_all` is the same as `all` but it checks the rules to be considered as matched. The `strict_all` is the same as `all` but it checks the rules
from left to right in the order they were listed. If one of these does not from left to right in the order they were listed. If one of these does not
match, the rest of the rules are not checked. This could be useful in situations match, the rest of the rules are not checked. This could be useful in situations
where you would for example combine `limit_queries` and `regex` rules. By using where you would for example combine `limit_queries` and `regex` rules. By using