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

HDDS-4022. Ozone s3 API return 400 Bad Request for head-bucket for non existing bucket. #1251

Merged
merged 3 commits into from
Jul 27, 2020

Conversation

bharatviswa504
Copy link
Contributor

What changes were proposed in this pull request?

Ozone s3 API returns 400 Bad Request for head-bucket for non-existing bucket.

**hrt_qa$ aws s3api --ca-bundle=/usr/local/share/ca-certificates/ca.crt --endpoint https://s3g:9879/ head-bucket --bucket fsdghj

An error occurred (400) when calling the HeadBucket operation: Bad Request**

It should return 404 as per AWS documentation:
https://docs.aws.amazon.com/cli/latest/reference/s3api/head-bucket.html

A client error (404) occurred when calling the HeadBucket operation: Not Found

What is the link to the Apache JIRA

https://issues.apache.org/jira/browse/HDDS-4022

How was this patch tested?

Added test.

Copy link
Member

@elek elek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 thanks the fix @bharatviswa504

Checked real AWS endpoint, just to be sure if this code is added for compatibility, but 404 seems to be the right answer.

@elek elek merged commit a123b4e into apache:master Jul 27, 2020
elek pushed a commit that referenced this pull request Jul 27, 2020
timmylicheng pushed a commit that referenced this pull request Aug 6, 2020
ChenSammi pushed a commit that referenced this pull request Aug 12, 2020
rakeshadr pushed a commit to rakeshadr/hadoop-ozone that referenced this pull request Sep 3, 2020
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

Successfully merging this pull request may close these issues.

3 participants