Handling Anonymous, chunking decisions, and existing checksums

[haydenbaker]

Motivation and Context

• If a request has an anonymous identity, we should not sign it, but we should still optionally encode it and add flexible checksum information to it
• If a request is chunk-encoding enabled, we still must do some checks before we decide to chunk-encode the payload (i.e. if checksum is in headers and it's unsigned, we should NOT chunk-encode)
• If a checksum is already provided in the request headers, we should not re-compute it or override it

Testing

• Run s3 integration tests
• Run unit tests

Screenshots (if appropriate)

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)

Checklist

• I have read the CONTRIBUTING document
• Local run of mvn install succeeds
• My code follows the code style of this project
• My change requires a change to the Javadoc documentation
• I have updated the Javadoc documentation accordingly
• I have added tests to cover my changes
• All new and existing tests passed
• I have added a changelog entry. Adding a new entry must be accomplished by running the scripts/new-change script and following the instructions. Commit the new file created by the script in .changes/next-release with your changes.
• My change is to implement 1.11 parity feature and I have updated LaunchChangelog

License

• I confirm that this pull request can be released under the Apache 2 license

[zoewangg]

Suggesting extracting it to a separate method and add javadoc to make it more clear

private boolean useChunkedEncoding(BaseSignRequest<?, ? extends AwsCredentialsIdentity> request) 

[sonarcloud]

SonarCloud Quality Gate failed.   

9 Bugs
0 Vulnerabilities
2 Security Hotspots
500 Code Smells

85.1% Coverage
4.4% Duplication

Catch issues before they fail your Quality Gate with our IDE extension SonarLint