Mozilla will shut down Pocket’s services on July 8, 2025. At that time users will no longer be able to access the Pocket website, apps and API. You can export your saved items and API data until October 8, 2025 before they are permanently removed. For more information, see this article.

Avatar for Username

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

Wildcard not working in cookies exceptions

cloudchasingfun
cloudchasingfun

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?

Chosen solution

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

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

Read this answer in context 👍 1

All Replies (2)

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

Chosen Solution

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

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

cloudchasingfun
cloudchasingfun Question owner

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!