Hi. I ran into problems when connecting to jabberd2 from various clients. In most of the cases it seems to be related to empty field resource in bind request just after authentication.
For example Bria for Android does not login at all to our server even when Bria for iOS works just fine. I traced communication and found one difference: Bria for Android (resource set to "a"): <iq id='uid:4f719780:25e9d6ff' type='set' from='[email protected]' xmlns='jabber:client'> <bind xmlns='urn:ietf:params:xml:ns:xmpp-bind'> <resource/> </bind> </iq> Bria for iOS (with same settings): <iq id='uid:4f7073b7:1dd7bd4c' type='set' from='[email protected]' xmlns='jabber:client'> <bind xmlns='urn:ietf:params:xml:ns:xmpp-bind'> <resource>a</resource> </bind> </iq> RFC 3920 states that server must be able to autogenerate resource name automatically, but client should send empty bind node with no resource at all. So it seems to be bug on client ... but we found this error with others clients we tested too (last stable version of Zoiper for example). Did any of you run into similar problems? Isn't there any simple solution or a patch? Thanks, Richard ________________________________ Prohlášení: k tomuto e-mailu je připojeno prohlášení, jehož plné znění naleznete na stránce http://www.ipex.cz/prohlaseni
