471,072 Members | 1,366 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,072 software developers and data experts.

How can I prevent Sessions from ending just because the browser window is closed

Hi Gang,

I would like to have my application retain sessions even after the user
closes their browser window, up unil the time the session is supposed
to time out. Right now if the user closes IE their session is
re-created. Is there any way around this?

Thanks,
Christian Blackburn

Jun 16 '06 #1
8 1742
What do you mean by 're created'?

If the user closes the browser, nothing happens to their session. The
session will continue to be around until timeout.

I don't know what you mean by the session being recreated when the user
closes the browser.

"Christian Blackburn" <ch*****************@Yahoo.com> wrote in message
news:11*********************@g10g2000cwb.googlegro ups.com...
Hi Gang,

I would like to have my application retain sessions even after the user
closes their browser window, up unil the time the session is supposed
to time out. Right now if the user closes IE their session is
re-created. Is there any way around this?

Thanks,
Christian Blackburn

Jun 16 '06 #2
"Christian Blackburn" <ch*****************@Yahoo.com> wrote in message
news:11*********************@g10g2000cwb.googlegro ups.com...
I would like to have my application retain sessions even after the user
closes their browser window, up unil the time the session is supposed
to time out.
That's right.
Right now if the user closes IE their session is re-created.
Of course it is. IIS has no means of knowing that a browser has been closed.
Is there any way around this?


A way round what? This is standard behaviour.
Jun 16 '06 #3
Hi Marina,

Thanks for your reply.

Marina Levit [MVP] wrote:
What do you mean by 're created'?
When a user logs into my website, the site populates their session with
their access credentials. I then record that the user is logged in by
placing their session in the database (is deleted automatically when
their session times out via Global.asax). This is to prevent
simultaneous logins.

Once they close the browser window, even for two seconds if they go
right back and try to view the website a new session is assigned and
they're unable to log in, because as far as the website knows their
session is already in use.
I don't know what you mean by the session being recreated when the user
closes the browser.


Once they go back to the page the website gives them a new session ID.
Thanks for your help,
Christian Blackburn

Jun 17 '06 #4
Hi Mark,

Thanks for your reply.
Mark Rae wrote:
I would like to have my application retain sessions even after the user
closes their browser window, up unil the time the session is supposed
to time out.
That's right.


That true the session is retained, but if they close their browser
within the 15 minute timeout period and go back to the site they'll
actually wind up with a different session entirely. That's exactly
what I don't want to happen.
Right now if the user closes IE their session is re-created.
Of course it is. IIS has no means of knowing that a browser has been closed.


That's true IIS doesn't, but their cookie-based session should be
retained or at least there should be some setting I can enable to make
it so.
Is there any way around this?


A way round what? This is standard behaviour.


In my opinion standard behaviour and logical behaviour are often at
odds especially with buggy software.

Cheers,
Christian Blackburn

Jun 17 '06 #5
"Christian Blackburn" <ch*****************@Yahoo.com> wrote in message
news:11**********************@c74g2000cwc.googlegr oups.com...
A way round what? This is standard behaviour.


In my opinion standard behaviour and logical behaviour are often at
odds especially with buggy software.


I can't help that...

Imagine the scenario of an Internet Café...

User 1 fires up Internet Explorer, goes to your site (or HotMail or
whatever) and does what they need to do.

When they've finished, they close the browser, inadvertently forgetting to
click the Logout button.

User 2 takes the seat recently vacated by User 1, fires up Internet Explorer
and goes to your site.

How on earth can your site or ISS or anything else for that matter tell at
that moment whether User 1 is back having just made a quick visit to the
coffee machine and therefore connect to User 1's pervious session, or
whether User 2 has just connected and therefore create a new session?
Jun 17 '06 #6
You may set a cookie on the client machine. Also set a time out limit
(say 2 minutes). Now if a user closes the window, and get to your site
again, this cookie will give you the last session id and you can
manipulate your code accordingly.

Yanesh Tyagi
Christian Blackburn wrote:
Hi Marina,

Thanks for your reply.

Marina Levit [MVP] wrote:
What do you mean by 're created'?

When a user logs into my website, the site populates their session with
their access credentials. I then record that the user is logged in by
placing their session in the database (is deleted automatically when
their session times out via Global.asax). This is to prevent
simultaneous logins.

Once they close the browser window, even for two seconds if they go
right back and try to view the website a new session is assigned and
they're unable to log in, because as far as the website knows their
session is already in use.

I don't know what you mean by the session being recreated when the user
closes the browser.

Once they go back to the page the website gives them a new session ID.
Thanks for your help,
Christian Blackburn

Jun 17 '06 #7
"Yanesh Tyagi" <ya**********@qualtech-consultants.com> wrote in message
news:O1**************@TK2MSFTNGP03.phx.gbl...
You may set a cookie on the client machine. Also set a time out limit (say
2 minutes). Now if a user closes the window, and get to your site again,
this cookie will give you the last session id and you can manipulate your
code accordingly.


And what if this is a shared public computer...?
Jun 17 '06 #8
Hi Mark and Yanesh,

The way mark is describing it is correct. The timeout doesn't work
like that. It's a session cookie, that will timeout either when the
browser is closed or when the timeout ocurrs whichever is first.

Cheers,
Christian

Jun 21 '06 #9

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

1 post views Thread by Onur Bozkurt | last post: by
2 posts views Thread by Mike May | last post: by
9 posts views Thread by Daniel Walzenbach | last post: by
21 posts views Thread by alistair_henderson | last post: by
3 posts views Thread by sophie_newbie | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.