Bug#981166: apt-cacher-ng HTTPS URLs cannot be pinned
Package: apt
Version: 2.1.18
Severity: wishlist
Control: affects -1 apt-cacher-ng
Quack,
I am using apt-cacher-ng and in order to use https I'm using the method
recommended by its author by prepending HTTPS/// to the host, which
gives URLs of the like:
http://HTTPS///myrepo.example.com/debian
Previously I was using o= to match but now prefers matching with the
origin. I realized that when using a proxy with this trick, and even if
I encode the slashes as %2f it is not matching. In fact after looking
into the code I found out it simply split at the first slash, and
matches with "HTTPS" which means it de facto matches all my configured
sources, not very practical.
I did not find any way to work around this problem. Would it be possible
to split using the non-decoded string maybe? (and we could ask the
apt-cacher-ng to recommend the encoded version instead) Or any other
solution?
Regards.
\_o<
--
Marc Dequènes
Reply to: