[ejabberd] pubsub delivery ignores /resource

Liam ejabberd at networkimprov.net
Mon Feb 1 23:26:57 MSK 2010


Here's the exchange (uuidx instances were actually real UUIDs)...

Subscriber (several slave at localhost/uuidx are already subscribed):

<iq from='slave at localhost/uuid2' to='pubsub.localhost'
    type='set' id='5284' xmlns='jabber:client'>
  <pubsub xmlns='http://jabber.org/protocol/pubsub'>
    <subscribe node='slave' jid='slave at localhost/uuid2'/>
</pubsub></iq>

<iq xmlns='jabber:client' from='pubsub.localhost' to='slave at localhost/uuid2'
    id='5284' type='result'>
  <pubsub xmlns='http://jabber.org/protocol/pubsub'>
    <subscription jid='slave at localhost/uuid2' subscription='subscribed'
subid='4F1CE1B16B4F'/>
</pubsub></iq>

Publisher:

<iq from='master at localhost/uuid1' to='pubsub.localhost'
    type='set' id='7562' xmlns='jabber:client'>
  <pubsub xmlns='http://jabber.org/protocol/pubsub'>
    <publish node='slave' jid='master at localhost/uuid1'>
      <item>
        data
</item></publish></pubsub></iq>

<iq xmlns='jabber:client' from='pubsub.localhost' to='master at localhost
/uuid1'
    id='7562' type='result'>
  <pubsub xmlns='http://jabber.org/protocol/pubsub'>
    <publish node='slave'>
      <item id='4F1CB17E4C2D'/>
</publish></pubsub></iq>

User connected as slave at localhost/uuid2 gets (no others are connected):

<message xmlns='jabber:client' from='pubsub.localhost' to='slave at localhost
/uuid3'>
  <headers xmlns='http://jabber.org/protocol/shim'/>
  <event xmlns='http://jabber.org/protocol/pubsub#event'>
    <items node='slave'>
      <item id='4F1CE379C405'>
        data
</item></items></event></message>

<message xmlns='jabber:client' from='pubsub.localhost' to='slave at localhost
/uuid4'>
  <headers xmlns='http://jabber.org/protocol/shim'/>
  <event xmlns='http://jabber.org/protocol/pubsub#event'>
    <items node='slave'>
      <item id='4F1CE379C405'>
        data
</item></items></event></message>

<message xmlns='jabber:client' from='pubsub.localhost' to='slave at localhost
/uuid5'>
  <headers xmlns='http://jabber.org/protocol/shim'/>
  <event xmlns='http://jabber.org/protocol/pubsub#event'>
    <items node='slave'>
      <item id='4F1CE379C405'>
        data
</item></items></event></message>

<message xmlns='jabber:client' from='pubsub.localhost' to='slave at localhost
/uuid2'>
  <headers xmlns='http://jabber.org/protocol/shim'/>
  <event xmlns='http://jabber.org/protocol/pubsub#event'>
    <items node='slave'>
      <item id='4F1CE379C405'>
        data
</item></items></event></message>

Node config:

    'pubsub#notify_retract': '0',
    'pubsub#persist_items': '0',
    'pubsub#publish_model': 'open',
    'pubsub#access_model': 'whitelist',
    'pubsub#send_last_published_item': 'never',
    'pubsub#notification_type': 'normal'


On Mon, Feb 1, 2010 at 12:02 AM, Liam <ejabberd at networkimprov.net> wrote:

> >Make sure you're subscribing with the resource in the jid attribute
>
> I am. One detail: the name of the node is the same as that of the user.
>
>
>
> On Sun, Jan 31, 2010 at 5:57 PM, Liam <ejabberd at networkimprov.net> wrote:
>
>> 2.1.1 on WinXP...
>>
>> I subscribe a user to a node twice with separate resource ids, e.g.
>> liam at localhost/123 liam at localhost/456
>>
>> When connected from one of those resources, a published item is delivered
>> twice to it.
>>
>> Bug? Misconfiguration?
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.jabber.ru/pipermail/ejabberd/attachments/20100201/9a314596/attachment.html>


More information about the ejabberd mailing list