AnInsomniacy/aria2-next v3.0.6

v3.0.6 - Fair Connection Sharing and Implied Ranges

on GitHub

Summary

Aria2 Next 3.0.6 shares a server's connections fairly between downloads when the server limits them, and keeps parallel connections for servers that answer a range request with a 206 but no Content-Range. Release assets cover the same seven platforms.

Changed

• Downloads from one server now share its connections. When the server refuses requests with 429 or 503, its limit is set to the connections it was serving across all downloads; each download keeps at least one connection and the rest are split by remaining bytes. A small download started first no longer starves a large one, and the server sees fewer refused requests. The limit drops at most once per window and grows back while the server stays calm, refusals in a row lengthen the pause before new requests, and Retry-After applies to the whole host. A server is asked afresh once no download uses it any more (#71).

Fixed

• A 206 without Content-Range is placed by its Content-Length when that spans exactly the requested range, as RFC 9110 allows. Downloads from such servers keep their parallel connections instead of falling back to a single connection from byte zero; If-Range still guards the file. A bytes= prefix in Content-Range is accepted (rayburst#734).

Downloads