You are right in that I don't really care about the session ID - just the
session. However, I find that even after doing session.abandon there are
still items in the Session collection (ie. session.count>0). This worries me
that information may copy from session to session! Appreciate any further
info you can provide,
Paul.
"Joel Leong" <ch******@hotmail.com> wrote in message
news:O%****************@TK2MSFTNGP10.phx.gbl...
The SessionID lasts as long as the browser session lasts even though the
session state expires after the indicated timeout period i.e the same
session ID can represent multiple sessions over time where the instance of
the browser remain the same. This is the normal behavior. Not sure why you
want a new session id?
"Paul W" <qq*@qqq.com> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl... Using default session handling (ie. inproc and with cookies). I have a
'logout' button that returns the user to the login screen and does a
session.abandon.
HOWEVER, if they then log back in (even with a different username) they
will have the same sessionid as before! This is not what I expected. Can
someone shed light on this, or how I can investigate further? Thanks,
Paul.
(Note - if the user closes their browser, and starts another browser
session then they get a NEW sessionid)