We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Mozilla サポートの検索

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.

詳しく学ぶ

このスレッドはアーカイブに保管されました。 必要であれば新たに質問してください。

Wildcard not working in cookies exceptions

  • 2 件の返信
  • 3 人がこの問題に困っています
  • 1 回表示
  • 最後の返信者: 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?

選ばれた解決策

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

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

この回答をすべて読む 👍 1

すべての返信 (2)

more options

選ばれた解決策

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

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

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!