Unsupported header x-amz-checksum-sha256 error for uploads

[jeffstreann]

This ticket system is to report bugs and feature requests. For support, visit the help page first.

• If you have trouble connecting to a server or your login credentials are not valid, try to resolve the issue with the assistance of your hosting service provider. Any such ticket will be closed with a resolution of thirdparty.

Describe the bug
On Cyberduck version 8.8.2 Not able to create folders, or upload files. When trying to create a folder or upload a file this message pop up

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
Should be able to create a folder, upload a file and a done.txt file to upload files to our platform.

Screenshots

Desktop (please complete the following information):

• OS: Windows 11 Home Single Language
• Version 22H2
• OS Build 22621.3447

Log Files
Please include the log file. You can reach the logging output in Preferences → Connection.

Additional context
Add any other context about the problem here.

[technotherion]

I hope that it is OK to piggyback off of this issue, this issue is the only other place I've seen this error.

My bookmark settings are as follows.

Object lock is NOT enabled on my buckets.

Experiencing the same issue on Windows 10 + Cyberduck 8.8.2.
Attempting to upload files to Backblaze B2 via Amazon S3.
I am able to delete files. I can not upload files or create new folders.

Creating a new folder causes this error:

Uploading a file causes this error:

Unfortunately, the program does not appear to allow me to copy and paste this error text.

I am also able to create new b2 buckets and do not experience any errors doing so. Said buckets show up correclty on the Backblaze website.

cyberduck.log

I am able to connect to the same buckets using S3 Browser and upload files correctly. is this maybe a AWS Signature v4 issue?

[dkocher]

This seems to be caused by the changes implemented for #15557. Please open a bug with Backblaze about this issue with their S3 implementation not being interoperable.

[dkocher]

@jeffstreann Do you also see this issue when uploading to B2 using S3?

[dkocher]

The incompatibility is documented ¹.

Requests that include the following checksum HTTP headers are rejected with a 400 Bad Requestresponse:
x-amz-checksum-crc32
x-amz-checksum-crc32c
x-amz-checksum-sha1
x-amz-checksum-sha256
x-amz-checksum-algorithm
x-amz-checksum-mode

Footnotes

1. https://www.backblaze.com/docs/cloud-storage-s3-compatible-api ↩

[jeffstreann]

@jeffstreann Do you also see this issue when uploading to B2 using S3?

correct. I am using version 8.7.3 (40979) temporarily, as any newer version gives me an error when trying to create folders or upload files.