On Fri, May 23, 2014 at 02:12:08PM +0200, Jim Klimov wrote: > While exploring our options, we brought over mirrors of (Em)Debian > repositories and deployed as local mirrors. There is also a corporate HTTP > proxy to access the internet for i.e. updates. > It is possible to configure a "localhost" or otherwise local server as a > backend server for a source (via "path_map") and use it if "use_proxy=0". > However, the internet sources are not accessible because explicit use of > the proxy is required by corporate networking. > It is possible to configure the internet sources like "ftp.XYZ.debian.org" > as backend servers for the sources and access them with "use_proxy=1". > However, the local (faster) mirrors of available packages, as well as > origin repositories of our own development, are thus inaccessible for > apt-cacher - because the corporate proxy does not relay those local > resources (hosted on each developer's "localhost" in the extreme case - and > obviously resolving to a different system by the corporate proxy server).
Actually, I think there maybe a way to do this already if you have curl 7.19.4 or later. If you set CURLOPT_NOPROXY to 'localhost', I think the libcurl backend should not use a proxy. Have a look at man curl_easy_setopt(3). You can do this by adding this fragment to a file in /etc/apt-cacher/conf.d libcurl = noproxy localhost Mark -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
