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

Merge branch '2.1' into 2.2

Browse Source
This commit is contained in:
Johan Wikman
2017-09-27 13:04:14 +03:00
parent 2633ad2fe4 e97f26f170
commit 7b6680b8fa
6 changed files with 70 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@ -51,13 +51,14 @@ all matching queries, or `ignore` which allows all queries to proceed.
The following statement types will always be allowed through when `action` is
set to `allow`:
- COM_QUIT: Client closes connection
- COM_PING: Server is pinged
- COM_CHANGE_USER: The user is changed for an active connection
- COM_SET_OPTION: Client multi-statements are being configured
- COM_FIELD_LIST: Alias for the `SHOW TABLES;` query
- COM_PROCESS_KILL: Alias for `KILL <id>;` query
- COM_INIT_DB: Alias for `USE <db>;`
- COM_PING: Server is pinged
- COM_PROCESS_INFO: Alias for `SHOW PROCESSLIST;`
- COM_PROCESS_KILL: Alias for `KILL <id>;` query
- COM_QUIT: Client closes connection
- COM_SET_OPTION: Client multi-statements are being configured
You can have both blacklist and whitelist functionality by configuring one
filter with `action=allow` and another one with `action=block`. You can then use