Opened 5 years ago

Closed 3 years ago

#11972 closed defect (fixed)

Make a test that measures both HTTP and DNS censorship

Reported by: cypherpunks Owned by: hellais
Priority: Medium Milestone:
Component: Archived/Ooni Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

This issue was automatically migrated from github issue #322Currently the http_requests test by itself does not have a way of detecting if the censorship is occurring because of HTTP, IP or DNS blocking. To determine this the user must also run another test (dnsconsistency, tcpconnect).

We could make a master test that performs all the various steps separately and records the results for every step to determine where the blocking is occurring.

Child Tickets

Change History (1)

comment:1 Changed 3 years ago by anadahz

Resolution: fixed
Severity: Normal
Status: newclosed

This has been already implemented to the web_connectivity test.

Note: See TracTickets for help on using tickets.