이러한 종류의 오류가 발생합니다.
2014/05/24 11:49:06 [오류] 8376 # 0 : * 54031 업스트림에서 응답 헤더를 읽는 동안 업스트림이 너무 큰 헤더를 보냈습니다. 클라이언트 : 107.21.193.210, 서버 : aamjanata.com, 요청 : "GET / the- 구자라트 정부 후원, 구자라트 정부 /, % 20https : /aamjanata.com/the-brainwash-chronicles-ponsored-gu-gujarat-government /, % 20https : /aamjanata.com/the-brainwash-chronicles- 구자라트 정부 후원, % 20https : /aamjanata.com/the-brainwash-chronicles-sponsored-gu-jara-government /, % 20https : /aamjanata.com/the-brainwash-chronicles-sponsored-by- 구자라트 정부 /,%20https:/aamjanata.com/the-brainwash-chronicles-sponsored by-gujarat-government /, % 20https : /aamjanata.com/the-brainwash-chronicles-sponsored-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- 구자라트 정부 후원, 구자라트 정부 /, % 20https : /aamjanata.com/the-brainwash-chronicles-ponsored-gu-gujarat-government /, % 20https : /aamjanata.com/the-brainwash-chronicles- 구자라트 정부 후원, % 20https : /aamjanata.com/the-brainwash-chronicles-sponsored-gu-jara-government /, % 20https : /aamjanata.com/the-brainwash-chronicles-sponsored-by- 구자라트 정부 /,%20https:/aamjanata.com/the-brainwash-chronicles-sponsored-by-gujarat-government/,%20https://aamjanata.com/the-brainwash-chronicles-sponsored-gu-jara-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- 구자라트 정부 후원, 구자라트 정부 /, % 20https : /aamjanata.com/the-brainwash-chronicles-ponsored-gu-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;
}그리고 서버 블록에서 : set $ 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";
}`