Projects tigase _server server-core Issues #31
Roster item with uppercase characters (#31)
Artur Hefczyc opened 1 decade ago
Due Date
2011-03-04

There appears to be a problem with the roster management if the item contains uppercase characters. The roster item seems to be removed correctly from the protocol point of view but it is still preserved in the database.

Hmmm, OK then I have another quick question that maybe you can take a look at while I collect the other XML data.

This is a roster remove of a user that doesn't exist in the database, but was added to the roster (I don't have the "add" XML but I can re-do and collect).

The "remove" XML:

SEND >>>>>>>>>>>>>>>> : Thu Jan 1 02:43:33 1970

<query xmlns="jabber:iq:roster">

  <item jid="aaaah@example.com" subscription="remove"/>

</query>

[9813.091552] CALL: [InfoQueryOutTask::ProcessStart] exit

RECV <<<<<<<<<<<<<<<< : Thu Jan 1 02:43:33 1970

RECV <<<<<<<<<<<<<<<< : Thu Jan 1 02:43:33 1970

<query xmlns="jabber:iq:roster">

  <item jid="aaaah@example.com" subscription="remove"/>

</query>

Here is the database after the remove

mysql> select nid,uid,pkey,pval from tig_pairs where pkey="roster" and uid=TigGetUserUID('cds3@example.com');

+------+-----+--------+----------------------------------------------------------------------------------------+

| nid | uid | pkey | pval | +------+-----+--------+----------------------------------------------------------------------------------------+

| 89 | 67 | roster | | +------+-----+--------+----------------------------------------------------------------------------------------+

1 row in set (0.00 sec)

Artur Hefczyc commented 1 decade ago

Nothing to do this time. Must have been fixed a while ago. Tested with TTS and it works correctly. Added a new test to TTS for future checking.

issue 1 of 1
Type
Bug
Priority
Normal
Assignee
RedmineID
67
Version
tigase-server-5.2.0
Estimation
8h
Issue Votes (0)
Watchers (0)
Reference
tigase/_server/server-core#31
Please wait...
Page is in error, reload to recover