If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below. ** If you are logged in, most ads will not be displayed. **

Linux FTP server, Windows Clients: Path Separator Problem

Hi,

I'm attempting to set up a Linux-based server to handle our public FTP. This will be replacing a rather overworked Windows box.

Our clients mainly use automated FTP scripts to supply us with files. I'm aiming to have the Linux server act as a complete 'drop-in' replacement for the Windows box. Key to this, is that I really want to avoid having to ask for changes at the client's end.

Currently, some of the PUT commands issued by the client will be storing to a path using Windows-style backslash-delimited paths.

For example, the root of one of our ftp homes may look something like:

/incoming/
/misc/

and the client app may do a PUT as follows (note the backslash)

PUT C:\SomeFile.Dat incoming\SomeFile.dat

I've tried a couple of FTP servers. pure-ftpd will see that 'incoming\SomeFile.dat', and fail with an invalid filename error. proftpd creates a file named 'incoming\SomeFile.dat' in the root of the ftp home.

I need an FTP server daemon which can handle both back- and forward-slash delimited paths. I'm currently trying to toy with proftpd's mod_rewrite module to replace \'s with /'s using a regex, but I'm failing miserably!

Has anyone got a solution to this? I can't imagine I'm the first to encounter this!