We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
User has reported an issue deploying larger actions with error returned: 413 Request Entity Too Large.
413 Request Entity Too Large
I've started devtools using docker compose and can reproduce the issue using the following command.
mkfile -n 512k source.js; ls -lh source.js; wsk action create test --kind nodejs:6 source.js -v
This is the response body from the CLI command.
<html> <head><title>413 Request Entity Too Large</title></head> <body bgcolor="white"> <center><h1>413 Request Entity Too Large</h1></center> <hr><center>openresty/1.13.6.1</center> </body> </html>
Using a file with less than 512KB doesn't have this issue, e.g. mkfile -n 511k. Looks like the default body size configuration from nginx in the api gateway service could be set as 512k? https://nginx.org/en/docs/http/ngx_http_core_module.html#client_max_body_size
mkfile -n 511k
If this is correct, can we update it to be the same as the maximum file size (48MB) for actions?
The text was updated successfully, but these errors were encountered:
Any workaround for this? This issue prevents me from using openwhisk locally...
Sorry, something went wrong.
@matthewpflueger Have you tried setting that configuration value for NGINX to a higher default and seeing if that helps?
Is there an update on this issue? I am facing the same and can't resolve it...
No branches or pull requests
User has reported an issue deploying larger actions with error returned:
413 Request Entity Too Large
.I've started devtools using docker compose and can reproduce the issue using the following command.
This is the response body from the CLI command.
Using a file with less than 512KB doesn't have this issue, e.g.
mkfile -n 511k
. Looks like the default body size configuration from nginx in the api gateway service could be set as 512k?https://nginx.org/en/docs/http/ngx_http_core_module.html#client_max_body_size
If this is correct, can we update it to be the same as the maximum file size (48MB) for actions?
The text was updated successfully, but these errors were encountered: