Prerequisites
Description
Cookies deleted on timed manner even for allowed domains
A specific URL where the issue occurs
Any. In this particular case forums.unity.com
Steps to Reproduce
- Go to forums.unity.com (by any resource, really)
- Login
- Close the tab and monitor the logger for info events
Ruleset
Global scope level: domain
cname-reveal: * true
https-strict: behind-the-scene false
matrix-off: about-scheme true
matrix-off: behind-the-scene true
matrix-off: chrome-extension-scheme true
matrix-off: chrome-scheme true
matrix-off: localhost true
matrix-off: moz-extension-scheme true
matrix-off: opera-scheme true
matrix-off: vivaldi-scheme true
matrix-off: wyciwyg-scheme true
no-workers: * true
no-workers: youtube.com false
noscript-spoof: * true
referrer-spoof: * true
referrer-spoof: behind-the-scene false
* * * block
* * css allow
* * frame block
* * image allow
* 1st-party * allow
* 1st-party cookie block
* 1st-party frame allow
* 1st-party script block
127.0.0.1 1st-party script allow
unity.com 1st-party cookie allow
unity.com 1st-party script allow
Supporting evidence


Your environment
- uMatrix version: 1.4.10b6
- Browser Name and version: Vivaldi 3.1/Chromium 83
- Operating System and version: Win7x64
Additional notes
According to the wiki and option description:
Blacklisted cookies are not prevented by uMatrix from entering your browser. However they are prevented from leaving your browser, which is what really matters. Not blocking cookies before they enter your browser gives you the opportunity to be informed that a site tried to use cookies, and furthermore to inspect their contents if you wish.
Once these blacklisted cookies have been accounted for by uMatrix, you can ask uMatrix to remove them from your browser if you wish so: just check the setting "Delete blocked cookies" in the Privacy tab.
I read it multiple times trying to imagine all possible meanings I might be missing (which is already very bad thing to begin with - option description shouldn't call for a meeting of wise men to debate what this or that means) but in the end I always come back to what seems logical and most reasonable - these domains that do not have rule allowing cookies out will be cleared.
My understanding is that when this feature was developed it sure was thought thru to flatten-out rules to make sure all checks are passed not just top level * * * block, so if I block cookies globally, but then allow for domain.com via 1st party rule - this will be the final flattened rule that is taken into account and therefore on the next iteration of a clean-up the cookie will be kept.
However, according to my observation and logger data that is not the case. Local storage also suffers form the same issue.
P.S. It would be nice to add a clarification how are allowed 3d party cookies processed. For example, if I allow google.com 3dparty cookies for youtube.com but block 1st party cookies on google.com - what the action will be performed during deletion, which will be kept or deleted?
P.P.S. Screenshot of the switchboard says 1.4.1b0 - ignore that, the shots are made on that version but later after an update on b6 the same issues were observed so it was tested on b6 as well.
Prerequisites
Description
Cookies deleted on timed manner even for allowed domains
A specific URL where the issue occurs
Any. In this particular case forums.unity.com
Steps to Reproduce
Ruleset
Global scope level: domain
Supporting evidence
Your environment
Additional notes
According to the wiki and option description:
I read it multiple times trying to imagine all possible meanings I might be missing (which is already very bad thing to begin with - option description shouldn't call for a meeting of wise men to debate what this or that means) but in the end I always come back to what seems logical and most reasonable - these domains that do not have rule allowing cookies out will be cleared.
My understanding is that when this feature was developed it sure was thought thru to flatten-out rules to make sure all checks are passed not just top level
* * * block, so if I block cookies globally, but then allow fordomain.comvia 1st party rule - this will be the final flattened rule that is taken into account and therefore on the next iteration of a clean-up the cookie will be kept.However, according to my observation and logger data that is not the case. Local storage also suffers form the same issue.
P.S. It would be nice to add a clarification how are allowed 3d party cookies processed. For example, if I allow
google.com3dparty cookies foryoutube.combut block 1st party cookies ongoogle.com- what the action will be performed during deletion, which will be kept or deleted?P.P.S. Screenshot of the switchboard says 1.4.1b0 - ignore that, the shots are made on that version but later after an update on b6 the same issues were observed so it was tested on b6 as well.