I'm writing a new Jabber client library in Python. I started off developing it against a Wildfire, but today I decided I'd test it against a different server. It didn't work, however. From what I've seen, it seem a problem with the XML parsing in ejabberd. Check this out:
OUTGOING: <ns0:starttls xmlns:ns0="urn:ietf:params:xml:ns:xmpp-tls" />
STANZA: <ns0:error xmlns:ns0="http://etherx.jabber.org/streams"><ns1:policy-violation xmlns:ns1="urn:ietf:params:xml:ns:xmpp-streams" /><ns1:text xml:lang="en" xmlns:ns1="urn:ietf:params:xml:ns:xmpp-streams">Use of STARTTLS required</ns1:text></ns0:error>
STANZA is an incoming stanza, outgoing is the data I sent. This works fine, however:
OUTGOING: <starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls" />
STANZA: <ns0:proceed xmlns:ns0="urn:ietf:params:xml:ns:xmpp-tls" />
With XML, though, first and second OUTGOING are exactly equivalent. Why does this not work in ejabberd?
Namespace
For now ejabberd do not take namespaces into account, but we are already aware of the problem and working on it.
--
Mickaël Rémond