What steps will reproduce the problem?
1. Send a Disco Info request to a JabberClient running CapsManager for no-
node.
2. Send a Disco Info request to a JabberClient running CapsManager for
node="the#caps#manager#hash".
For both responses, the node is set to "the#caps#manager#hash", when it
should be left blank for the first case.
This prevents requestors from seeing valid information on the nodeless JID.
To fix, comment out : info.Node = NodeVer in CapsManager.cs's IQ handler.
Original issue reported on code.google.com by jcpst...@gmail.com on 4 Aug 2008 at 7:59
Original issue reported on code.google.com by
jcpst...@gmail.com
on 4 Aug 2008 at 7:59