Bug #69625 [Opn]: php-fpm return http 200 response on nginx without SCRIPT_FILENAME

Edit report at https://bugs.php.net/bug.php?id=69625&edit=1 ID: 69625 User updated by: cfc4n at cnxct dot com Reported by: cfc4n at cnxct dot com -Summary: http 200 response on nginx without SCRIPT_FILE +Summary: php-fpm return http 200 response on nginx without SCRIPT_FILENAME Status: Open Type: Bug Package: FPM related Operating System: linux PHP Version: 5.6.9RC1 Block user comment: N Private report: N New Comment: edit summary Previous Comments: ------------------------------------------------------------------------ [2015-05-12 05:13:42] cfc4n at cnxct dot com Description: ------------ In nginx config.conf file, configure info without fastcgi_param SCRIPT_FILENAME, Any PHP files are returned blank response and http 200 status. Because init_request_info function set default http response status 200, request_method is null in fpm_main.c near line 985. And if SCRIPT_FILENAME was not set in CGI protocol, SG(request_info).request_method \ SG(sapi_headers).http_response_code will not be reset . The program will terminate at "if (!SG(request_info).request_method)" near line 1838 in fpm_main.c , But http response status was 200 ,In fact it's a bug , The http response will be 404 , There is comment in fpm_main.c near line 1846 "/* If path_translated is NULL, terminate here with a 404 */" . So, I think the code of SG(request_info).path_translated determine should be placed in front of SG(request_info).request_method . Move line 1846-1855 into line 1835 . more detail : http://www.cnxct.com/php-return-empty-result-on-nginx-without-script_filename/ Expected result: ---------------- return http response 404 and write php_error log whiteout SCRIPT_FILENAME ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=69625&edit=1