aboutsummaryrefslogtreecommitdiffstats
path: root/plugins
diff options
context:
space:
mode:
authorKim Alvefur <zash@zash.se>2020-04-11 19:31:15 +0200
committerKim Alvefur <zash@zash.se>2020-04-11 19:31:15 +0200
commit608d6dd75669b3b8bcc526b91dad865ae89af79a (patch)
tree70f55bab55f2ec57f4040e81dd768d6bd1f5f7ac /plugins
parent1f92aa928062b406778e78ab9c1030b8d6be5bed (diff)
downloadprosody-608d6dd75669b3b8bcc526b91dad865ae89af79a.tar.gz
prosody-608d6dd75669b3b8bcc526b91dad865ae89af79a.zip
mod_component: Specify an error source for Component unavailable errors
It is somewhat ambiguous where an error really comes from in the case of an external component. Setting by to the bare host at least distinguishes it from JIDs with a node- or resourcepart.
Diffstat (limited to 'plugins')
-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 afcfc68c..9ffc496e 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"));
+ event.origin.send(st.error_reply(stanza, "wait", "service-unavailable", "Component unavailable", module.host));
end
end
return true;