On Thu, Jun 03, 2004 at 02:36:37PM -0600, Craig Hollabaugh wrote: > I'm trying to send an iq with <query xnlns='jabber:iq:private'> > between my custom non-IM clients. I noticed that jabberd v1.4.3 > intercepts and bounces the message. I see in jsm/modules/mod_xml.c > that the server returns a TERROR_NOTACCEPTABLE message.
You can't do that. jabber:iq:private is a namespace that has special meaning to a server (at least servers that support it), which is why you're getting an error when you try to route around the server. > I don't have jabberd v2 running yet to check for similar behavior but > looking at the source, sm/mod_iq_private.c, I see > > /* we're only interested in no to, to our host, or to us */ > if(pkt->to != NULL && jid_compare_user(sess->jid, pkt->to) != 0 && > strcmp(sess->jid->domain, pkt->to->domain) != 0) > return mod_PASS; > > Does returning mod_PASS mean that my iq queries with > xnlns='jabber:iq:private' will be routed to my custom client? It looks like j2 will pass it on to the client, thats correct. Whether it should is another story - I think the results of such an action (using a predefined namespace in a non-standard way) is undefined at best. > ps. I want to use the jabber:iq:private namespace for my app instead > of developing a new one that does the same thing. If you want to guarantee that it works correctly everywhere, use a custom namespace. Rob. -- Robert Norris GPG: 1024D/FC18E6C2 Email+Jabber: [EMAIL PROTECTED] Web: http://cataclysm.cx/
signature.asc
Description: Digital signature
_______________________________________________ jdev mailing list [EMAIL PROTECTED] https://jabberstudio.org/mailman/listinfo/jdev
