Re: ange-ftp vs. $ftp_proxy

[Benjamin Riefenstahl <Benjamin.Riefenstahl@epost.de>]

Hi Dan,


Dan Jacobson <jidanni@dman.ddts.net> writes:
> the entire Emacs Info manual and ange-ftp.el do not mention the word
> ftp_proxy.

Nor does ange-ftp.el mention the words HTTP, HTML, URL or W3.  To me
that indicates that AngeFTP can only do FTP.

> (getenv "ftp_proxy") for me gives "http://localhost:8080/",
> i.e. wwwoffle.

To me this indicates that you have an FTP-to-HTTP gateway running, but
AngeFTP doesn't do HTTP, so this is not usefull to AngeFTP.

> Why not "modernize" ange-ftp to use the ftp_proxy env variable if it
> finds it non empty?  e.g. would wget or lynx be so oblivious? No.

Wget and lynx are primarily HTTP application.  They just also do FTP,
if required.  AngeFTP only does FTP.


If you want AngeFTP to use a proxy, it should be an FTP-to-FTP relay.

If you want to do HTTP, you can look at w3 or emacs-w3m (sp?). 

If you want the same convenience for HTTP, that AngeFTP gives for FTP,
than you need WebDAV support.  I'm not aware of an ELisp implemention
for that or if anybody works on this currently.


Hope this helps, benny