[ 
https://issues.apache.org/jira/browse/NET-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16356931#comment-16356931
 ] 

Johannes Frank commented on NET-642:
------------------------------------

No it doesn't because setProxy() resets the Socketfactory to a 
DefaultSocketFactory (which does not utilize TLS) - execPROT("P") earlier 
replaces the socket factory with a specific FTPSSocketFactory and initializes 
the SSL/TLS Context - all of which is lost when setProxy bluntly resets the 
socketfactory to default afterwards in your example.

> 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
(v7.6.3#76005)

Reply via email to