Closed GoogleCodeExporter closed 8 years ago
Mathias,
What Desktop Environment are you using for your tests? (Note: libproxy favors
the DE specific configuration over envvars; so if you're in either gnome or
KDE, those specific settings win in any case).
Original comment by dominiqu...@gmail.com
on 6 Mar 2012 at 8:26
Original comment by dominiqu...@gmail.com
on 6 Mar 2012 at 8:26
KDE 4.8.1
Original comment by mathias....@gmail.com
on 20 Mar 2012 at 9:37
and my DE is set to "use env vars", which are set up for "no proxy for ftp".
Original comment by mathias....@gmail.com
on 20 Mar 2012 at 9:37
Mathias provided the requested info...
Original comment by dominiqu...@gmail.com
on 1 Apr 2012 at 1:40
is ftp_proxy not set or is it set 'empty'?
export ftp_proxy="" is not the same as unset ftp_proxy
in case the variable is not set, a 'http fallback is assumed'.
Original comment by dominiqu...@gmail.com
on 1 Apr 2012 at 1:45
ftp_proxy is not set at all:
lemmy@sai:~> set|grep _proxy
http_proxy=http://kotoko.eregion.home:8080
https_proxy=http://kotoko.eregion.home:8080
no_proxy='localhost, 127.0.0.1, .eregion.de, .eregion.home'
Original comment by mathias....@gmail.com
on 1 Apr 2012 at 2:41
maybe "assuming a http fallback" is a bad idea?
In my case, the fallback means that the browser tries to do FTP via my proxy
which is simply not supported by privoxy. That's why ftp_proxy is not set.
Original comment by mathias....@gmail.com
on 1 Apr 2012 at 2:42
in this case you really should "set" ftp_proxy to be empty.
This should get you set up correctly
ftp_proxy="" (do not use a proxy)
ftp_proxy not set: fall back as this is what most users expect to happen and
what historically always did happen in most implementations).
Original comment by dominiqu...@gmail.com
on 1 Apr 2012 at 2:53
Original issue reported on code.google.com by
mathias....@gmail.com
on 6 Mar 2012 at 12:47