aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorKim Alvefur <zash@zash.se>2020-04-13 02:46:03 +0200
committerKim Alvefur <zash@zash.se>2020-04-13 02:46:03 +0200
commit2f67c339a3a06a759fe504a2158113e826369e27 (patch)
treed3d9e07949c335de5212e2f65be2fbf9cb278fa7
parent54e37ffe8d4562adc974a61359a8bfef8e0dcd29 (diff)
downloadprosody-2f67c339a3a06a759fe504a2158113e826369e27.tar.gz
prosody-2f67c339a3a06a759fe504a2158113e826369e27.zip
mod_component: Reply with a different error when not connected
The wait, service-unavailable is overloaded by XEP-0045 to mean that the room has reached the maximum number of users. See #1495. Bouncing errors for components is tricky since there is no way to tell that it comes from the server hosting the component, not from the other end of the component connection.
-rw-r--r--plugins/mod_component.lua2
1 files changed, 1 insertions, 1 deletions
diff --git a/plugins/mod_component.lua b/plugins/mod_component.lua
index 9ffc496e..2189aceb 100644
--- a/plugins/mod_component.lua
+++ b/plugins/mod_component.lua
@@ -132,7 +132,7 @@ function module.add_host(module)
end
module:log("warn", "Component not connected, bouncing error for: %s", stanza:top_tag());
if stanza.attr.type ~= "error" and stanza.attr.type ~= "result" then
- event.origin.send(st.error_reply(stanza, "wait", "service-unavailable", "Component unavailable", module.host));
+ event.origin.send(st.error_reply(stanza, "wait", "remote-server-timeout", "Component unavailable", module.host));
end
end
return true;