https://bugs.kde.org/show_bug.cgi?id=358048
Bug ID: 358048
Summary: URL parser doesn't handle edge cases well
Product: telepathy
Version: git-latest
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: common-internals
Assignee: kde-telepathy-b...@kde.org
Reporter: k...@kdex.de
The current implementation doesn't play well with URLs that contain a trailing
dot:
https://example.com/users/example.
is wrongly parsed as
https://example.com/users/example
and
https://example.com/users/example?
is, too, wrongly parsed as:
https://example.com/users/example
The relevance of the latter case is debatable, since in URLS, "?" commonly only
serves as a delimiter in front of the GET arguments. So, not parsing it
shouldn't make a difference to the URL pointed to.
The period, on the other hand, makes a drastic difference, since this is a
quite common character allowed in usernames for a lot of websites. Since most
RESTful websites have URL schemes such as `/users/${username}`, this completely
breaks the ability to freely link to your user page (which is how I found this
bug).
Reproducible: Always
Steps to Reproduce:
1. Open a KTp conversation.
2. Send a URL to somebody that ends with "." or "?".
Actual Results:
The characters "." and "?" aren't parsed, although they are valid URLs.
Expected Results:
The parser should match these characters, too.
--
You are receiving this mail because:
You are watching all bug changes.
