CWD path with \ between 0.9.60 and 1.6.1

[dcclayton]

Hi,

I have an FTP client (IBM) that connects to FZS 0.9.60:

Code: Select all

Connecting to remote host 10.1.5.24 using port 21.                              
220-FileZilla Server 0.9.60 beta                                                
220-written by Tim Kosse (tim.kosse@filezilla-project.org)                      
220 Please visit https://filezilla-project.org/                                 
IBM                                                                             
331 Password required for ibm                                                   
230 Logged on                                                                   
UNIX emulated by FileZilla                                                      
CWD finance\bacs\bacs-ddr\sales\                                                
250 CWD successful. "/finance/bacs/bacs-ddr/sales" is current directory.

The client sends the path with \

When I try and use FZS 1.6.1, it doesn't handle the \ and works with the /

Code: Select all

Connecting to remote host 10.1.5.45 using port 21.
220-FileZilla Server 1.6.1                        
220 Please visit https://filezilla-project.org/   
ibmbackup                                         
331 Please, specify the password.                 
230 Login successful.                             
UNIX emulated by FileZilla.                       
CWD finance\bacs\bacs-ddr\sales\                  
550 Invalid file name or path                     
CWD finance/bacs/bacs-ddr/sales/                  
250 CWD command successful

Is there a configuration setting I can change to make 1.6.1 accept the path with the \?

Thanks

[botg]

This is desired and intentional behavior. FileZilla Server implements TVFS as defined in RFC 3659, the only path separator is the forward slash. For consistency across platforms, this is not configurable. You need to update to a more modern client.

[dcclayton]

The software developers have changed the client to use a /. I agree is the correct way going forward and was a bit of a bug that it was allowed prior.