Possible filename corruption on transfer resume/transfer

Jim Snyder
Joined:: 2018-05-07
Posts:: 1
Location:: Columbus, Ohio

Possible filename corruption on transfer resume/transfer

2018-05-07 17:01

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?

Reply with quote

martin◆ Site Admin
Joined:: 2002-12-10
Posts:: 40,567
Location:: Prague, Czechia

Re: Possible filename corruption on transfer resume/transfer

2018-05-08

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 https://winscp.net/eng/docs/resume#automatic

Reply with quote

You can post new topics in this forum

Possible filename corruption on transfer resume/transfer

Possible filename corruption on transfer resume/transfer

Re: Possible filename corruption on transfer resume/transfer

Documentation

Support

Associations

Follow Us