error 413 request entity large chrome

Overview Today encountered a problem, in the PHP program upload picture has the following error: http:413 Request Entity Too Large. Development environment: CentOS + Nginx + PHP + MySql Solution To solve this problem, depending on the size of the uploaded data file, you

Returned by the WCF server: (413) Request Entity Too Large, wcfentity We can all guess that the file is too large to pass out of the default WCF range, so we need to modify the file. Both the server and client must be modified. First, the client: 　　 The above is generated b

), this avoid lots of type judging. But text body would always return string type. Detectjson: Custom JSON request detect function. Default is null .app.use (bodyparser{function (CTX) { return /\.json$/i.test ( (Ctx.path); } )); Extendtypes: Support Extend types:App.use (Bodyparser ({ extendtypes: { json: [//}}) ]; onerror: Support custom error handle, if koa-bodyparser throw a

If the client certificate is enabled on a single directory or file of the web server, website, or site, the client may see an HTTP 413 error when uploading a large file. If a client sends a long HTTP request (such as a POST request) to a Web server running IIS 6.0, the IIS

official server is not available.Then you see a hint error with a 443 port.It dawned on me, is it the reason of https?Change the keyword to search the data again.Finally, I found this solution.Http://stackoverflow.com/questions/18279007/413-request-entity-too-large-on-https

Today, upgrade a server to the latest IIS8.5, and then deploy the Web site, there is a relatively old ASP site found the problem, upload a slightly larger file error, pass a dozens of k file to no problem, we all know that IIS default upload file size is 30M, and now upload 1M have problems, the following gives a solution. Upload error message is: Request object

WebService processes large data volumes The following error occurs when processing large data volumes through WebService: Soap fault: An exception occurs when running the specified extension in the configuration file. ---> Exceeds the maximum request length.Solution: Because the uploaded file is greater than the defaul

Error logging in the server is similar to this: 124.65.133.242––[27/oct/2014:14:30:51 +0800] "-" 400 0 "-" "-"124.65.133.242––[27/oct/2014:14:31:45 +0800] "-" 400 0 "-" "-"124.65.133.242––[27/oct/2014:14:31:45 +0800] "-" 400 0 "-" "-"124.65.133.242––[27/oct/2014:14:31:45 +0800] "-" 400 0 "-" "-" Casing After analyzing the log files of Nginx, it is found that a number of 400 errors are generated after a normal visit, each of which is about 1-6 conse

Elk Architecture: Elasticsearch+kibana+filebeatVersion information:Elasticsearch 5.2.1Kibana 5.2.1Filebeat 6.0.0 (preview)Today in the Elk Test, the Kibana above the discover regardless of the index, found that will be error:[Request] Data too large, data for [And in the Elasticsearch log you can see:Org.elasticsearch.common.breaker.CircuitBreakingException: [

Copy Code code as follows: Request-uri Too Large The requested URL ' s length exceeds the capacity limit for this server. The reason for this request-uri Too Large problem mentioned above is as follows: The Apache error is that the length of the URL exceeds the