[jira] [Comment Edited] (NET-642) using execPROT on FTPSClients with Proxy Settings removes Proxy Settings

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] [Comment Edited] (NET-642) using execPROT on FTPSClients with Proxy Settings removes Proxy Settings

JIRA jira@apache.org

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

Johannes Frank edited comment on NET-642 at 8/11/17 10:17 AM:
--------------------------------------------------------------

I have the unit test but how and to which branch should I create a PR for that?

Edit: NVM, done. You have a Pull Request https://github.com/apache/commons-net/pull/27


was (Author: djgummikuh):
I have the unit test but how and to which branch should I create a PR for that?

> 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
(v6.4.14#64029)
Loading...