I read through that, but I still don't follow why the server would not send some kind of response back to the user about the contact not existing, even if it's just another roster push to remove the contact. But in both cases, whether or not the contact exists, I get the same response:
<iq id="push3246656642" xmlns="jabber:client" from="user@mydomain" to="user@mydomain/myresource" type="set"> <query xmlns="jabber:iq:roster"> <item ask="subscribe" subscription="none" jid="contact@mydomain"></item> </query> </iq> On Fri, Nov 2, 2012 at 2:05 AM, Philipp Hancke <[email protected]> wrote: >> Unfortunately, I don't think I'm getting that error response with the >> version of ejabberd that I'm using. I'll double check it and inquire >> in the ejabberd list if this turns out to be the case. > > > if the error is delivered to the client the server is doing something wrong. > Even though (iirc) 6121 does not explicitly specify how to handle the error, > delivering it to a users client without modifying the roster is certainly > not the right thing. > > See http://www.ietf.org/mail-archive/web/xmpp/current/msg00057.html and > http://www.ietf.org/mail-archive/web/xmpp/current/msg01406.html for some > background information. > > _______________________________________________ > JDev mailing list > Info: http://mail.jabber.org/mailman/listinfo/jdev > Unsubscribe: [email protected] > _______________________________________________ _______________________________________________ JDev mailing list Info: http://mail.jabber.org/mailman/listinfo/jdev Unsubscribe: [email protected] _______________________________________________
