ejabberd - Comments for "IQ question"

leeb wrote: Thanks once again

mfoss — Tue, 07 Jun 2011 21:49:07 +0000

leeb wrote:

Thanks once again badlop, wish I had spotted that!

I notice that I can send IQs of type result without the namespace attribute.

That's because ejabberd doesn't check it right now. But maybe it does in the future, or other XMPP servers do, or other clients, etc.

leeb wrote:

Is that valid? It is hard to understand the meaning of the RFC there.

I don't know either. But you can be in the safe corner by always including your custom xmlns in my-custom-query element.

Thanks once again badlop,

leeb — Tue, 07 Jun 2011 15:40:30 +0000

Thanks once again badlop, wish I had spotted that!

I notice that I can send IQs of type result without the namespace attribute. Is that valid? It is hard to understand the meaning of the RFC there.

ejabberd 2.1.6 verifies IQ a

mfoss — Tue, 07 Jun 2011 14:40:00 +0000

ejabberd 2.1.6 verifies IQ a little more than older versions, and some invalid IQs may not be allowed anymore, see https://support.process-one.net/browse/EJAB-1320

Your Iq element has as invalid child element, see http://tools.ietf.org/html/rfc6120#section-8.4

Quote:

... an IQ stanza of type "get" or "set" MUST contain one
such child element. Such a child element MAY have any name and MUST
possess a namespace declaration (other than "jabber:client", "jabber:
server", or "http://etherx.jabber.org/streams") that defines the data
contained within the child element. Such a child element is called
an "extension element". An extension element can be included either
at the direct child level of the stanza or in any mix of levels.

I've added in your "child element" a namespace declaration, and now the stanza is delivered correctly to the other room occupant in my tests:

<body rid='340429760'
      xmlns='http://jabber.org/protocol/httpbind'
      sid='9f751cb790d7e0d728623329d8ede1a1520e1ac7'>
  <iq to='abc@conference.abc.com/test'
      id='4465:exec'
      type='set'
      xmlns='jabber:client'>
    <my-custom-query xmlns="jabber:iq:leeb" />
  </iq>
</body>