413 Request Entity Too Large #8849
-
Version InformationServer Version: v2.0.7 What is the current behaviour?I have created a function that takes a JSON array of objects as input. While calling the function from the Hasura console getting the below error for the input of size 3.46MB `GraphQL Error (Code: 413): {"response":{"error":"\r\n<title>413 Request Entity Too Large</title>\r\n\r\n 413 Request Entity Too Large\r\nnginx\r\n\r\n\r\n","status":413,"headers":{}} Not able to find any details on where can I set the limit in the console against the input. Any suggestions??? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
|
Where is your Hasura hosted? The error seems to be coming from nginx... |
Beta Was this translation helpful? Give feedback.
-
|
Hasura is hosted on kubernetes. |
Beta Was this translation helpful? Give feedback.
-
|
@Ganesh1991 you will need to update the maximum size that nginx is allowed to handle. This unfortunately is not something Hasura controls. Also, 3mb is a really large JSON payload that might be worth reducing into more than one request. |
Beta Was this translation helpful? Give feedback.
@Ganesh1991 you will need to update the maximum size that nginx is allowed to handle. This unfortunately is not something Hasura controls. Also, 3mb is a really large JSON payload that might be worth reducing into more than one request.
https://medium.com/@svsh227/error-413-request-entity-too-large-in-nginx-with-client-max-body-size-changes-in-nginx-6aacd525fe11