ejabberd - Comments for "2.1 Beta Pubsub invalid-payload"

Fix in progress

Liam — Wed, 21 Oct 2009 23:37:12 +0000

Thanks for resolving this in rc3!

Tracked in

mfoss — Wed, 21 Oct 2009 18:08:18 +0000

Tracked in https://support.process-one.net/browse/EJAB-1083

I paste here initial replies

mfoss — Wed, 21 Oct 2009 17:11:52 +0000

I paste here initial replies provided by Christophe Romain. If they don't solve the questions, you can submit your questions as tickets in the bug tracker, and they will get more detailed analysis.

Replies:

1) pubsub#type was, at the begining of plugin implementation, mapped with node plugin name. I think this is not used anymore. I'd have to check this. pubsub#type is allowed in form. I just think it's informative only (not linked with anything).

2) Not including plain text.

3) Multiple items is bad idea and I think this have been removed in 1.13

Pubsub bug reports

Liam — Tue, 20 Oct 2009 23:41:14 +0000

In 2.1.0-rc1...

1) The node config form does not include <field var='pubsub#type'/> -- let alone define that as Atom. The pubsub module should allow configuring this field.

2) The pubsub spec doesn't specify Atom as the default node namespace. The spec is silent on what payload namespaces are allowed if pubsub#type is undefined, but the obvious answer is ANY, including plain text. The pubsub module should allow that.

3) The spec permits multiple <item> elements in a publish request, and that doesn't work for me in rc1.

SOLVED

Chris Hagan — Wed, 02 Sep 2009 05:43:46 +0000

We have now successfully published against 2.1.

Turns out the issue was that the item node must contain an entry node, the namespace of which must explicitly be 'http://www.w3.org/2005/Atom'. This is confusing, as the XEP0060 error spec goes:

<iq type='error'
    from='pubsub.shakespeare.lit'
    to='hamlet@denmark.lit/elsinore'
    id='publish1'>
  <pubsub xmlns='http://jabber.org/protocol/pubsub'>
    <publish node='princely_musings'>
      <item id='ae890ac52d0df67ed7cfdf51b644e901'>
        ... INVALID PAYLOAD ...
      </item>
    </publish>
  </pubsub>
  <error type='modify'>
    <bad-request xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/>
    <invalid-payload xmlns='http://jabber.org/protocol/pubsub#errors'/>
  </error>
</iq>

It would be more informative to a beginner like me to have it read:

<iq type='error'
    from='pubsub.shakespeare.lit'
    to='hamlet@denmark.lit/elsinore'
    id='publish1'>
  <pubsub xmlns='http://jabber.org/protocol/pubsub'>
    <publish node='princely_musings'>
      <item id='ae890ac52d0df67ed7cfdf51b644e901'>
         <entry xmlns='...INVALID NAMESPACE...'>
            ...INVALID PAYLOAD...
         </entry>
      </item>
    </publish>
  </pubsub>
  <error type='modify'>
    <bad-request xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/>
    <invalid-payload xmlns='http://jabber.org/protocol/pubsub#errors'/>
  </error>
</iq>

Anyway, that's fixed. Thanks to everyone who looked on and particularly to badlop for helping.

Thanks, I'll try that this

Chris Hagan — Wed, 02 Sep 2009 03:29:48 +0000

Thanks, I'll try that this morning.

(Later that morning):

Following the example you provided, I've changed my pubsub config to 'flat', so that now the node name is simply "/mr0". The node is created without error and is discoverable through Psi. However trying to publish to it (using agsXmpp) sends the stanza:

<iq id="agsXMPP_5" type="set" to="pubsub.civic.adm.monash.edu"><pubsub xmlns="http://jabber.org/protocol/pubsub"><publish node="mr0"><item>0:STROKE</item></publish></pubsub></iq>

Which elicits a response of:

<iq xmlns="jabber:client" type="error" from="pubsub.civic.adm.monash.edu" to="0@civic.adm.monash.edu/agsXMPP" xml:lang="en" id="agsXMPP_5"><pubsub xmlns="http://jabber.org/protocol/pubsub"><publish node="mr0"><item>0:STROKE</item></publish></pubsub><error type="modify" code="400"><bad-request xmlns="urn:ietf:params:xml:ns:xmpp-stanzas" /><invalid-payload xmlns="http://jabber.org/protocol/pubsub#errors" /></error></iq>

This seems to me to be behaving the same way as before. Is my publish stanza correctly constructed? Thanks for your help.

EDIT:

By changing my node in the publish tag to "pubsub.civic.adm.monash.edu/mr0" the error has become a 404: Item not found. I'm not sure whether this is an improvement, but it certainly seems that the earier error is pretty much the response to any nonsensical item; a stanza whose node is "NONSENSE" will result in the same 400, for instance, so the 404 seems like it might be better?

EDIT:

Probably not an improvement. None of the tutorials use qualified node names. Also the XEP doesn't mention 404s, although the meaning is fairly clear.

A similar example works for

mfoss — Tue, 01 Sep 2009 12:40:24 +0000

A similar example works for me.

I installed ejabberd 2.1.0-beta2, created an account, logged in, and then followed the second example found in
How to use ejabberd's pubsub module. The one that says "Example for 2.1.0 with plugin "flat"."

I have this in ejabberd.cfg

{modules, [
  ...
  {mod_pubsub,   [
                  {access_createnode, pubsub_createnode},
                  {pep_sendlast_offline, false},
                  {last_item_cache, false},
                  {plugins, ["flat", "pep"]}
                 ]},
  ...
]}.

In your case, as you want to continue using the "/home/SERVER/USERNAME" paths, you can add this plugin to the mod_pubsub option: "hometree"