Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hard-coded Host header domain in aws_s3_get_object_size_message_new #206

Closed
bpiper opened this issue Aug 23, 2022 · 1 comment
Closed

Hard-coded Host header domain in aws_s3_get_object_size_message_new #206

bpiper opened this issue Aug 23, 2022 · 1 comment
Assignees

Comments

@bpiper
Copy link

bpiper commented Aug 23, 2022

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.

@yasminetalby yasminetalby added the needs-triage This issue or PR still needs to be triaged. label Sep 20, 2023
@yasminetalby yasminetalby self-assigned this Sep 20, 2023
@yasminetalby yasminetalby removed the needs-triage This issue or PR still needs to be triaged. label Sep 20, 2023
@yasminetalby
Copy link
Contributor

Hello @bpiper ,

I will be closing this issue as the original issue has been resolved. If you have any further inquiries or question please let me know!

Best regards,

Yasmine

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants