Closed Bug 162571 Opened 22 years ago Closed 21 years ago

IDN: Can't access site with non-ascii char in URI

Categories

(Core :: Internationalization, defect)

Product:
Core
Component:
Internationalization
Platform:
x86
All
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED DUPLICATE of bug 157388

People

(Reporter: hwaara, Assigned: nhottanscp)

References

(
URL
)

Details

(Keywords: helpwanted, intl, qawanted) 

More and more sites are starting to use non-ASCII characters (such as å, ä and
ö) in their domain names.  I can't access these in Mozilla, but I can in IE6.

This is *very* important that it works for us in Europe.
Oh, by the way, I'm using Mozilla 1.0 to test this. (Can't download a later one
right now.)
+qawanted - need to find IDN testser
Keywords: qawanted
Summary: Can't access site with non-ascii char in URI → IDN: Can't access site with non-ascii char in URI
IDN tester? If you tell me how, maybe I can test...
+neeti - do you want to get any l18n people involved?
Keywords: helpwanted
darin, i thought that this was working?
Assignee: new-network-bugs → darin
-> intl
Assignee: darin → yokoyama
Component: Networking → Internationalization
QA Contact: benc → ruixu
reassing to nhotta, depend on bug 112979
Assignee: yokoyama → nhotta
Depends on: 112979
Keywords: intl
QA Contact: ruixu → ylong
I think this is a dup of 112979, not a depend on 112979, right?
Is this related to bug 157388, maybe even a duplicate? Or are the .nu domains
problems with letters like זרו etc. a different case?
Just discovered that the test-case for this bug is a .nu domain too. I must be
sleeping today (just wrote a comment in a wrong bug too). Anyway, I guess this
and 157388 are duplicates?
I agree with the resolution to this problem in bug 112979 and bug 157388: 
Mozilla should support IDNA (as adopted) only.

It appears that .nu supports the adopted IDNA as well, the test URL of this 
report is also accessible as www.xn--hkan-qoa.nu.
resolved as dupe of bug 157388. It works for me.

*** This bug has been marked as a duplicate of 157388 ***
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.