Re: server variables with international (accented) characters

Context.User is set with FormsAuth.

you can try this sample page to verify the values:
http://www.leastprivilege.com/ShowContextsASPXASMX.aspx

-----
Dominick Baier (http://www.leastprivilege.com)

Dominick,

Thank you for the answer. For various reasons we need to use
FormAuthentication and LOGON_USER server variable in our application.
Request.LogonUserIdentity and Context.UserIdentity are not set in this
case.

However, my problem is not that LOGON_USER doesn't carry the
information I need - it does contain the domain user name. This name
is just stripped from all accented characters so instead of
"'QA\größer1" I'm getting "QA\grer1". I don't think this is right
behavior and my question was does anybody know why it may happen and
what, if anything, could be done to fix this.

Thank you
MKouts
"Dominick Baier" wrote:

you shouldn't rely on server variables - they are implementation
details.

You get the IIS authentication outcome from Request.LogonUserIdentity
and the ASP.NET client from Context.User.Identitiy.

-----
Dominick Baier (http://www.leastprivilege.com)
Hi,

It looks like "LOGON_USER" server variable gets stripped of all
accented characters when queried in ASP.NET through:

Request.ServerVariables.Get( "LOGON_USER" )

The same server variable for the same type of HTTP request contains
proper domain user name string with accented characters when
inspected in another non-.NET ISAPI dll.

I could not find anyone else reporting this behavior so could it be
a machine specific ASP.NET configuration issue?



.

Quantcast