Opened 4 years ago
#12094 new Bug report
Can't restart an upload for a zero length file
| Reported by: | Ian Bagley | Owned by: | |
|---|---|---|---|
| Priority: | normal | Component: | FileZilla Server |
| Keywords: | restarting upload | Cc: | |
| Component version: | server 0.9.60 beta | Operating system type: | Windows |
| Operating system version: | v 1909 (18363.592) |
Description
Client is WinSCP 5.15.9
Trying to upload a file. User has access to target directory for all except delete. So update allowed.
If file is partially complete it works:
(000012) 18/01/2020 19:04:46 - video (192.168.0.1)> 227 Entering Passive Mode (188,223,138,227,207,103)
(000012) 18/01/2020 19:04:46 - video (192.168.0.1)> REST 35178070
(000012) 18/01/2020 19:04:46 - video (192.168.0.1)> 350 Rest supported. Restarting at 35178070
(000012) 18/01/2020 19:04:46 - video (192.168.0.1)> STOR 03-One Man, One Woman.wav
(000012) 18/01/2020 19:04:46 - video (192.168.0.1)> 150 Opening data channel for file upload to server of "/uploads/03-One Man, One Woman.wav", restarting at offset 35178070
(000012) 18/01/2020 19:04:46 - video (192.168.0.1)> TLS connection for data connection established
(000012) 18/01/2020 19:04:48 - video (192.168.0.1)> 226 Successfully transferred "/uploads/03-One Man, One Woman.wav"
If file is present but zero length, i.e. a previous upload failed just after file creation but before any content, it fails:
(000012) 18/01/2020 19:04:56 - video (192.168.0.1)> 227 Entering Passive Mode (188,223,138,227,207,94)
(000012) 18/01/2020 19:04:56 - video (192.168.0.1)> REST 0
(000012) 18/01/2020 19:04:56 - video (192.168.0.1)> 350 Rest supported. Restarting at 0
(000012) 18/01/2020 19:04:56 - video (192.168.0.1)> STOR 09-I'm A Marionette.wav
(000012) 18/01/2020 19:04:56 - video (192.168.0.1)> 550 Permission denied
Instead of restarting at 0, instead it seems to try and do an overwrite but it can't because it can't delete the file. Deleting files being denied by design. Maybe it thinks, "it's zero length, I might as well do the overwrite thing". In this situation there is no way to resolve from client side.
