FileServer FileUploaded event file path contains "filepart" for larger files being upload

0 votes
asked Sep 6 by craigd (150 points)

When monitoring file uploads to a FileServer instance using the FileUploaded event, FileTransferredEventArgs filename fields contain a suffix of "filepart" for files of any significant size.

As far as I can tell, the event is only called when the file transfer is completed, so I am confused why the event doesn't have the final file name. Is this by design and i am doing something incorrectly?

Kind Regards

Applies to: File Server

1 Answer

0 votes
answered Sep 6 by Lukas Matyska (38,360 points)
selected Sep 8 by craigd
Best answer

As far as I know, FileServer should not modify any names which comes from client. So it seems that the "filepart" suffix was added by client.

Can you please send us communication log to (or post it here). It can be created like this:

var server = new FileServer();
server.LogWriter = new Rebex.FileLogWriter("C:/server/log.txt", Rebex.LogLevel.Debug);

This is server log when I upload 185 MB file:

2017-09-06 18:45:10.649 DEBUG SftpModule(1)[8] SFTP: Opening file '/OUT/' (Create, Write): success.
2017-09-06 18:45:15.033 DEBUG SftpModule(1)[10] SFTP: Closing file '/OUT/': success.

My output from FileUploaded event:

File upload finished.
User: 'tester'
File: 'c:\temp\OUT\'
total bytes: 185523333

As you can see, there is no "filepart" suffix.

commented Sep 6 by craigd (150 points)
I have executed testing  using Mac OSX sftp command and also WinSCP.   It looks like the behaviour of WinSCP is different to Mac.

code is here:
class Program
        static void Main(string[] args)
            var server = new FileServer();
            server.Bind(22, FileServerProtocol.Sftp);
            server.Keys.Add(new SshPrivateKey("private.key", "test"));
            server.Users.Add("WinSCP", "test", "C:/ftproot");
            server.Users.Add("MacOSX", "test", "C:/ftproot");
            server.FileUploaded += Server_FileUploaded;
            server.LogWriter = new Rebex.FileLogWriter("C:/ftproot/log.txt", Rebex.LogLevel.Debug);

        private static void Server_FileUploaded(object sender, FileTransferredEventArgs e)
            File.AppendAllText("C:/ftproot/UploadLog.txt", $"{DateTime.Now.ToString("u")} COMPLETE BytesTransferred={e.BytesTransferred.ToString("#,##0")} Path='{e.Path}' User='{e.User.Name}'\r\n");

I have sent logs from above via email.
commented Sep 7 by Lukas Matyska (38,360 points)
Thank you for the log file. It showed that the "filepart" behavior is done by WinSCP client on purpose. For some files (probably greater than X bytes), WinSCP uploads the file with .filepart extension and after successful transfer it renames it to original name. See following part of the log:

2017-09-07 07:12:31.145 DEBUG SftpModule(2)[20] SFTP: Getting item info on '/IMG_0041.JPG': not found.
2017-09-07 07:12:31.145 DEBUG SftpModule(2)[21] SFTP: Getting item info on '/IMG_0041.JPG.filepart': not found.
2017-09-07 07:12:31.146 DEBUG SftpModule(2)[21] SFTP: Opening file '/IMG_0041.JPG.filepart' (Create, Write): success.
2017-09-07 07:12:31.156 DEBUG SftpModule(2)[21] SFTP: Closing file '/IMG_0041.JPG.filepart': success.
2017-09-07 07:12:31.165 DEBUG SftpModule(2)[21] SFTP: Renaming '/IMG_0041.JPG.filepart' to '/IMG_0041.JPG': success.
2017-09-07 07:12:31.166 DEBUG SftpModule(2)[21] SFTP: Setting item info on '/IMG_0041.JPG': success.

WinSCP performs these steps:

 1. Check whether '/IMG_0041.JPG' exists
 2. Check whether '/IMG_0041.JPG.filepart' exists
 3. Upload file to '/IMG_0041.JPG.filepart'
 4. Rename '/IMG_0041.JPG.filepart' to '/IMG_0041.JPG'

This behavior cannot be modified by the server.
commented Sep 8 by craigd (150 points)
Thankyou so much for this. Wasn't something I considered!

It seems there is a way to turn off this behaviour in WinSCP so that should be sufficient.