nginx 错误502 upstream sent too big header while reading response header from upstream
来源:互联网 发布:kettle 大数据 编辑:程序博客网 时间:2024/06/05 20:13
查看nginx的错误日志,得到以下错误信息:
upstream sent too big header while reading response header from upstream
按字面意思理解应该是upstream负载均衡的模块转发的header头超出限制值了,查看配置文件中的相关配置,并搜索相关信息。
网上同类型的错误原因,说是cookie携带的header太多了,让你设置:
fastcgi_buffer_size 128k;
fastcgi_buffers 8 128k;
优化这些配置值,其中fastcgi_buffers 8 128k 这句,fastcgi_buffers 32 32k 这样更好,内存是整块分配和释放的,减少单位k数能尽可能利用。
在http配置段设置
{
proxy_buffer_size 128k;
proxy_buffers 32 32k;
proxy_busy_buffers_size 128k;
proxy_temp_file_write_size 128k;
}
proxy_temp_file_write_size 这个选项的值不能小于proxy_buffer_size,否则报错。
优化后,错误日志中没有继续出现报错。
另外,如果你用nginx做负载均衡的话,改了上述参数没用的的话,在转发的配置上,修改proxy_buffer_size、proxy_buffers、proxy_busy_buffers_size的值。
配置示例:
location / {
proxy_buffer_size 128k;
proxy_buffers 32 32k;
proxy_busy_buffers_size 128k;
add_header X-Static transfer;
proxy_redirect off;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_pass http://backend;
}
如果需要后端PHPCGI的设置:
location ~ \.php$ {
fastcgi_buffer_size 128k;
fastcgi_buffers 32 32k;
include /etc/nginx/fastcgi_params;
fastcgi_pass 127.0.0.1:9000;
fastcgi_index index.php;
fastcgi_param SCRIPT_FILENAME /host/web/$fastcgi_script_name;
}
总结原因:
proxy是nginx作为client转发时使用的,如果header过大,超出了默认的1k,就会引发上述的upstream sent too big header。
fastcgi_* 可以理解成nginx接受client请求时的响应使用的。
upstream sent too big header while reading response header from upstream
按字面意思理解应该是upstream负载均衡的模块转发的header头超出限制值了,查看配置文件中的相关配置,并搜索相关信息。
网上同类型的错误原因,说是cookie携带的header太多了,让你设置:
fastcgi_buffer_size 128k;
fastcgi_buffers 8 128k;
优化这些配置值,其中fastcgi_buffers 8 128k 这句,fastcgi_buffers 32 32k 这样更好,内存是整块分配和释放的,减少单位k数能尽可能利用。
在http配置段设置
{
proxy_buffer_size 128k;
proxy_buffers 32 32k;
proxy_busy_buffers_size 128k;
proxy_temp_file_write_size 128k;
}
proxy_temp_file_write_size 这个选项的值不能小于proxy_buffer_size,否则报错。
优化后,错误日志中没有继续出现报错。
另外,如果你用nginx做负载均衡的话,改了上述参数没用的的话,在转发的配置上,修改proxy_buffer_size、proxy_buffers、proxy_busy_buffers_size的值。
配置示例:
location / {
proxy_buffer_size 128k;
proxy_buffers 32 32k;
proxy_busy_buffers_size 128k;
add_header X-Static transfer;
proxy_redirect off;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_pass http://backend;
}
如果需要后端PHPCGI的设置:
location ~ \.php$ {
fastcgi_buffer_size 128k;
fastcgi_buffers 32 32k;
include /etc/nginx/fastcgi_params;
fastcgi_pass 127.0.0.1:9000;
fastcgi_index index.php;
fastcgi_param SCRIPT_FILENAME /host/web/$fastcgi_script_name;
}
总结原因:
proxy是nginx作为client转发时使用的,如果header过大,超出了默认的1k,就会引发上述的upstream sent too big header。
fastcgi_* 可以理解成nginx接受client请求时的响应使用的。
- nginx 错误502 upstream sent too big header while reading response header from upstream
- nginx 错误502 upstream sent too big header while reading response header from upstream
- nginx 错误502 upstream sent too big header while reading response header from upstream
- 502错误. Nginx日志:upstream sent too big header while reading response header from upstream
- 修复Nginx 502错误:upstream sent too big header while reading response header from upstream
- Nginx 错误502 upstream sent too big header while reading response header from upstream
- 错误502 upstream sent too big header while reading response header from upstream
- 修复Nginx报错:upstream sent too big header while reading response header from upstream
- 修复Nginx报错:upstream sent too big header while reading response header from upstream
- 69331 upstream sent too big header while reading response header from upstream
- php-fpm upstream sent too big header while reading response header from upstream
- 1345#0: *640 upstream sent too big header while reading response header from upstream
- upstream sent too big header while reading response header from upstream
- upstream sent invalid header while reading response header from upstream 错误解决
- while reading response header from upstream
- nginx upstream timed out (110: Connection timed out) while reading response header from upstream
- upstream sent too big header 502 Bad Gateway
- nginx recv() failed (104: Connection reset by peer) while reading response header from upstream解决方法
- MFC基本框架
- 联想服务客户端,100%解决您的电脑难题
- as3加密入门-1使用alchemy进行代码混淆
- 大正数减法(华为2013校园招聘上机笔试题 )
- 2013年9月22日星期日(准备工作:分离ddraw的math和interface)
- nginx 错误502 upstream sent too big header while reading response header from upstream
- ACM学习-POJ-1082-Calendar Game
- 使用VS2010 + VirtualDDK 调试驱动
- 带锁的门__简单题
- 转载新闻 你应该知道的一些 Linux 技巧
- 浏览器添加手机客户端访问
- 线程处理函数pthread_cleanup_push / pthread_cleanup_pop
- iPhone开发中的图像处理相关要点
- Wince6.0 下Camera(OV3640) 驱动开发笔记1——基于S5PC100