Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature]: Resume downloads #2051

Closed
radiumatic opened this issue Feb 15, 2024 · 3 comments
Closed

[Feature]: Resume downloads #2051

radiumatic opened this issue Feb 15, 2024 · 3 comments

Comments

@radiumatic
Copy link

radiumatic commented Feb 15, 2024

Hi,
Currently, if dnf or the connection is interrupted, dnf starts the download over. This is specially problematic in unstable networks. You don't want to restart a 200MB download with a very slow connection.

Curl definitely supports resuming downloads. If compatibility is the concern, the accept-ranges header can be checked to ensure the mirror webserver supports this feature. Adding an option to only download from mirrors that support it would also be great.

https://developer.mozilla.org/en-US/docs/Web/HTTP/Range_requests#checking_if_a_server_supports_partial_requests

Assuming that every mirror serves the same binary, it wouldn't cause any problem when switching mirrors.

Please consider this issue with dnf5 as well.

@jan-kolarik
Copy link
Member

Hi, I believe this is a duplicate of the librepo issue, which you can find here: rpm-software-management/librepo#293. Since both dnf4 and dnf5 use librepo as the backend, it's a common issue.

@radiumatic
Copy link
Author

Hi, I believe this is a duplicate of the librepo issue, which you can find here: rpm-software-management/librepo#293. Since both dnf4 and dnf5 use librepo as the backend, it's a common issue.

It seems to be the case, however, the file gets removed also when the connection is interrupted or "suddenly closed". I didn't find any mention of this in that issue.

@jan-kolarik
Copy link
Member

Hi, I believe this is a duplicate of the librepo issue, which you can find here: rpm-software-management/librepo#293. Since both dnf4 and dnf5 use librepo as the backend, it's a common issue.

It seems to be the case, however, the file gets removed also when the connection is interrupted or "suddenly closed". I didn't find any mention of this in that issue.

Thanks, I've linked this use case in that issue. I'll close this one now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants