[Mono-devel-list] Re: [Mono-patches] mcs/class/System.Web/System.Web ChangeLog,1.210,1.211 HttpContext.cs,1.26,1.27

[Sébastien Pouliot]

Hello,

I think this issue is a little more complex. See #59683 for another sample.
The authentication section of the web.config file may change the behaviour
of the property (which would explain the different results).

Sebastien Pouliot
http://pages.infinit.net/ctech/poupou.html


-----Original Message-----
From: mono-devel-list-admin at lists.ximian.com
[mailto:mono-devel-list-admin at lists.ximian.com]On Behalf Of Gonzalo
Paniagua Javier
Sent: 9 juin 2004 16:16
To: Pedro Martinez; Mono Development
Subject: [Mono-devel-list] Re: [Mono-patches]
mcs/class/System.Web/System.Web ChangeLog,1.210,1.211
HttpContext.cs,1.26,1.27


El mié, 09-06-2004 a las 15:27, Pedro Martinez  escribió:
> Update of /cvs/public/mcs/class/System.Web/System.Web
> In directory mono-cvs.ximian.com:/tmp/cvs-serv30119
>
> Modified Files:
> 	ChangeLog HttpContext.cs
> Log Message:
> 2004-06-09  Pedro Martínez Juliá  <yoros at wanadoo.es>
>
>     * HttpContext: User property returns its own "user" value because
>     the context can walk through different Threads. When "User" property
>     is changed, change "Thread.CurrentPrincipal" too.

This patch is wrong. Changing Context.User does not affect the
Thread.CurrentPrincipal, as you can see in the attached simple test
case. I've reverted it.

-Gonzalo