Closed eveningcafe closed 1 year ago
Okay, I figured it out. The Warp client uses path-style requests, while the server uses domain-style requests. https://github.com/minio/minio/tree/master/docs/config#domain
Can we support for domain-style requests (as an --option ) in Warp? This would be useful for people who want to use Warp to benchmark AWS S3 buckets (or another s3 compatitive system), as AWS plans to deprecate path-style requests in the future (https://aws.amazon.com/blogs/aws/amazon-s3-path-deprecation-plan-the-rest-of-the-story/).
Date: Mon, 26 Jun 2023 02:30:50 GMT X-Amz-Id-2: txb249f3012ca94666939f4-006498f85a X-Amz-Request-Id: txb249f3012ca94666939f4-006498f85a X-Openstack-Request-Id: txb249f3012ca94666939f4-006498f85a X-Trans-Id: txb249f3012ca94666939f4-006498f85a
Your server does not implement GetObject with partNumber https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObject.html#API_GetObject_RequestSyntax
Please fix your server this has nothing to do with pathStyle v/s DNS bucket style.
Warp version latest. When I test the multipart upload functionality, I encounter a bug. I'm unsure whether it is a bug on the server or the client side. Has anyone else experienced the same issue?
Result