Bug 379195 - Konversation can't handle IDN urls
Summary: Konversation can't handle IDN urls
Status: RESOLVED NOT A BUG
Alias: None
Product: konversation
Classification: Applications
Component: general (show other bugs)
Version: 1.6
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Konversation Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-04-25 13:53 UTC by bugs5.kde.org
Modified: 2017-04-25 16:08 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description bugs5.kde.org 2017-04-25 13:53:29 UTC 
Well, I just read an article about IDN urls and how they are used for phishing. One of the examples given was https://www.xn--80ak6aa92e.com/ (not apple) which shows in some browsers as apple.com.

Anway, when I paste that url in Konversation and click on it to open it, an error message pops up:

Malformed URL
Invalid hostname (contains invalid characters); source was "https://www..com/"; scheme = "https", host = "", path = "/"


The URL is correct but it seems Konversation can't handle IDN urls properly.
Comment 1 Peter Simonsson 2017-04-25 15:21:21 UTC 
So far it seems the problem is QUrl::toEncoded() not returning the punycoded url
Comment 2 Peter Simonsson 2017-04-25 16:08:36 UTC 
Seems it's some form of phishing protection in QUrl that kicks in as other punycode urls works fine. For example http://xn--6kry05bl4a.no works fine. So I'll close this one as phishing isn't really a good usecase. ;)