Swiftdiff options
| author | Edwin Mons <edwin.mons@isode.com> | 2018-04-18 15:12:35 (GMT) |
|---|---|---|
| committer | Edwin Mons <edwin.mons@isode.com> | 2018-04-18 15:12:35 (GMT) |
| commit | 8fe63ff4b47cfa3b1e988f348b34ac7d36ce7b9b (patch) | |
| tree | ad8808aa5fda08174dc0f5f54540f621c471d513 /3rdParty/Boost/src/boost/config | |
| parent | fa2c9c62260ad793edf7082922d4ccda2a9564d8 (diff) | |
| download | swift-8fe63ff4b47cfa3b1e988f348b34ac7d36ce7b9b.zip swift-8fe63ff4b47cfa3b1e988f348b34ac7d36ce7b9b.tar.bz2 | |
Mark jids with an empty domainpart as invalid
When Swiften parsed jids with an empty domainpart (e.g. user@/resource),
it would mark the jid as valid, and treat the localpart as domainpart.
RFC 6122 states in 2.2 that "A domainpart MUST NOT be zero bytes in
length".
Unit tests for both a bare jid and a full jid with an empty domainpart
have been added.
Test-Information:
Unit tests pass on Debian 9
Change-Id: Iadaf399cd4158666bfcdd6c075b8bf2102ff5538
Diffstat (limited to '3rdParty/Boost/src/boost/config')
0 files changed, 0 insertions, 0 deletions