Large files cause "body size too long" error
See original GitHub issueTransforming a large (9.8MB) gif causes a body size too long
error. This seems related to the 6MB body payload size, as described in the Lambda Limits page. I think this issue will face image formats other than .gif, that’s just what I’ve seen it pop up on. Log screenshot below.
Any advice for how to work around this?
At the moment, I have an onError
function on my <img />
tags that replaces the src with the original non-resized URL. But - this occurs in the worst case scenario, where we have huge files - so it’s really not desirable.
Issue Analytics
- State:
- Created 5 years ago
- Comments:13 (4 by maintainers)
Top Results From Across the Web
Large files cause "body size too long" error · Issue #35 - GitHub
Transforming a large (9.8MB) gif causes a body size too long error. This seems related to the 6MB body payload size, as described...
Read more >What Is a 413 Request Entity Too Large Error & How to Fix It
A 413 HTTP error code occurs when the size of a client's request exceeds the server's file size limit. This typically happens when...
Read more >Attachment size exceeds the allowable limit error - Outlook
Attachment size exceeds the allowable limit error when you add a large attachment to an email message in Outlook.
Read more >AWS Lambda - Body Size is Too Large Error ... - Stack Overflow
In one endpoint I am getting "body size is too long" printed to the cloudwatch log. The response I get from the function...
Read more >Fixing 413 Request Entity Too Large Errors - KeyCDN Support
A 413 Request Entity Too Large error occurs when a request made from a client is too large to be processed by the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
My json data response is 750kb (<<5MB). Why am I also getting this error? @stewwan if your file is 300kb why do you get the error too?
We have added this as a feature request to our backlog for an upcoming release, but don’t have an ETA for when it will be ready. Marking the ticket for closure in the meantime.