Hi micah, On Thu, Apr 17, 2014 at 01:01:54PM -0400, micah wrote: > > I haven't seen any resolution to this problem, just wanted to check in > about it. > > Andi, you said that you allowed all package sources to work around the > issue - can you detail how you did that? I tried to add a glob to the > mirror-dstdomain.acl, but redirections were still refused.
I fear my 'solution' does not help much in your case: I just removed the acl completely. I looked at the issue when trying to find a package cache for debian-lan <URL:https://wiki.debian.org/DebianLAN>. However, I finally decided that it would be better to tune the already implemented squid (for general web traffic) to cache packages too. In that case, restrictions to packet repositories make of course no sense. So I just copied the interesting parts of the squid-deb-proxy configuration (<URL:http://sources.debian.net/src/squid-deb-proxy/0.8.7/squid-deb-proxy.conf>) to my squid configuration (c.f. <URL:http://anonscm.debian.org/gitweb/?p=collab-maint/debian-lan.git;a=blob;f=fai/config/scripts/PROXY/10-config>). Perhaps it is possible to block all content you don't expect from a package repository, but apply no restrictions to the 'package' sources as a workaround? Best regards, Andi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
