During use of NGINX, if the request message is too large in the front-end POST request, it is usually necessary to increase the value of the client_max_body_size property, which defaults to 1M. Avoid 413 Request Entity Too Large.
You can optionally set it in HTTP {} : client_max_body_size 20m; Controls all requests received by NGINX
You can also optionally set it in Server {} : client_max_body_size 20m; Controls the requests received within the server
You can also optionally set client_max_body_size 20m in Location {}; Controls the request that matches the routing rules of Location
You can optionally set it in HTTP {} : client_max_body_size 20m; Controls all requests received by NGINX
You can also optionally set it in Server {} : client_max_body_size 20m; Controls the requests received within the server
You can also optionally set client_max_body_size 20m in Location {}; Controls the request that matches the routing rules of Location
Read More:
- Nginx upload error 413 request entity too large
- IIS “Bad Request – Request Too Long. HTTP Error 400. The size of the request headers is too long.”
- The file server reports an error of 413, and the file uploaded by nginx reports an error of 413 request entity too large
- Bad Request – Request Too Long. HTTP Error 400. The size of the request headers is too long
- Nginx front end and back end separation + service cluster reverse proxy
- mysql5.7.26：[ERR] 1118 – Row size too large (＞ 8126)
- The back end cannot receive the parameters passed by the front end
- Flask Request an extension before_request after_request errorhandler
- [nodejs] error request aborted after request routing in post mode
- Error domain = nsurlerrordomain code = – 1001 “request timeout occurred in swift alamofire get request. ” UserInfo={NSUnderlyingErro
- request:fail url not in domain list or Cannot send network request to localhost
- Springboot project: error parsing HTTP request header note: further occurrences of HTTP request parsing
- Record a front end error net:: err_ HTTP2_ PROTOCOL_ ERROR 200
- WebView loadrequest request request error “nsurlconnection finished with error – Code – 1022”
- When configuring the proxy with Vue, the front-end requests the server-side error 504; the Vue console reports the error occurred while trying to proxy request
- In the HTML page request Ajax times 400 error, solve Yii submit post form 400 error, and Ajax post request 400 problem (example code)
- Error: The size of the connection buffer (131072) was not large enough
- Flume receives an error when a single message is too large
- Tdengine failed to start, start request repeated too quickly for taosd.service
- What are the web front end technologies? What are the differences between cookie and session