The report itself is correct, thanks for this!
However while the patch fixed one problem, it creates another one.
The problem connected to low granularity (rounded to one second) of the
MHD's internal timer. If connection timeout is set to one second (for
example) then connection may expire at
I would say that the timer granularity and the fix are two different things,
even if granularity would be finer, the checking condition like before was
wrong and would lead to unnecessary busy cycles. Is a timeout of only one
second a real use case? In any way, your example below would result in
Please see my comments below.
On 12.08.2021 12:36, Irion, Alexander wrote:
I would say that the timer granularity and the fix are two different things,
even if granularity would be finer, the checking condition like before was
wrong and would lead to unnecessary busy cycles.
That's correct i
