Hello Mark, If I understand your proposal correctly, this would allow a list of proxies to be defined for use with a set of backend servers, allowing for even more flexibility (if different proxies are needed to access different repositories). This sounds like a good idea, at least as long as it remains possible to configure some of the targets to be tried for access using several methods (proxy/proxies and direct, whichever happens to work at the moment - with reevaluations done if a previously working method no longer succeeds for whatever reason out of our control).
I'd prefer to set up a complex server-side installation (apt-cacher picking different routes to get the packages it does not have in cache) rather than maintain complex setups for each APT client program ;) Thanks, //Jim --- I think we could address this by optionally having the configuration option http_proxy be a list (similar to path_map) that is used to lookup request hostnames and return the upstream proxy to be used. No entry in the list for a direct request. Would that address your case? Best wishes Mark
