Download from local S3 Bucket is not working in the latest version

[Bjoerntr]

we have a local s3 bucket and with the latest version i cannot dowload files anymore.

with version the transfer is incomplete.

reverting to version

i can download

checked also version 8.4.0 Download incomplete

[Bjoerntr]

if I open the pdf directly in Cyberduck, the file can be retrieved

[kirilyer]

I'm also experiencing a similar problem with S3.

Here, I have a suspicion that it is related to how S3 treats compressed files, in my case they were written using AWS Firehose.

I managed to reproduce the problem with simple AWS CLI commands: I created a text file with random strings and created a copy of it which I compressed, then I uploaded it to S3 using the following commands:

# uploading the regular text file
aws s3 cp test.txt s3://some-bucket/path/

# uploading the compressed file without special flags
aws s3 cp test_compressed.txt.gz s3://some-bucket/path/

# uploading the compressed file and telling S3 it is a compressed file
aws s3 cp --content-type text/plain --content-encoding gzip test_compressed_with_content_encoding_gzip.txt.gz s3://some-bucket/path/

This is the transfers window from Cyberduck:

First two files downloaded without problems. The third says it's failed although the file is downloaded and is complete and opens without problems.

Note the transfer size of the third file - it seems that either Cyberduck or, more probable, S3 itself uncompresses the file on retrieval and thus the downloaded size is bigger than the size that S3 initially reports for the compressed file which makes Cyberduck think that the download is incomplete.

I know that S3 behaves like that when downloading compressed files from the web console but it didn't seem to be an issue until the latest versions of Cyberduck.

Edit: I'm using Cyberduck v8.4.2 on MacOS Monterey 12.3.1.

[dkocher]

@kirilyer Your issue relates to #12767. Can you confirm the downloaded file will be the original uncompressed file.

[dkocher]

@Bjoerntr Please include the log file and reopen the issue. You can reach the logging output in Preferences → Connection.