I'm having trouble with 500 errors that I'm pretty sure are coming from the Jetty container.
My internal logging is showing that I am responding with a status 200 and a valid response.
Smaller responses work fine but larger responses are failing with a 500 at the client and I can see that 500 in the API Gateway logs.
We are using HTTP direct in this case so it's an HTTP API gateway.
Given that it's size-related, I suspect that GZIP compression is the issue. specifically chunked responses or maybe incorrect content lengths.
I've implemented GZIP inside my handler in an attempt to stop jetty from implementing compression.
All these attempts have failed and don't have any telemetry or logs indicating the true source of the failure.
To learn more I suspect we need to enable jetty logs to stop being swallowed and start appearing in the CloudWatch logs but I haven't have any luck in finding how to do this.
Are there instructions somewhere on how to enable or increase the level of logging from the Jetty container?
I suspect this might be setting a system property via the override options in the cloud formation template but I wanted to ask here first.
