Exceeded maximum allowed payload size #1815
Labels
bug
This issue is a bug.
module/lambda-client-lib
needs-reproduction
This issue needs reproduction.
p2
This is a standard priority issue
Describe the bug
Hi,
We have an ASP.NET Core Web API running, hosted in a Lambda function. The API uses Top Level Statements and the package Amazon.Lambda.AspNetCoreServer.Hosting.
The function acts as a Proxy Server which enables our API clients to access a lot of legacy SOAP services. In front of the Lambda function there is an API Gateway.
Some of the responses from the SOAP Services exceeds the Lambda response limit of 6MB. When this occurs the underliying Lambda runtime client receives an HTTP 413 error and throws an exception which crashes the whole application, because this happens during startup of the .net application.
I'm not sure if it is a bug or not. How can we handle those errors. In such cases the calling client application should also receive HPP 413 and not 500.
Regression Issue
Expected Behavior
Application doesn't crash, exception can be handled and send back to the client.
Current Behavior
When response size is greater than 6 MB, Lambda function receives an HTTP 413 error and crashes. The calling client receives a HTTP 500 error, probably because of the crashed application. The exception occurs during startup of the application:
{"errorMessage":"Exceeded maximum allowed payload size (6291556 bytes).","errorType":"RequestEntityTooLarge"}
Reproduction Steps
n/a
Possible Solution
No response
Additional Information/Context
No response
AWS .NET SDK and/or Package version used
Amazon.Lambda.AspNetCoreServer.Hosting 1.7.0
Targeted .NET Platform
.NET Core 8.0
Operating System and version
Docker container
The text was updated successfully, but these errors were encountered: