199903 - Set site in cookie sites as "not being able to set cookies" - cookies are still set per privacy policy

Status: RESOLVED DUPLICATE of bug 199883

(Core :: Networking: Cookies, defect)

Description

[Arjen Dragt]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4a) Gecko/20030329
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4a) Gecko/20030329

Privacy policies over-ride the settings of the Cookie Manager/Cookie sites
settings.  I tried this with washingtonpost.com - they have no defined privacy
policy, and my settings state that such sites should be flagged before.
I then add them to the "site cannot set cookies" list (and remove the cookies
from my stored cookies).  I close the browser and go back in to washingtonpost.com

Once again, cookies are set.

Reproducible: Always

Steps to Reproduce:
1.Set privacy settings as desired.
2.Browse to site.  Go into cookies and remove/block future cookies from this site.
3.Close browser and go back into same site - cookie will be reset.

Actual Results:  
Cookies are stored on machine again even though they are on the "cannot set
cookies" list.

Expected Results:  
Blocked the cookies.

Comment 1

[[e-mail]]

this is most likely a dup of bug 199883.

reporter: this is a little tricky to test, but... here's what I recommend you
do, just to confirm my diagnosis is correct:

1) turn on "ask me before storing a cookie" in your prefs
2) browse to washingtonpost.com, and note the site name in the dialogs that pop
up. there may be several different ones, so maybe just write them all down. (i'm
talking about the site in the main dialog, not the "cookie host" in the
drop-down fields)
3) edit your cookperm.txt manually, and alter the existing entry for
"washingtonpost.com" (or something similar) to the site you wrote down in step
2. you may have to copy/paste this line if you need several entries.
4) confirm that the blocking now works.

the problem is that the permission list entry for 'don't allow removed cookies
to be reaccepted later' and the actual site don't match exactly, so we don't
honor the permission entry. this is due to a recent rewrite of permissions code.
we'll hopefully fix this soon...

Comment 2

[[e-mail]]

one last comment. please back up your cookperm.txt before following that
procedure. ;)

Comment 3

[[e-mail]]

marking r/d per reporter's comment in private mail.

*** This bug has been marked as a duplicate of 199883 ***