I believe the problem is erroneous URL encoding/escaping. With `deb mirror://mirrors.ubuntu.com/mirrors.txt` in sources.list, apt- cacher-ng's logs show this:
403 Forbidden file type or location: http://mirrors.ubuntu.com/mirrors.txt?arch=amd64&dist=saucy-updates Adding anything matching /mirrors.txt/ to acng's volatile file list (VfilePattern) changes this from a 403 Forbidden (generated by acng) to a 404 (proxied from mirrors.ubuntu.com). However hitting http://mirrors.ubuntu.com/mirrors.txt?arch=amd64&dist =saucy-updates directly is 200 OK. Using mitmproxy I can see that apt-cacher-ng is URL-escaping the question mark and ampersands: >> GET >> http://mirrors.ubuntu.com/mirrors.txt%3farch%3damd64%26dist%3dsaucy-updates ← 404 text/html 327B 303.73kB/s So that explains the 404, and it probably also explains the 403; once URL-escaped, it's probably not matching the default VfilePattern regexp. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1237456 Title: mirror: protocol failing again To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-cacher-ng/+bug/1237456/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
