Compression

Request compression and transfer encoding for Sentry envelope submissions.

SDKs are heavily encouraged to compress the request body before sending it to the server to keep the data small. The preferred method for this is to send a content-encoding header. The following content encodings are accepted by Relay and Sentry:

  • gzip: Using the LZ77 compression algorithm.
  • deflate: Using zlib structure with the deflate compression algorithm.
  • br: Using the Brotli algorithm.
  • zstd: Using the zstd algorithm.

Transfer encoding is recommended for only very large requests. Set the header to transfer-encoding: chunked, which allows omission of the content-length header and requires the request body to be wrapped into chunk headers.

See MDN for more details.

Previous
Authentication
Next
Offline Caching
Was this helpful?
Help improve this content
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").