66fd1569b8
The main issue I see inside tracex at the moment is that we construct the HTTP measurement from separate events. This is fragile because we cannot be sure that these events belong to the same round trip. (Currently, they _are_ part of the same round trip, but this is a fragile assumption and it would be much more robust to dispose of it.) To prepare for emitting a single event, it's imperative to have two distinct fields for HTTP request and response headers, which is the main contribution in this commit. Then, we have a bunch of smaller changes including: 1. correctly naming 'response' the DNS response (instead of 'reply') 2. ensure we always use pointer receivers Reference issue: https://github.com/ooni/probe/issues/2121 |
||
---|---|---|
.. | ||
atomicx | ||
bytecounter | ||
cmd | ||
engine | ||
fakefill | ||
fsx | ||
httpx | ||
humanize | ||
kvstore | ||
legacy/assetsdir | ||
measurex | ||
mlablocate | ||
mlablocatev2 | ||
model | ||
multierror | ||
netxlite | ||
platform | ||
ptx | ||
randx | ||
runtimex | ||
scrubber | ||
shellx | ||
stuninput | ||
torlogs | ||
tunnel | ||
tutorial | ||
version | ||
README.md |
Directory github.com/ooni/probe-cli/internal
This directory contains private Go packages.
As a reminder, you can always check the Go documentation of a package by using
go doc -all ./internal/$package
where $package
is the name of the package.
Some notable packages: