Response Compression

Most endpoints support HTTP response compression, which can speed up requests by decreasing the amount of data that needs to be transferred. In many cases, this is done automatically, but if you need to confirm whether it is working, the details are as follows:

1. The request must provide an Accept-Encoding header with the compression formats your HTTP client supports. For example, Accept-Encoding: gzip, deflate, br, zstd
   1. Many HTTP clients, including browsers like Google Chrome, set this header automatically.
   2. gzip is the only encoding Arcadia supports currently.
2. If the header includes a compression format that Arcadia supports (gzip), the response will be compressed with that encoding and will include the header Content-Encoding: gzip
   1. Many HTTP clients decompress the response automatically based on the Content-Encoding header.
   2. If the response did not include the Content-Encoding header, then it was not compressed.