Repository navigation
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
CLA
Description of the pull request
The default
HttpClientnever setsAutomaticDecompression, so it sends noAccept-Encodingand the API returns every response uncompressed. This turns on gzip for both default handlers (HttpClientHandlerandSocketsHttpHandler). A caller-suppliedClientOptions.HttpClientis untouched.The API already serves gzip, brotli and zstd to every client that asks; only this SDK's default client doesn't ask. One server-side app using 2.1.1 pulls ~232 GB/day of QueryChannels responses (avg 334 KB) uncompressed. A live QueryChannels response measured 240 KB plain vs 17 KB gzipped.
Testing (no
dotnettest changes; the existing suite needs live credentials):Accept-Encoding(14.5 KB on the wire); this branch sendsgzip(388 B), decodes the body and still reads the rate-limit headers, for both thenet6.0(SocketsHttpHandler) andnetstandard2.0(HttpClientHandler) builds.HttpClientdeserialize to identical objects, rate limits included, on both builds.🤖 Generated with Claude Code