Two things: 1) the 'to' attribute (as well as the 'id' attribute) are part of the jabber:client namespace. 2) namespaces are not used correctly by the server - while the resulting stream is well-formed XML and does use namespaces correctly, there is no flexibility on *how* you use those namespaces. For instance, if you started the stream off with <jabber:stream> instead of <stream:stream>, it would have also broken.
- David Waite Fabrice DESRE - FT.BD/FTRD/DMI/GRI wrote: > Hello, > > Writing my own client, I found something >strange in the open source server : if I >initiate the session with : ><?xml version='1.0'?> ><stream:stream to='jabber' > xmlns:stream='http://etherx.jabber.org/streams' > xmlns='jabber:client'> > <iq id='A3' type='get'> > <query xmlns='jabber:iq:auth'> > <username>fabrice</username> > </query> > </iq> ></stream:stream> > > everything works fine, but if I send : > ><?xml version='1.0'?> ><stream:stream to='jabber' > xmlns:stream='http://etherx.jabber.org/streams'> > <iq xmlns='jabber:client' id='A3' type='get'> > <query xmlns='jabber:iq:auth'> > <username>fabrice</username> > </query> > </iq> ></stream:stream> > >then the server sends me this error and closes the connection : ><?xml version='1.0'?> ><stream:stream xmlns:stream='http://etherx.jabber.org/streams' > id='3BBB0DE3' > xmlns='jabber:client' > from='jabber'> > <stream:error>Invalid Namespace</stream:error> ></stream:stream> > > I don't understand the rationale of this error message. My first XML >stream is perfectly valid and the QName of the elements are the same >in both cases. >I didn't find any mention of this requirement in the docs so I guess >it's a bug in the server ? > > Fabrice > _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
