You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I visited that link the page Consent-o-Matic (correctly) recognises the consent dialog it'll show. Unfortunately, since this is proxied through the *.translate.goog domain, and the HTML modified some, the consent dialog doesn't actually work.
Consent-o-Matic went into an infinite loop: filling and submitting the consent dialog, which caused a reload, which showed the dialog because the cookie was broken. (Technically: the Set-Cookie header is blocked due to an invalid domain, after rewriting, so the CONSENT cookie can't be modified, etc, etc...)
This cookie problem is a very common experience with web content accessed through the .translate.goog proxy system; I can't think of the last time one actually worked as expected. Which is maybe just me, but...
Anyway, I'd suggest that y'all block activity on any subdomain of translate.goog by default, to avoid this going forward.
The text was updated successfully, but these errors were encountered:
Example: https://cs-au-dk.translate.goog/da/news-events/consent-o-matic-dk?_x_tr_sl=da&_x_tr_tl=en&_x_tr_hl=en&_x_tr_pto=wapp
When I visited that link the page Consent-o-Matic (correctly) recognises the consent dialog it'll show. Unfortunately, since this is proxied through the
*.translate.goog
domain, and the HTML modified some, the consent dialog doesn't actually work.Consent-o-Matic went into an infinite loop: filling and submitting the consent dialog, which caused a reload, which showed the dialog because the cookie was broken. (Technically: the
Set-Cookie
header is blocked due to an invalid domain, after rewriting, so theCONSENT
cookie can't be modified, etc, etc...)This cookie problem is a very common experience with web content accessed through the
.translate.goog
proxy system; I can't think of the last time one actually worked as expected. Which is maybe just me, but...Anyway, I'd suggest that y'all block activity on any subdomain of
translate.goog
by default, to avoid this going forward.The text was updated successfully, but these errors were encountered: