Skip to content
This repository has been archived by the owner on Jul 21, 2021. It is now read-only.

Cookie blocked but not removed, issue 384 still exists in uMatrix #17

Closed
tharrisone opened this issue Oct 26, 2014 · 3 comments
Closed

Comments

@tharrisone
Copy link

gorhill/httpswitchboard#384

As per post on Wilders Secrurity:

My privacy settings are set to delete blocked cookies and wipe session cookies every 15 mins. I wiped all my cookies and went to a random site and waited for 30 mins and that cookie is still there. I can send you my settings info also if you need it. Eonline.com is not whitelisted at all and I have cookies, scripts, xhr, frames blocked by default.

@gorhill
Copy link
Owner

gorhill commented Oct 26, 2014

Yes, I disconnected the handling of cookie while I re-factored, forgot to plug back the code. I step through the code and cookies are removed, not sure what the problem is in HTTPSB.

@tharrisone
Copy link
Author

This is very strange, I deleted my chromium folder started fresh installed uMatrix and set my privacy settings appropriately and 30 mins later the blocked cookies are still in my list via chrome://settings/cookies. I could make a video if you like, also I am on chromium-dev vers Version 40.0.2194.2 (64-bit)

@gorhill
Copy link
Owner

gorhill commented Oct 27, 2014

Like I said, the cookie cleaning code is not working, I did not release a version yet with it working again. I am testing this one thoroughly given the re-factoring of the matrix.

Noxgrim pushed a commit to Noxgrim/uMatrix that referenced this issue Dec 29, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants