# HG changeset patch
# User Kim Alvefur <zash@zash.se>
# Date 1586738763 -7200
# Node ID 23319613504898bec385daa1a7c72d1deea50f89
# Parent  cb55554438524d4e0c36802ff856bac99b9eaa1f
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.

diff -r cb5555443852 -r 233196135048 plugins/mod_component.lua
--- a/plugins/mod_component.lua	Fri Aug 21 14:14:29 2020 +0100
+++ b/plugins/mod_component.lua	Mon Apr 13 02:46:03 2020 +0200
@@ -132,7 +132,7 @@
 			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;