{"version":"2.1.246","anchor":"request-bodies-can-be-gzipped-with-random-padding-to-hide-th","canonical_anchor":"request-bodies-can-be-gzipped-with-random-padding-to-hide-th","heading":"Request bodies can be gzipped with random padding to hide their length","tier":"internal","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/request-bodies-can-be-gzipped-with-random-padding-to-hide-th","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Request bodies can be gzipped with random padding to hide their length\n\nRequest bodies can be gzipped with random padding so their compressed size hides the real length.\n\n**What**\n\nA new helper can compress an outbound request body, first appending a newline and between 0 and 256 random spaces or tabs so the compressed size does not reveal the exact payload length, and setting `Content-Encoding: gzip`. It does nothing unless a compression-decision function is supplied at the call site and picks gzip for that URL; otherwise the request is sent as before.\n\n**Details**\n\n- The padding is added before compression, so it affects the transmitted size rather than the content the server parses.\n\n**Evidence**\n\n`{ body: EP(i), headers: { \"Content-Encoding\": \"gzip\" } }`\n\n- Area: Internals\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 4\/5"}