Public bug reported: I'm stuck behind a proxy that seems to filter the if-range header from requests from apt-cacher-ng.
This means that when apt-cacher-ng tries to refresh a volatile file by passing "If-Range: <last known modification time" and "Range: bytes=<last byte of the file>", all the remote server ever sees is the request for the last byte. apt-cacher-ng gets a HTTP 206 response back and concludes that the file hasn't changed. This causes lots of grief because the Release file isn't updated, so the trust path from Release.gpg -> Release -> Packages.bz2 -> checksums of packages is busted. I see this comment in apt-0.8.16~exp12ubuntu8/apt-pkg/acquire-item.cc: // File was already in place. It needs to be re-downloaded/verified // because Release might have changed, we do give it a differnt // name than DestFile because otherwise the http method will // send If-Range requests and there are too many broken servers // out there that do not understand them ..suggesting that I'm far from alone with this problem. ** Affects: apt-cacher-ng (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/983128 Title: Please provide a way to prevent If-Range header use To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-cacher-ng/+bug/983128/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs