Increase Body Parser Limit to Fix 413 Error on update-template Endpoint #12
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While invoking the update-template API, I encountered a
413Payload Too Large HTTP error code. Upon investigation, it appears that the size of the form-data in the request was exceeding server limits, despite being only approximately70kbin size.This issue is particularly relevant when using no-code email editors, as the emails generated can easily reach or exceed this threshold. Reviewing the
config/bodyParser.jsconfiguration file, I noticed that there was no explicit limit set for the body size, which led me to believe that the default limit imposed by the framework was too low for our use case.To address this problem, I have increased the body parser limit to
10mb. This change effectively resolves the issue and allows emails of larger sizes to be processed without encountering a413error.Please consider merging this adjustment to ensure smooth operation of the update-template endpoint for all users.