Pidgin disconnect immediately

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Connect to BOSH server using Pidgin
2.
3.

What is the expected output? What do you see instead?
It's working w/ Openfire's BOSH server, but not node-xmpp-bosh

What version of the product are you using? On what operating system?
Ubuntu 11.10 beta2
Openfire 3.7.1
node-xmpp-bosh 0.4.3
Pidgin 2.10.0

Please provide any additional information below.
Here is the debug log: http://pastebin.com/71ALxZXv

Original issue reported on code.google.com by rgv151 on 13 Oct 2011 at 9:36

[GoogleCodeExporter]

This is a known issue with pidgin: http://developer.pidgin.im/ticket/14070

We might consider "hacking" a fix in nxb if pidgin doesn't fix it. However, it 
might be at the cost of some complexity and performance.

Original comment by dhruvb...@gmail.com on 13 Oct 2011 at 11:45

• Changed state: Invalid

[GoogleCodeExporter]

After https://code.google.com/p/node-xmpp-bosh/issues/detail?id=23 is resolved, 
it would be easier to add a configuration option to let the server admin decide 
whether to eagerly respond to session creation requests (current strategy) or 
wait for the <stream:features/> packet before responding.

Original comment by dhruvb...@gmail.com on 14 Oct 2011 at 1:30

[GoogleCodeExporter]

I'd like to help out with this one, but I'm unsure of what to do.  From reading 
this and related issues it sounds like NXB needs to wait for the XMPP server to 
respond with <stream:features> before forwarding that stanza onto the client 
instead of responding immediately.  

The above discussion mentions 
https://code.google.com/p/node-xmpp-bosh/issues/detail?id=23 but it sounds like 
this other issue is resolved.  The source code has not been released since 
November so I'm assuming that I will need to copy the code out of SVN in order 
to make the changes.  One question: how does the resolution of issue 23 affect 
the resolution of this issue?

Anyhow, thanks for the great job you guys have done so far.

megaphone.ejabberd@gmail.com

P.S. You can see a running description of the project that I would like to use 
NXB for at http://megaphone-ejabberd.blogspot.com/

Original comment by megaphon...@gmail.com on 12 Dec 2011 at 3:22

[GoogleCodeExporter]

We'll have a look at this issue early next year (beginning of January) and 
hopefully fix it then. The fix would probably involve having a configuration 
option to make the NXB responses compatible with what pidgin expects. This 
would affect the login time for multiple streams if this option is enabled.

Original comment by dhruvb...@gmail.com on 13 Dec 2011 at 4:53

• Changed state: Reopened

[GoogleCodeExporter]

@rgv151: Commit #491 tries to fix this. Please could you check and report back 
on whether it works for you.

Original comment by dhruvb...@gmail.com on 24 Dec 2011 at 10:23

[GoogleCodeExporter]

Tried out commit 491, but pidgin is now reporting "503: service unavailable".  
This is similar to problems that I was seeing when I tried to modify NXB myself 
and it seemed to be due to pidgin wanting to see a response to its requests in 
the next packet it receives.  NXB, in accordance with the BOSH spec, sends an 
empty response immediately, and then sends the reply from the server later on.  

As with the original problem with the features stanza, this is an issue with 
pidgin, not with NXB.  Unfortunately, it could mean that every time you solve 
this issue, it just pops up again with the next stanza in the sequence.

Thanks for taking a look at this! 

Original comment by megaphon...@gmail.com on 25 Dec 2011 at 9:31

[GoogleCodeExporter]

@megaphone.ejabberd: You shouldn't see 503. Did you change the config file to 
set pidgin_compatible (check the example config file) to be true and pass that 
as --config?

Original comment by dhruvb...@gmail.com on 25 Dec 2011 at 11:08

[GoogleCodeExporter]

OK, missed using the config file before.  Tried using it pidgin_compatible and 
it is able to connect.  Thanks!

Original comment by megaphon...@gmail.com on 25 Dec 2011 at 11:42

[GoogleCodeExporter]

Original comment by dhruvb...@gmail.com on 1 Feb 2012 at 2:01

• Changed state: Fixed