Node-xmpp-bosh - Do I need any other XMPP for user auth #47
Comments
|
You don't need to setup prosody on the same (5280) port. In fact, you should disable any inbuilt bosh support in any of the xmpp servers you are using. NXB will let users connect to any xmpp server through it (it is a essentially an http proxy that allows xmpp access via http). You do however need to have prosody/openfire/ejebberd (any one of them) running if you want to authenticate users on your own domain. Can you post the exact error you get on IE7? |
|
Now I getting below message as below on Centos unix console.. [2012-08-27 13:32:52.557] [DEBUG] [response.js] - d5413499-1f26-44fb-bce6-8fec2e896096 SENT(706434): <body xmlns="http://jabber.org/protocol/httpbind" stream="4fe3c0ce-6be0-4ea7-b075-664fac088054" sid="d5413499-1f26-44fb-bce6-8fec2e896096" wait="20" ver="1.6" polling="35" inactivity="70" requests="2" hold="1" from="example.com" content="text/xml; charset=utf-8" xmpp:restartlogic="true" xmlns:xmpp="urn:xmpp:xbosh" window="2"/> |
|
Yes, this means that the BOSH connectivity with the client & the xmpp server seems to be working. I have no idea what the "key" and "newkey" parameters are - they are probably some custom attributes that the client is sending the xmpp server. They will most likely remain uninterpreted. |
|
Hello Dhruv, Thanks a lot for your quick response & hard work you are doing for node-xmpp-bosh. Keep it up.
node -v0.6.18 How to I update my npm-xmpp-bosh to latest version. Current npm-xmpp-bosh is update via NPM tool. You could see I have latest NPM version.
jappix/jappix#142 - Here Vanorayon told that YOu have fixed JSON GET fix. ( 3 days ago ) jappix/jappix#136 - Please review this thread where Vanorayon has mentioned that there is bug in JSON GET fix. ( 6 days ago )
Rgds |
|
All errors will be sent to standard output and standard error on the terminal on which you are running. You can redirect them to files if you wish. You will probably need to setup Jappix Mini and point it (the host) to the correct BOSH server. First try with the default Jappix BOSH server at jappix.org and then try using your own. As far as we know, there is no issue with the GET handler on current master. Vanaryon reported a few bugs, which to the best of my knowledge were fixed, and there aren't any open issues in that department. If you are willing to wait for a couple of days, you can download v0.6.2, which is (the current master) being tested. |
|
Jappix mini still not working node-xmpp-bosh.I have downloaded the latest ZIP file for node-xmpp-bosh & tried on all node - v0.6.18 I have run node-xmpp-bosh as #nohup node ./run-server.js & You can check my website www.chandancollection.com having node-xmpp-bosh server. If required, I will share the root access. +----------------------------------------------------------------------------------------------------------------+ org/protocol/httpbind" key="82d7f47c94f033ffc18133249342cc1266b7d062"/> |
|
@hzzg6y Please could you explain what the "key" attribute is and why it is different for every request? |
I was able to successfully compile node-xmpp-bosh
npm version is 1.1.21
node version is 0.6.18
node-xmpp-bosh is 0.6.1 with package.json "log4js": "= 0.4.2"
Do I need Prosody or openfire when I have node-xmpp-bosh up & running. As I need to have user authentication who will access the Jappix Mini.
If your answer is yes for above question, I am using prosody which uses 5280... how should I configure both so that jappix mini <---> node-xmpp-bosh <----> prosody / Openfire. Please provide some more details here. I have both node-xmpp-bosh & prosody or openfire on same server. Here Jappix mini code is on my websites otherservers.
Node-xmpp-bosh works fine on IE9, Firefox & chrome [ shows message text as Bidirectional-streams Over Synchronous HTTP ] however on IE7 it gives message as getting file information when I type http://url:5280/http-bind
Thanks
The text was updated successfully, but these errors were encountered: