You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I believe this is responsible for an object metadata request failing when trying to copy objects using the AWS Java SDK v2 Transfer Manager API (and presumably for other clients using this library). I raised aws/aws-sdk-java-v2#3370 initially, then tracked the problem to the changes introduced in #166 .
The object metadata request will fail if talking to a local Minio server, e.g. the endpoint specified is localhost:9100, in theory the Host header value should be my-bucket.localhost:9100 (as it is for other SDK client requests), but is actually my-bucket.s3.us-west-2.amazonaws.com, to which Minio will understandably respond with a 404. I don't know if this also fails when talking to Amazon S3 for regions other than us-west-2.
I'm not familiar enough with this code (and haven't touched C in too long) to offer a solution, but perhaps @cmello or someone else could take a look. No doubt the actual request endpoint is readily available somewhere and can be used to construct the Host header value.
The text was updated successfully, but these errors were encountered:
I believe this is responsible for an object metadata request failing when trying to copy objects using the AWS Java SDK v2 Transfer Manager API (and presumably for other clients using this library). I raised aws/aws-sdk-java-v2#3370 initially, then tracked the problem to the changes introduced in #166 .
The object metadata request will fail if talking to a local Minio server, e.g. the endpoint specified is
localhost:9100
, in theory the Host header value should bemy-bucket.localhost:9100
(as it is for other SDK client requests), but is actuallymy-bucket.s3.us-west-2.amazonaws.com
, to which Minio will understandably respond with a 404. I don't know if this also fails when talking to Amazon S3 for regions other than us-west-2.I'm not familiar enough with this code (and haven't touched C in too long) to offer a solution, but perhaps @cmello or someone else could take a look. No doubt the actual request endpoint is readily available somewhere and can be used to construct the Host header value.
The text was updated successfully, but these errors were encountered: