Quote: The developers are

mfoss — Wed, 27 Jan 2010 14:43:23 +0000

Quote:

The developers are telling me that:

Those developers are hiding you important information. ejabberd replies to the client queries, so it's important to consider not only ejabberd reply, but also the related client query.

I tested ejabberd 2.1.2 compiled from source code in Debian, using the Tkabber client with two different client configurations

First I use STARTTLS encryption and SASL authentication (RFC 3920 compliant). The client sends to ejabberd:

<stream:stream
 xmlns:stream='http://etherx.jabber.org/streams'
 xmlns='jabber:client'
 to='localhost'
 xml:lang='es'
 version='1.0'>

Then ejabberd replies to the client:

<stream:stream
 xmlns='jabber:client'
 xmlns:stream='http://etherx.jabber.org/streams'
 id='3804815462'
 from='localhost'
 version='1.0'
 xml:lang='en'>

Second, I disable STARTTLS and SASL (like in old Jabber protocol, before RFC 3920 was written). The client sends to ejabberd:

<stream:stream
 xmlns:stream='http://etherx.jabber.org/streams'
 xmlns='jabber:client'
 to='localhost'
 xml:lang='es'>

Then ejabberd replies to the client:

<stream:stream
 xmlns='jabber:client'
 xmlns:stream='http://etherx.jabber.org/streams'
 id='2262839397'
 from='localhost'
 xml:lang='en'>

ejabberd - Comments for "XMPP Version not being sent to application"

Quote: The developers are