IDN does not resolve to correct names in all cases - external links such as css and favicon.ico

VERIFIED WORKSFORME

Status

()

Core
Internationalization
VERIFIED WORKSFORME
15 years ago
14 years ago

People

(Reporter: Patrik Wallström, Assigned: smontagu)

Tracking

Trunk
x86
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030704 Debian/1.4-1
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030704 Debian/1.4-1

When accessing an IDN named page, for example http://www.räksmörgås.se/ (the
content is about to be changed), the css and favicon.ico links resolves to UTF-8
coded links instead of ACE-coded links. The result of this is that external css
files does not work, neither does favicon.ico.

Reproducible: Always

Steps to Reproduce:
1. Surf to http://www.räksmörgås.se/
2. View info on that page
3. Notice the broken stylesheet and favicon.ico



Expected Results:  
Use ACE-coded names instead of UTF-8, and converted those names to readable names.

Comment 1

15 years ago
bug 191388 ?
Um... The page loads fine in a current build.  Page info shows the right urls. 
With an older build I do see the problem...

I bet bug 166996 fixed this.  Please retest with a current nightly.

Comment 3

15 years ago
WFM 20030710 winxp firebird trunk.
(Reporter)

Comment 4

15 years ago
With build "Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030714
Debian/1.4-2" it still behaves odd. No stylesheet or favicon is loaded while the
loaded page is an IDN URL.

http://www.räksmörgås.se/

Press the two links at the end of the page for demonstration.
The two links show identical results with a current trunk build.  Please test a
mozilla.org build, not a Debian one -- the Debian Mozilla package maintainers
often make changes to the version they distribute, and these changes sometimes
break things.

Comment 6

14 years ago
Patrik Wallström, are you satisfied that Mozilla is handling this situation 
correctly?  If so, please mark this bug   Resolved|WorksForMe
(Reporter)

Updated

14 years ago
Status: UNCONFIRMED → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → FIXED
no patch known
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
-> worksforme
Status: UNCONFIRMED → RESOLVED
Last Resolved: 14 years ago14 years ago
Resolution: --- → WORKSFORME

Updated

14 years ago
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.