515837 - Google Cookies Listed in Exceptions List Are Still Accepted

Status: RESOLVED DUPLICATE of bug 480892

(Camino Graveyard :: Preferences, defect)

Description

[tbd73]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en; rv:1.8.1.23) Gecko/20090815 Camino/1.6.9 (like Firefox/2.0.0.23)
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en; rv:1.8.1.23) Gecko/20090815 Camino/1.6.9 (like Firefox/2.0.0.23)

I have added 7 or 8 google domains to my cookie exceptions list, including:

www.google.com, google.com, .google.com, googleleadservices.com, .googleleadservices.com, and others.

For a day or two, cookies are not accepted/sent to/from google, but after a day or two of browsing, I seem to have a cookie that has been accepted (e.g. google.com) from a google domain I have previously added to my exceptions list when I view cookies and search the list for, "goo".

Also, couldn't .google.com & google.com be covered by a single exception?

Reproducible: Sometimes

Steps to Reproduce:
1. Visit http://www.google.com
2. View cookies & search for, "google"
3. Remove & block the 4 or 5 google cookies that have been saved
4. Use Camino to browse the web for a couple days (including Google searches)
5. View cookies & search for, "google"
6. Look for any google cookies that should have been blocked
Actual Results:  
I find cookies that should have been blocked & again remove & block them (adding them to the exceptions list again); browse for a couple days more; repeat & again find cookies that should have been blocked.

Expected Results:  
Blocked any cookies from a domain ending in, "google.com", "googleleadservices.com", etc.

None

Comment 1

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

For reasons beyond my ability to explain, ".google.com" and "google.com" are two very different things to Gecko (and different things to different parts of Gecko) :(

If you add an exception for ".google.com" we add an exception for that, but the part of Gecko that handles exceptions says that's an invalid syntax and ignores it, letting the cookies be added.

What you want is to have an exception for "google.com", so if you have an exception for "www.google.com" (or some other google domain without a leading "."), you can choose "Expand exception to all of google.com" from the action menu and create the exception you want (note this will probably actually break any Google services that rely on cookies, in case you did want to use them).

The fact that you need a "something.google.com" to expand an exception to all of google.com is covered by bug 480779, but the general problem you're having with ".google.com" not blocking any google.com cookies is bug 480892.