400错误请求 - 请求标头或cookie太大

use*_*793 37 ruby-on-rails nginx

我使用我的Rails应用程序从nginx获得400 Bad Request请求标头或cookie太大.重新启动浏览器可以解决问题.我只在我的cookie中存储一个字符串id,所以它应该很小.

我在哪里可以找到nginx错误日志?我查看了nano /opt/nginx/logs/error.log,但它没有任何相关内容.

我试着设定以下但没有运气:

location / {
    large_client_header_buffers  4 32k;
    proxy_buffer_size  32k;
}
Run Code Online (Sandbox Code Playgroud)

nginx.conf

#user  nobody;
worker_processes  1;
#error_log  logs/error.log;
#error_log  logs/error.log  notice;
#error_log  logs/error.log  info;
#pid        logs/nginx.pid;
events {
  worker_connections  1024;
}
http {
passenger_root /home/app/.rvm/gems/ruby-1.9.3-p392/gems/passenger-3.0.19;
passenger_ruby /home/app/.rvm/wrappers/ruby-1.9.3-p392/ruby;
include       mime.types;
default_type  application/octet-stream;
sendfile        on;
keepalive_timeout  65;
client_max_body_size 20M;
server {
    listen       80;
    server_name  localhost;
    root /home/app/myapp/current/public;
    passenger_enabled on;
    #charset koi8-r;
    #access_log  logs/host.access.log  main;

# location / {
#   large_client_header_buffers  4 32k;
#   proxy_buffer_size  32k;
# }

     #  location / {
     #   root   html;
     #   index  index.html index.htm;
     #   client_max_body_size 4M;
#   client_body_buffer_size 128k;
# }
    #error_page  404              /404.html;

    # redirect server error pages to the static page /50x.html
    #
    error_page   500 502 503 504  /50x.html;
    location = /50x.html {
        root   html;
    }

    # proxy the PHP scripts to Apache listening on 127.0.0.1:80
    #
    #location ~ \.php$ {
    #    proxy_pass   http://127.0.0.1;
    #}

    # pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000
    #
    #location ~ \.php$ {
    #    root           html;
    #    fastcgi_pass   127.0.0.1:9000;
    #    fastcgi_index  index.php;
    #    fastcgi_param  SCRIPT_FILENAME  /scripts$fastcgi_script_name;
    #    include        fastcgi_params;
    #}

    # deny access to .htaccess files, if Apache's document root
    # concurs with nginx's one
    #
    #location ~ /\.ht {
    #    deny  all;
    #}
}


# another virtual host using mix of IP-, name-, and port-based configuration
#
#server {
#    listen       8000;
#    listen       somename:8080;
#    server_name  somename  alias  another.alias;

#    location / {
#        root   html;
#        index  index.html index.htm;
#    }
#}


# HTTPS server
#
#server {
#    listen       443;
#    server_name  localhost;

#    ssl                  on;
#    ssl_certificate      cert.pem;
#    ssl_certificate_key  cert.key;

#    ssl_session_timeout  5m;

#    ssl_protocols  SSLv2 SSLv3 TLSv1;
#    ssl_ciphers  HIGH:!aNULL:!MD5;
#    ssl_prefer_server_ciphers   on;

#    location / {
#        root   html;
#        index  index.html index.htm;
#    }
#}

}
Run Code Online (Sandbox Code Playgroud)

这是我的代码存储cookie和Firebug中的cookie的屏幕截图.我使用firebug来检查存储的会话,我发现New Relic和jQuery也存储了cookie; 这可能是超出cookie大小的原因吗?

在此输入图像描述

def current_company
  return if current_user.nil?
  session[:current_company_id] = current_user.companies.first.id if session[:current_company_id].blank?
    @current_company ||= Company.find(session[:current_company_id])
end
Run Code Online (Sandbox Code Playgroud)

Bra*_*och 78

这就是错误所说的 - Request Header Or Cookie Too Large.你的一个标题非常大,nginx拒绝它.

你正走在正确的轨道上large_client_header_buffers.如果你检查文档,你会发现它只在http或中有效server上下文中.将它压缩到服务器块,它将工作.

server {
    # ...
    large_client_header_buffers 4 32k;
    # ...
}
Run Code Online (Sandbox Code Playgroud)

顺便说一句,默认的缓冲区编号和大小是48k,所以你的错误标题必须是超过8192字节的标题.在您的情况下,所有这些cookie(组合到一个标题)远远超过限制.那些混合面包饼干特别大.

  • 感谢您的发布和上下文。总是总比知道要更改原因和更改要好得多! (2认同)

use*_*793 15

通过添加修复

server {
  ...
  large_client_header_buffers 4 16k;
  ...
} 
Run Code Online (Sandbox Code Playgroud)

  • 这个解决方案的基本原理是什么?对问题的解释有一点帮助未来的访客. (6认同)

dr.*_*tru 10

关于上面的答案,但client_header_buffer_size需要提到的是:

http {
  ...
  client_body_buffer_size     32k;
  client_header_buffer_size   8k;
  large_client_header_buffers 8 64k;
  ...
}
Run Code Online (Sandbox Code Playgroud)

  • 为了完整起见,client_header_buffer_size 的文档声明如下:“设置读取客户端请求头的缓冲区大小。对于大多数请求,1K 字节的缓冲区就足够了。但是,如果请求包含长 cookie,或者来自 WAP 客户端,它可能不适合 1K。如果请求行或请求头字段不适合此缓冲区,则分配由 large_client_header_buffers 指令配置的更大缓冲区。 (3认同)