HttpContext.Current.User is it unique?

[Sjaakie]

Hi,

Is HttpContext.Current.User unique for each visitor or is it shared
across an application?

Have some problems that might have to do with this and found
contradictory answers on this question.

Thanks!

[Chris S.]

It's taken from HTTP headers (the docs say HTTP request), so yes it
should be unique and will be taken from IIS's authentication.

[Sjaakie]

Chris S. > It's taken from HTTP headers (the docs say HTTP request), so
yes it

should be unique and will be taken from IIS's authentication.

Thanks.
Although it didn't solve my problem I now know where not to look.

[Vadym Stetsyak]

HttpContext represents the context of particular Http request.
User property is responsible for authorized visitors. That is if users load web app with anonymous auth.

Then afaik you will have the same user, but many visitors.

You can use Session property of Page class. Session is unique for each visitor. A combination if Session and HttpContext can be used
to distinguish between visitors with the same auth.

--
Vadym Stetsyak aka Vadmyst
http://vadmyst.blogspot.com

"Sjaakie" <ke**@secret.it> wrote in message news:43***********************@news.xs4all.nl...

Hi,

Is HttpContext.Current.User unique for each visitor or is it shared
across an application?

Have some problems that might have to do with this and found
contradictory answers on this question.

Thanks!

[John Timney \( MVP \)]

The context is unique to the current request and bound to each individual
user session when the request begins, until the request completes and the
response is returned when the context then goes out of scope.
--
Regards

John Timney
Microsoft MVP

"Sjaakie" <ke**@secret.it> wrote in message
news:43***********************@news.xs4all.nl...

Hi,

Is HttpContext.Current.User unique for each visitor or is it shared across
an application?

Have some problems that might have to do with this and found contradictory
answers on this question.

Thanks!

[Chris S.]

It's taken from a HTTP header as the headers collection will show you.

[Sjaakie]

Chris S. schreef:

It's taken from HTTP headers (the docs say HTTP request), so yes it
should be unique and will be taken from IIS's authentication.

Maybe you have a clue what's causing this ...

I built a site with custom formsauthentication which acts pretty weird
for some people. These (3) people have in common that their surnames are
'Doe' and that all 3 live in Hong Kong. Login, email and passwords differ.
Authentication is based on a combination of login and password. If both
match with values in database an authenticationticket is generated and
stored into a cookie.

Userdetails are queried from the database using
HttpContext.Current.User.Identity.Name-value as login. Which should be
the login of the current user.
Somehow these 3 people all see the userdetails of one particular mister
Doe. Checked my procedures multiple times to make sure I didn't store
credentials into the application cache, which wasn't the case.

Could it be possible the server is caching the Identity.Name?
Or could this have to do with some sort of proxy-server?
Or something else....