It would still seem to be a bug though that its responding to nodes that do not really exist, it should only be responding with the full server details when the node attribute is not present, if it is there and the server does not understand the particular node it should be returning a "not found" error.

Dnia 2008-03-17, pon o godzinie 05:22 -0700, NehaP pisze:
I am referring to the XEP 0013 specification. The spec mentions the
following [...]

Well...
$ grep 0013 README.protocol XEP-0013 Flexible Offline Message Retrieval -

The server does not advertise
<feature var='http://jabber.org/protocol/offline'/> on disco#info.

So... jabberd 2.1.23 does not support XEP-0013.




Reply via email to