![]() ![]() ![]() So, again, we're stuck using Minio as 'middle-ware' and end up facing the eTag issue. The last response I found from Seafile was that they support S3 and it's up to any other providers to properly implement S3 compatibility - not a great response but actually pretty reasonable. Backblaze really needs to step-up and fix this issue or provide a viable workaround since it is not a trivial issue and that December 2020 is getting really old.Īs far as I've heard, Seafile is not prioritizing any form of compatibility with B2 (Backblaze) which is really unfortunate. Apparently others have asked also and they haven't heard back in an even longer period of time.įor now, the best option is to use Minio release RELEASE.T05-05-17Z since it does not have the problematic eTag handling. ![]() I tried asking Backblaze about this but haven't heard anything back after like 4 months. Seems that B2 does not handle eTags properly (more accurately: not the same as S3). It seems I'm not the only one with the same problem: I'm not an expert but, from my understanding, this is not limited to Seafile. My credentials are ok, as tested with another tools. Response:Įrror reading uploaded data: StreamCorruptedException(null) ![]() common/s3-client.c(621): Authorization: AWS4-HMAC-SHA256 Credential=KEY/20200715/us-west-001/s3/aws4_request,SignedHeaders=host x-amz-content-sha256,Signature=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX common/s3-client.c(722): Request headers: common/s3-client.c(720): S3 error status for PUT: 400. common/s3-client.c(940): S3 error status for HEAD: 403. ![]()
0 Comments
Leave a Reply. |