search

cicku / libproxy

Automatically exported from code.google.com/p/libproxy
GNU Lesser General Public License v2.1
1 stars 0 forks source link

libproxy falsely suggests proxy for ftp:// urls if no ftp proxy is set up #175

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. configure your proxy through the http_proxy and https_proxy env vars
2. do *not* configure $ftp_proxy
3. use the proxy cmdline tool to check a ftp:// url

What is the expected output? What do you see instead?
expected: direct://
instead: content of $http_proxy

What version of the product are you using? On what operating system?
using libproxy 0.4.7 on openSUSE

Please provide any additional information below.

Original issue reported on code.google.com by mathias....@gmail.com on 6 Mar 2012 at 12:47

GoogleCodeExporter commented 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

GoogleCodeExporter commented 8 years ago

Original comment by dominiqu...@gmail.com on 6 Mar 2012 at 8:26

GoogleCodeExporter commented 8 years ago 
KDE 4.8.1

Original comment by mathias....@gmail.com on 20 Mar 2012 at 9:37

GoogleCodeExporter commented 8 years ago 
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

GoogleCodeExporter commented 8 years ago 
Mathias provided the requested info...

Original comment by dominiqu...@gmail.com on 1 Apr 2012 at 1:40

GoogleCodeExporter commented 8 years ago 
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

GoogleCodeExporter commented 8 years ago 
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

GoogleCodeExporter commented 8 years ago 
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

GoogleCodeExporter commented 8 years ago 
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