If a download stalls, i.e., no bytes are received for a significant period, it may be better to restart the download as this may indicate a network glitch.
For large requests (e.g. downloads in the GiB to TiB range) this is a better configuration parameter than a simple timeout, as the transfers will take minutes or hours to complete. Relying on a timeout value for them would not work, as the timeout would be too large to be useful. For small requests, this is as effective as a timeout parameter, but maybe unfamiliar and thus harder to reason about.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-04-02 UTC."],[[["The page provides documentation for the `DownloadStallTimeoutOption` across multiple versions, ranging from 2.11.0 to the latest release candidate, 2.37.0-rc."],["`DownloadStallTimeoutOption` is used to manage download interruptions due to network issues, by restarting downloads if no bytes are received for a certain period."],["This configuration is specifically designed for large downloads, where traditional timeouts are ineffective due to the long duration of the transfers."],["The `DownloadStallTimeoutOption` works by specifying a time duration, during which if no bytes are received, it will be considered a stall, and it uses `std::chrono::seconds` as its type alias."]]],[]]
