Closed
Bug 368115
Opened 18 years ago
Closed 18 years ago
Issue with Cookie and new browser.
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 117222
People
(Reporter: salini_joseph, Unassigned)
Details
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; InfoPath.1; .NET CLR 2.0.50727)
Build Identifier: Mozilla/5.0(XII;U;Linux86_64;)en-us;rv1.8.0.8;Gecko/2006//07Redht
I am trying to open two sessions from a desktop. I am able to login in to two sessions. But the new session is getting populated or existing session is updated with the new session. And the previous session is not getting logged out. The no of session is limited to 4. because of this issue (previuos session is not getting logged out) i am not able to proceed further. I am storing the session in Cookie. So please advice me in this regards.
Reproducible: Always
Steps to Reproduce:
1.Open one Mizilla Browser copy one login url which is using cookie to store session id
2.Try to login.
3.Open second mozilla
4.Copy the same url used for login in the first time.
5.use the same user id and password to login.
6.refresh the previous browser.
7.log out from the latest session.
8.try to refresh the previous session(Browser)
Actual Results:
1.Open browser.
2.Able to login
3.Login page should be there.
4.Able to log in.
5.Able to login.
6.It should refresh the page.
7.Should show log out.
8.it will logout from the new browser also.
Expected Results:
8. It should not log outfrom the previous session.
It may be because we are using cookie. Is there any way to handle this from our side?
![]() |
||
Comment 1•18 years ago
|
||
Are you actually starting a new instance? Like with a separate profile and what not?
You can't have two instances using the same profile -- if you're using the same profile you're just connecting to the existing instance with XRemote and opening a new window...
Updated•18 years ago
|
Group: security
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•