Content-Encoding being disregarded when outputing API Gateway HTTP V2 Response

[driverpt]

Expected Behavior

If Content-Encoding is gzip or brotli, the output is supposed to be Binary + Base64, not based on Binary Mime Types

Actual Behaviour

Content-Encoding is disregarded and Response easily exceeds the 20 MB Limit on AWS Lambda

Steps To Reproduce

No response

Environment Information

No response

Example Application

https://github.com/driverpt/micronaut-aws-lambda-20mb-limit

Version

4.9.4

[sdelamo]

how to reproduce this in Lambda?

[driverpt]

Hello,

Updated the Example application url: https://github.com/driverpt/micronaut-aws-lambda-20mb-limit

For some context: We have a Downstream Service that returns more than 20MB of JSON Payload which we need to proxy to the Web Frontend. This issue does not happen if we attach the Downstream Service directly because it automatically encodes as gzip, when Micronaut returns this JSON in Lambda Service, it's never compressed using gzip, it just serializes as regular JSON. As a workaround we created a pure Java Lambda that compresses as gzip if Accept-Encoding: gzip is there