ejabberd - Comments for "SASL PLAIN authentication failing with Jabber.org"

Problem solved

shubs6 — Tue, 25 Aug 2009 10:54:01 +0000

The issue was with JHB (JabberHTTPBind servlet v1.1.1). As the XMPP restart packet does not have child nodes so it was not forwarding it to the server. Though when you see the debug logs it prints XMPP RESTART so you think that the packet was sent. Only when we looked closely into the network traffic we noticed that. So it will be solved at JHB's end.

You are developing a XMPP client, right?

mfoss — Mon, 24 Aug 2009 10:22:02 +0000

You are developing a XMPP client, right? Are you testing it with a public, free, production XMPP server? Do you consider this a good idea?

If your client is untested and buggy, is it a good idea to test it in a server where many other people are chatting?

Why don't you install ejabberd in your machine, and test your client against it? You can also install other free XMPP servers, and test your client against them, too.

Delving more in the logs and

shubs6 — Wed, 19 Aug 2009 12:26:13 +0000

Delving more in the logs and BOSH implementation details I can see that I'm not getting any response from Jabber.org server for XMPP restart packet.

After this i Send resource binding packet but since the stream hasn't restarted I dont get that either.

Now what is the reason behind eJabberD 2.x version (Jabber.org) not responding to it? During my search and logs from successfully connecting client I see that client is not sending the OPEN stream tag prior to XMPP restart which is

<stream:stream to="jabber.org" xmlns="jabber:client" xmlns:stream="http://etherx.jabber.org/streams" version="1.0" > 

after successful Auth.

Is this tag required or is there some other problem with server? Actually due to technical issue with Flex I'm unable to create an OPEN stream tag. It always creates a CLOSED one so i cannot myself make change to the code and see the difference.