Requests that are adjusted for (web client) emulation purposes might add request headers that impact the response. An example of this is the Accept-Encoding request header. It might be very well that a web client by default adds that header, but that adding it will cause also the response to change, as the server will now assume it can be compressed (in case the value is non-null and non-identity.

While most clients can probably handle this, it is better if we respect such preferences and decompress for the user in case they did not request to compress to begin with.