datomic

steveb8n 2025-05-05T23:25:18.249049Z

Q: We are using HTTP Direct with IONs in cloud and having trouble with larger responses throwing 500s. Conversation with AI suggests that this could be jetty g-zipping the response and the API gateway not being able to handle the chunked, g-zipped response. We haven’t figured out how to enable logs to see the true problem source. Does anyone have any experience with behavior like this?

danieroux 2025-05-06T18:03:55.336449Z

Are you running into the 30s API Gateway limitation? https://stackoverflow.com/questions/54299958/how-can-i-set-the-aws-api-gateway-timeout-higher-than-30-seconds/54300708#54300708

danieroux 2025-05-06T18:06:48.526789Z

This Cloudwatch metric should tell you:

steveb8n 2025-05-06T21:29:46.583689Z

No, the handler returns in 2 secs in the logs so it's size, not time which is triggering the problem. I'm gonna try to enable jetty logging to see if that exposes the truth

steveb8n 2025-05-05T23:25:50.763159Z

We saw similar behaviour when not using HTTP Direct but the size threshold was larger.

steveb8n 2025-05-05T23:26:21.677559Z

I’ve been trying to figure out how to disable GZIP in the Jetty container run in the cloud, but I’m failing hard on that challenge.