Join the Mozilla’s Test Days event from Dec 2–8 to test the new Firefox address bar on Firefox Beta 134 and get a chance to win Mozilla swag vouchers! 🎁

Avatar for Username

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

Wildcard not working in cookies exceptions

cloudchasingfun
cloudchasingfun
more options

I need to block cookies from a whole set of subdomains, which I don't even know all. So I tried setting a block rule for "http://*.domain.com" and "https://*.domain.com" but cookies are still allowed. When I set a specific "http://www.subdomain13.domain.com" rule, it works, but I want any and all subdomains to be blocked. What should I do?

I need to block cookies from a whole set of subdomains, which I don't even know all. So I tried setting a block rule for "http://*.domain.com" and "https://*.domain.com" but cookies are still allowed. When I set a specific "http://www.subdomain13.domain.com" rule, it works, but I want any and all subdomains to be blocked. What should I do?

Keazen oplossing

Could you try it without the asterisk? In other words:

http://domain.com https://domain.com

Dit antwurd yn kontekst lêze 👍 1

Alle antwurden (2)

jscher2000 - Support Volunteer
jscher2000 - Support Volunteer
  • Top 10 Contributor
more options

Keazen oplossing

Could you try it without the asterisk? In other words:

http://domain.com https://domain.com

cloudchasingfun
cloudchasingfun Fraacheigener
more options

jscher2000, it works! It doesn't make much sense when you first think about it, but it works. And it also respects sub-rules. E.g., if http://domain.com is blocked and http://subdomain1.domain.com is allowed, cookies are all blocked, but those created when visiting any http://subdomain1.domain.com URL are allowed (even if they relate or belong to http://domain.com, but I guess this has to do with the third party cookies setting, and this does not bother me, at least for now).

So thanks!