Adds gzip handler to JDK http client based on header #35225
+134
−4
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.
Title
Implement custom BodyHandler for GZIP decompression in JdkClientHttpRequest
Description
Problem: JDK HTTP Client doesn't automatically decompress responses.
Solution: creating a custom BodyHandler that checks Content-Encoding and applies GZIPInputStream when necessary.
Key Changes:
compressionEnabled
toJdkClientHttpRequestFactory
andJdkClientHttpRequest
.buildRequest()
method to addAccept-Encoding
header withgzip
value when compression is enabled.DecompressingBodyHandler
that implementsBodyHandler<InputStream>
. The apply() method in the custom handler checks theContent-Encoding
header.gzip
, it uses BodySubscribers.mapping to wrap the InputStream with GZIPInputStream.Otherwise, it uses the default BodySubscribers.ofInputStream().
Testing Steps: