Bug#283718: apt does not (always) honor the no_proxy environment variable

2005-01-11 Thread Michael Vogt
On Sun, Jan 09, 2005 at 02:03:07AM -0800, Matt Zimmerman wrote: On Tue, Nov 30, 2004 at 11:09:34PM +0100, Mario Lorenz wrote: Despite previous assertions to the contrary (see eg. #118780), the no_proxy environment variable is not always properly honored. I believe mvo was looking into

Bug#283718: apt does not (always) honor the no_proxy environment variable

2005-01-11 Thread Mario Lorenz
Am 11. Jan 2005, um 12:54:57 schrieb Michael Vogt: But I keep wondering why the putenv(no_proxy) call is there in the first place? I tested the behaviour of this attached patch with squid and it works fine. Its simply too late to make this call. The problem is that direct ftp is handled

Bug#283718: apt does not (always) honor the no_proxy environment variable

2005-01-09 Thread Matt Zimmerman
On Tue, Nov 30, 2004 at 11:09:34PM +0100, Mario Lorenz wrote: Despite previous assertions to the contrary (see eg. #118780), the no_proxy environment variable is not always properly honored. I believe mvo was looking into this. -- - mdz

Bug#283718: apt does not (always) honor the no_proxy environment variable

2004-11-30 Thread Mario Lorenz
Package: apt Version: 0.5.27 Despite previous assertions to the contrary (see eg. #118780), the no_proxy environment variable is not always properly honored. In my particular case, I have a FTP URL of a local mirror in sources.list, and a http://hostname:port style URL in both ftp_proxy and