commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (JIRA)" <>
Subject [jira] [Commented] (NET-508) Add support for FTP proxies
Date Tue, 04 Jun 2013 19:09:20 GMT


Sebb commented on NET-508:

AFAICT it's already possible to use NET code with an FTP proxy.
One just has to connect (and perhaps login) to the proxy rather than the target host, and
then tell the proxy how to connect to the target host.

After that presumably one uses standard FTP commands which are routed via the proxy.

What about logout? How does that work?

I not entirely convinced that there is a need to create a special method to do the work.

Expecially since there is no standard for this - the resulting method might become very complicated
if it has to support lots of different server types. That is going to be additional work to
maintain, and the user base for such proxies is likely to be a very small percentage of NET

Whereas it would be relatively easy for the end user to create a specific login script for
their particular proxy, perhaps from an example template which they could customise.
> Add support for FTP proxies
> ---------------------------
>                 Key: NET-508
>                 URL:
>             Project: Commons Net
>          Issue Type: Improvement
>          Components: FTP
>    Affects Versions: 3.2
>            Reporter: Arno Unkrig
> The COMMONS-NET FTP client supports 'FTP over HTTP', but not the other popular FTP proxy
schemes. The article
> describes some of them, but not very precisely an obviously a bit incorrect.
> I added proxy support for the ANT FTP task in
> (search for string "proxyServer"), but I believe that the feature should be implemented
in COMMONS-NET, not in the application, maybe like this:
> {code}
> connectToProxyAndLogin(server, port, userid, password, proxyServer, proxyPort, proxyUserid,
> {code}
> The proxy server that I (must) use is
> {noformat}
> 220 McAfee Web Gateway 7.2.0 build 13935
> {noformat}
> , and from experiments it supports the following authentication schemes:
> {noformat}
>  (1) USER pu PASS pp OPEN[:port] USER u                     PASS p
>  (2) USER pu PASS pp                          USER[:port] PASS p
>  (3) USER pu PASS pp SITE[:port] USER u                     PASS p
> {noformat}
> I don't know which FTP proxy servers support which of these flavors, but (2) appears
to be the most natural and robust to me.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message