Avoid 416 error: Handlet presence of a (previously) completed archive download
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 51
- Forks
- 40
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 3
Description
Noticed while testing some changes to the updater:
2025-10-03T16:17:44+0000 BzQpH9dVFp [info] previous download found; resuming from 291.18MiB
2025-10-03T16:17:44+0000 BzQpH9dVFp [warn] fail to download archive from https://github.com/nextcloud-releases/server/releases/download/v32.0.0/nextcloud-32.0.0.zip. Error: 416
It's a bit weird, as 291.18MiB is the full size of the download. In the end we should handle the error 416 and do a full download.
FYI @joshtrichards since you implemented the resume logic.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Trace the updater's archive resume logic and the handling of HTTP 416 responses, using the reported log and download URL as the starting case. Reproduce a previously completed archive download and verify that a 416 response causes a full download instead of failing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100