我遇到了这些错误：
2014/05/24 11:49:06 [错误] 8376＃0：* 54031上游在从上游读取响应头时发送了太大的头，客户端：107.21.193.210，服务器：aamjanata.com，请求：“GET /the-brainwash-chronicles-sponsored-by-gujarat-government/,%20https:/aamjanata.com/the-brainwash-chronicles-sponsored-by-gujarat-government/,%20https:/aamjanata.com/the-brainwash -chronicles赞助逐古吉拉特邦政府/，％20https：/aamjanata.com/the-brainwash-chronicles-sponsored-by-gujarat-government /，％20https：/aamjanata.com/the-brainwash-chronicles-sponsored逐古吉拉特邦政府/，％20https：/aamjanata.com/the-brainwash-chronicles-sponsored-by-gujarat-government /，％20https：/aamjanata.com/the-brainwash-chronicles-sponsored-by-gujarat - 政府/，％20https：/aamjanata.com/the-brainwash-chronicles-sponsored-by-gujarat-government /，％20https：/aamjanata.com/the-brainwash-chronicles-sponsored-by-gujarat-government/， ％20https：/aamjanata.com/the-brainwash-chronicles-sponsored-by-gujarat-government /，％20https：/aamjanata.co M /的-洗脑 - 编年史主办逐古吉拉特邦政府/，％20https：/aamjanata.com/the-brainwash-chronicles-sponsored-by-gujarat-government /，％20https：/aamjanata.com/the-洗脑-编年史主办逐古吉拉特邦政府/，％20https：/aamjanata.com/the-brainwash-chronicles-sponsored-by-gujarat-government /，％20https：/aamjanata.com/the-brainwash-chronicles-赞助逐古吉拉特邦政府/，％20https：/aamjanata.com/the-brainwash-chronicles-sponsored-by-gujarat-government/,%20https：//aamjanata.com/the-brainwash-chronicles-sponsored-by -gujarat政府/，％20https：/aamjanata.com/the-brainwash-chronicles-sponsored-by-gujarat-government /，％20https：/aamjanata.com/the-brainwash-chronicles-sponsored-by-gujarat-government /,%20https:/aamjanata.com/the-brainwash-chronicles-sponsored-by-gujarat-government/,%20https:/aamjanata.com/the-brainwash-chronicles-sponsored-by-gujarat-government/,%20https ：/aamjanata.com/the-brainwash-chronicles-sponsored-by-gujarat-government /，％20https：/aamjanata.com/the-brainwash -chronicles赞助逐古吉拉特邦政府/，％20ht
总是一样的。一个url一遍又一遍地用逗号分隔重复。无法弄清楚造成这种情况的原因。有人有想法吗？
更新：另一个错误：
http request count is zero while sending response to client
这是配置。还有其他不相关的东西，但这部分已添加/编辑
fastcgi_cache_path /var/nginx-cache levels=1:2 keys_zone=WORDPRESS:100m inactive=60m;
fastcgi_cache_key "$scheme$request_method$host$request_uri";
fastcgi_cache_use_stale error timeout invalid_header http_500;
fastcgi_ignore_headers Cache-Control Expires Set-Cookie;
proxy_buffer_size 128k;
proxy_buffers 4 256k;
proxy_busy_buffers_size 256k;
# Upstream to abstract backend connection(s) for PHP.
upstream php {
#this should match value of "listen" directive in php-fpm pool
server unix:/var/run/php5-fpm.sock;
}
然后在服务器块中： 设置$ skip_cache 0;
# POST requests and urls with a query string should always go to PHP
if ($request_method = POST) {
set $skip_cache 1;
}
if ($query_string != "") {
set $skip_cache 1;
}
# Don't cache uris containing the following segments
if ($request_uri ~* "/wp-admin/|/xmlrpc.php|wp-.*.php|/feed/|index.php|sitemap(_index)?.xml") {
set $skip_cache 1;
}
# Don't use the cache for logged in users or recent commenters
if ($http_cookie ~* "comment_author|wordpress_[a-f0-9]+|wp-postpass|wordpress_no_cache|wordpress_logged_in") {
set $skip_cache 1;
}
location / {
# This is cool because no php is touched for static content.
# include the "?$args" part so non-default permalinks doesn't break when using query string
try_files $uri $uri/ /index.php?$args;
}
location ~ \.php$ {
try_files $uri /index.php;
include fastcgi_params;
fastcgi_pass php;
fastcgi_read_timeout 3000;
fastcgi_cache_bypass $skip_cache;
fastcgi_no_cache $skip_cache;
fastcgi_cache WORDPRESS;
fastcgi_cache_valid 60m;
}
location ~ /purge(/.*) {
fastcgi_cache_purge WORDPRESS "$scheme$request_method$host$1";
}`
答案 0 :(得分：337)
将以下内容添加到您的conf文件
fastcgi_buffers 16 16k;
fastcgi_buffer_size 32k;
答案 1 :(得分：108)
即适用于ngx_http_proxy_module
除了fastcgi之外，proxy模块还将请求标头保存在临时缓冲区中。
因此，您可能还需要增加proxy_buffer_size和proxy_buffers，或者完全禁用它（请阅读nginx documentation）。
http {
proxy_buffer_size 128k;
proxy_buffers 4 256k;
proxy_busy_buffers_size 256k;
}
http {
proxy_buffering off;
}
答案 2 :(得分：9)
在Plesk 12中，我将nginx作为反向代理运行（我认为是默认代理）。因此，当前的最佳答案不起作用，因为nginx也作为代理运行。
我去了FileName。
然后在该页面的底部，您可以设置附加nginx指令，我将其设置为前两个答案的组合：
Subscriptions | [subscription domain] | Websites & Domains (tab) | [Virtual Host domain] | Web Server Settings答案 3 :(得分：5)
如果您正在使用Symfony框架： 在弄乱Nginx配置之前，请先尝试禁用ChromePHP。
1 - 打开app / config / config_dev.yml
2 - 评论以下几行：
#chromephp:
#type: chromephp
#level: info
ChromePHP将调试信息json编码打包在X-ChromePhp-Data标头中，这对于使用fastcgi的nginx的默认配置来说太大了。
来源：https://github.com/symfony/symfony/issues/8413#issuecomment-20412848
答案 4 :(得分：3)
添加：
fastcgi_buffers 16 16k;
fastcgi_buffer_size 32k;
proxy_buffer_size 128k;
proxy_buffers 4 256k;
proxy_busy_buffers_size 256k;
到 nginx.conf 中的服务器{}
对我有用。
答案 5 :(得分：2)
我们最终意识到我们的一台服务器遇到了这个已经破坏了fpm配置，导致通常记录到磁盘的php错误/警告/通知是通过FCGI套接字发送的。当部分标题在缓冲区块中分割时，看起来有一个解析错误。
因此将php_admin_value[error_log]设置为实际可写的内容并重新启动php-fpm就足以解决问题。
我们可以用较小的脚本重现问题：
<?php
for ($i = 0; $i<$_GET['iterations']; $i++)
error_log(str_pad("a", $_GET['size'], "a"));
echo "got here\n";
提高缓冲区使得502s更难以击中但并非不可能，例如原生：
bash-4.1# for it in {30..200..3}; do for size in {100..250..3}; do echo "size=$size iterations=$it $(curl -sv "http://localhost/debug.php?size=$size&iterations=$it" 2>&1 | egrep '^< HTTP')"; done; done | grep 502 | head
size=121 iterations=30 < HTTP/1.1 502 Bad Gateway
size=109 iterations=33 < HTTP/1.1 502 Bad Gateway
size=232 iterations=33 < HTTP/1.1 502 Bad Gateway
size=241 iterations=48 < HTTP/1.1 502 Bad Gateway
size=145 iterations=51 < HTTP/1.1 502 Bad Gateway
size=226 iterations=51 < HTTP/1.1 502 Bad Gateway
size=190 iterations=60 < HTTP/1.1 502 Bad Gateway
size=115 iterations=63 < HTTP/1.1 502 Bad Gateway
size=109 iterations=66 < HTTP/1.1 502 Bad Gateway
size=163 iterations=69 < HTTP/1.1 502 Bad Gateway
[... there would be more here, but I piped through head ...]
fastcgi_buffers 16 16k; fastcgi_buffer_size 32k;：
bash-4.1# for it in {30..200..3}; do for size in {100..250..3}; do echo "size=$size iterations=$it $(curl -sv "http://localhost/debug.php?size=$size&iterations=$it" 2>&1 | egrep '^< HTTP')"; done; done | grep 502 | head
size=223 iterations=69 < HTTP/1.1 502 Bad Gateway
size=184 iterations=165 < HTTP/1.1 502 Bad Gateway
size=151 iterations=198 < HTTP/1.1 502 Bad Gateway
所以我认为正确的答案是：修复你的fpm配置，以便将错误记录到磁盘上。
答案 6 :(得分：2)
我不确定问题是否与php发送的标头有关。 确保已启用缓冲。简单的方法是创建一个proxy.conf文件：
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;
client_max_body_size 100m;
client_body_buffer_size 128k;
proxy_connect_timeout 90;
proxy_send_timeout 90;
proxy_read_timeout 90;
proxy_buffering on;
proxy_buffer_size 128k;
proxy_buffers 4 256k;
proxy_busy_buffers_size 256k;
还有fascgi.conf文件：
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
fastcgi_param QUERY_STRING $query_string;
fastcgi_param REQUEST_METHOD $request_method;
fastcgi_param CONTENT_TYPE $content_type;
fastcgi_param CONTENT_LENGTH $content_length;
fastcgi_param SCRIPT_NAME $fastcgi_script_name;
fastcgi_param REQUEST_URI $request_uri;
fastcgi_param DOCUMENT_URI $document_uri;
fastcgi_param DOCUMENT_ROOT $document_root;
fastcgi_param SERVER_PROTOCOL $server_protocol;
fastcgi_param GATEWAY_INTERFACE CGI/1.1;
fastcgi_param SERVER_SOFTWARE nginx/$nginx_version;
fastcgi_param REMOTE_ADDR $remote_addr;
fastcgi_param REMOTE_PORT $remote_port;
fastcgi_param SERVER_ADDR $server_addr;
fastcgi_param SERVER_PORT $server_port;
fastcgi_param SERVER_NAME $server_name;
fastcgi_buffers 128 4096k;
fastcgi_buffer_size 4096k;
fastcgi_index index.php;
fastcgi_param REDIRECT_STATUS 200;
接下来，您需要通过以下方式在默认配置服务器中调用它们：
http {
include /etc/nginx/mime.types;
include /etc/nginx/proxy.conf;
include /etc/nginx/fastcgi.conf;
index index.html index.htm index.php;
log_format main '$remote_addr - $remote_user [$time_local] $status '
'"$request" $body_bytes_sent "$http_referer" '
'"$http_user_agent" "$http_x_forwarded_for"';
#access_log /logs/access.log main;
sendfile on;
tcp_nopush on;
# ........
}
答案 7 :(得分：2)
我有一个部署到 EBS 的 django 应用程序，我使用的是在 64 位 Amazon Linux 2 上运行的 Python 3.8。以下方法对我有用（注意，如果您使用的是以前的 Linux 版本，文件夹结构可能会有所不同。有关更多信息，见official documentation here
制作 .platform 文件夹及其子目录，如下所示：
|-- .ebextensions # Don't put nginx config here
| |-- django.config
|-- .platform # Make ".platform" folder and its subfolders
|-- nginx
| -- conf.d
| -- proxy.conf
请注意，proxy.conf 文件应该放在 .platform 文件夹中，而不是 .ebextensions 文件夹或 .elasticbeanstalk< /strong> 文件夹。扩展名应以 .conf 结尾，而不是 .config。
在 proxy.conf 文件中，直接复制并粘贴以下几行：
client_max_body_size 50M;
large_client_header_buffers 4 32k;
fastcgi_buffers 16 32k;
fastcgi_buffer_size 32k;
proxy_buffer_size 128k;
proxy_buffers 4 256k;
proxy_busy_buffers_size 256k;
无需发出重启 nginx 的命令（适用于 Amazon Linux 2）
再次将源代码部署到elastic beanstalk。
答案 8 :(得分：2)
在 php-fpm 中运行 Symfony 应用程序和在 docker 容器中运行 nginx 时遇到同样的问题。
经过一番研究发现是php-fpm的stderr写入nginx日志引起的。 IE。 php 警告（在 Symfony 调试模式下密集生成）在 docker logs php-fpm 中重复：
[09-Jul-2021 12:25:46] WARNING: [pool www] child 38 said into stderr: ""
[09-Jul-2021 12:25:46] WARNING: [pool www] child 38 said into stderr: "NOTICE: PHP message: [debug] Notified event "kernel.response" to listener "Symfony\Component\HttpKernel\EventListener\DisallowRobotsIndexingListener::onResponse"."
[09-Jul-2021 12:25:46] WARNING: [pool www] child 38 said into stderr: ""
[09-Jul-2021 12:25:46] WARNING: [pool www] child 38 said into stderr: "NOTICE: PHP message: [debug] Notified event "kernel.response" to listener "Symfony\Component\HttpKernel\EventListener\StreamedResponseListener::onKernelResponse"."
[09-Jul-2021 12:25:46] WARNING: [pool www] child 38 said into stderr: ""
[09-Jul-2021 12:25:46] WARNING: [pool www] child 38 said into stderr: "NOTICE: PHP message: [debug] Notified event "kernel.finish_request" to listener "Symfony\Component\HttpKernel\EventListener\LocaleListener::onKernelFinishRequest"."
[09-Jul-2021 12:25:46] WARNING: [pool www] child 38 said into stderr: ""
[09-Jul-2021 12:25:46] WARNING: [pool www] child 38 said into stderr: "NOTICE: PHP message: [debug] Notified event "kernel.finish_request" to listener "Symfony\Component\HttpKernel\EventListener\RouterListener::onKernelFinishRequest"."
[09-Jul-2021 12:25:46] WARNING: [pool www] child 38 said into stderr: ""
[09-Jul-2021 12:25:46] WARNING: [pool www] child 38 said into stderr: "NOTICE: PHP message: [debug] Notified event "kernel.finish_request" to listener "Symfony\Component\HttpKernel\EventListener\LocaleAwareListener::onKernelFinishRequest"."
[09-Jul-2021 12:25:46] WARNING: [pool www] child 38 said into stderr: ""
[09-Jul-2021 12:25:46] WARNING: [pool www] child 38 said into stderr: "NOTICE: PHP message: [debug] Notified event "kernel.terminate" to listener "Symfony\Component\HttpKernel\EventListener\ProfilerListener::onKernelTerminate"."
[09-Jul-2021 12:25:46] WARNING: [pool www] child 38 said into stderr: ""
和docker logs nginx：
2021/07/09 12:25:46 [error] 30#30: *2 FastCGI sent in stderr: "ller" to listener "OblgazAPI\API\Common\Infrastructure\EventSubscriber\LegalAuthenticationChecker::checkAuthentication".
PHP message: [debug] Notified event "kernel.controller_arguments" to listener "Symfony\Component\HttpKernel\EventListener\ErrorListener::onControllerArguments".
PHP message: [debug] Notified event "kernel.response" to listener "Symfony\Component\HttpKernel\EventListener\ResponseListener::onKernelResponse".
PHP message: [debug] Notified event "kernel.response" to listener "Symfony\Component\HttpKernel\DataCollector\RequestDataCollector::onKernelResponse".
PHP message: [debug] Notified event "kernel.response" to listener "Symfony\Component\HttpKernel\EventListener\ProfilerListener::onKernelResponse".
PHP message: [debug] Notified event "kernel.response" to listener "Symfony\Bundle\WebProfilerBundle\EventListener\WebDebugToolbarListener::onKernelResponse".
PHP message: [debug] Notified event "kernel.response" to listener "Symfony\Component\HttpKernel\EventListener\DisallowRobotsIndexingListener::onResponse".
PHP message: [debug] Notified event "kernel.response" to listener "Symfony\Component\HttpKernel\EventListener\StreamedResponseListener::onKernelResponse".
PHP message: [debug] Notified event "kernel.finish_request" to listener "Symfony\Component\HttpKernel\EventListener\LocaleListener::onKernelFinishRequest".
PHP message: [debug] Notified event "kernel.finish_request" to listener "Symfony\Component\HttpKernel\EventListener\RouterListener::onKernelFinishRequest".
PHP message: [debug] Notified event "kernel.finish_request" to listener "Symfony\Component\HttpKernel\EventListener\LocaleAwareListener::onKernelFinishRequest".
PHP message: [debug] Notified event "kernel.exception" to listener "Symfony\Component\HttpKernel\EventListener\ErrorListener::logKernelException".
PHP message: [debug] Notified event "kernel.exception" to listener "Symfony\Component\HttpKernel\EventListener\ProfilerListener::onKernelException".
然后nginx日志以
结尾2021/07/09 12:25:46 [error] 30#30: *2 upstream sent too big header while reading response header from upstream ...
我收到了 502 错误。
在 nginx 配置中增加 fastcgi_buffer_size 有帮助，但它似乎更像是抑制问题，而不是治疗。
更好的解决方案是禁用 php-fpm 以通过 FastCGI 发送日志。发现可以通过在php.ini中设置fastcgi.logging=0来实现（默认为1）。 php docs。
将其更改为 0 后，问题消失，nginx 日志看起来更清晰docker logs nginx：
172.18.0.1 - - [09/Jul/2021:12:36:02 +0300] "GET /my/symfony/app HTTP/1.1" 401 73 "-" "PostmanRuntime/7.26.8"
172.18.0.1 - - [09/Jul/2021:12:36:04 +0300] "GET /my/symfony/app HTTP/1.1" 401 73 "-" "PostmanRuntime/7.26.8"
并且所有 php-fpm 日志仍然在 php-fpm 日志中。
答案 9 :(得分：0)
在搜索此错误时，这仍然是Google上最高的SO问题，所以让我们碰一下。
出现此错误并且不想立即深入研究NGINX设置时，您可能需要检查到调试控制台的输出。 以我为例，我正在将大量文本输出到FirePHP / Chromelogger控制台，由于所有这些都是作为标头发送的，因此导致了溢出。
如果此错误仅是由发送大量日志消息引起的，则可能不需要更改Web服务器设置。
答案 10 :(得分：0)
在我们的例子中，我们收到了这个 nginx 错误，因为我们的后端生成了一个很长的 URL 的重定向响应：
HTTP/1.1 301 Moved Permanently
Location: https://www.example.com/?manyParamsHere...
出于好奇，我们将那个大 URL 保存到一个文件中，它的大小为 4.4 Kb。
在配置文件 /etc/nginx/conf.d/some_site.conf 中添加两行帮助我们修复了这个错误：
server {
# ...
location ~ ^/index\.php(/|$) {
fastcgi_pass php-upstream;
fastcgi_split_path_info ^(.+\.php)(/.*)$;
include fastcgi_params;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
# Add these lines:
fastcgi_buffer_size 32k;
fastcgi_buffers 4 32k;
}
}
在官方 nginx documentation 上阅读有关这些参数的更多信息。