我有nginx 1.6.2服务一个wordpress网站，用php-fpm。
固定链接设置如下： /blog/%postname%/
nginx正确地为网站页面（ / ， /products ， /contact …）以及博客文章（在/blog/ ）提供服务。 404s可以很好地用于博客文章（即example.com/blog/idontExist将以404响应）。 但是，浏览到example.com/iDontExist会得到HTTP 200响应和网站索引页的内容，而不是404。
这是我的nginx.conf：
server { server_name example.com; root /var/local/example.com/; access_log /var/log/nginx/example.com-access.log main; error_log /var/log/nginx/example.com-error.log; error_page 404 /index.php?$request_uri; location ~ \.php$ { try_files $uri =404; fastcgi_split_path_info ^(.+\.php)(/.+)$; # fastcgi_split_path_info ^(/blog)(/.*)$; include /etc/nginx/fastcgi_params; #fastcgi_intercept_errors on; #fastcgi_param PATH_TRANSLATED $document_root$fastcgi_path_info; fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name; fastcgi_pass unix:/var/run/php5-fpm.sock; fastcgi_index /index.php; } location / { auth_basic "private section"; auth_basic_user_file /var/local/example.com/conf/.htpasswd; try_files $uri $uri/ /index.php?$args; } location ~ /\.ht { deny all; } }
这里是我的fastcgi_params：
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 HTTPS $https if_not_empty; 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; # bug workaround : http://trac.nginx.org/nginx/ticket/321 set $path_info $fastcgi_path_info; fastcgi_param PATH_INFO $path_info; # PHP only, required if PHP was built with --enable-force-cgi-redirect fastcgi_param REDIRECT_STATUS 200;
我已经阅读并尝试了许多基于论坛上的变化，但没有任何工作。
事实certificate，通过编辑php.ini已经解决了这个问题：
cgi.fix_pathinfo=0
取而代之
cgi.fix_pathinfo=1
然后重新加载php-fpm守护进程。