I recently ran into a small friction point while using HttpLoggingInterceptor to inspect response bodies. Currently, the interceptor handles gzip seamlessly, allowing us to read the logged response body in plain text. However, it doesn't seem to support brotli decompression.
Given that brotli is now one of OkHttp's default accepted encodings (and widely used for better compression), it would be incredibly helpful if the logging interceptor could handle it with the same out-of-the-box support it gives to gzip.
I recently ran into a small friction point while using
HttpLoggingInterceptorto inspect response bodies. Currently, the interceptor handlesgzipseamlessly, allowing us to read the logged response body in plain text. However, it doesn't seem to supportbrotlidecompression.Given that
brotliis now one of OkHttp's default accepted encodings (and widely used for better compression), it would be incredibly helpful if the logging interceptor could handle it with the same out-of-the-box support it gives togzip.