Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

"Enable Check for Subdomains" setting doesn't work.

See original GitHub issue

The setting Enable Check for Subdomains doesn’t do a thing. Even if unchecked, it still adds a rule containing the subdomain upon whitelisting the domain from the popup UI, and also acts like that.

STR:

Have Enable Check for Subdomains unchecked in Cookie Settings.
Go to http://status.telenet.be/?language=nl and set the rule Never Clean (WhiteList) from the popup UI.
Navigate to https://www2.telenet.be/nl/ and see that the domain is not whitelisted.
Check the Cookie Whitelist and see that status.telenet.be was added.

Your settings

All default, except Enable Check for Subdomains unchecked.

OS/version: Win7 x64
Browser/version: Firefox 54.0.1
Cookie AutoDelete version: 1.4.1

Issue Analytics

State:
Created 6 years ago
Comments:9 (6 by maintainers)

Top GitHub Comments

1reaction

ke-dcommented, Aug 29, 2017

With that setting on, google.com will protect cookies from calendar.google.com. Also with that new version that setting will be deprecated since it will not be needed when you can use wildcards.

0reactions

woctezumacommented, Aug 29, 2017

In the meantime, with the setting ON, is it equivalent to whitelist mail.google.com and google.com? Say, what is the impact on calendar.google.com?