[
https://issues.apache.org/jira/browse/VFS-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yubao Liu updated VFS-660:
--------------------------
Description:
[https://github.com/apache/commons-vfs/pull/35]
In PASV mode, the FTP server returns its server IP (eg. pasv_address in
vsftpd.conf),
when clients are from different subnets through NAT, they expect different
server IP.
This patch exposes the workaround in commons-ftp into commons-vfs:
* use EPSV mode instead of PASV mode, EPSV mode returns only server port
* use PASV mode but overwrite the returned server IP with HostnameResolver
was:
[https://github.com/apache/commons-vfs/pull/35]
In PASV mode, the FTP server returns its server IP (eg. pasv_address in
vsftpd.conf),
when clients are from different subnets through NAT, they expect different
server IP.
This patch exposes the workaround in commons-ftp into commons-vfs:
* use EPSV mode instead of PASV mode, PASV mode returns only server port
* use PASV mode but overwrite the returned server IP with HostnameResolver
> expose workaround for connecting to FTP server from different subnets in PASV
> mode
> ----------------------------------------------------------------------------------
>
> Key: VFS-660
> URL: https://issues.apache.org/jira/browse/VFS-660
> Project: Commons VFS
> Issue Type: Improvement
> Affects Versions: 2.2.1
> Reporter: Yubao Liu
> Priority: Major
> Fix For: 2.2.1
>
>
> [https://github.com/apache/commons-vfs/pull/35]
>
> In PASV mode, the FTP server returns its server IP (eg. pasv_address in
> vsftpd.conf),
> when clients are from different subnets through NAT, they expect different
> server IP.
> This patch exposes the workaround in commons-ftp into commons-vfs:
> * use EPSV mode instead of PASV mode, EPSV mode returns only server port
> * use PASV mode but overwrite the returned server IP with HostnameResolver
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
