Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

don't consent-o-matic pages accessed through google translate #342

Open
slippycheeze opened this issue Aug 9, 2023 · 0 comments
Open

don't consent-o-matic pages accessed through google translate #342

slippycheeze opened this issue Aug 9, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@slippycheeze
Copy link

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 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.

@svnhub svnhub added the enhancement New feature or request label Aug 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants