Opened 18 years ago
Closed 15 years ago
#945 closed Bug report (outdated)
File corruption when uploading via SSL (client problem)
|Reported by:||sundansx||Owned by:||Tim Kosse|
|Keywords:||Cc:||sundansx, Tim Kosse|
|Component version:||Operating system type:|
|Operating system version:|
I am using the newest Filezilla Server and newest
I have SSL implicit FTPS setup on both sides. I
uploaded a 3Mb zip file and it is corrupted at the
destination. I am using a proxy (I tried socks 5 and
http proxies) and passive mode. I have used autoTYPE
and also forced BINARY; I have tried this with and
without compression and it still fails. I also am
experiencing a lot of dropped connections that I think
are related to the client.
So to figure out which side is having problems, I used
the WSFTP client to connect to filezilla server via
SSL. and it works fine uploading the same file with no
change to FZ server properties.
It looks like the client might be truncating the files,
as the filesizes look like:
source file: 3,837,305 bytes
dest file: 3,832,693 bytes
FTP open says corrupted file.
thanks for providing a cool program with mucho features.
Change History (3)
comment:1 by , 18 years ago
comment:2 by , 18 years ago
I temporarily worked around the outgoing proxy here and
uploaded the same zip file to the same destination via ssl
and it was successful. So it seems to be related to the
Filezillaclient(win2k)->http1.1 or Socks5
To accomodate the proxy and NAT router I use passive ftp
with port restriction on both ends to 5000-5050 (a port for
my VIOP sits at 5060)
comment:3 by , 15 years ago
|Status:||assigned → closed|
Should have been fixed long time ago. Try the most recent version.
Using both SSL and proxy? I've never tried that combination
myself, I'll do some testing.