This release adds a new --content-encodings flag which configures the server to handle response compression based on the Accept-Encoding header. This can fairly easily move compression to Envoy's efficient stack, and in simple testing, we see an app using Starlette's gzip middleware perform 2x better when using pyvoy's native support instead, with no change to the app (it stops receiving Accept-Encoding).
Note, this is a convenience via the CLI and programmatic interface rather than a new feature - content encoding could always be configured when using Envoy config directly without the CLI.
Full Changelog: v1.0.1...v1.1.0