Can a stalled download in #KGet be resumed without redownloading already downloaded content?

The file is https://public.db.files.1drv.com/y4mVErXGDq33Kw1khYR-Ag3FSmDwYAoTEYmBH230BxXKOlaH8DtsPVUWHlCV85VCjLr_uMcKadKcXAsKjXKu_2eHa4IqVoQkQT_SXIQcRZHVzUe1uJ98vp_lLXo7QJ8mbyVnZYQ-MatsmbpFzU77d6jjbQYThjtoegmuwVZUUiKpFikwGBm_ZDtkLjDp3OntIrz7Rp2SHnr33VPKZxn21WqkRoZCB4d3NqwbY4zFNzv2rk?AVOverride=1

In order to prepare, I set my power settings so that the PC downloading the file would not sleep

because that presumably prevent it downloading. I then left it to download for a few hours, and it downloaded approximately

and was continuing at a steady pace. Consequently, I left it for a few more hours, and came back to check again, only to find that it had

Stalled

per

Can this be remediated? Would more information be necessary? I’m not sure where to go from here – I don’t want to download the 28 GiB already downloaded again.

KGet will resume if the source supports range requests.

That URL doesn’t respond with an Accept-Ranges header, so it appears the source does not support resuming.

1 Like

How could one check?

You can use curl -I to check the headers.

1 Like

Seems like the stall was because it took so long to download that the server revoked my authentication to access the file, so that wouldn’t have been much use. :<

curl -I 'https://public.db.files.1drv.com/y4mVErXGDq33Kw1khYR-Ag3FSmDwYAoTEYmBH230BxXKOlaH8DtsPVUWHlCV85VCjLr_uMcKadKcXAsKjXKu_2eHa4IqVoQkQT_SXIQcRZHVzUe1uJ98vp_lLXo7QJ8mbyVnZYQ-MatsmbpFzU77d6jjbQYThjtoegmuwVZUUiKpFikwGBm_ZDtkLjDp3OntIrz7Rp2SHnr33VPKZxn21WqkRoZCB4d3NqwbY4zFNzv2rk?AVOverride=1'
HTTP/2 404 
content-length: 0
p3p: CP="BUS CUR CONo FIN IVDo ONL OUR PHY SAMo TELo"
x-msnserver: DU6PPF08F80DDA5
strict-transport-security: max-age=31536000; includeSubDomains
ms-cv: zabwaeg96kOLCh7WLkgDwg.0
x-qosstats: {"ApiId":0,"ResultType":2,"SourcePropertyId":0,"TargetPropertyId":42}
x-throwsite: 4fd7.4ddf
x-clienterrorcode: ItemDoesNotExist
x-errorcodechain: ItemNotFound,UrlExpired
x-asmversion: UNKNOWN; 19.1258.922.2014
x-cache: CONFIG_NOCACHE
x-msedge-ref: Ref A: 890036906C3C4EADA33BB1FFC1B37BFA Ref B: LTSEDGE2113 Ref C: 2023-10-08T01:12:44Z
date: Sun, 08 Oct 2023 01:12:44 GMT

Thanks lots, though! That shall be useful in a lot of scenarios.