[Bug 28599] regression in 0.9.13: fails to connect to jabberd2 2.2.7.1, prosody 0.6.1

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=28599

Simon McVittie <simon.mcvittie at collabora.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|regression in 0.9.13: fails |regression in 0.9.13: fails
                   |to connect to jabberd2      |to connect to jabberd2
                   |2.2.7.1                     |2.2.7.1, prosody 0.6.1

--- Comment #5 from Simon McVittie <simon.mcvittie at collabora.co.uk> 2010-06-21 04:43:42 PDT ---
It turns out this affects my Prosody 0.6.1 installation, too; we should
probably release 0.9.14 sooner rather than later, if this is a common server
bug.

Outgoing IQ:

(telepathy-gabble:2069): wocky-DEBUG: _write_node_tree: Serializing tree:
* iq xmlns='jabber:client' type='get' to='smcv at XXX' id='788917834034'
    * query xmlns='http://jabber.org/protocol/disco#info'

Reply:

(telepathy-gabble:2069): wocky-DEBUG: Parsing chunk: <iq id='788917834034'
type='error' to='smcv at XXX/reptile'><error type='cancel'><service-unavailable
xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/></error></iq>

I also get these messages, because Prosody omits @from on the reply:

(telepathy-gabble:2069): wocky-DEBUG: handle_iq_reply: wocky-porter.c:842:
'(null)' (normal: '(null)') attempts to spoof an IQ reply from 'smcv at XXX'
(telepathy-gabble:2069): gabble-DEBUG: connection_iq_unknown_cb: got unknown
iq:
* iq xmlns='jabber:client' id='788917834034' type='error' to='smcv at XXX/reptile'
    * error type='cancel'
        * service-unavailable xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'

and the connection attempt eventually fails:

(telepathy-gabble:2069): gabble-DEBUG: bare_jid_disco_cb: Got disco error on
bare jid: Request for info on smcv at XXX timed out

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.