Dnia 2011-05-27, pią o godzinie 20:23 -0400, Jefry Lagrange pisze: > <stream:features xmlns:stream='http://etherx.jabber.org/streams'> > <mechanisms xmlns='urn:ietf:params:xml:ns:xmpp-sasl'> > <mechanism>PLAIN</mechanism> > <mechanism>DIGEST-MD5</mechanism> > </mechanisms> > <auth xmlns='http://jabber.org/features/iq-auth'/> > <register xmlns='http://jabber.org/features/iq-register'/> > </stream:features>
You should notice: "2. Stream Feature After negotiating use of TLS and authenticating via SASL, the receiving entity returns a new stream header" This means, you will get XEP-0198 feature only after you authenticate. But you skipped the crucial part before: <stream:stream xmlns:stream='http://etherx.jabber.org/streams' xmlns='jabber:client' from='xiaoka.com' version='1.0' id='ubre3l5aid3tpsa98179qn2swxysfzxaaopeavos' xmlns:ack='http://www.xmpp.org/extensions/xep-0198.html#ns'>[...] See the xmlns:ack namespace definition? We support XEP-0198: Stanza Acknowledgements [1], not XEP-0198: Stanza Acknowledgements that replaced it. You will get <ack:ack xmlns:ack="http://www.xmpp.org/extensions/xep-0198.html#ns"/> stream feature after you authenticate. [1] http://xmpp.org/extensions/attic/xep-0198-0.3.html -- Tomasz Sterna Instant Messaging Consultant : Open Source Developer http://tomasz.sterna.tv/ http://www.xiaoka.com/ -- To unsubscribe send a mail to jabberd2+unsubscr...@lists.xiaoka.com
