Custom Query (8105 matches)
Results (382 - 384 of 8105)
|#7948||duplicate||Active ftp over socks proxy implemented incorrectly|
In Filezilla 3.5.3, specify active ftp and no fallback, and a socks5 proxy. Connect to a ftp server, this is done correctly over the socks proxy. Download something, and observe that a *passive* data connection is created over the socks proxy instead of an active one.
|#1179||Active mode data connection is made from the wrong port|
According to the FTP specification (RFC0959), in active FTP mode, the data connection should be made from port L-1, where L is the port that the server is listening for control connections (see section 3.2 Establishing Data Connections, paragraph 1). This should be true for every active mode transfer.
FileZilla Server attempts to bind the outgoing port as per specification, but fails to do this when another active mode data connection exists. The second connection will get port L+1, and if a third connection is opened, then it will get an arbitrary OS-assigned port.
0.9.4, 0.9.8a, 0.9.19)
host to the same server host.
-n" on the client host.
requested local port is already used by another socket.
setsockopt(socket, SOL_SOCKET, SO_REUSEADDR, ...) call, passing TRUE as the option value, before binding the socket.
|#1775||Active/Passive selection per server|
It would be nice if the passive switch were moved from the settings menu to individual servers in the site manager list. Some servers require an active connection and some require a passive connection.