Enhancment: Gracefully handle downloading if Range Requests aren't supported

Open
#55 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
go
Domain
cli, networking

Research direction

No file, test, or entry point is identified in the issue; begin by locating the range-request handling and its download tests. Done means a server without Range support no longer causes pget to error and the complete-download behavior is covered, including whether it is optional.

Written by the indexing model from the issue text.

Description

enhancement

If a range request isn't supported pget will error. PGET should instead download the complete file slowly (at least optionally).

Dominant language
Go
Stars
151
Forks
7
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from replicate/pget

All issues in replicate/pget

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.