Files uploaded using FTP are corrupted on server

Advertisement

Golfer
Joined:
Posts:
2
Location:
UK

Files uploaded using FTP are corrupted on server

Is this a known issue (I could not find it)?

I am using WinSCP Synchronise option in 4.0.0 (Build 342) to upload files onto UNIX server using FTP protocol. However, some ascii files are regularly corrupted, with the last part of the file appended twice (last block?). As some of these files are PHP scripts, this corrupts the PHP scripting.

Is there a workaround for this problem? I so much wish to use WinSCP for FTP transfers, but this is a significant problem.

Thanks,
Nick.

Reply with quote

Advertisement

Golfer
Joined:
Posts:
2
Location:
UK

Re: Files uploaded using FTP are corrupted on server

Thanks Martin,

I had not seen the History page, sorry!

I am looking forward to being able to use WinSCP for FTP transfers as well as the existing formats.

Thank you for developing this into the WinSCP product.

Much appreciated.

Nick.

Reply with quote

Pepillo
Guest

Problem still exists!

I am using WinSCP 4.1.9 (Build 416) under Windows (Norton Commander style, german language) to upload files onto UNIX server (Type L8, No native text mode transfers) using FTP protocol. Sometimes (but continuous!) after pressing F5 to start ASCII file uploads (PHP scripts) WinSCP reports "Lost connection, time is up", reconnects and resumes. After that the destination file on the server is corrupted, with the last part of the file appended twice. After repeating the file upload (F5), the destination file has double size, after another upload it has triple size, and so on ...
Disabling the automatic reconnect does not solve the problem.
So I have to close the connection, reconnect and redo the file upload.
This is a significant problem, because the corrupted PHP script damages the related web site for some seconds!
The history page reports this error fixed since 4.0.1 beta, but it still exists in 4.1.9 (maybe in 4.2 beta?).
I really like WinSCP and would be happy if this can be fixed!
Thank you very much!
Pepillo

Reply with quote

martin
Site Admin
martin avatar
Joined:
Posts:
41,468
Location:
Prague, Czechia

Re: Problem still exists!

Pepillo wrote:

I am using WinSCP 4.1.9 (Build 416) under Windows (Norton Commander style, german language) to upload files onto UNIX server (Type L8, No native text mode transfers) using FTP protocol. Sometimes (but continuous!) after pressing F5 to start ASCII file uploads (PHP scripts) WinSCP reports "Lost connection, time is up", reconnects and resumes. After that the destination file on the server is corrupted, with the last part of the file appended twice. After repeating the file upload (F5), the destination file has double size, after another upload it has triple size, and so on ...
Disabling the automatic reconnect does not solve the problem.
So I have to close the connection, reconnect and redo the file upload.
This is a significant problem, because the corrupted PHP script damages the related web site for some seconds!
The history page reports this error fixed since 4.0.1 beta, but it still exists in 4.1.9 (maybe in 4.2 beta?).
Can you send me an email, so I can send you back a debug version of WinSCP to track the problem? Please include link back to this topic in your email. Also note in this topic that you have sent the email. Thanks.

You will find my address (if you log in) in my forum profile.

Reply with quote

Advertisement

Pepillo
Joined:
Posts:
3
Location:
Germany

Problem did not occur anymore

I used the debug version of WinSCP for a week for all my file transfers. The problem did not occur anymore with this version. So I assume the problem is fixed in the last beta version and I will upgrade to 4.2.2 beta.
Usually I'm afraid of beta versions, therefore I didn't try the upgrade before.
Thank you very much!
Pepillo

Reply with quote

martin
Site Admin
martin avatar
Joined:
Posts:
41,468
Location:
Prague, Czechia

Re: Problem did not occur anymore

Pepillo wrote:

I used the debug version of WinSCP for a week for all my file transfers. The problem did not occur anymore with this version. So I assume the problem is fixed in the last beta version and I will upgrade to 4.2.2 beta.
Usually I'm afraid of beta versions, therefore I didn't try the upgrade before.
Let me know if 4.2.2 helps or not.

Reply with quote

Pepillo
Joined:
Posts:
3
Location:
Germany

Re: Problem did not occur anymore

Just to close this thread:
I'm using WinSCP 4.2.3 beta since 4 weeks now, and I never again encountered the corrupted file problem or the timeout problem anymore with this version. So I confirm the problem to be fixed.

WinSCP continues to be the best FTP client available!
Thank you very much, good job!

Pepillo

Reply with quote

Advertisement

wwwalker
Joined:
Posts:
4
Location:
Caboolture QLD Australia

corrupted HTML header when uploaded using FTP

When I upload using WinSCP 5.7 Build 5125 on Windows 8.1, I get some of header lines e.g. meta inserted near bottom corrupting HTML.

I had to ssh to server and edit using vi to find error and correct it on server.

That is when I worked out it was not the Apache server but the FTP client.

This is a bug in WinSCP.

It did not happen on earlier versions.

The corrupted HTML came from meta tags in HEAD and <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">.

Sample of corrupted HTML:

Before:

<li><a name="20060213"></a><a href="...">'Your say</a> <i>Central Western Daily</i>, 13 Feb 2006 - re Workcover NSW locking small business into an agency not of their choice for 12 months
</ul>
</ul>

After:

<li><a name="20060213"></a><a href="...">'Your say</a> <i>Central Western Daily</i>, 13 Feb 2006 - re Workcover NSW locking s<html> <head> <meta name="description" value="WWce for 12 months </ul> </ul>

Reply with quote

wwwalker
Joined:
Posts:
4
Location:
Caboolture QLD Australia

sftp needed to stop HTML being corrupted

It was not WinSCP 5.7 that corrupted upload of HTML to my hosting company a2hosting.com.

HTML was also corrupted on put but not get using Windows FTP to my hosting company.

I zipped the HTML file and used binary and it was not corrupted using put with Windows FTP to my hosting company but I had to ssh in to unzip the file.

I tested upload using WinSCP 5.7 on another site using sftp and HTML was not corrupted.

I then got weird port number for sftp off my hosting company and found sftp using WinSCP 5.7 to my hosting company does not corrupt HTML files any more.

So it was not WinSCP 5.7 at all. It was the protocol and the hosting company's port settings - all very devious of the hosting company which took 2 or 3 days to sort out.

Reply with quote

Advertisement

You can post new topics in this forum