Red Hat Bugzilla – Bug 278301
pidgin loads firefox with wrong url when domain name is internationalized
Last modified: 2007-11-30 17:07:47 EST
Description of problem:
When opening url to a website from pidgin, firefox fails to load the correct url
when domain name contains non ascii characters.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. In pidgin send a message containing "http://www.ÑÐ²Ð°Ñ‚Ð±Ð°Ñ‚Ð°.com/". This is
domain name in cyrillic.
2. The other person in the conversation receives the message and it is
recognised as hyperlink. I can read the cyrillic text and click on the link.
3. Firefox loads with url:
http://www.%d1%81%d0%b2%d0%b0%d1%82%d0%b1%d0%b0%d1%82%d0%b0.com which looks like
url encoded cyrillic string.
4. The correct url is: http://www.xn--80aaacd3gjc.com/
5. If written directly in Firefox address bar in cyrillic this domain name is
translated correctly and page loads.
pidgin starts Firefox with url encoded cyrillic string. Firefox fails to load
the page since it's not an IDN and it's not translated.
Firefox is started with correct parameter and translates the IDN to the actual
value as it does when user types the address manually.
This request was evaluated by Red Hat Product Management for
inclusion in a Red Hat Enterprise Linux release. Since this
bugzilla is in a component that is not approved for the current
release, it has been closed with resolution deferred. You may
reopen this bugzilla for consideration in the next release.
The correct behavior of pidgin would need to be translating the unicode into IDN
before passing it as a parameter to the web browser.
Please file a bug with upstream for them to consider support of IDN translation,
or a suggested patch if you have a proposed solution. We will only ship fixes
that are accepted by upstream.
This however might make pidgin vulnerable to the IDN spoofing phishing security
hole. There is an important security reason why IDN display was disabled in web
browsers. It is too easy to fool someone into clicking something that appears
to be one address when it is really something different.
(In reply to comment #2)
> Please file a bug with upstream for them to consider support of IDN translation.
Unfortunately their server can't handle the load. I will retry later to file
Filed upstream at http://developer.pidgin.im/ticket/3445