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

IPv6 Cookies aren't deleted #485

tsia opened this Issue Jan 14, 2019 · 1 comment


None yet
2 participants
Copy link

tsia commented Jan 14, 2019

Describe the Bug/Feature

Every time the Extension clears cookies it claims to be removing cookies of the same 2 sites.
Even when i hit the clean button manually. It seems to be an issue with IPv6 Addresses.
according to Firefox those cookies haven't been used for a long time

Screenshot in which the bug can be seen



Steps for anyone to reproduce the bug

  • open a site via its ipv6 address (e. g. https://[2a03:4000:6:310e:216:3eff:fe53:99b3]/ (yes, the cert is invalid))
  • hit the clean button or wait for Cookie-AutoDelete to delete the cookies

Your settings

  • Enable Automatic Cleaning? Delay Before Cleaning: 60 Second(s)

  • Enable Cleanup on Domain Change

  • Enable Cleanup Log and Counter

  • Show Number of Cookies for that Domain

  • Show Notification After Cookie Cleanup 3 Second(s)

  • Clean Cookies from Open Tabs on Startup?

  • Enable Support for Firefox's Container Tabs?

  • Localstorage Cleanup (Firefox 58+)?

  • OS/version: Debian Linux 9.6

  • Browser/version: Firefox 64.0.2

  • Cookie AutoDelete version: 3.0.0


This comment has been minimized.

Copy link

mrdokenny commented Jan 15, 2019

This looks like a bug in Firefox. I filed

As a workaround, you can whitelisting *:*:*:*:*:*:*:* for now so the activity log doesn't get flooded.

Whitelisting the site doesn't work cause in regular expression [.*] means something completely different than \[.*\]. So what I will do is patch it so it will allow you to whitelist the site normally and even do [*].

mrdokenny added a commit that referenced this issue Jan 15, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment