Skip to content
This repository has been archived by the owner on Dec 15, 2021. It is now read-only.

connect to wildfire im server error #27

Closed
Jajcus opened this issue May 3, 2011 · 5 comments
Closed

connect to wildfire im server error #27

Jajcus opened this issue May 3, 2011 · 5 comments

Comments

@Jajcus
Copy link
Owner

Jajcus commented May 3, 2011

in processing input bind result stanza:

jiddd@myserver.com/pyxmpp

to="myserver.com/838805ce" field was incorrect processed.
suggestion :
insert after stanzaprocessor.py line 265 :

    if to and to.node == None :
    to = None
@Jajcus
Copy link
Owner Author

Jajcus commented May 3, 2011

This is a WildFire/OpenFire bug. I think it has been fixed by now.

--Jajcus

@Jajcus
Copy link
Owner Author

Jajcus commented May 3, 2011

I just test with most recently version of openfire, 3.6.0. it still has the same problem.

--anonymous

@NoRefill
Copy link

I just tried this with openfire 3.7.0 and still has the same problem. I have to put the "fix" shown above in for things to work. I haven't done a whole lot of research on this issue. Does openfire know this is a problem? Is it being pushed back at pyxmpp?

@Jajcus Jajcus closed this as completed in 43e0048 Aug 23, 2011
@Jajcus
Copy link
Owner Author

Jajcus commented Aug 23, 2011

I have added the workaround, as specific as possible (I would prefer not to accept any badly addressed stanza, even though it shouldn't matter much on a client connection). Please verify if it works for you.

It seems someone tried to report the problem upstream, but the post was ignored: http://community.igniterealtime.org/thread/35966

@NoRefill
Copy link

I confirmed that the patch you committed for process_stanza() fixes the problem I was having with openfire. Thanks.

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

No branches or pull requests

2 participants