nginx proxy_buffer_size 解决后端服务传输数据过多,其实是header过大的问题
来源:互联网 发布:最好的网络营销软件 编辑:程序博客网 时间:2024/06/05 08:34
nginx proxy_buffer_size 解决后端服务传输数据过多,其实是header过大的问题
这三个参数已设置就搞定了额
proxy_buffer_size 64k;proxy_buffers 4 32k;proxy_busy_buffers_size 64k;
本着精益求精的精神我翻了官网
官网解释
总体来说我还是没懂。我把报错信息放出来,以后用得着。
开发说nginx502了,后端访问jesery没问题
不行curl -i -v "test.lebi.letv.cn/report/rest/saiku/api/query/7C53220D-A870-1FE3-9353-4A6F967F25CB/result/metadata/hierarchies/%5BDM_REC.DIM_LIVE_STATION%5D.%5BDM_REC.DIM_LIVE_STATION.LIVE_STATION_NAME%5D/levels/DM_REC.DIM_LIVE_STATION.LIVE_STATION_NAME?result=false&_=1489736122190"可以curl -i -v "http://10.142.165.45:8080/report/rest/saiku/api/query/7C53220D-A870-1FE3-9353-4A6F967F25CB/result/metadata/hierarchies/%5BDM_REC.DIM_LIVE_STATION%5D.%5BDM_REC.DIM_LIVE_STATION.LIVE_STATION_NAME%5D/levels/DM_REC.DIM_LIVE_STATION.LIVE_STATION_NAME?result=false&_=1489736122190"
日志对比
返回502"10.73.137.12","[17/Mar/2017:16:32:08 +0800]","HTTP/1.1","-","GET","/report/rest/saiku/api/query/7C53220D-A870-1FE3-9353-4A6F967F25CB/result/metadata/hierarchies/%5BDM_REC.DIM_LIVE_STATION%5D.%5BDM_REC.DIM_LIVE_STATION.LIVE_STATION_NAME%5D/levels/DM_REC.DIM_LIVE_STATION.LIVE_STATION_NAME?result=false&_=1489736122190","502","http://test.lebi.letv.cn/report/rest/saiku/api/query/7C53220D-A870-1FE3-9353-4A6F967F25CB/result/metadata/hierarchies/%5BDM_REC.DIM_LIVE_STATION%5D.%5BDM_REC.DIM_LIVE_STATION.LIVE_STATION_NAME%5D/levels/DM_REC.DIM_LIVE_STATION.LIVE_STATION_NAME?result=false&_=1489736122190","172","0.157","10.142.165.45:8080","-","curl/7.35.0","0.157","329","328"正常了"10.73.137.12","[17/Mar/2017:16:32:47 +0800]","HTTP/1.1","-","GET","/report/rest/saiku/api/query/7C53220D-A870-1FE3-9353-4A6F967F25CB/result/metadata/hierarchies/%5BDM_REC.DIM_LIVE_STATION%5D.%5BDM_REC.DIM_LIVE_STATION.LIVE_STATION_NAME%5D/levels/DM_REC.DIM_LIVE_STATION.LIVE_STATION_NAME?result=false&_=1489736122190","200","http://test.lebi.letv.cn/report/rest/saiku/api/query/7C53220D-A870-1FE3-9353-4A6F967F25CB/result/metadata/hierarchies/%5BDM_REC.DIM_LIVE_STATION%5D.%5BDM_REC.DIM_LIVE_STATION.LIVE_STATION_NAME%5D/levels/DM_REC.DIM_LIVE_STATION.LIVE_STATION_NAME?result=false&_=1489736122190","1342118","4.350","10.142.165.45:8080","-","curl/7.35.0","0.180","329","1346306"
我测了下,返回的json数据大约1.3M,可能是返回值太大,超过了阈值,但是超过了哪个呢,比较纠结。
查看error日志得到upstream sent too big header while reading response header from upstream,说header太大了。好好学习下header
2017/03/17 16:32:08 [error] 17441#0: *403548696 upstream sent too big header while reading response header from upstream, client: 10.73.137.12, server: test.lebi.letv.cn, request: "GET /report/rest/saiku/api/query/7C53220D-A870-1FE3-9353-4A6F967F25CB/result/metadata/hierarchies/%5BDM_REC.DIM_LIVE_STATION%5D.%5BDM_REC.DIM_LIVE_STATION.LIVE_STATION_NAME%5D/levels/DM_REC.DIM_LIVE_STATION.LIVE_STATION_NAME?result=false&_=1489736122190 HTTP/1.1", upstream: "http://10.142.165.45:8080/report/rest/saiku/api/query/7C53220D-A870-1FE3-9353-4A6F967F25CB/result/metadata/hierarchies/%5BDM_REC.DIM_LIVE_STATION%5D.%5BDM_REC.DIM_LIVE_STATION.LIVE_STATION_NAME%5D/levels/DM_REC.DIM_LIVE_STATION.LIVE_STATION_NAME?result=false&_=1489736122190", host: "test.lebi.letv.cn"
0 0
- nginx proxy_buffer_size 解决后端服务传输数据过多,其实是header过大的问题
- 在网络传输过程中解决加载图片过多,过大问题
- 解决由于Office文档过大导致的传输问题
- java后端发布的接口数据是如何加密传输
- Nginx-proxy_buffer_size and fastcgi_buffer
- 解决map集合数据过多get操作慢的问题
- 通过Nginx访问后端应用,ERR_CONTENT_LENGTH_MISMATCH 问题的解决
- 通过Nginx访问后端应用,ERR_CONTENT_LENGTH_MISMATCH 问题的解决
- 补充--解决由于Office文档过大导致的传输问题
- WCF 通过web.config配置文件解决传输内容过大问题
- post数据过大的问题
- nginx + fcgi的 header问题
- 解决GET提交JSON数据在后端的乱码问题
- Silverlight在调用wcf时传输数据过大的解决办法
- 解决打开文件过多的问题
- 解决Firefox占用系统资源过多的问题
- 解决TCP连接数过多的问题
- 解决TCP连接数过多的问题
- [Android]通过JNI实现卸载自身App后台发送Http请求~
- vector容器添加和删除元素
- Spring框架入门介绍
- Samba文件共享配置
- 自定义 ToolBar 实现标题栏
- nginx proxy_buffer_size 解决后端服务传输数据过多,其实是header过大的问题
- (TrustCom 2015)基于Trustzone的智能手机双因子认证通用安全架构
- springmvc服务端校验hibernate validation配置
- Composer详细安装教程
- Linux加载DTS设备节点的过程(以高通8974平台为例)
- ubuntu安装DBI,DBD-MYSQL
- R语言中实现表的链接-merge函数
- JS展望之
- poj 3685 二分法(边界条件)