Why must ftp_proxy be HTTP?

[Fung Chai]

Hi,

I went through the source code (src/retr.c) of wget-1.8.1 and notice that
the ftp_proxy must be HTTP; the user cannot specify it as ftp://proxy:port.
In the direct mode (ie, use_proxy is set to false), retrieve_url() will use
the FTP protocol to retrieve a file, but will use the HTTP protocol to
retrieve the file via the proxy.

Why is this?

I was trying to mirror an FTP site with wget.  I had to specify ftp_proxy,
without which, wget seems to hang.  I noticed that I could not get the
timestamps of any file.  Nor did I get any .listing file, instead I got
autogenerated index.html of the directory.  Please advice.

Please reply to me directly as I am not on the mailing list.  Thanks in
advance.

Regards,
fclim.

Re: Why must ftp_proxy be HTTP?

[Ian Abbott]

On Tue, 7 May 2002 17:18:57 +0800 , Fung Chai [EMAIL PROTECTED]
wrote:

I went through the source code (src/retr.c) of wget-1.8.1 and notice that
the ftp_proxy must be HTTP; the user cannot specify it as ftp://proxy:port.
In the direct mode (ie, use_proxy is set to false), retrieve_url() will use
the FTP protocol to retrieve a file, but will use the HTTP protocol to
retrieve the file via the proxy.

Please try the current development version of Wget from the CVS
repository, as this has support for FTP gateway proxy servers
(FWTK-style proxies, according to the ChangeLog), but the
functionality needs testing.