Remove the output checksum validation skip warning if object is not fetched from S3 #3034
+10
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some users complains (e.g. #3024) the response checksum validation skip warning would be printed out when the object is not actually fetched from S3. Both Go SDK checksum middleware and S3 work correctly. This PR just turns off the validation skip warning to not scare users who update their SDK to latest version.
By submitting this PR, it is guaranteed that flex checksum unit and integration tests passed. Manual test using following code confirms the warning log no longer shows when no object is returned from S3, which should resolve #3024 :