Actually, since this is MS I suppose UNICODE means UTF-16LE. Quoting the
referred page:

"""
A Unicode string is a string in which each character is represented as a
16-bit little-endian value (16-bit UCS-2 Transformation Format,
little-endian byte order, with no Byte Order Mark and no null-terminator).
The string "hello" in Unicode would be represented hexidecimally as
"0x680065006c006c006f00".
"""

Regards

- Audun Nordal

-----Original Message-----
From: curl-library-bounces_at_cool.haxx.se
[mailto:curl-library-bounces_at_cool.haxx.se] On Behalf Of Dan Fandrich
Sent: 3. mars 2005 08:02
To: libcurl development
Subject: Re: International Characters in NTLM Usernames

On Wed, Mar 02, 2005 at 06:41:46PM -0800, hep monk wrote:
> Hi Seshu,
>
> I did decode the NTLM type 3 message. It contains the username in exactly
the
> same way that IE does:
>
> fen\xEAtre
>
> where the \xEA means the byte with hex value EA.
>
> Yet, the NTLM handshake doesn't work with libCurl. It's puzzling.
>
>
>
> Seshubabu Pasam <pasam_at_seshubabu.com> wrote:
>
> I am not sure if libCurl is capable of handling non-ASCII chars.
Daniel?
> But since you already sniffed the packets etc, why don't you decode
them?
> The type-3 message should have the user name in it. Take a look at
http://
> davenport.sourceforge.net/ntlm.html to find out the offset of the
username
> in the type-3 message.

This document talks about a "negotiated encoding", "either UNICODE or OEM".
Perhaps libcurl negotiates a different encoding than other browsers. Did
you try sending the username in UTF-8 instead?

>>> Dan

-- 
http://www.MoveAnnouncer.com              The web change of address service
          Let webmasters know that your web site has moved