No. Authentication.conf provides additional information based on the host used.
The problem here is that pycurl is used as blackbox and our wrapper do not attempt to decorate the HTTP[S]_PROXY variable(s).
Then, the urllib implementation lacks SSPI support.
For your last question, authentication.conf doesn't try to associate a proxy with a project.
Proxies are associated with hosts. If your projects are on different hosts, then fine.
Wether or not you need a proxy for a host is also configured via the no_proxy environment variable.
Or more appropriately for windows (but this is relevant for urllib implementation only) from either the environment variables *or* the Internet Settings found in the registry by python (see python urllib.py getproxies_registry() for the gory details).
No. Authentication.conf provides additional information based on the host used.
The problem here is that pycurl is used as blackbox and our wrapper do not attempt to decorate the HTTP[S]_PROXY variable(s).
Then, the urllib implementation lacks SSPI support.
For your last question, authentication.conf doesn't try to associate a proxy with a project.
Proxies are associated with hosts. If your projects are on different hosts, then fine.
Wether or not you need a proxy for a host is also configured via the no_proxy environment variable.
Or more appropriately for windows (but this is relevant for urllib implementation only) from either the environment variables *or* the Internet Settings found in the registry by python (see python urllib.py getproxies_ registry( ) for the gory details).
What bzr http implementation are you using ?