IIS session and IE7

[abcd]

I have asp and asp.net web application. When I run it in IE7 in first tab it
starts a new session. When I open second tab and browse to the same site the
new session is not started (infact I need to have new session there).
Whereas, 2 IE instances generate 2 unique sessions. Only issue is with IE
tabs. Firefox also has similar things but lets not talk about firefox here.
I am more concerned with IE only.

Any tips/tricks/missing knowledge.

[sorry if I have posted this to the wrong audiences]

 

[Evertjan.]

abcd wrote on 17 jan 2007 in microsoft.public.inetserver.asp.general:

I have asp and asp.net web application. When I run it in IE7 in first
tab it starts a new session. When I open second tab and browse to the
same site the new session is not started (infact I need to have new
session there). Whereas, 2 IE instances generate 2 unique sessions.
Only issue is with IE tabs. Firefox also has similar things but lets
not talk about firefox here. I am more concerned with IE only.

Any tips/tricks/missing knowledge.

[sorry if I have posted this to the wrong audiences]

The behavour of cookies in diggerent browsers is a clientside issue,
ASP is strictly serverside code, so how it's session.id cookie is handled
is out of reach of ASP.

The same probably goes for asp.net, but that has it's own NG's, or so they
say, this NG is classic ASP only.

This does not mean, that this tab issue is not important to ASP
programmers, so thank you for mentioning it.

It could be that some clever serverside programming can alliviate the
consequences.

 

[abcd]

Evertjan

I am more interested in Session.sessionid value which is server side thing.
Having a unique session ID matters to the web applications which are already
developed to do so. IE7 tabs does not meet this requirement. I dont know why
it is designed like that. Thats what I am trying to dig.

[Just saying this is not approprate group is not the solution. ]

abcd wrote on 17 jan 2007 in microsoft.public.inetserver.asp.general:

I have asp and asp.net web application. When I run it in IE7 in first
tab it starts a new session. When I open second tab and browse to the
same site the new session is not started (infact I need to have new
session there). Whereas, 2 IE instances generate 2 unique sessions.
Only issue is with IE tabs. Firefox also has similar things but lets
not talk about firefox here. I am more concerned with IE only.

Any tips/tricks/missing knowledge.

[sorry if I have posted this to the wrong audiences]

The behavour of cookies in diggerent browsers is a clientside issue,
ASP is strictly serverside code, so how it's session.id cookie is handled
is out of reach of ASP.

The same probably goes for asp.net, but that has it's own NG's, or so they
say, this NG is classic ASP only.

This does not mean, that this tab issue is not important to ASP
programmers, so thank you for mentioning it.

It could be that some clever serverside programming can alliviate the
consequences.

 

[Evertjan.]

abcd wrote on 17 jan 2007 in microsoft.public.inetserver.asp.general:

abcd wrote on 17 jan 2007 in microsoft.public.inetserver.asp.general:

I have asp and asp.net web application. When I run it in IE7 in
first tab it starts a new session. When I open second tab and browse
to the same site the new session is not started (infact I need to
have new session there). Whereas, 2 IE instances generate 2 unique
sessions. Only issue is with IE tabs. Firefox also has similar
things but lets not talk about firefox here. I am more concerned
with IE only.

Any tips/tricks/missing knowledge.

[sorry if I have posted this to the wrong audiences]

The behavour of cookies in diggerent browsers is a clientside issue,
ASP is strictly serverside code, so how it's session.id cookie is
handled is out of reach of ASP.

The same probably goes for asp.net, but that has it's own NG's, or so
they say, this NG is classic ASP only.

This does not mean, that this tab issue is not important to ASP
programmers, so thank you for mentioning it.

It could be that some clever serverside programming can alliviate the
consequences.

[Please do not toppost on usenet]

I am more interested in Session.sessionid value which is server side
thing. Having a unique session ID matters to the web applications
which are already developed to do so. IE7 tabs does not meet this
requirement. I dont know why it is designed like that. Thats what I am
trying to dig.

[Just saying this is not approprate group is not the solution. ]

I did not JUST say that, but I think, as I said, it is a clientside thing
what happens to the cookie and the only way ASP can deal with that is not
needing the single browser window, so clever programming.

There, though I doubt that be a IIS settings solutution, but that also is
outside the scope of ASP programming.

So let's ask this question:

Why is it so important for your web program[ming] to not to have two
windows in one session?

If you/we know that, then perhaps we can make it unimportant by
programming tweaks.

Example:

Say that submitting two forms would mess up your programme?
Whel, then give the form a onetime hidden value, that is checked
serverside.

 

[Anthony Jones]

Evertjan

I am more interested in Session.sessionid value which is server side thing.
Having a unique session ID matters to the web applications which are already
developed to do so. IE7 tabs does not meet this requirement. I dont know why
it is designed like that. Thats what I am trying to dig.

Actually this isn't really much different in IE6. Opening a new Tab in IE7
is pretty much the same function as using IE6's 'open in new window'. In
both cases the new window runs in the same IExplore process.

ASP uses a transient cookie to store a SessionID. This cookie behaves just
like any other cookie in that whenever a request is made to a path that
matches the one specified when it was created it will get sent in the
request. It only differs from standard cookies in that it never gets
written to disk and therefore is only available to the process that received
it.

An ASP application can not maintain two different sessions on behalf of a
single client browser process (unless that browser did some very clever
sandboxing, I don't know of any that do).