Closed
Bug 243441
Opened 21 years ago
Closed 21 years ago
allow blocking of all cookies from a domain
Categories
(Core :: Networking: Cookies, enhancement)
Core
Networking: Cookies
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: jwjr, Assigned: darin.moz)
Details
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (Compact)
Build Identifier:
Surfing Ebay, I get a fair number of cookies of this form:
e-n.y-1shz2prbmdj6wvny-1sez2pra2dj6wjnyqod5sgow6dj6x9ny-1seq-2-2.stats.esomniture.com
Naturally, the lengthy part is slightly different for each auction; my
COOKPERM.TXT file is starting to get ungainly with them.
What I (obviously) want is to be able to block "*.esomniture.com" - that is, all
possible cookies from the entire domain, regardless of subdomains.
In Cookie Pal (which I used to adore, before they stopped upgrading it), there
was a checkbox on the cookie deletion dialog with the notation "*.#####.###",
where "#####.###" was the domain of the cookie just received. Unchecking this
box resulted in the exact same behavior I'm seeing now; checking it would either
block or allow all cookies from that domain.
Please note this is _not_ a duplicate of Bug 69758, in that I'm asking for a
simple domain name comparison, rather than a more extensive and difficult regexp
match.
Reproducible: Always
Steps to Reproduce:
Comment 1•21 years ago
|
||
add "esomniture.com" to cookperm.txt (or hostperm.1 in newer builds) and be a
happy man. We make that *.esomniture.com by default. Or just use the cookie manager.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
Reporter | ||
Comment 2•21 years ago
|
||
Well, I'll be darned. A quick edit of COOKPERM.TXT did the trick. Thanks! -JW
You need to log in
before you can comment on or make changes to this bug.
Description
•