You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What did not work as expected? Are there error messages in the log? What
was the unexpected behavior? What was the expected result?
I am doing a simple publish-purge-fetch test to ensure that my client implements it correctly. However, the response from ejabberd when I request the deleted item is incorrect. The item is created like this (XML pretty-printed for readability; C->S means client-to-server, S->C means server-to-client):
If there are no items at the node or the requested items do not exist, the service SHOULD return an IQ stanza of type "result" with an empty <items/> element.
I would expect ejabberd to reply with an empty <items/> element as it does for a generic items query:
18.01, 17.12 (docker images)
Linux.
Docker image from https://hub.docker.com/r/ejabberd/ecs/
I am doing a simple publish-purge-fetch test to ensure that my client implements it correctly. However, the response from ejabberd when I request the deleted item is incorrect. The item is created like this (XML pretty-printed for readability;
C->S
means client-to-server,S->C
means server-to-client):Then the node is purged:
And the item is requested to check that the purge has worked:
Now ejabberd unexpectedly replies with an error:
Which is incorrect according to XEP-0060 §6.5.9.12:
I would expect ejabberd to reply with an empty
<items/>
element as it does for a generic items query:The text was updated successfully, but these errors were encountered: