[ http://issues.apache.org/jira/browse/FTPSERVER-53?page=all ]

Niklas Gustavsson closed FTPSERVER-53.
--------------------------------------

    Resolution: Fixed
      Assignee: Niklas Gustavsson

Fixed. The current implementation is pretty naive but does the job. It supports 
listing a port values (as before) as well as both closed and open ended ranges. 
So, for example:
1,2,3
1-3
-3
1,2,3-8

> Support specifying a range of passive ports
> -------------------------------------------
>
>                 Key: FTPSERVER-53
>                 URL: http://issues.apache.org/jira/browse/FTPSERVER-53
>             Project: FtpServer
>          Issue Type: Improvement
>            Reporter: Clinton Foster
>         Assigned To: Niklas Gustavsson
>
> The config.data-connection.passive.ports configuration parameter allows 
> specifying either 0 (any available port) or a comma-separated list of ports. 
> But passive mode is increasingly becoming the standard these days, and it 
> isn't practical to specify all the ports needed for a reasonable number of 
> simultaneous passive connections in a comma-separated list. I believe most 
> FTP server administrators expect to be able to specify a range of ports.
> It would probably be sufficient to assume if the configuration string 
> contains a dash, it specifies a range instead of a list. Even better would be 
> to allow a comma-separated list of multiple ranges and/or individual ports, 
> e.g. 1025-2025,5055-6000,2323.  But initially I think it would be sufficient 
> to support only a single range. In other words, if the value contains a dash 
> anywhere in the string, assume it is a range of ports. (If multiple ranges 
> are needed, support for this could easily be added later without breaking 
> existing configurations.)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to