Skip to content

Handle S3 API failures that return 200 OK #783

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

Closed
wants to merge 2 commits into from
Closed

Handle S3 API failures that return 200 OK #783

wants to merge 2 commits into from

Conversation

amsa
Copy link

@amsa amsa commented Jan 22, 2018

The SDK relies on HTTP status codes to determine whether or not the operation succeeded. However, in certain APIs such as CompleteMultipartUpload, the API may return 200 OK with an error in the response body. In those cases, the response body needs to be inspected for errors. This fix only checks response bodies of non-GET requests that return XML as the response type. #658 #781

The SDK relies on HTTP status codes to determine whether or not the
operation succeeded. However, in certain APIs such as
CompleteMultipartUpload, the API may return 200 OK with an error in the
response body. In those cases, the response body needs to be inspected
for errors. This fix only checks response bodies of non-GET requests
that return XML as the response type.
@amsa amsa changed the title Handle S3 API failures that returns 200 OK Handle S3 API failures that return 200 OK Jan 25, 2018
@marcomagdy
Copy link
Contributor

I don't have a better solution.
@singku and @wps132230 please chime in if you have any.
@amsa can you rebase this PR on master please?

@github-actions
Copy link

github-actions bot commented Aug 8, 2020

Greetings! Sorry to say but this is a very old issue that is probably not getting as much attention as it deservers. We encourage you to check if this is still an issue in the latest release and if you find that this is still a problem, please feel free to open a new one.

@github-actions github-actions bot added closing-soon This issue will automatically close in 4 days unless further comments are made. closed-for-staleness and removed closing-soon This issue will automatically close in 4 days unless further comments are made. labels Aug 8, 2020
@github-actions github-actions bot closed this Aug 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants