MUC accepts joining room with incorrect value for since attribute in history element
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
#7443: added support for legacy delay timestamp formatting to TimestampHelper
#7443: added validation of presence/x/history element attributes and disabled by default sending timestamps in XEP-0091
#1 Updated by Andrzej Wójcik 12 months ago
- Status changed from New to In Progress
- % Done changed from 0 to 90
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.