fix: http trace interceptor not keeping original HttpBody properties and LogMode not behaving as expected #1035
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.
Issue #
fixes awslabs/aws-sdk-kotlin#1198
Description of changes
HttpBody
properties like content length from the originalHttpBody
when duplicating it. The issue in awslabs/aws-sdk-kotlin#1198 seems to have been caused by the fact that the original body was anAwsChunked
body with atransfer-encoding: chunked
header. When we replace the body during the trace call it was replaced with a non-equivalent in-memory byte array body which always has a content length.LogRequestWithBody
andLogResponseWithBody
should implyLogRequest
andLogResponse
respectively. I discovered this trying to debug this issue and seeing the incorrect behaviors for dumping the canonical request from S3By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.