解决nginx报错信息 client intended to send too large body: 1331696 bytes
2017-02-04 17:16
666 查看
解决nginx报错信息 client intended to send too large body: 1331696 bytes
1,nginx后台error日志报错
2016/02/05 16:23:56 [error] 12024#0: *441106971 connect() failed (111: Connection refused) while connecting to upstream, client: 113.214.1.10, server: localhost, request: "GET /h5teb/ugcH5/index.htm?source=android&mall=8&TGC=911FDD2F99B84D528F0A7EE71780A943 HTTP/1.1", upstream: "http://113.214.1.23:8000/h5teb /ugcH5/index.htm?source=android&mall=8&TGC=911FDD2F99B84D528F0A7EE71780A943", host: "www.testcrm.com" 2016/02/05 16:48:14 [error] 12013#0: *441119082 client intended to send too large body: 1331696 bytes, client: 113.214.1.10, server: localhost, request: "POST /h5teb/complaints/save.htm HTTP/1.1", host: "www.testcrm.com", referrer: "http://www.testcrm.com/h5teb/complaints/index.htm"
2,web工程中添加对文件上传的限制
web工程部署了一个单独的nginx,在http{后面添加限制100m的上限
client_max_body_size 100m; [nginx@wgq_idc_web_1_21 logs]$ vim /usr/local/nginx/conf/nginx.conf http { include mime.types; server_tokens off; sendfile on; tcp_nopush on; tcp_nodelay on; keepalive_timeout 65; log_format main '$proxy_add_x_forwarded_for $remote_user [$time_local] "$request" ' '$status $body_bytes_sent "$http_referer" ' '"$http_user_agent" "$http_x_forwarded_for" ' 'upstream: $upstream_addr'; access_log off; client_max_body_size 100m;
3,静态资源中添加对文件上传的限制
静态资源部署了一个单独的nginx,在转发location中进行配置100m的上限,client_max_body_size 100m;:
[fastdfs@wgq_test_crm~]$ vim /usr/local/nginx/conf/nginx.conf location /group1/M00 { root /data/fastdfs/data; include gzip.conf; ngx_fastdfs_module; client_max_body_size 100m; expires 12h; } location /group2/M00 { root /data/fastdfs_group2/data; ngx_fastdfs_module; client_max_body_size 100m; #access_log /usr/local/nginx/logs/group2_pic.log main; expires 12h; include gzip.conf; }
4,然后重新加载2组nginx服务器,问题解决了,不会再报错了。
感谢阅读,希望能帮助到大家,谢谢大家对本站的支持!
您可能感兴趣的文章:
- Nginx报403 forbidden错误 (13: Permission denied)的解决办法
- nginx提示:500 Internal Server Error错误的解决方法
- NGINX下配置404错误页面的方法分享
- 为Nginx自定义404,502错误页面的方法
- nginx调用php-fpm出错解决方法和nginx配置详解
- 实现Nginx中使用PHP-FPM时记录PHP错误日志的配置方法
- Linux服务器nginx访问日志里出现大量http 400错误的请求分析
- Nginx静态文件响应POST请求 提示405错误的解决方法
- Nginx中报错:Permission denied与Connection refused的解决
相关文章推荐
- nginx报错 client intended to send too large body: 1331696 bytes
- nginx报错 client intended to send too large body: 1331696 bytes
- 文件上传失败 -nginx报错 client intended to send too large body: 1331696 bytes
- android文件上传413 nginx [error] 9679#0: *318855 client intended to send too large body: 1593409 bytes
- Nginx错误:[error] 106793#0: *46318 client intended to send too large body: 3738202 bytes
- nginx: client intended to send too large body
- Nginx报错:upstream timed out (110: Connection timed out)和client intended to send too large body【转】
- client intended to send too large body
- mysql导入数据库文件最大限制更改解决方法You probably tried to upload too large file
- 解决:Bitmap too large to be uploaded into a texture exception
- 解决:Bitmap too large to be uploaded into a texture exception
- 解决:Bitmap too large to be uploaded into a texture exception
- flex结合svn时this client is too old to work with working copy错误解决方法。
- Bitmap too large to be uploaded into a texture (587x7696, max=2048x2048) 的解决方法
- SVN:This client is too old to work with working copy…解决办法
- SVN:This client is too old to work with working copy…解决办法
- 【Flume】Rpc sink XX closing Rpc client:NettyAvroRpcClient {xx} …… Failed to send events 问题解决
- 【Vegas原创】outlook发送时,报550 5.7.1 client does not have permissions to send as this sender解决方法
- 解决:Bitmap too large to be uploaded into a texture exception
- PhpMyaAmin导入sql文件时出现You probably tried to upload too large file的解决办法