Andrzej Wójcik (Tigase) opened 4 years ago
|
|
The issue is actually a little more complex. According to XEP-0030 it is possible to query any item returned by However, XEP-0030 provides a way to limit queries (to inform client that query for info of a PubSub node item is not supported) by adding to the PubSub node The solution here is to add to PubSub support for identity of category @bmalkow I think this will solve your issue which you have seen in BeagleIM when it was possible to expand items which would list all PubSub nodes leading to the infinite loop of nodes and items. |
|
@andrzej.wojcik after our discussion (and your example about running a query against main server domain) it occurred to me that we may review our handling of discovery and add those identities in all relevant places (if missing) and not only in pubsub. And one more comment - we do currently already send |
|
If I'm correct, we have done everything we could on the server side and the issue was fixed in BeagleIM by adding a few checks. |
|
AFAIR the idea was to add (as mentioned in https://xmpp.org/extensions/xep-0030.html#items-hierarchy) category identity for collections and leafs: I'm not sure if there are other places that may require it (MUC comes to mind, but AFAIR Bartosz made some fixes a while back and most likely it's handled correctly, but checking it out wouldn't hurt) |
|
As I've checked, MUC works fine and hierarchy was added to PubSub already. |
Type |
Bug
|
Priority |
Normal
|
Assignee | |
Version |
tigase-server-8.2.0
|
Spent time |
2h 45m
|
There is nothing more inside PubSub node item, so it should not return
disco#items
as a supported feature. Currently, as it is returned, clients think that they should query subitems and as PubSub node item has nonode
attribute in disco result are quering PubSub component nodes once again.