Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Payload Too Large #288

Closed
manuelfink opened this issue Jan 29, 2017 · 6 comments
Closed

Payload Too Large #288

manuelfink opened this issue Jan 29, 2017 · 6 comments

Comments

@manuelfink
Copy link

I just tried to fire a bunch of mutations against the graphql-server. This now throws an error 413 Payload Too Large. How can I increase the payload?

@manuelfink
Copy link
Author

thought this is a problem of graphql-server however it is caused by bodyParser and resolved through bodyParser.json({limit: '50mb'})

@christianTrepp
Copy link

Thanks for the info! Had same problem.

@gburchfield
Copy link

Wow, I originally thought my 413 Payload Too Large response had a root cause from my nginx proxy server especially since the documentation said it's 413 codes may be displayed differently in the browser. Long story short after a ton of debugging I fell onto this feed and found the root cause was the default bodyParser.json() limit of 100kb. I set that just like @manuelfink and it fixed my problem!

@rmacuna
Copy link

rmacuna commented Jun 5, 2021

Hello I'm having the same issue but I have no luck with my code:

app.use(express.json({ limit: '50mb' }))

@harbolaez
Copy link

trying above and no luck, any idea?

@jekabs-karklins
Copy link

app.use(express.json({ limit: '50mb' }));
worked for me

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 20, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants