Opened 15 years ago
Last modified 15 years ago
#5039 new Bug report
Filezilla Seems To Upload Part Files
Reported by: | Gary Jackson | Owned by: | |
---|---|---|---|
Priority: | normal | Component: | FileZilla Client |
Keywords: | incomplete upload | Cc: | |
Component version: | Operating system type: | Windows | |
Operating system version: | Windows XP Pro SP3 |
Description
Using Filezilla Client 3.3.0.1
When I upload new files, Filezilla keeps giving me messages that the file already exists, but the pre-existing file is only a part of the original. I keep on having to click on "resume" to continue uploading.
I've used filezilla for over a year on this PC. Never had a problem before.
Change History (2)
comment:1 by , 15 years ago
Operating system version: | Windows xp home edition → Windows XP Pro SP3 |
---|
comment:2 by , 15 years ago
■os_version changed from Windows xp home edition to Windows XP Pro SP3
Same thing happening here. I have been able to upload large folders (in excess of 50MB) containing lots of small images (5-100kb each), but since I've upgraded to Windows XP Pro SP3 I can now only load part files - only half of these small files 180-250kb upload then Filezilla starts transferring again in a loop with each subsequent attempt transferring less and less.
I have been uploading files to my web server for over a year now (on windows xp) and have never before had any transfer, regardless of size, fail to upload.
I suspect that Filezilla is incompatible with Windows XP Pro SP3 - the files are copied much too fast.
The workaround I am using is uploading the files through my webhost's control panel facility, then I only use Filezilla to check that the files have uploaded to the correct size. A pity - Filezilla used to be good.
Same thing happening here.
I can get small files through (< 1MB), but bigger files report that they are uploading (very fast) in the progress pane, then hang at around 10MB. After maybe 5-10 seconds, winodow pops up asking to replace current file, which is always at around file size 1,700,000.
I managed to get a file through that was 1,601,376 bytes, so it seems the problem lies at around 1.5 MB?