Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reset cache/cookies of containers without deleting them #303

Closed
pollti opened this issue Mar 2, 2017 · 40 comments · Fixed by #2654
Closed

Reset cache/cookies of containers without deleting them #303

pollti opened this issue Mar 2, 2017 · 40 comments · Fixed by #2654
Assignees
Labels
👍 Feature Request Feature requests users would like to see in this addon
Milestone

Comments

@pollti
Copy link

pollti commented Mar 2, 2017

It would be great to have an option to delete a container's data (cache/cookies/...) without recreating the container.

@groovecoder groovecoder added enhancement Needs: UX Needs to be reviewed by the UX team labels Mar 2, 2017
@groovecoder groovecoder added this to the Stretch milestone Mar 2, 2017
@groovecoder groovecoder removed the Needs: UX Needs to be reviewed by the UX team label Mar 3, 2017
@groovecoder groovecoder removed this from the Stretch milestone Apr 28, 2017
@maxnordlund
Copy link

This also ties in to the cookie deletion modal inside the settings. As far as I can tell, deleting a cookie there deletes it in all containers. Which means I need to login into all my accounts in various containers, which is rather unfortunate.

Perhaps more concretely, I would like to wipe all (or some) cookies from the default container leftover from setting up the various containers. I.e. visited github in default before assigning it to "work". Now every time I visit some other site, GitHub can potential track me.

Related, but not for this issue, is the ability to block cookies in some containers. See #1193

@AdKiller
Copy link

The option to delete cache and cookies of a specific container is a must.

@oneEyedCharlie
Copy link

Um, when will this get fixed? It's been 18 months?

@jbyler
Copy link

jbyler commented Dec 4, 2018

I assumed when using the "Clear Cookies and Site Data..." button that only cookies and site data from the current container would be affected. When I discovered that cookies from other containers were also deleted, it made me wonder if the multi-account containers add-on was actually segregating cookies at all. After doing some research I believe that the problem is just with clearing cookies, not with setting cookies—but I want to emphasize the potential for losing trust with users if the "Clear Cookies and Site Data" feature does not respect containers.

@bugz8unny69
Copy link

but I want to emphasize the potential for losing trust with users if the "Clear Cookies and Site Data" feature does not respect containers.

I'm a bit dubious using the '(dis)trust', nevertheless, I agree with the premise of the argument (feature request).

@activescott
Copy link

Combined with #1346 this would be very powerful. I want to allow new sites/pages to open in a default container and only open a site in a container with my cookies in it when I explicitly choose too. Then periodically delete cookies from the default container (or on a policy like every day or on FF close).

@NeatWolf
Copy link

Duh, I can't believe this hasn't been implemented yet?

How am I supposed to clean my cache of a container if it gets broken?
I'm surprised this essential feature is missing!

@cruzzer
Copy link

cruzzer commented Jan 9, 2020

Dear Mozilla Team.

This would be a highly appreciated feature.
For example add a drop-down menu in the "Clear All history" dialog for selecting the container, including the default container. This would allow clearing only that specific container.

As of now, we have to clear the history of all containers and then re-login to the websites of that container. In my case, I would like to more often clear the history of my default container, but leave my specific containers untouched.

@Joseei
Copy link

Joseei commented Feb 13, 2020

Dear Mozilla Team.

This would be a highly appreciated feature.
For example add a drop-down menu in the "Clear All history" dialog for selecting the container, including the default container. This would allow clearing only that specific container.

As of now, we have to clear the history of all containers and then re-login to the websites of that container. In my case, I would like to more often clear the history of my default container, but leave my specific containers untouched.

This 100%. I'd love to have some containers where the cookies are never cleared (so to stay logged in), even when I clear all history/cookies from the "Privacy & Security" menu and also vice versa where I can delete cache/cookies inside a certain container only if need be. There needs to be options and flexibility around this.

@w457381n
Copy link

Absolutely agree here. The Multi-Account Containers combined with the ability to automatically destroy all cookies for one of the containers when you exit or on a periodic basis (24-hours?) would be a great addition. I've found "Cookie Quick Manager" that allows me to do this manually, but I'd love to see it built in as a "self destructing container" feature.

@do-adams
Copy link

do-adams commented Mar 9, 2020

Seconding this feature request. This capability is essential, but I can second @dbm1175 and confirm that Cookie Quick Manager integrates very nicely with the containers and allows you to achieve this functionality right now!

@popindavibe
Copy link

Not sure if I'm just doing it plain wrong, but the container is keeping cached files not matter the cache-control policy associated to a resource. My only way to force a refresh this way is to do it from the dev panel tool Disable cache checkbox.
I could hardly recommend that plugin to anyone with such shortcomings. Please correct me and tell me that there is a solution for this.
I've been truly enjoying the comfort this plugin, especially in providing a simple way to handle different account connections to the same website. I hope this will be addressed.

@ameaninglessname
Copy link

I think this extension does anything you want : Cookie-AutoDelete

@poiNt3D
Copy link

poiNt3D commented Apr 17, 2021

I think this extension does anything you want : Cookie-AutoDelete

No, it does not. I use Cookie-AutoDelete for a long time, then i noticed that some stupid poll i clicked (without authorizing) remembered the answer. I tried manually deleting container cookies in Cookie-AutoDelete without any luck.
Clearing all browser cache\cookies helped.

@politas
Copy link

politas commented Dec 1, 2021

It's great that there are some solutions for clearing cookies from containers, but we really need a way to clear the cache from a container. Currently, it seems you need to delete the whole container and re-create it. Global cache clear does not clear the cache of containers!

@shmerl
Copy link

shmerl commented Dec 4, 2021

To clarify, when you do clear all cache from the settings, does it also clear it for all containers or only for no container?

@Kaleb-JCI
Copy link

As a developer who uses multi-account containers to log into various dev/staging/production/overseas environments. It would definitely be nice to be able to clear the cookies/cache/local storage for a given container without affecting the other containers.

@crisp5
Copy link

crisp5 commented Mar 9, 2022

I tried manually deleting container cookies in Cookie-AutoDelete without any luck. Clearing all browser cache\cookies helped.

This might have to do with Total Cookie Protection. If you enable ETP Strict, Firefox isolates cookies and storage according to their first and third party contexts. Cookie AutoDelete hasn't been updated to handle the new behavior, the issue is being tracked here.

My current settings are ETP Strict + Clear data on exit (with whitelisted sites for persistent logins within containers). Unfortunately, this means whitelisted site data is kept in every container. I'd like to be able to keep Google cookies in the Google container and clear them outside of it.

@calebplum
Copy link

This would be really convenient when you've accidentally logged into a site in the wrong container.

@warrenson
Copy link

This would be very useful indeed

@Kryptos-FR
Copy link

Any update on this? It makes using containers completely useless. Lots of website rotate their authentication data (as it is good practice) and cached data of such authentication makes the container failing to work after the first rotation.

It should be a basic feature.

@timur-g
Copy link

timur-g commented Dec 19, 2023

This one is important, but do not overreact and annoy with "It makes using containers completely useless." which is not true.
When a site issue happens, just (temporarily) Disable Cache via Developer-Network.

@Kryptos-FR
Copy link

Kryptos-FR commented Dec 19, 2023

It's not an HTTP cache issue (which is the only thing that can be disabled in the Developer console). It is a site data/cookie cache issue.

@djbrown
Copy link

djbrown commented Dec 21, 2023

I also don't think that missing this feature makes containers useless..
Cookie Quick Manager has great support for containers and is my current solution/workaround.
But I don't know of any solutions for other Client-side storage besides cookies e.g. Web Storage (sessionStorage and localStorage), IndexedDB and Cache (from Serviceworker).

@politas
Copy link

politas commented Dec 22, 2023

This one is important, but do not overreact and annoy with "It makes using containers completely useless." which is not true. When a site issue happens, just (temporarily) Disable Cache via Developer-Network.

Please don't use terms like "just" when describing something that is not obvious in the UI. How would a user even know how to do this? I don't know how to disable the cache. I'm actually using a completely different browser on my desktop because of this issue.

@SlackWhat
Copy link

I would like very much that feature too.
It just makes sense. We can already assign specific websites to a container, have proxy and vpn settings within that container. It would only make sens to also be able to delete the cookies and cache specific to that container!

@squarrell
Copy link

i have no idea if i'm replying in the right place. last week my gmail stopped loading in my containers. it's only my gmail. i used to have them pinned and it was so convinient. my 2 primary emails in two separate tabs.

now i cannot open them on first go even off pinned. i try to load my gmail on the tab i was using before and it automatically opens a new tab and confirms which container i want to use.

what happened? it was so sudden and i don't understand! i didn't change anything on my computer.

i deleted my cookies and cache but it didn't help

@rafeerahman rafeerahman linked a pull request Aug 1, 2024 that will close this issue
7 tasks
groovecoder added a commit that referenced this issue Aug 28, 2024
#303: Reset cookies in site manager
@groovecoder
Copy link
Member

The fix for this has been released. #2672

@ddybing
Copy link

ddybing commented Sep 26, 2024

The fix for this has been released. #2672

Awesome! Great job.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
👍 Feature Request Feature requests users would like to see in this addon
Projects
None yet