refactor(webconnectivity@v0.5): improve logging clarity (#964)
We're bumping the experiment's version number because we changed the name of the field used to contain late/duplicate DNS responses. We have also changed the algorithm to determine `#dnsDiff`. However, the change should only impact how we log this information. Overall, here the idea is to provide users with a reasonably clear explanation of how the probe maps observations to blocking and accessible using expected/unexpected as the conceptual framework. Part of https://github.com/ooni/probe/issues/2237
This commit is contained in:
parent
d6a362d96f
commit
5e76c6ec92
9 changed files with 88 additions and 33 deletions
|
|
@ -53,6 +53,7 @@ func (tk *TestKeys) analysisHTTPDiff(logger model.Logger,
|
|||
tk.BlockingFlags |= analysisFlagSuccess
|
||||
return
|
||||
}
|
||||
logger.Infof("HTTP: body length: MISMATCH (see #%d)", probe.TransactionID)
|
||||
if tk.HeadersMatch != nil && *tk.HeadersMatch {
|
||||
logger.Infof(
|
||||
"HTTP: statusCodeMatch && headersMatch => #%d is successful",
|
||||
|
|
@ -61,6 +62,7 @@ func (tk *TestKeys) analysisHTTPDiff(logger model.Logger,
|
|||
tk.BlockingFlags |= analysisFlagSuccess
|
||||
return
|
||||
}
|
||||
logger.Infof("HTTP: uncommon headers: MISMATCH (see #%d)", probe.TransactionID)
|
||||
if tk.TitleMatch != nil && *tk.TitleMatch {
|
||||
logger.Infof(
|
||||
"HTTP: statusCodeMatch && titleMatch => #%d is successful",
|
||||
|
|
@ -69,6 +71,9 @@ func (tk *TestKeys) analysisHTTPDiff(logger model.Logger,
|
|||
tk.BlockingFlags |= analysisFlagSuccess
|
||||
return
|
||||
}
|
||||
logger.Infof("HTTP: title: MISMATCH (see #%d)", probe.TransactionID)
|
||||
} else {
|
||||
logger.Infof("HTTP: status code: MISMATCH (see #%d)", probe.TransactionID)
|
||||
}
|
||||
|
||||
tk.BlockingFlags |= analysisFlagHTTPDiff
|
||||
|
|
|
|||
Loading…
Reference in a new issue