Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BadRequest exception from XMPP #152

Open
smondet opened this issue Dec 29, 2016 · 4 comments
Open

BadRequest exception from XMPP #152

smondet opened this issue Dec 29, 2016 · 4 comments
Labels

Comments

@smondet
Copy link

smondet commented Dec 29, 2016

Trying to /connect, I see the new "user" appear on Gajim for less than a second; then it disconnects, with an exception but no other error message:

11:53:28 *** connecting *** to talker.to (188.68.34.213 on port 5222)
11:53:29 *** TLS session info *** (TLS_1_2 TLS_RSA_WITH_AES_256_CBC_SHA256)
11:53:30 XXXXX@talker.to/Jackline: [_>o] (now online)
11:53:30 XXXXX@talker.to/Gajim: [_>o] (now online)
11:53:30 *** async error *** XMPP.Make(M)(XmlParser)(IDCallback).BadRequest
@hannesm
Copy link
Owner

hannesm commented Jan 1, 2017

since you can reproduce, could you run jackline -d true, which will create an out.txt in your current working directory. If you send the last line(s) from that file, they should be sufficient to see the problem.

thanks!

@smondet
Copy link
Author

smondet commented Jan 1, 2017

the last line is:

[11:35:24] IN TLS: <presence from='XXXXX@talker.to/Jackcline'><priority>10</priority></presence><iq id='lx42' type='set'><query ver='12' xmlns='jabber:iq:roster'><item jid='gbahelzb55mikilljkxz' ask='subscribe' subscription='none'/></query></iq>

@hannesm
Copy link
Owner

hannesm commented Jan 1, 2017

I think I need some more context (maybe up to the last OUT TLS)? Is gbahelzb55mikilljkxz a random string or did you mask a real jabber id with a random string for privacy issues?

@hannesm hannesm added the bug label Jan 21, 2017
@hannesm
Copy link
Owner

hannesm commented Jan 31, 2017

unable to find the root source of the issue -- but the jid returned in the roster (not containing any @ character) is strange. I guess this will be fixed once a more pure XMPP library is in place (which may take a while)...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants