You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 8, 2021. It is now read-only.
We have logic in our code that will write the response to S3 and redirect the client to the S3 URL if the content length is > 900,000. We have requests that are failing but yet that do not exceed the 900,000. I have added debug logs in the boostrap code as follows:
For the request in question, the output was
Total response length: 892878
which clearly is under 900,000 but yet when the lambda execution finishes, some 100K+ is added to the response length which fails the request with LambdaResponseTooLarge.
So my question is where is the 100K+ of addition bytes coming from
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We have logic in our code that will write the response to S3 and redirect the client to the S3 URL if the content length is > 900,000. We have requests that are failing but yet that do not exceed the 900,000. I have added debug logs in the boostrap code as follows:
$totalResponseLength = strlen(print_r($response, true));
printf("Total response length: %d\n", $totalResponseLength);
For the request in question, the output was
Total response length: 892878
which clearly is under 900,000 but yet when the lambda execution finishes, some 100K+ is added to the response length which fails the request with LambdaResponseTooLarge.
So my question is where is the 100K+ of addition bytes coming from
The text was updated successfully, but these errors were encountered: