Aglet

Triage a large download that resumes at the wrong range

A resumed download can restart from zero, append overlapping bytes, or continue against a different document revision. Triage should record the partial file length, requested and returned ranges, selected identity, and final bytes. The aim is to find the first disagreement without trusting a percentage alone.

Establish what is happening

  1. Capture the partial state

    Record document identity or revision, total length if known, local bytes retained, interruption point, and the next range requested. Note whether the reader paused, lost connectivity, closed the app, or retried from a stale partial file.

  2. Compare range evidence

    Inspect response range, total length, content type, and identity context against the local partial length. Mark inclusive or exclusive endpoints and identify whether a response can be appended safely to the retained bytes.

  3. Classify the result

    Classify the case as restart, overlap, gap, revision mismatch, unsupported resume, or unclear server response. Preserve a successful full download for comparison and state what recovery action is safe for the observed partial state.

What to carry forward

Triage is complete when the partial length, requested range, returned range, document identity, and assembled result are recorded. If range or identity evidence is absent, classify the missing evidence separately from the observed inability to resume.

Technical background: MDN reference.

Keep the decision with the work.

Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.

Create an account See the product workflow