Session ID with multiple browsers

[jack_c_brinegar]

I am trying to identify a problem that has just been reported to our
team. It seems that when a user opens 2 browsers, and with the second
browser, the user logs into our web application (ASP.NET), then the
session for that browser is not transferred to any new browsers that
are spawned using the javascript window.open statement.

However, if the user logs into the web app using the first browser
instance (not the second), then all is fine.

In debugging, we can see the SessionID and it seems that the browser
that is created use the Session from the first browser. What are we
doing wrong?

Any ideas/help would be great.

[Brock Allen]

You're not going to like this, but I typically recommend to not use Sesison
state if possible. If you are going to use it, then you need to code it in
such a way to avoid the multiple browser issue. IOW, write the code to assume
the user always has 2 (or 3 or 4) browsers open.

-Brock
DevelopMentor
http://staff.develop.com/ballen

I am trying to identify a problem that has just been reported to our
team. It seems that when a user opens 2 browsers, and with the second
browser, the user logs into our web application (ASP.NET), then the
session for that browser is not transferred to any new browsers that
are spawned using the javascript window.open statement.

However, if the user logs into the web app using the first browser
instance (not the second), then all is fine.

In debugging, we can see the SessionID and it seems that the browser
that is created use the Session from the first browser. What are we
doing wrong?

Any ideas/help would be great.

[Robbe Morris [C# MVP]]

Correct. When you open a new browser window without
it coming from a page in your app, a new browser session
is created. It works this way with most browsers.

--
2004 and 2005 Microsoft MVP C#
Robbe Morris
http://www.masterado.net

Earn $$$ money answering .NET Framework
messageboard posts at EggHeadCafe.com.
http://www.eggheadcafe.com/forums/merit.asp

<ja*************@uhc.com> wrote in message
news:11*********************@g47g2000cwa.googlegro ups.com...

I am trying to identify a problem that has just been reported to our
team. It seems that when a user opens 2 browsers, and with the second
browser, the user logs into our web application (ASP.NET), then the
session for that browser is not transferred to any new browsers that
are spawned using the javascript window.open statement.

However, if the user logs into the web app using the first browser
instance (not the second), then all is fine.

In debugging, we can see the SessionID and it seems that the browser
that is created use the Session from the first browser. What are we
doing wrong?

Any ideas/help would be great.

[Robbe Morris [C# MVP]]

Correct. When you open a new browser window without
it coming from a page in your app, a new browser session
is created. It works this way with most browsers.

--
2004 and 2005 Microsoft MVP C#
Robbe Morris
http://www.masterado.net

Earn $$$ money answering .NET Framework
messageboard posts at EggHeadCafe.com.
http://www.eggheadcafe.com/forums/merit.asp

<ja*************@uhc.com> wrote in message
news:11*********************@g47g2000cwa.googlegro ups.com...

I am trying to identify a problem that has just been reported to our
team. It seems that when a user opens 2 browsers, and with the second
browser, the user logs into our web application (ASP.NET), then the
session for that browser is not transferred to any new browsers that
are spawned using the javascript window.open statement.

However, if the user logs into the web app using the first browser
instance (not the second), then all is fine.

In debugging, we can see the SessionID and it seems that the browser
that is created use the Session from the first browser. What are we
doing wrong?

Any ideas/help would be great.