{"version":"2.1.321","anchor":"fetch-style-call-forwards-compress-option-and-encodes-body","canonical_anchor":"fetch-style-call-forwards-compress-option-and-encodes-body","heading":"Some network requests can now pass a compression option and non-text bodies","tier":"internal","area":"Network","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/fetch-style-call-forwards-compress-option-and-encodes-body","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Some network requests can now pass a compression option and non-text bodies\n\nOne of Claude Code's request builders now forwards a compression option and no longer forces the request body into text\n\n**Unclear.** It is not clear which requests use this builder, so it is unknown what a user would notice.\n\n**What**\n\nOne part of Claude Code that prepares network requests has changed in two ways:\n\n- Compression option: it now passes a compression setting through when one is given.\n\n- Request body: it encodes the body with a helper and no longer converts the body to plain text.\n\n**Why**\n\nThis may let these requests carry content that is not text, such as binary files.\n\n- Area: Network\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}