Software / code / prosody-modules
Changeset
4152:87daef9ed4e7
Improve mod_firewall readme
| author | Christian Weiske <cweiske@cweiske.de> |
|---|---|
| date | Mon, 21 Sep 2020 21:57:25 +0200 |
| parents | 4149:bb60db2b2cd1 |
| children | 4154:a2d5834d4a9e |
| files | mod_firewall/README.markdown |
| diffstat | 1 files changed, 9 insertions(+), 2 deletions(-) [+] |
line wrap: on
line diff
--- a/mod_firewall/README.markdown Mon Sep 21 15:49:54 2020 +0100 +++ b/mod_firewall/README.markdown Mon Sep 21 21:57:25 2020 +0200 @@ -68,6 +68,12 @@ If multiple files are specified and they both add rules to the same chains, each file's rules will be processed in order, but the order of files is undefined. +Reloading Prosody's configuration also reloads firewall rules. + +Make sure that `firewall_scripts` is in the global section of the configuration file +and not below a virtual host or a component - unless you want per-vhost +firewall rules. + Conditions ---------- @@ -587,8 +593,9 @@ --------------- ------------------------------------------------------------------------------------------------------------------------ `LOG=message` Logs the given message to Prosody's log file. Optionally prefix it with a log level in square brackets, e.g. `[debug]` -You can include expressions in log messages, using `$(...)` syntax. For example, to log the stanza that matched the rule, you can use $(stanza), -or to log just the top tag of the stanza, use $(stanza:top_tag()). +You can include expressions in log messages, using `$(...)` syntax. For example, to log the stanza that matched the rule, you can use `$(stanza)`, +or to log just the top tag of the stanza, use `$(stanza:top_tag())`. +To fetch the sender JID, use `$(stanza.attr.from)`. Example:
