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
@@ -23,18 +23,19 @@ When a client can handle a Large Response, it must send a request with the HTTP
23
23
24
24
If the client provides the large response MIME type, the Lambda will not log an error using `Log.error`. Instead, it will rewrite the original response with a reference to the offloaded large payload. Furthermore, the rewritten response will include the HTTP header `Content-Type` with the value `application/large-response.vnd+json`.
25
25
26
-
If the client does not provide the large response MIME type, the Lambda will log an error with `Log.error`, and the response will fail due to an excessively large response body.
26
+
If the client does not provide the large response MIME type, the Lambda will log an error with `Log.error` and rewrite the original response with a custom message (can be configured) and HTTP status code 413 (Payload Too Large).
| sizeLimitInMB |`number`| Maximum allowed size limit in MB, e.g 6 |
37
+
| outputBucket |`string`| Identifier or name of the output S3 bucket |
38
+
| customErrorMessage |`string \| (event:APIGatewayProxyEventV2) => string `| Custom error message to be returned when the response is too large and the client does not support large responses (no accept header) |
38
39
| groupRequestsBy |`function - mapper`| Function to group requests, based on API Gateway event V2. Defaults to 'all' |
0 commit comments