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
We currently automatically detect the root domain of the site by parsing the hostname and extracting the last two parts (e.g. "some.privacy.example.com" -> "example.com").
However, some websites will have a root domain with three parts, like "example.co.uk", so this existing automatic detection will fail and will attempt to set the cookie to "co.uk" instead!
Steps to Reproduce
n/a - this is easy to understand in the code, but actually hard to reproduce "in the wild" as we'd need to deploy to a website with this style of domain.
Expected behavior
We should either:
Automatically detect these types of "known" multi-level root domains
Provide a configuration option to override what the cookie domain should be
I'm partial to option 2 as it feels like a safer choice and gives the user control over this behaviour.
The text was updated successfully, but these errors were encountered:
Bug Description
We currently automatically detect the root domain of the site by parsing the hostname and extracting the last two parts (e.g. "some.privacy.example.com" -> "example.com").
However, some websites will have a root domain with three parts, like "example.co.uk", so this existing automatic detection will fail and will attempt to set the cookie to "co.uk" instead!
Steps to Reproduce
n/a - this is easy to understand in the code, but actually hard to reproduce "in the wild" as we'd need to deploy to a website with this style of domain.
Expected behavior
We should either:
I'm partial to option 2 as it feels like a safer choice and gives the user control over this behaviour.
The text was updated successfully, but these errors were encountered: