406560 - Cookie blocking doesn't appear to be working; started with upgrade to version 2.0.0.10

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[Lyle Bergman]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.11) Gecko/20071127 Firefox/2.0.0.11
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.11) Gecko/20071127 Firefox/2.0.0.11

Had the website www.startribune.com in my blocked cookie list, and the blocking was working fine. When Firefox upgraded itself from 2.0.0.9 to 2.0.0.10, the blocking no longer worked, even though the site was still in the blocked list. I tried deleting all the entries in the list and reentering them (and restarting Firefox), but the site was still allowed to save cookies. 2.0.0.11 didn't fix this.

Reproducible: Always

Steps to Reproduce:
1.  Enter www.startribune.com into the blocked cookie list (Tools > Options > Privacy > Exceptions)
2.  Make sure the Allow Cookies from sites option is checked
3.  Go to the website
4.  Now view the cookies (Tools > Options > Privacy > Show Cookies).  A cookie from www.startribune.com will be listed.
Actual Results:  
The cookie from the site was accepted and saved

Expected Results:  
The cookie from the site should not be accepted and saved

This started happening immediately after Firefox was upgraded from 2.0.0.9 to 2.0.0.10.  2.0.0.11 didn't fix the issue.

Comment 1

[[e-mail]]

can you check to see what happens if you add startribune.com to the blocked list?

(also, please make sure you delete relevant cookies before testing, since adding entries to the block list won't automatically delete them)

Comment 2

[Lyle Bergman]

OK, leaving off "WWW" from the address seems to have fixed the problem.  Although in 2.0.0.9, it didn't seem to be a problem.

Comment 3

[[e-mail]]

hmm, i don't think any relevant changes went into 2.0.0.10 - the most likely cause is that the site is now setting cookies from the startribune.com host instead.

the simplest way to prove or disprove that is to test 2.0.0.9 again. the installer is available at:
ftp://ftp.mozilla.org/pub/mozilla.org/firefox/releases/2.0.0.9/win32/en-US

could you please install that, run it with your default profile (it shouldn't break anything), and re-test? if you can confirm it's broken again, we can dig into this. (the build should automatically update itself to 2.0.0.11 again in due course.)

Comment 4

[Lyle Bergman]

Installed 2.0.0.9 and it now appears to behave the same as 2.0.0.11 (i.e., the cookie gets saved with "WWW" in the address).  The reason for blocking the cookie was to prevent the "registration" page from coming up.  Having the www.startribune.com address set to be blocked appeared to take care of that until 2.0.0.10. But it looks like maybe the cookie was getting saved the entire time and something else was preventing that registration page from coming up. 

I'm beginning to wonder if the website changed something just at that particular point in time.

Comment 5

[Tyler Downer [He/Him]]

This bug was originally reported on Firefox 2.x or older, which is no longer supported and will not be receiving any more updates. I strongly suggest that you update to Firefox 3.6.6 or later, update your plugins (flash, adobe, etc.), and retest in a new profile. If you still see the issue with the updated Firefox, please post here. Otherwise, please close as RESOLVED > WORKSFORME
http://www.mozilla.com
http://support.mozilla.com/kb/Managing+profiles
http://support.mozilla.com/kb/Safe+mode

Comment 6

[Tyler Downer [He/Him]]

No reply, INCOMPLETE. Please retest with Firefox 3.6.8 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.