Avatar for Username

Търсене в помощните статии

Избягвайте измамите при поддръжката. Никога няма да ви помолим да се обадите или изпратите SMS на телефонен номер или да споделите лична информация. Моля, докладвайте подозрителна активност на "Докладване за злоупотреба".

Научете повече

Тази тема беше архивирана. Моля, задайте нов въпрос ако имате нужда от помощ.

Wildcard not working in cookies exceptions

  • 2 отговора
  • 3 имат този проблем
  • 244 изгледи
  • Последен отговор от cloudchasingfun

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?

Избрано решение

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

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

Прочетете този отговор в контекста 👍 1

Всички отговори (2)

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

Избрано решение

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

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

cloudchasingfun
cloudchasingfun Задаващият въпроса
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!