Hello Christian, It seems related to the FF, I'm using ANSI strings. A quote from StackOverflow:
[1] > > - Opera uses UTF-8; > > > - IE uses the system's default codepage (which you have no way of > knowing, other than it's never UTF-8), and silently mangles characters that > don't fit into to it using the Windows ‘guess a random character that looks > a bit like the one you wanted or maybe just not’ secret recipe; > > > - Mozilla uses only the lower byte of character codepoints, which has > the effect of encoding to ISO-8859-1 and mangling the non-8859-1 characters > irretrievably... except when doing XMLHttpRequests, in which case it uses > UTF-8; > > > - Safari and Chrome encode to ISO-8859-1, and fail to send the > authorization header at all when a non-8859-1 character is used. > > I'm not sure what encoding each browser uses in the real string, so I'll recomend the user to use only ASCII. My only concern would be problem using special characters in the password, but fortunately it works fine there in all browsers. :-) Thank you and happy hacking! [1] http://stackoverflow.com/questions/702629/utf-8-characters-mangled-in-http-basic-auth-username On Sun, Mar 13, 2016 at 10:39 AM, Christian Grothoff <[email protected]> wrote: > My best guess is that it could be a case of character set missmatch > (i.e. UTF-8 vs. ISOxxxx). You should check which charset you're using > to encode passphrases in your code and what charset FF used to send the > password (in particular use Wireshark or some other network capture tool > to look at the exact data being exchanged), and see if converting fixes > the issue. At least that seems to me to be the most likely candidate > for the cause. If you find out what happens, please let us know! > > Happy hacking! > > Christian -- Silvio Clécio
