アップストリームからの応答ヘッダーを読み取っているときにアップストリームが送信したヘッダーが大きすぎる 質問する

次のようなエラーが発生します:

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-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-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-sponso red-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-sponsored-by-gujarat-government/、%20https:/aamjanata.com/the-b rainwash-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/、%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;
    }

    # 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";
    }`