fix(backend): raise /graphql body limit to 1mb (ARG-449)#2343
Merged
Conversation
`express.json()` used the default 100kb limit on the /graphql route, causing legitimate large requests to be rejected with 413 "Payload Too Large". Bump the limit to 1mb. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Argos notifications ↗︎
|
This file contains hidden or 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
1 participant
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.
Problem
The
/graphqlroute parsed request bodies withexpress.json()using the default 100 kB limit. Legitimate large requests (big mutations / largevariablespayloads) were rejected with a 413 "Payload Too Large" error thrown byexpress.json()before the request even reached Apollo.Fix
Raise the limit to
1mb:Related: #2342 ensures any remaining 413s are reported to Sentry at
errorlevel.🤖 Generated with Claude Code