Pre bug report discussion: Empty transfers

[chrispink]

MacOS 12.6.3 Cyberduck 8.6.0

I am getting persistent empty transfers (0 B). As far as I can tell, it's only with overwrites.

The Transfer window reports successful, with a summary of bytes transferred but the file is empty and the listing shows 0 B
Repeating the transfer give the same result
The only way to work around this behaviour is to quit and restart Cyberduck. This consistently resolves the issue temporarily.

This is happening since the previous version of Cyberduck, the version above was an update to try and resolve the issue.

Does anyone else have this issue?

[tatze96]

Is a specific protocol (e.g. WebDAV, S3, OneDrive, etc.) affected?
Does the transfer behavior occur in combination with specific files (file extension, file size)?

[chrispink]

[chrispink]

[chrispink]

[chrispink]

I have two windows open, Cyberduck and FileZilla. I can transfer with Cyberduck and get a 0 B on the server, then transfer the same file with FileZilla and get the expected result (repeatedly and consistently).

So, if it is the server, I'd appreciate a clue as what the difference is that is making the server behave differently for the two FTP programmes.

I will say that I don't this is IP switching as I've monitored my IP during this test and it has remained constant.

[chrispink]

And, if it is the server, why does relaunching Cyberduck reset the issue (briefly)?