年底了事情真多,club服务器有问必答 提交页面 提交出这个问题

The page you are looking for is temporarily unavailable.Please try again later.

一看就知道是nginx的请求的错误,,惆怅啊。。

就开启了 错误日志查看。。。

tail -f error.log
就具体错误是 :

upstream sent too big header while reading response header from upstream

我们是nginx反向代理
proxy是nginx作为client转发时使用的,如果header过大,超出了默认的1k,就会引发上述的upstream sent too big header (说白了就是nginx把外部请求给后端apache ,apache返回的header  太大nginx处理不过来就导致了。

server {
        listen       80;
        server_name  *.xywy.com ;

large_client_header_buffers 4 16k;

#charset koi8-r;

# access_log off;

location / {

#添加这3行 ,
                proxy_buffer_size 64k;
                proxy_buffers   32 32k;
                proxy_busy_buffers_size 128k;

proxy_set_header Host $host;
           proxy_set_header X-Real-IP       $remote_addr;
           proxy_set_header X-Forwarded-For  $proxy_add_x_forwarded_for;

set $baiduspider '';

if ( $http_user_agent ~ Baiduspider) {
              set $baiduspider Baidu;
          }

............

如果是 nginx+PHPcgi 就该

fastcgi_connect_timeout 60;
fastcgi_send_timeout 180;
fastcgi_read_timeout 180;
fastcgi_buffer_size 128k;
fastcgi_buffers 4 256k;
fastcgi_busy_buffers_size 256k;
fastcgi_temp_file_write_size 256k;
fastcgi_intercept_errors on
011/01/07 11:12:57 [error] 10770#0: *38585340 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 116.22.131.154, server: *.xywy.com, request: "GET /ysmp/index.php?did=124994 HTTP/1.0", upstream: "http://127.0.0.1:8080/ysmp/index.php?did=124994", host: "xywy.yn16.com"

后来原来那错误没了出了新错误了 upstream timed out 超时?

server {
        listen       80;
        server_name  *.xywy.com ;
  large_client_header_buffers 4 16k;
        client_max_body_size 300m;
        client_body_buffer_size 128k;
        proxy_connect_timeout 600;
        proxy_read_timeout 600;
        proxy_send_timeout 600;
                proxy_buffer_size 64k;
                proxy_buffers   4 32k;
                proxy_busy_buffers_size 64k;
                proxy_temp_file_write_size 64k;
        #charset koi8-r;

# access_log off;

后来参数我又改了下 就好了。。。

可以参考:

http://wiki.nginx.org/NginxHttpProxyModule

http://blog.sina.com.cn/s/blog_5dc960cd0100i4mt.html

本文转自 houzaicunsky 51CTO博客,原文链接:   13页http://blog.51cto.com/hzcsky/475574

upstream sent too big header while reading response header from upstream相关推荐

  1. nginx 错误502 upstream sent too big header while reading response header from upst

    原文参考:http://hi.baidu.com/wastorode/item/ec86ade6ac0af7a2c10d75f4 sudo gedit /var/log/nginx/error.log ...

  2. [temp]Nginx 错误502 upstream sent too big header while reading response header from upstream

    Nginx 502 Bad Gateway的含义是请求的PHP-CGI已经执行,但是由于某种原因(一般是读取资源的问题)没有执行完毕而导致PHP-CGI进程终止. Nginx 504 Gateway ...

  3. Nginx 错误502 upstream sent too big header while reading response header from upstream

    Nginx 502 Bad Gateway的含义是请求的PHP-CGI已经执行,但是由于某种原因(一般是读取资源的问题)没有执行完毕而导致PHP-CGI进程终止. Nginx 504 Gateway ...

  4. nginx 502错误 upstream sent too big header while reading response header from upstream

    原本的设置是 proxy_buffer_size 4k; proxy_buffers 4 32k; proxy_busy_buffers_size 64k; 在这种配置下,使用fiddler进行抓包分 ...

  5. recv() failed (104: Connection reset by peer) while reading response header from upstream

    场景:为了得到用户在线等实时信息,在客户端做了个ajax轮训,每隔5秒请求一次: 用户量一上来,于是问题就来了,页面各种卡nginx日志文件 [root@iZt web]# tail -f /data ...

  6. nginx响应超时upstream timed out (110: Connection timed out) while reading response header from upstream

    问题描述 解决方法 提高nginx网络吞吐量buffers优化指令说明 nginx代理超时配置 nginx缓存区大小设置 问题描述 后台server服务响应时间正常,但是请求没有打到服务器,在ngin ...

  7. 解决 ”upstream prematurely closed connection while reading response header from upstream“ 问题,运行环境为:ngi

    解决 "upstream prematurely closed connection while reading response header from upstream" 问题 ...

  8. 502 Proxy Error The proxy server received an invalid response from an upstream server

    Proxy Error The proxy server received an invalid response from an upstream server. The proxy server ...

  9. Sent non-empty 'Sec-WebSocket-Protocol' header but no response was received

    Sent non-empty 'Sec-WebSocket-Protocol' header but no response was received

最新文章

  1. camera摄像原理之三:色温和自动白平衡【转】
  2. 【OpenCV十六新手教程】OpenCV角检测Harris角点检测
  3. RHEL 5搭建Samba服务器详细过程
  4. IE中页面不居中,火狐谷歌等正常
  5. LeetCode 86分割链表87扰乱字符串
  6. 穆里尼奥:与范加尔风格不同,转变需要时间
  7. asp.net Linux 界面,在 ASP.NET 中实现不同角色的用户使用不同登录界面的方法
  8. nuxt项目打包上线之二
  9. 华为云发起美食图片分类大赛!奖品丰厚还可免费使用云资源
  10. linux下keytool生成证书_Keytool生成https证书步骤0014
  11. 华为笔试题分享:分糖果
  12. 实用的活动报名微信小程序应用
  13. ARM-Linux 交叉编译工具链安装
  14. 华氏温度和摄氏温度的转换-C语言
  15. Third season seventeenth episode,Ross and Rachel can not stay at one place???
  16. 苹果设备的微信数据收集
  17. 自我检查,看清自己 看清自己什么皮肤。
  18. Python Socket网络编程(一)初识Socket和Socket初步使用
  19. Oracle EBS MTL_SUPPLY作用
  20. Unity中使用软连接快速切换平台

热门文章

  1. Java编程初学水仙花典型例题:
  2. 相机模型-Unified Camera Model
  3. C实战——高配版贪吃蛇游戏设计
  4. linux 脱机安装包,linux 离线下载rpm安装包
  5. 前端入职第一天,应该做什么
  6. rtx3090能组成超级计算机吗,惊人的核心怎么来的?RTX3090架构魔术揭秘
  7. 数据结构C++边学边做--二叉树的实现(二叉链表实现遍历操作)
  8. 验证码无法改变的问题(验证码看不清,换一个,却不起作用)
  9. django之跨表查询及添加记录
  10. 2019世界地球日,美厦三恒系统与您一起守护我们的地球母亲