firefox browse ftp through http proxy
sss...@gmail.com
My corp use only http proxy 192.168.1.100:8080.
When I use wget, e.g.
$ ftp_proxy=192.168.1.100:8080 wget ftp://ftp.xxx.com/
it does not work.
$ http_proxy=192.168.1.100:8080 wget http://www.xxx.com/
it works.
$ firefox ftp://ftp.xxx.com/
..... set all proxies to 192.168.1.100:8080...
it works.
I was confused. I want ftp site accessable in order to update freebsd
package. Is that possible?
give some clue.
Alex K.
I'm confused, too. ;-)
You appear to be saying that it *does* work using Firefox, so it would
seem that your issue relates to wget, rather than FF.
If you are, indeed, asking about wget, then perhaps you could try asking
on a wget forum, newsgroup, or mailing list.
--
Alex K.
Roland de Ruiter
It probably has to do with the FTP data connection mode, active or
passive. This mode determines which party (the client or the server)
initiates the data stream connection. [FTP also uses the command stream,
a connection initiated by the client (wget, Firefox) to port 21 (by
default) on the server.]
In most cases, passive mode works better if you are behind a firewall
(or a proxy, in your case).
<http://en.wikipedia.org/wiki/File_Transfer_Protocol#Connection_methods>
Don't know if wget or FF use passive or active mode by default.
wget has the option to switch between active and passive mode with the
passive_mode=off and passive_mode=on options, respectively. Additionally
there's the commandline argument --no-passive-ftp.
<quote from="man wget">
--no-passive-ftp
Disable the use of the passive FTP transfer mode. Passive FTP mandates
that the client connect to the server to establish the data connection
rather than the other way around.
If the machine is connected to the Internet directly, both passive and
active FTP should work equally well. Behind most firewall and NAT
configurations passive FTP has a better chance of working. However, in
some rare firewall configurations, active FTP actually works when
passive FTP doesn't. If you suspect this to be the case, use this
option, or set "passive_ftp=off" in your init file.
</quote>
So, you may want to try:
ftp_proxy=192.168.1.100:8080 passive_mode=off wget ftp://ftp.xxx.com/
or
ftp_proxy=192.168.1.100:8080 passive_mode=on wget ftp://ftp.xxx.com/
or even
ftp_proxy=192.168.1.100:8080 wget --no-passive-ftp ftp://ftp.xxx.com/
See also:
<http://www.gnu.org/software/wget/manual/html_node/index.html>
<http://www.gnu.org/software/wget/manual/html_node/Startup-File.html>
--
Regards,
Roland
sss...@gmail.com
Yes, wget is simple. FF maybe use some special techniques to make ftp
access work.
my ftp_proxy does not exist. http_proxy=192.168.1.100:8080 does exist.
>$ ftp_proxy=192.168.1.100:8080 wget ftp://ftp.xxx.com/
>it does not work. {ERROR -1: Malformed status line. }
maybe
$ http_proxy=192.168.1.100:8080 wget ftp://ftp.xxx.com/
but also returns
ERROR -1: Malformed status line.
Alex K.
>> You appear to be saying that it *does* work using Firefox, so it
>> would seem that your issue relates to wget, rather than FF.
>
> Yes, wget is simple. FF maybe use some special techniques to make ftp
> access work.
No special techniques at all.
In your original message, you stated:
> $ firefox ftp://ftp.xxx.com/
> ..... set all proxies to 192.168.1.100:8080...
> it works.
So, I took that to mean that you started FF, and, *within* FF's
preferences, you set the proxies. That is *only* for FF, and has no
effect on external programs, such as wget.
> my ftp_proxy does not exist. http_proxy=192.168.1.100:8080 does exist.
>> $ ftp_proxy=192.168.1.100:8080 wget ftp://ftp.xxx.com/
>> it does not work. {ERROR -1: Malformed status line. }
> maybe
> $ http_proxy=192.168.1.100:8080 wget ftp://ftp.xxx.com/
> but also returns
> ERROR -1: Malformed status line.
It sounds to me like, for whatever reason, wget is not picking up the
ftp proxy variable, but thats just a guess.
Again, as I stated in my first response:
"If you are, indeed, asking about wget, then perhaps you could try
asking on a wget forum, newsgroup, or mailing list."
Information on their mailing lists can be found here:
http://wget.addictivecode.org/MailingLists
--
Alex K.