Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)


Topic review


Re: Possible filename corruption on transfer resume/transfer

Please attach a full session log file showing the problem (using the latest version of WinSCP).

To generate the session log file, enable logging, log in to your server and do the operation and only the operation that causes the error. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you can mark the attachment as private.

Why do you suspect "temporary renaming"? Anyway, see
Jim Snyder

Possible filename corruption on transfer resume/transfer

We just switched from FileZilla to WinSCP for transfers of .txt and .csv files to a certain client. We received notice from them that the filename for one of the files they received was begun with a carriage return. How does the temporary renaming work and is this possibly caused by enabling transfer resume/transfer to temporary filename for a non-binary file transfer?