[Feature] server timeouts #1015
Description
I've been downloading files from a server that is often timing out, heavy throttling of the number of connections per server, and only downloading bursts of data round-robin with other users. (coomer)
First - this means that I can't queue a download as ABDM as checks the file exists first. 80% of my downloads fail at this point. I can sit and refresh several times but I wish to just bypass the check :) It also doesn't show the difference between 'server timeout' vs '404 file not found' which initially was very confusing. Also, it doesn't check to see if the file has possibly already been downloaded based on filename unless it succeeds this check which makes it very difficult to quickly check which links were queued.
Second, if the queue is running and at that moment gets as timeout, the download will immediately change to amgiguous 'error' and not queue and retry. Ideally I just want it to be tried again later.
Third, to make sure I don't trigger Cloudflare throttling, i've needed to put the whole queue to "1x download only" and "300x retries". The downloads burst a few mb at a time, meaning ABDM spends more time disconnecting and reconnecting rather than having a longer timeout for this server - tho I can't be sure as I can't find logs. There are multiple servers they use. Ideally a "per server setting" for "only X connections to this server maximum" would be ideal, along with the retry override for these servers (or a timeout setting of some kind)
Server details - coomer.st (eg n2.coomer.st)
Currently using v1.8.3. Happy to split into feature requests if needed :)