AnInsomniacy/aria2-next v2.8.2

v2.8.2 - Crash Recovery and HTTP Range Controls

on GitHub

Summary

Aria2 Next 2.8.2 fixes completed downloads returning after a crash, prevents duplicate torrent submissions from failing the original task, and adds an optional HTTP range-size limit.

Fixed

• Crash recovery: save terminal task state before releasing HTTP recovery data or reporting completion. Failed session writes remain pending and are retried, rather than being treated as saved.
• Session changes: persist pause, resume, removal and task-option changes when session saving is configured. Report write failures to RPC clients and retain recovery data until the corresponding state has been committed.
• Duplicate torrents: route libtorrent's add result to the submitting task, so a duplicate-add error cannot mark the existing torrent as failed.
• Changing HTTP resources: with automatic range sizing, a changed ETag, Last-Modified value or resource size can trigger one restart of an engine-owned partial download from zero, using a single full request. Bytes from different representations are never combined; files without matching recovery ownership remain protected.

Added

• --stream-max-range-size=<SIZE> limits individual HTTP byte-range requests, including the initial request and retries. It applies to single- and multi-connection downloads, accepts byte counts or K, M, G suffixes, and supports values up to 1G. The default, 0, keeps automatic range sizing.

For servers that reject requests larger than 5 MiB:

aria2-next --stream-max-range-size=5M "https://example.com/file.iso"

With a nonzero limit, a server that ignores Range causes an explicit failure; the engine will not bypass the limit with a whole-file request. SFTP transfers, media segment requests and torrent piece sizes are unaffected.

Downloads

The release workflow builds standalone executables and uploads these assets with SHA-256 checksums:

Full changelog: v2.8.1...v2.8.2