Closed ghost closed 11 years ago
The <dummy></dummy>
is causing a problem. This is added to prevent entity expansion and other forms of attacks on the xml stream. The BOSH parser has been changed with the correct fix and doesn't use the dummy tags any more, but the websocket bit has been largely ignored.
It's funny that it fails with strophe since that is the one we've been testing with.
ps. You need to enclose code any anything else that is pre-formatted and you want to be displayed verbatim in a pair of triple ticks (`).
But I can make this work as well?
Commit c5523d22cb43c7742834e555714b494919da57d2 tries to hack-fix this. Please do let me know of it works for you.
I guess it is working well. although the chat is not working, but I guess that is the script. Thank you very much...
Welcome & thanks for reporting! :)
I was using an incorrect protocol. The correct protocol was proposed by you (for websockets): https://github.com/superfeedr/strophejs/tree/protocol-ed , not the one I was using: https://gist.github.com/739147
Again, thanks for your great work.
Welcome - and thanks for the updates!
Hi,
Im using this chat script: https://github.com/szimek/xmpp-chat In backend is running node-xmpp-bosh over ejabberd
I am also using Strophe, and to work with WebSockets use https://gist.github.com/739147
But, node-xmpp-bosh says this error:
I newbie in NodeJS, XMPP and WebSockets, so I have no idea who may be failing
PD: sorry for my english