I tried to re-create your setup for reproducing the bug.
This is what I've done using Trusty 14.04.3 for all machines:
Created a router vm that will nat all traffic and manage dns/dhcp of a dedicated subnet for those tests.
On this subnet there is a apt-mirror setup vm with squid-deb-proxy installed (using apache2 default setup to serve files)
The dns redirect fr.archive.ubuntu.com and archive.ubuntu.com to the apt-mirror setup (mirror: 192.168.101.2)
I have a client vm in this subnet, with a squid-deb-proxy-client setup. I could update and install packages both from fr.archive.ubuntu.com and archive.ubuntu.com, while checking that it really end-up in the apt-mirror vm, and that was the case for both targets. No 403 errors, and using stock squid-deb-proxy mirror-dstdomain.acl file.
So I will mark it as incomplete, because I couldn't reproduce it, feel free to re-open with more details if you think it is still relevant.
Hi José,
I tried to re-create your setup for reproducing the bug.
This is what I've done using Trusty 14.04.3 for all machines:
Created a router vm that will nat all traffic and manage dns/dhcp of a dedicated subnet for those tests.
On this subnet there is a apt-mirror setup vm with squid-deb-proxy installed (using apache2 default setup to serve files)
The dns redirect fr.archive. ubuntu. com and archive.ubuntu.com to the apt-mirror setup (mirror: 192.168.101.2)
I have a client vm in this subnet, with a squid-deb- proxy-client setup. I could update and install packages both from fr.archive. ubuntu. com and archive.ubuntu.com, while checking that it really end-up in the apt-mirror vm, and that was the case for both targets. No 403 errors, and using stock squid-deb-proxy mirror- dstdomain. acl file.
So I will mark it as incomplete, because I couldn't reproduce it, feel free to re-open with more details if you think it is still relevant.