-
-
Notifications
You must be signed in to change notification settings - Fork 380
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
Default to disable privacy badger when domain is localhost or 127.0.0.1 #817
Comments
Do you mean that privacy badger should not run when localhost is in the url bar, or localhost as a third-party should never be marked as tracking? |
How should this work?
|
Yeah, I think this is the right approach -- this would almost always be someone testing out a development version of a site, so (a) they should already know and control what trackers are on the page, and (b) the snitch map entries for their page will be useless for debugging later.
I can imagine this happening, again, in a development scenario. Maybe. I don't think there's any reason to add a |
Definetely need this. Happens to me a lot. |
I just ran into an issue during development on an unrelated project that was actually just privacy badger blocking requests to the fqdn of the host I was port forwarding. On first glance it doesn't seem like a crazy idea to trust localhost or 127.0.0.1 to not maliciously track you.
If you agree this change should be put in place, I would be happy to submit a PR.
The text was updated successfully, but these errors were encountered: