You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, we use ejabberd_local:route_iq when server wants to ask client something. I.e. it wants to send IQ get or set to the client.
It is used in mod_caps, for example. Or could be used in mod_ping or similar modules (but I think mod_ping uses optimized version, because mod_ping requests are send by the same server node as a client on - so no need to route response from between nodes).
So, idea is simple - we route IQ to some client in cluster, it could be on another node. But once we receive iq type=result, what should we do with it? we use IQ ids which contain the node number, where to send the reply for the actual processing by the server.
Your case - client sends an IQ result for IQ we never asked for (unless you have some module which sends IQ get/setto the client and puts from="my.domain.com" in it)
We should fix parsing though, and just ignore such unexpected/unwanted IQs.
Getting:
parse_iq_id_failed
, getting bad iq, without_
symbol, what could be source of such iqs?<iq xmlns='jabber:client' id='c6f59123b9721df6' to='my.domain.com' type='result'/>
Source file where error happening: ejabberd_local.erl:447
The text was updated successfully, but these errors were encountered: