Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Avatar for Username

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信，及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

话题已存档。 如果需要帮助请提出新问题。

Wildcard not working in cookies exceptions

  • 2 个回答
  • 3 人有此问题
  • 281 次查看
  • 最后回复者为 cloudchasingfun
  • 已解决

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?

被采纳的解决方案

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

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

定位到答案原位置 👍 1

所有回复 (2)

jscher2000 - Support Volunteer
jscher2000 - Support Volunteer

选择的解决方案

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

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

cloudchasingfun
cloudchasingfun 提问者

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!