MozillaZine

www.sextracker.com cookie is not blocked with sextracker.com

User Help for Seamonkey and Mozilla Suite
Guest
Guest
 

Post Posted December 29th, 2004, 12:11 pm

Why If I block "sextracker.com" cookie then "www.sextracker.com" cookie is not blocked?
why sextracker.com doesn't block all *.sextracker.com variants?
I use Mozilla 1.7.5

Guest
Guest
 

Post Posted December 29th, 2004, 12:22 pm

with IE if I block "dangerousSite.com" then variant like "ads.dangerousSite.com" or "server2.dangerousSite.com" are blocked, but with Mozilla NOT!!!

ByronB
 
Posts: 345
Joined: November 18th, 2003, 2:52 pm

Post Posted December 29th, 2004, 3:15 pm

>*.sextracker.com variants

It appears that Mozilla, like IE, doesn't allow wildcard expressions

Libra
 
Posts: 268
Joined: September 22nd, 2004, 6:49 pm

Post Posted December 29th, 2004, 6:48 pm

For IE I use IESpyads and it has a lot of *. sites listed and blocked (in the Restricted Zone).

Sincerely, Libra

Guest
Guest
 

Post Posted December 30th, 2004, 11:54 am

With IE the * is not necessary, because if you block thisDomain.com then automatically all *.thisDomain.com sites are blocked!
With Mozilla this is not true!

danielwang
 
Posts: 386
Joined: July 30th, 2003, 9:28 am

Post Posted December 30th, 2004, 1:23 pm

does blocking ".sextracker.com" (note the leading dot) work?

ByronB
 
Posts: 345
Joined: November 18th, 2003, 2:52 pm

Post Posted December 30th, 2004, 3:12 pm

One of the problems with blocking the whole server.

I am a co-owner of 12 Yahoo groups, I need certain cookies to show Yahoo my status, But I don't need Yahoo's 3 rd party advertisers

If I block the whole server then my groups status is also blocked
If I accept then I also have to accept over 200 of their crapware advertisers

Mozilla gives me the choice I need


Just a different thought

Guest
Guest
 

Post Posted December 31st, 2004, 8:09 am

but why if you block a cookie from http://thisDomain.com using thisdomain.com filter then the cookie from http://thisdomain.com (without WWW) is not blocked? is it a bug?

Guest
Guest
 

Post Posted December 31st, 2004, 8:09 am

but why if you block a cookie from http://thisDomain.com using thisdomain.com filter then the cookie from http://www.thisdomain.com (with WWW) is not blocked? is it a bug?

osmium
 
Posts: 11
Joined: October 25th, 2003, 9:28 pm
Location: austin, texas usa

Post Posted January 1st, 2005, 10:31 pm

There is some difficulty about programmatically deciding what the domain is, especially in relation to preventing/allowing cross-domain cookies. See bugs 252342 and 253974.

What Moz/FF needs, IMHO, is something that lets the user choose whether to apply settings to the subdomain only or to the whole domain. In the cookie confirmation dialog, when the user is blocking or allowing cookies, it would allow the user to choose, for example, "apply to all cookies from domainname.com" or "apply to cookies from ads.domainname.com only".

I searched for a bug on this and could not find one.

Return to SeaMonkey Support


Who is online

Users browsing this forum: No registered users and 0 guests