{"version":"2.1.247","anchor":"telemetry-bodies-padded-with-random-whitespace-before-compre","canonical_anchor":"telemetry-bodies-padded-with-random-whitespace-before-compre","heading":"Telemetry bodies padded with random whitespace before compression","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/telemetry-bodies-padded-with-random-whitespace-before-compre","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Telemetry bodies padded with random whitespace before compression\n\nTelemetry requests get random padding so their compressed size hides the real payload length.\n\n**What**\n\nCompressed telemetry requests now get a newline and a random run of 0 to 256 spaces or tabs appended first, so the compressed size no longer reveals the exact payload length. Only on the gzip path.\n\n**Evidence**\n\n`Math.random() < 0.5 ? \" \" : \"\\t\"`\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}