Johannes Frank commented on NET-642:

The issue with the java way of using proxies is that it's totally cumbersome. 
The fact that commons-net has its own proxy management is basically one of the 
major selling points for us to keep using commons-net. We already have this 
proxy management for several other things but whenever we have alternative 
approaches we take them. Main issue is that especially with proxies that have 
authentication you can basically only have one set of credentials for any given 
proxy server at any given time.

> using execPROT on FTPSClients with Proxy Settings removes Proxy Settings
> ------------------------------------------------------------------------
>                 Key: NET-642
>                 URL: https://issues.apache.org/jira/browse/NET-642
>             Project: Commons Net
>          Issue Type: Bug
>          Components: FTP
>    Affects Versions: 3.6
>         Environment: Java 1.8.0_112
> Linux 64bit
>            Reporter: Johannes Frank
>            Priority: Critical
> In Reference to https://issues.apache.org/jira/browse/NET-578
> I'm trying to establish an FTPS Connection via a HTTP Proxy. The Control 
> Connection is properly established, however the Moment I do execPROT the 
> Proxy settings are resetted by call to setSocketFactory(new 
> FTPSSocketFactory(context)); in FTPSClient.java:534.
> This causes FTPSClients with a call to execPROT to actually ignore the proxy 
> settings and attempt to contact the FTPS Server directly for data connections.
> Since we are required to use PROT P this is currently blocking our feature 
> for FTPS Connections via HTTP proxy.

This message was sent by Atlassian JIRA

Reply via email to