Safari content blocking API provides rules with action block-cookies:
Strips cookies from the header before sending it to the server. This only blocks cookies otherwise acceptable to Safari's privacy policy. Combining with ignore-previous-rules doesn't override the browser’s privacy settings.
This is nothing compared to what $cookie rules are capable of in other AdGuard versions. However, we can improve the situation a little bit if we accompany block-cookie content blocking rules with "advanced rules". The purpose of the "advanced rules" will be to use Javascript and remove cookies via document.cookie.
Briefly, here's what I suggest.
A rule like that: $cookie=test,domain=google.com
Should be converted to two rules.
- One is a safari content blocking API rule:
{ trigger: { "if-domain": "google.com*" }, "action": { type: "block-cookies" } }.
- The other one is an advanced rule that will run a script removing the cookie using
document.cookie
This is certainly far from the $cookie rules capabilities, but it's better than nothing anyways.
Safari content blocking API provides rules with action
block-cookies:This is nothing compared to what
$cookierules are capable of in other AdGuard versions. However, we can improve the situation a little bit if we accompanyblock-cookiecontent blocking rules with "advanced rules". The purpose of the "advanced rules" will be to use Javascript and remove cookies viadocument.cookie.Briefly, here's what I suggest.
A rule like that:
$cookie=test,domain=google.comShould be converted to two rules.
{ trigger: { "if-domain": "google.com*" }, "action": { type: "block-cookies" } }.document.cookieThis is certainly far from the
$cookierules capabilities, but it's better than nothing anyways.