aboutsummaryrefslogtreecommitdiffstats
path: root/tests/json/fail2.json
diff options
context:
space:
mode:
authorLennart Sauerbeck <devel@lennart.sauerbeck.org>2017-03-18 18:47:28 +0100
committerLennart Sauerbeck <devel@lennart.sauerbeck.org>2017-03-18 18:47:28 +0100
commit1727434f1180a250baaa761266bbc2fa79b3391a (patch)
tree9ee3d9624b0cc51df7c47474ced3a2b042bdbed6 /tests/json/fail2.json
parentd3509b1b61b0a71ff3cd1a242cb24be12c5e11d9 (diff)
downloadprosody-1727434f1180a250baaa761266bbc2fa79b3391a.tar.gz
prosody-1727434f1180a250baaa761266bbc2fa79b3391a.zip
muc: Allow clients to change multiple affiliations or roles at once (#345)
According to XEP-0045 sections 9.2, 9.5 and 9.8 affiliation lists and role lists should allow mass-modification. Prosody however would just use the first entry of the list and ignore the rest. This is fixed by introducing a `for` loop to `set` stanzas of the respective `muc#admin` namespace. In order for this loop to work, the error handling was changed a little. Prosody no longer returns after the first error. Instead, an error reply is sent for each malformed or otherwise wrong entry, but the loop keeps going over the other entries. This may lead to multiple error messages being sent for one client request. A notable exception from this is when the XML Schema for `muc#admin` requests is violated. In that case the loop is aborted with an error message to the client. The change is a bit bigger than that in order to have the loop only for `set` stanzas without changing the behaviour of the `get` stanzas. This is now more in line with trunk, where there are separate methods for each stanza type. References: #345
Diffstat (limited to 'tests/json/fail2.json')
0 files changed, 0 insertions, 0 deletions