tigase doesn't validate value for the type='subscription' (#47)

Wojciech Kapcia (Tigase) opened 1 decade ago

If the type is "subscription", then the 'value' attribute MUST be one of "both", "to", "from", or "none" as defined RFC 3921, where "none" includes entities that are totally unknown to the user and therefore not in the user's roster at all. These values are exact matches, so that "both" means a bidirectional subscription (not "from" or "to" only).

Parent Issue
- XEP-0016: Privacy Lists (#45) Closed

Activities

Artur Hefczyc commented 1 decade ago

More details is needed on this issue. Could you please provide some information what part of the code this ticket is referring to or what is the use case or steps to replicate problem.
Artur Hefczyc commented 1 decade ago

Never mind, I just noticed the parent task is privacy lists so now I know what it is about. Pushed to version 5.2.x
Andrzej Wójcik (Tigase) commented 1 decade ago

Added validation of added/updated privacy list
Login to comment

Type	Bug
Priority	Normal
Assignee	Wojciech Kapcia (Tigase)
RedmineID	115
Version	tigase-server-5.2.0
Estimation	0
Spent time	0

Issue Votes (0)

Watchers (0)

Reference

tigase/_server/server-core#47