Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=2.7.11 2021-09-16T20:40:05Z 2021-09-16T20:40:05Z David Kalnischkies david@kalnischkies.de 2021-09-16T20:02:26Z urn:sha1:1edf8551cef0a7db7fdcdd5d6b06aec2ea7bb70d RFC7233 3.2 If-Range specifies the comparison to be an exact match, not a less or equal, which makes no sense in this context anyhow. Our server exists only to write our tests against it so this isn't much of a practical issue. I did confirm with a crashing server that no test (silently) depends on this or exhibits a different behaviour not explicitly checked for. 2021-09-16T20:40:00Z David Kalnischkies david@kalnischkies.de 2021-09-16T17:48:33Z urn:sha1:d013f8957c0d464e0059cc107ca79d887cf9f8aa Debian buster (oldstable) ships 6.1 while bullseye (stable) ships 6.5 and so the later is 'fixed'. Upstream declares 6.0 still as supported. It might be still a while we encounter "bad" versions in the wild, so if we can detect and work around the issue at runtime automatically we can save some users from running into "persistent" partial files. References: https://varnish-cache.org/docs/6.4/whats-new/changes-6.4.html#changes-in-behavior 2021-09-16T20:38:46Z David Kalnischkies david@kalnischkies.de 2021-09-16T17:33:24Z urn:sha1:61c1d7d3658fdcd4b32f8b071cef7941120f8abc apt makes heavy usage of HTTP1.1 features including Range and If-Range. Sadly it is not obvious if the involved server(s) (and proxies) actually support them all. The Acquire::http::AllowRange option defaults to true as before, but now a user can disable Range usage if it is known that the involved server is not dealing with such requests correctly.