Fixed the issue where S3 multipart client failed to download zero-byt…

[zoewangg]

…e file

Motivation and Context

Fixed the issue where S3 multipart client failed to download zero-bye file, causing Content range header is missing to throw.

The root cause is that the SDK assumed content-range header is always returned, but that's not the case; S3 doesn't return a content-range header for 0 byte objects. The fix is to use content length instead. It will throw exception if this is not the first part, which is an error case.

Testing

Added unit tests and integ 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

[sonarqubecloud]

Quality Gate passed

Issues
5 New issues
1 Accepted issue

Measures
0 Security Hotspots
86.1% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud