As long as the code from asp or asp.net knew what to look for in that cookie, it shouldn't matter.
I'm not sure about the browser closing thing (I'm sure someone here does), but you could just set the lifetime of the cookie to be something like an hour or so, assuming you knew that most users wouldn't be hanging around that long (1/2 hour might even be doable).
that is the answer I was looking for. How would you expire a cookie after 1 hour? Also if you try to create a new cookie with the same name does it override the old info??
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.