From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; m18) Gecko/20000929 Netscape6/6.0b3 BuildID: 2000092908 Reproducible: Always Steps to Reproduce: Actual Results: Expected Results: Please do NOT %-encode domain names. Use UTF-8 directly instead. Similarly, the "file name part" should use UTF-8 directly. Ideally, the entire URL should be in UTF-8 directly, including form field data.

Could you specify a spec for that?

Quoting a mail message from keka@im.se. > I'm not sure if you're referring to the entire bug report, > or just the quoted part... > > Using %-encoding for domain names is just plain wrong. > There is no specification supporting such practice. > Ideally, using UTF-8 for domain names will be (part of) > the future for domain names, though there is much discussion > in the IETF IDN working group about various "ASCII-ified" > Unicode domain names (sort of similar to BASE64, or Quoted- > printable). None has been decided upon, and ideally that > will only be transitional. UTF-8 actually work, now(!) in > domain names for web pages. Yes, in practice. Set IE 5 (...) > to "always send URLs in UTF-8", and check out the > internationalised domain names that you can find links to > under http://whats.nu. (Yes, they've added a fix so that > your %-encoded domain names work too, but nobody is heading > that way.) > > There is no spec, or real plan, that I know of for UTF-8 > in the "file name part" of a http URL; but there is prior > art (in IE 5...). For ftp file names there is a spec., > RFC 2640, that recommends support for file names in UTF-8 > (see clause 3.1 of RFC 2640, FTP Internationalisation). > > /Kent Karlsson

There is already a bug file for this issue, so mark this as a dup. *** This bug has been marked as a duplicate of 43852 ***

Verified as dup.