Closed
Bug 576949
Opened 14 years ago
Closed 13 years ago
Proxy authentication with i18n login error
Categories
(Firefox :: General, defect)
Tracking
()
People
(Reporter: alexander.voropay, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9.1.9) Gecko/20100315 Firefox/3.5.9 (.NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; ru; rv:1.9.2.6) Gecko/20100625 Firefox/3.6.6 I'm trying to use Firefox/Windows with SQUID proxy and Basic authentication. Due to our organization policy we have to use full user's names in international (i18n) encoding (Russian Cyrillic in our case). Unfortunately, Firefox sends user authentication in Russian Cyrillic (as answer for proxy's 407) in VEIRD chrset encoding. HTTP request to proxy with authentification: ============= User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; ru; rv:1.9.2.6) Gecko/20100625 Firefox/3.6.6 Accept: text/css,*/*;q=0.1 Accept-Language: ru,en-us;q=0.7,en;q=0.3 Accept-Encoding: gzip,deflate Accept-Charset: windows-1251,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Proxy-Connection: keep-alive Proxy-Authorization: Basic EDQ8OD04QUJAMEI+QDpGbHZieQ== ========= Autorization decoding: $ echo EDQ8OD04QUJAMEI+QDpGbHZieQ== | base64 -d | od -t x1 0000000 10 34 3c 38 3d 38 41 42 40 30 42 3e 40 3a 46 6c 0000020 76 62 79 0000023 The name:pass entered was Adminstraror:admin (where Administrator is in Russian) The name becomes junk, seems a second byte from the the UTF-8 w/o high bit. Other browsers, Google Chome as exampe, use UTF-8 for username encoding: ================== User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/533.4 (KHTML, like Gecko) Chrome/5.0.375.99 Safari/533.4 Proxy-Authorization: Basic 0JDQtNC80LjQvdC40YHRgtGA0LDRgtC+0YA6YWRtaW4= Accept: text/css,*/*;q=0.1 Accept-Encoding: gzip,deflate,sdch Accept-Language: ru-RU,ru;q=0.8,en-US;q=0.6,en;q=0.4 Accept-Charset: windows-1251,utf-8;q=0.7,*;q=0.3 ================== $ echo 0JDQtNC80LjQvdC40YHRgtGA0LDRgtC+0YA6YWRtaW4= | base64 -d | od -t x1 0000000 d0 90 d0 b4 d0 bc d0 b8 d0 bd d0 b8 d1 81 d1 82 0000020 d1 80 d0 b0 d1 82 d0 be d1 80 3a 61 64 6d 69 6e 0000040 Chrome uses good Cyrillic in UTF-8 as you see. Reproducible: Always Steps to Reproduce: 1. Use proxy with Basic authentication 2. Enter i18n name as porxy login Actual Results: Wrong encoding Expected Results: UTF-8 or Windows local CodePage
Reporter | ||
Updated•14 years ago
|
OS: Windows XP → Windows 7
Reporter | ||
Comment 1•14 years ago
|
||
Yeah, i've sent this request from my notebook with Firefox/3.5.9 while my test machine uses Firefox/3.6.6
Updated•13 years ago
|
Version: unspecified → 3.6 Branch
Comment 2•13 years ago
|
||
Dupe of bug 41489, but everybody is very weary with the UTF-8 encoding, as there are problems with backwards compatibility and such.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•