Hi Florian, > Subject says it all: Is an IQ request sent by the client to its bare JID > equal to sending it without 'to' attribute? > > I've looked at RFC 6120 § 8.1.1.1. and 10.3.3., but couldn't get an > answer out. >
I think § 10.3.3 is clear on this topic. I’d answer your question with „yes“. Although in practice it’s not always implemented this way. At least by Openfire, which often treats no ‚to‘ attribute in IQs as if it were sent to the server (server’s domain bare JID). E.g. it returns (or returned in an older version) the server uptime in XEP-0012 (instead of the user’s logout date) or the server features + identities instead of the user’s pubsub account (+features) when querying disco#info. When doing roster queries *with* a ‚to‘ attribute (current user’s bare JID), it even returned no result at all (in version 3.9). There are corresponding bugs in the issue tracker: https://issues.igniterealtime.org/browse/OF-462 https://issues.igniterealtime.org/browse/OF-875 https://issues.igniterealtime.org/browse/OF-872 https://issues.igniterealtime.org/browse/OF-982 From a client point of view, it’s probably the safest way to always include the ‚to‘ attribute (well, except for roster queries), in order to not run into such server bugs. — Christian _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
