accessing MinIO S3 server and get "A header you provided implies functionality that is not implemen
I am using MinIO for S3 service. everything works perfectly except for file edits. When I quit the program and it goes to save the file back on the server, I always get an error message (even though it works).
Doesn't happen with Backblaze, wasabi backends, just my MinIO server. Is this a problem with my MinIO server or a bug in Cloudberry?
this appears to be a bug in the MinIO server since it works on all other sites.
I filed a bug:
Basically, Cloudberry calls both PutObjectACL and HeadObject and MinIO doesn't implement either of them.
MinIO won't fix either.
Cloudberry shouldn't be making the HEAD call on upload.
Cloudberry should ignore the PutObjectACL error. Perhaps an option to do that? Or simply not make that call.
Sign in or register to add a comment.
Add a Comment
Welcome to MSP360 Forum!
MSP360 Managed Products
Managed Backup - General
Managed Backup Windows
Managed Backup Mac
Managed Backup Linux
Managed Backup SQL Server
Managed Backup Exchange
Managed Backup Microsoft 365
Managed Backup G Workspace
Backup for Linux
Backup SQL Server
Connect Free/Pro (Remote Desktop)
Backup to Minio (Choosing Minio vs S3 Compatitble?)
Backup to Local MinIO Server (error: "The authorization header is malformed")
If we use AWS-CLI to copy files to the S3 bucket, can ClouldBerry Drive work with them properly ?
Backup fails with "S3 Transfer Acceleration is not configured on this bucket" error
Terms of Service
Useful Hints and Tips
Created with PlushForums
© 2024 MSP360 Forum