Closed
Bug 1364466
Opened 8 years ago
Closed 8 years ago
Cookie lost with custom container
Categories
(Core :: Networking: Cookies, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: tech, Assigned: amchung)
Details
(Whiteboard: [necko-active])
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:53.0) Gecko/20100101 Firefox/53.0
Build ID: 20170506155913
Steps to reproduce:
- Enable containers in about:config
- Create a new custom container
- Open tab on this constainer and generate a cookie
- Close the tab to come back later
Actual results:
Sometimes (it is very irregular) I lost my cookies on the custom container.
In fact, I much use aws console in my work. On this platform, you can "assume role" (connect to customer account from master account). Aws console keep (only) the last 5 assumed roles in history (so you can switch role for these 5 roles easily and quickly). This history is stored in cookie according aws documentation :
http://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use_switch-role-console.html
To workaround this limitation, I used "multifox" extension :
https://github.com/hultmann/multifox
But this extension can not work with recent firefox version due to XPCOM depreciation so I begin to use "contextual tab / container" which is a super and native firefox feature (good idea).
Everything seems perfect until today where I get the confirmation that, sometimes, I lost my session for a custom contianer.
In fact, I created a custom container for each customer and today I assumed role for a specific customer this morning. Since this morning I possible closed tab, containers, firefox and this afternoon I come back to a closed container and notice my whole session was lost (no assume role, no aws history, no aws favourites ..).
This bug seems totaly irregular because :
- I still have old session (last week) but lost session from this morning so no time related
- I just tried to close container and firefox to relaunch after generate cookies session and it works. But I sure at 100% that I lost my session of this morning.
Expected results:
In any case, I should retrieve my cookies for each separated container and not lost them.
Updated•8 years ago
|
Component: Untriaged → Networking: Cookies
Product: Firefox → Core
Hi guys,
I am sorry I continued tests but impossible to find the pattern to reproduce,
I still have the problem on v53 but seems very random.
From today, I will test nightly version.
Have a good day
| Assignee | ||
Comment 3•8 years ago
|
||
Ok, I will take a look at this issue.
Assignee: nobody → amchung
Flags: needinfo?(amchung)
Comment 4•8 years ago
|
||
Experienced but not consistant. Having to log into gmail, and outlook.live email acnts when I never log out, and reentering some cookie data (zip code) to tv.com only with FireFox on Windows 7 (unupdated for a year since falling victum to the phony FF update site) This began with 53.0.2 but downgrading to 52 only slightly improved things.
Side note; when using tools, info, and looking at cookies of an active page where videos keep downloading (tv.com), when I delete a cookie, the next one moves to the top of the list but the expiration date changes in front of my eyes because the deleted cookie is rewritten. I attributed that to some pointer losing sync BUT that might explain my second sentence. Usual values are end-of-session, years in future, 5 minutes in future.
Updated•8 years ago
|
Whiteboard: [necko-active]
| Assignee | ||
Comment 5•8 years ago
|
||
Hi,
I can't reproduce this bug, and I have tried three times to amazon.com.
Would you help me to use the nightly 56 to reproduce this bug?
Thanks!
Flags: needinfo?(tech)
| Assignee | ||
Comment 6•8 years ago
|
||
Hi,
I closed this bug first, please feel free to reopen this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
Hi all,
Sorry for the late answer.
Since I switched to firefox nightly I never seen this bug again however it appears often in v53.
So this issue could stay closed.
Thanks for your support, I like this feature.
Regards
Flags: needinfo?(tech)
You need to log in
before you can comment on or make changes to this bug.
Description
•