[ejabberd] Ejbabberd *not* returning xmpp version on <stream:stream/> from time to time - Starttls

Franky Orson franky.orson at gmail.com
Mon May 2 12:13:47 MSD 2011


Running Ejabberd 2.1.3 - I connect fine with my own client using SASL most
of the time but then as I'm testing disconnection and re-connection, I'm
finding that Ejabberd is not setting the version when replying to my
<stream:stream> request - see below - 1st paragraph is when it is working
fine, then the 2nd paragraph is when the 'version' is not being sent as part
of the reply from Ejbabberd like if it was not supporting XMPP version 1.0
as defined in RFC 3920 - this is mostly happening after a reconnection with
the server but it is working 2 times out of the 3 - weird!

2011-05-02 00:34:20.681 [79543:40b] SEND: <?xml version='1.0'?>
2011-05-02 00:34:20.681 [79543:40b] SEND: <stream:stream
xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams'
version='1.0' to='myTest-server.com'>
2011-05-02 00:34:20.821 [79543:40b] RECV: <?xml version='1.0'?>
*// Version being set fine here on this attempt...*
2011-05-02 00:34:20.822 [79543:40b] RECV: <stream:stream
xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams'
id='1519821603' from='myTest-server.com' *version='1.0'* xml:lang='en'>
2011-05-02 00:34:20.822 [79543:40b] RECV: <stream:features>
2011-05-02 00:34:20.822 [79543:40b] RECV: <starttls
xmlns='urn:ietf:params:xml:ns:xmpp-tls'/>
2011-05-02 00:34:20.823 [79543:40b] RECV: <mechanisms
xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>
2011-05-02 00:34:20.823 [79543:40b] RECV: <mechanism>
2011-05-02 00:34:20.823 [79543:40b] RECV: DIGEST-MD5</mechanism>
2011-05-02 00:34:20.823 [79543:40b] RECV: <mechanism>
2011-05-02 00:34:20.823 [79543:40b] RECV: PLAIN</mechanism>
2011-05-02 00:34:20.824 [79543:40b] RECV: </mechanisms>
2011-05-02 00:34:20.824 [79543:40b] RECV: <register xmlns='
http://jabber.org/features/iq-register'/>
2011-05-02 00:34:20.824 [79543:40b] RECV: </stream:features>
2011-05-02 00:34:20.825 [79543:40b] SEND: <auth
xmlns='urn:ietf:params:xml:ns:xmpp-sasl' mechanism='DIGEST-MD5'/>
...
...

Handskake working, etc...

*** Now, here the issue after reconnecting (works 2 times out of 3)* - the
sample below failed and makes my client thinks Ejabberd does support SAS
(not RFC 3920 compliant), hence I initiate the old way of authenticating
with 'jabber:iq:auth'

2011-05-02 00:34:50.222 [79543:40b] SEND: <?xml version='1.0'?>
2011-05-02 00:34:50.222 [79543:40b] SEND: <stream:stream
xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams'
version='1.0' to='myTest-server.com'>
2011-05-02 00:34:50.299 [79543:40b] RECV: <?xml version='1.0'?>
*// SEE BELOW - NO VERSION SET ON REPLY FROM EJABBERD!*
2011-05-02 00:34:50.300 [79543:40b] RECV: <stream:stream
xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams'
id='1443222350' from='myTest-server.com' xml:lang='en'>
2011-05-02 00:34:50.300 [79543:40b] SEND: <iq type="get">
  <query xmlns="jabber:iq:auth"/>
</iq>
2011-05-02 00:34:50.300 [79543:40b] RECV: <stream:error>
2011-05-02 00:34:50.300 [79543:40b] RECV: <invalid-namespace
xmlns='urn:ietf:params:xml:ns:xmpp-streams'/>
2011-05-02 00:34:50.301 [79543:40b] RECV: </stream:error>

Settings as:

{listen,
 [
  {5222, ejabberd_c2s, [
                        {access, c2s},
                        {shaper, c2s_shaper},
                        {max_stanza_size, 65536},
                        %%zlib,
                        starttls, {certfile, "/etc/ejabberd/ejabberd.pem"}
                       ]},
]}.

Any idea why this would be happening?

Thanks in advance,

--Frank
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.jabber.ru/pipermail/ejabberd/attachments/20110502/b96a91ba/attachment.html>


More information about the ejabberd mailing list