MUC accepts joining room with incorrect value for since attribute in history element (#106)

Andrzej Wójcik (Tigase) opened 7 years ago

MUC accepts joining a room with incorrect value for since attribute in history element. In this case, it assumes that since attribute was not set and creates confusion. If the value for the attribute is incorrect (not parsable), the component should respond with bad-request error.

Related
- Cannot join to room with Swift (#108) In QA

Activities

Andrzej Wójcik (Tigase) commented 7 years ago

I've added validation for all history attributes and code sending proper errors. I've disabled by default sending timestamp in the message in legacy delay format - XEP-0091. (this can be enabled). I've added a test case to confirm that verification of history attributes works properly.

I still need to add information to documentation about to how to enable legacy delay timestamps.
Andrzej Wójcik (Tigase) commented 7 years ago

Documentation added.
Login to comment

Type	Bug
Priority	Normal
Assignee	Wojciech Kapcia (Tigase)
RedmineID	7443
Version	tigase-server-8.0.0rc1

Issue Votes (0)

Watchers (0)

Reference

tigase/_server/tigase-muc#106