If accessing http://www.צה.com, error message lacks URL

VERIFIED WORKSFORME

Status

()

Core
Internationalization
VERIFIED WORKSFORME
16 years ago
16 years ago

People

(Reporter: Junk_HbJ, Assigned: nhottanscp)

Tracking

({intl})

Trunk
mozilla1.2alpha
x86
All
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

16 years ago
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9) Gecko/20010505
BuildID:    2001051403

If you click onto http://www.צה.com, you get the error message "www..com could
not be found."

Reproducible: Always
Steps to Reproduce:
1. Click onto http://www.צה.com

Actual Results:  Error message "www..com could not be found ..."

Expected Results:  Error message "www.צה.com could not be found ..."

This is a spinoff of bug 80942.

Comment 1

16 years ago
Confirmed.

Please note that 'å', 'ä' and 'ö' are all valid characters in .nu domain names.

CC some networking people too...
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: mozilla1.0
OS: Windows 98 → All

Comment 2

16 years ago
reassigning to gagan.  part of URI cleanup/iDNS work.  
Assignee: nhotta → gagan
(Assignee)

Updated

16 years ago
Keywords: intl

Updated

16 years ago
QA Contact: andreasb → jonrubin

Comment 3

16 years ago
I think this is a direct result of bug 81024
Depends on: 81024

Comment 4

16 years ago
->neeti
Assignee: gagan → neeti
Target Milestone: --- → mozilla1.0

Comment 5

16 years ago
mass change, switching qa contact from jonrubin to ruixu.
QA Contact: jonrubin → ruixu
(Reporter)

Comment 6

16 years ago
We have a nice change here: The error message is now:
"www.%C3%B6%C3%A4.com could not be found".

Comment 7

16 years ago
the cause of this new problem is the fix for bug 110418, which was an essential
security fix.  this may simply be a duplicate of the problem now reported in bug
42898.

cc'ing william tan.

Comment 8

16 years ago
-> nhotta
Assignee: neeti → nhotta
(Assignee)

Updated

16 years ago
Target Milestone: mozilla1.0 → mozilla1.2

Comment 9

16 years ago
This is fixed by attachment 71035 [details] in bug 124042.
Depends on: 124042
No longer depends on: 81024

Comment 10

16 years ago
I see the correct error message using 2002030403 on Win2K.
(Assignee)

Updated

16 years ago
Status: NEW → ASSIGNED

Comment 11

16 years ago
wfm using 2002032003 on win2k
Status: ASSIGNED → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → WORKSFORME

Comment 12

16 years ago
It can not be reproduced with 20020322 trunk builds on Windows, Mac and Linux.
Verified.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.