#1832 Empty but present "publisher" attribute.

Reporter Werner
Owner Nobody
Stars ★ (1)
  • Compliance
  • Milestone-0.12
  • Status-NeedInfo
  • Priority-Medium
  • Type-Defect
  1. Werner on

    Hello, when sending a message, it appears that the "publisher" attribute on the "item" tag can be present, but not empty. For example, from a trace I received when working with xmpp-rs: [2023-12-03T12:28:11Z DEBUG tokio_xmpp::xmpp_codec] << <message xmlns='jabber:client' from="monk@unboiled.info" id="ct_sNv7I4itFYrf9k0yVHP79" to="mizah@mizah.xyz/VkIKBZNY7gNS" type="headline" xml:lang="en"><event xmlns='http://jabber.org/protocol/pubsub#event'><items node="urn:xmpp:avatar:metadata"><item id="cc46bf25841d73bcb6ab3d832ad9a287f8b06faa" publisher=""><metadata xmlns='urn:xmpp:avatar:metadata'><info bytes="2213" id="cc46bf25841d73bcb6ab3d832ad9a287f8b06faa" type="image/png"/></metadata></item></items></event></message> Note the `publisher=""` See https://xmpp.org/extensions/xep-0060.html#publisher-publish-success-publisher unboiled.info is running Prosody version 0.12.4 on Linux

  2. Werner on

    Correction: publisher attribute can be present, but empty.

  3. Zash on

    Thanks for the report. Could you please include pubsub and which storage backend is used?

    • tags Status-NeedInfo
  4. Zash on

    One plausible explanation I have found if SQL storage is used is that the publisher is stored in a NOT NULL field, which defaults to the empty string.

    • tags Milestone-0.12

New comment

Not published. Used for spam prevention and optional update notifications.