-
Notifications
You must be signed in to change notification settings - Fork 142
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
webconnectivity: investigate failure=nil and blocking=nil #1511
Comments
Web Connectivity v0.5 correctly flags the first website as down: https://explorer.ooni.org/m/20240124141110.292023_IT_webconnectivity_0321bf33bc821d88. It still flags the second website as error, so there's a need to investigate more: https://explorer.ooni.org/m/20240124141213.940181_IT_webconnectivity_ec61e2543261a5fe |
This commit adds data collected from ooni/probe#1511 (comment) that helps us to understand why `minipipeline` flags the measurement as `accessible = null` and `blocking = null`.
) This diff fixes ooni/probe#1511 (comment). This is the rationale of the diff: we need to track the origin of IP addresses: * "dns" if discovered using DNS; * "th" if discovered using the test helper; * null otherwise. When filtering for classic analysis, we include "dns" entries if resolved using getaddrinfo, drop "th" entries because they're not relevant, and include null entries under the assumption that the probe discovered them either directly from the input URL or because a redirect redirected to an URL containing an IP address. We also update the minipipeline test suite and show that the only changes are related to the test added by #1471.
Here's a measurement after we fixed the issue with the second input URL: https://explorer.ooni.org/m/20240124155344.998365_IT_webconnectivity_ae1968b0b836d2e6. |
This commit adds data collected from ooni/probe#1511 (comment) that helps us to understand why `minipipeline` flags the measurement as `accessible = null` and `blocking = null`.
…ni#1472) This diff fixes ooni/probe#1511 (comment). This is the rationale of the diff: we need to track the origin of IP addresses: * "dns" if discovered using DNS; * "th" if discovered using the test helper; * null otherwise. When filtering for classic analysis, we include "dns" entries if resolved using getaddrinfo, drop "th" entries because they're not relevant, and include null entries under the assumption that the probe discovered them either directly from the input URL or because a redirect redirected to an URL containing an IP address. We also update the minipipeline test suite and show that the only changes are related to the test added by ooni#1471.
and
The text was updated successfully, but these errors were encountered: