|
Andrzej Wójcik (Tigase) opened 5 years ago
|
|
|
@wojtek What if that resource is comming from a remote server over S2S? should we validate that and send an error back over S2S? |
|
As per discussion - we should normalize to Unicode 3.2. |
|
|
I've moved this issue to PubSub as I've confirmed in the email archive that it was related to PubSub. I've added a workaround for MySQL to store only utf8mb3 compatible characters in the participant's field (I've stripped invalid chars only from the resource part). |
| Type |
Bug
|
| Priority |
Normal
|
| Assignee | |
| Version |
tigase-server-8.1.0
|
| Spent time |
2h 15m
|
Issue Votes (0)
Watchers (0)
We could either change the backend to support emoji in resources (which will require a lot of changes to tables and indexes) or we can just forbid users to bind with resources containing emojis.
According to XMPP RFC, only chars from Unicode 3.2 are allowed within the resource part of the JID.
Another solution would be to catch those resources and replace them during bind requests by rejecting resource supplied by client and providing server-generated resource.