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

webconnectivitylte: expire DNS whoami results #2671

Closed
bassosimone opened this issue Feb 8, 2024 · 0 comments · Fixed by ooni/probe-cli#1499
Closed

webconnectivitylte: expire DNS whoami results #2671

bassosimone opened this issue Feb 8, 2024 · 0 comments · Fixed by ooni/probe-cli#1499

Comments

@bassosimone
Copy link
Contributor

bassosimone commented Feb 8, 2024

We use a singleton and never expire the cache. Which means potentially we miss cases where the network changes. To avoid this issue, we need to implement expiring such that we issue whoami queries periodically.

@bassosimone bassosimone self-assigned this Feb 8, 2024
bassosimone added a commit to ooni/probe-cli that referenced this issue Feb 8, 2024
Because the singleton is always active, we need to expire the cache
otherwise we don't catch changes in the client network.

Part of ooni/probe#2669

Closes ooni/probe#2671
Murphy-OrangeMud pushed a commit to Murphy-OrangeMud/probe-cli that referenced this issue Feb 13, 2024
Because the singleton is always active, we need to expire the cache
otherwise we don't catch changes in the client network.

Part of ooni/probe#2669

Closes ooni/probe#2671
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant