Closed
Bug 81019
Opened 24 years ago
Closed 23 years ago
If accessing http://www.צה.com , error message lacks URL
Categories
(Core :: Internationalization, defect)
Tracking
()
VERIFIED
WORKSFORME
mozilla1.2alpha
People
(Reporter: Junk_HbJ, Assigned: nhottanscp)
References
()
Details
(Keywords: intl)
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•24 years ago
|
||
Confirmed.
Please note that 'å', 'ä' and 'ö' are all valid characters in .nu domain names.
CC some networking people too...
Comment 2•24 years ago
|
||
reassigning to gagan. part of URI cleanup/iDNS work.
Assignee: nhotta → gagan
Updated•24 years ago
|
QA Contact: andreasb → jonrubin
Comment 5•23 years ago
|
||
mass change, switching qa contact from jonrubin to ruixu.
QA Contact: jonrubin → ruixu
We have a nice change here: The error message is now:
"www.%C3%B6%C3%A4.com could not be found".
Comment 7•23 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.
Assignee | ||
Updated•23 years ago
|
Target Milestone: mozilla1.0 → mozilla1.2
This is fixed by attachment 71035 [details] in bug 124042.
Comment 10•23 years ago
|
||
I see the correct error message using 2002030403 on Win2K.
Assignee | ||
Updated•23 years ago
|
Status: NEW → ASSIGNED
Comment 11•23 years ago
|
||
wfm using 2002032003 on win2k
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
Comment 12•23 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.
Description
•