Mercurial > prosody-modules

comparison mod_firewall/README.markdown @ 2036:7ba6ed553c93

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
mod_firewall/conditions: Add FROM_EXACTLY and TO_EXACTLY
author Matthew Wild <mwild1@gmail.com>
date Mon, 01 Feb 2016 20:24:51 +0000
parents ce991c678370
children 2ec7c0b8a371
comparison
equal deleted inserted replaced
2035:39774b078dde 2036:7ba6ed553c93
181 FROM: <<admin%d*>>@example.com 181 FROM: <<admin%d*>>@example.com
182 182
183 **Note:** It is important to know that 'example.com' is a valid JID on 183 **Note:** It is important to know that 'example.com' is a valid JID on
184 its own, and does **not** match 'user@example.com'. To perform domain 184 its own, and does **not** match 'user@example.com'. To perform domain
185 whitelists or blacklists, use Zones. 185 whitelists or blacklists, use Zones.
186
187 Condition Matches
188 ----------- -------------------------------------------------------
189 `FROM_EXACTLY` The JID in the 'from' attribute exactly matches the given JID
190 `TO_EXACTLY` The JID in the 'to' attribute exactly matches the given JID
191
192 These additional conditions do not support pattern matching, but are
193 useful to match the exact to/from address on a stanza. For example, if
194 no resource is specified then only bare JIDs will be matched. TO and FROM
195 match all resources if no resource is specified to match.
186 196
187 **Note:** Some chains execute before Prosody has performed any 197 **Note:** Some chains execute before Prosody has performed any
188 normalisation or validity checks on the to/from JIDs on an incoming 198 normalisation or validity checks on the to/from JIDs on an incoming
189 stanza. It is not advisable to perform access control or similar rules 199 stanza. It is not advisable to perform access control or similar rules
190 on JIDs in these chains (see the chain documentation for more info). 200 on JIDs in these chains (see the chain documentation for more info).