Preserve content-length when calling mark in SdkLengthAwareInputStream

[alextwoods]

Preserve content-length when calling mark in SdkLengthAwareInputStream

Motivation and Context

This does not change when exceptions are raised - it only changes the text in the exception.

Prior to this change, when mark was called on a SdkLengthAwareInputStream, it would reset the expected length to be the remaining bytes. If all of the bytes were not read from the stream the exception would have the message: The request content has fewer bytes than the specified content-length: <length based on remaining bytes when mark was called>. With this change, the specified content-length in the exception will be the originally provided length.

Modifications

• Makes length final on construction and adds a new markedRemaining to store the number of remaining bytes.

Testing

New and existing 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
2 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud

[github-actions]

This pull request has been closed and the conversation has been locked. Comments on closed PRs are hard for our team to see. If you need more assistance, please open a new issue that references this one.