Externalize Tracker Timeout

[phweda]

qBittorrent version and Operating System

4.x - all OSs

What is the problem

Users with inherent high Network latency (like internet great firewalls), and or slower tracker responses, have active torrents/tracker(s) marked as Not Working.

What is the expected behavior

Users with high Network latency are able to increase the default tracker response timeout. Add UI variable to configure the currently hard coded timeout.
See:
line 48 - const int KEEP_ALIVE_DURATION = 7 * 1000; // milliseconds
https://github.com/qbittorrent/qBittorrent/blob/master/src/base/http/server.cpp

Steps to reproduce

Introduce an artificial latency of 6,000+ ms to the tracker response. With ≈6,200 ms total response time virtually all Torrents/Trackers are marked 'Not Working'.

[hu6360567]

Any Updates on this issue? I'm expriencing the same problem with about 7000ms delay of the tracker response.

[simonbcn]

Currently this problem is serious because due to COVID-19 and the confinement of a large part of the world's population, the Internet is very saturated in certain countries and this causes enormous delays in communication which leads to this error.

[phweda]

4.2.5 release seems to have the underlying issue fixed. 4.2.4 libtorrent changes/fixes?

Using 4.2.5:
Win 10 - 80+ days no network issues.
Ubuntu 20.04 35+ days no network issues.