Looking deeper, I think we might also have a backend that's not correctly handling If-Range and returning the 416 before considering if the Release file is out of date, which is why we get stuck in a file size mismatch between Releases and Packages.gz.
Does look like there are maybe some issues around the handling of that error, and certainly the check for the host supporting range support. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849368 Title: apt-get update issues invalid range requests for previously completed downloads To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1849368/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
