[keelerm84]

The compress_events option now defaults to true. The SDK gzip-compresses
analytics and diagnostic event payloads and sends them with a
Content-Encoding: gzip header. This reduces egress bandwidth for
customers who send events directly to LaunchDarkly.

Relay Proxy versions before 8.9 cannot accept compressed events.
Customers who send events through the Relay Proxy should set
compress_events: false. Older Relay Proxy versions cannot decode the
payloads, and newer versions decode and re-encode them, which adds
overhead.

The stub HTTP server in the specs now decodes a request body based on
its Content-Encoding header instead of a constructor flag.

---

Note

Overview
Breaking change: compress_events now defaults to true, so analytics event POSTs are gzip-compressed with Content-Encoding: gzip unless callers set compress_events: false.

Docs now call out that Relay Proxy versions before 8.9 cannot accept compressed payloads and should disable compression; newer proxies decode and re-compress, which adds CPU cost.

Specs were updated to assert the new default, document the opt-out on Config, and make the stub HTTP server decode bodies from the request’s Content-Encoding header instead of a test-only enable_compression flag.

^{Reviewed by Cursor Bugbot for commit 0ddd5e6. Bugbot is set up for automated code reviews on this repo. Configure here.}