Re: [idn] Web navigation for IDN resolving

["David Leung \(Neteka Inc.\)" <david@neteka.com>]

From our testing results, we found out the same thing too... and worst of
all the new IE6 will DROP all IDN that is not within the locale set in the
regional setting of the OS.

i.e. if you set the locale to Japanese, ONLY characters contain in the
Japanese range will work and all the others will be DROPPED, try setting the
regional settings to say Korean or some other locale and if you have
"Chinese".tw the new IE will only sent .tw!!

We have try to replace the url.dll and urlmon.dll with the previous IE5 dlls
and it works again, we have pinpoint the functions inside these dlls and
send a bug fix report to MS but they still have not fix it yet... I think
this will prohibit the expand of IDN in China and Taiwan.

David Leung
Chief Technology Officer
Neteka Inc.
T: (416) 971-4302
http://w!.neteka.com
----- Original Message -----
From: "Edmon Chung" <edmon@neteka.com>
To: "tsenglm@計網中心.中大.tw" <tsenglm@cc.ncu.edu.tw>; <idn@ops.ietf.org>;
<yves_arrouye@hotmail.com>
Sent: Tuesday, March 26, 2002 10:18 AM
Subject: Re: [idn] Web navigation for IDN resolving


> This is a rather interesting and serious observation.  Does it not
therefore
> mean that RealNames/MS is effectively hijacking all IDN requests through
an
> IE browser?
>
> ----- Original Message -----
> From: "tsenglm@計網中心.中大.tw" <tsenglm@cc.ncu.edu.tw>
> To: <idn@ops.ietf.org>; <yves_arrouye@hotmail.com>
> Sent: Tuesday, March 26, 2002 5:09 AM
> Subject: Re: [idn] Web navigation for IDN resolving
>
>
> > Dear Yves Arrouye:
> >          Thanks your descriptions.   I think this message  from Mr.
> YangWoo
> > Ko (newcat@spsoft.co.kr) is the key point:
> > I am still wondering what "looks like a domain name" means
> >
> > >
> > > The DNS lookup happened *before* the string was URL-encoded and passed
> to
> > > Autosearch, which only happen after a failure.
> >           The ASCII Domain Name (even without dot) will be  put to do
DNS
> > lookup first, but IDN domain name will not . The IDN  will be
intercepted
> to
> > auto.search.msn.com  directly without doing DNS lookup.  That means the
> IDN
> > input with native coded string without http://  protocol head will be
> > interpreted as  "not a legal domain name"  by IE.
> >           The server of  Realname can not found these IDN in non
contract
> > supporting, so it is an error for Realname or IDN resolving, but the
> return
> > error cause the halting of browser will disturb the further regular
> > processing of these UTF-8 IDN.   That is my understanding of these
strange
> > processing to IDN .
> >
> > L.M.Tseng
> >
> >
> >
>
>