无论NGINX状态码如何,PHP-FPM始终返回200

时间:2018-09-17 20:39:05

标签: php nginx http-status

我使用NGINX和PHP-FPM进行了基于PHP的错误页面配置。但是,当我请求example.com/nothing(不存在的页面)时,PHP-FPM返回200状态代码,而不是NGINX返回的正确404状态代码。其他错误也会发生这种情况(例如,当NGINX的状态为403时,example.com/assets使用PHP-FPM返回200)。本质上,我希望PHP-FPM所做的是镜像NGINX显示的状态代码(用NGINX显示的状态代码覆盖200状态代码),因此我的错误页面显示了正确的信息。我知道您可以在使用http_response_code();时通过指定状态代码来更改状态代码,但是我希望服务器在不对正确的状态代码进行硬编码的情况下执行此操作。

错误页面:<? echo http_response_code(); ?>

NGINX错误页面配置:

set $errorDocs "/var/www/GLOBAL_RESOURCES/error";
recursive_error_pages on;
location ^~ $errorDocs {
  internal;
  alias $errorDocs;
}
#Resolve error asset location 404s
location /errorAssets {
  root $errorDocs;
}
error_page 404 /404.php;
location = /404.php {
  root $errorDocs;
  include /etc/nginx/xenon-conf/headers/fpm-params.conf;
}

PHP-FPM设置:

include /etc/nginx/fastcgi_params;
include /etc/nginx/fastcgi.conf;
fastcgi_intercept_errors on;
proxy_intercept_errors on;
try_files $uri =404; 
fastcgi_split_path_info ^(.+\.php)(/.+)$;
fastcgi_pass  unix:/var/run/php-fpm/www.sock;
fastcgi_index index.php;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;

快速CGI配置:

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  REQUEST_SCHEME     $scheme;
fastcgi_param  HTTPS              $https if_not_empty;

fastcgi_param  GATEWAY_INTERFACE  CGI/1.1;
fastcgi_param  SERVER_SOFTWARE    nginx;

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;

# PHP only, required if PHP was built with --enable-force-cgi-redirect
#fastcgi_param  REDIRECT_STATUS    200; 

网站配置:

server {
  listen 80;
  server_name example.com www.example.com;
  access_log /var/log/nginx/example.com.access.log;
  include /etc/nginx/xenon-conf/headers/php-fpm-enable.conf;
  include /etc/nginx/xenon-conf/headers/master-failover.conf;

  set $webRoot "/var/www/example.com";
  root $webRoot;
}

NGINX配置:

user nginx;
worker_processes auto;
error_log /var/log/nginx/error.log;
pid /run/nginx.pid;

# Load dynamic modules. See /usr/share/doc/nginx/README.dynamic.
include /usr/share/nginx/modules/*.conf;

events {
  worker_connections 1024;
}

http {
  log_format  main  '$remote_addr - $remote_user [$time_local] "$request" '
                  '$status $body_bytes_sent "$http_referer" '
                  '"$http_user_agent" "$http_x_forwarded_for"';

  access_log  /var/log/nginx/access.log  main;

  sendfile            on;
  tcp_nopush          on;
  tcp_nodelay         on;
  keepalive_timeout   65;
  types_hash_max_size 4096;

  include             /etc/nginx/mime.types;
  default_type        application/octet-stream;

  # Load modular configuration files from the /etc/nginx/conf.d directory.
  # See http://nginx.org/en/docs/ngx_core_module.html#include
  # for more information.
  include /etc/nginx/conf.d/*.conf;

  ### CUSTOM HTTP SERVER MASS IMPORTS ###
  include /etc/nginx/xenon-conf/websites/*.web;
  include /etc/nginx/xenon-conf/mapping/*.map;
}

### CUSTOM GENERIC STREAM MASS IMPORTS ###
include /etc/nginx/xenon-conf/stream/*.conf;

谢谢!

2 个答案:

答案 0 :(得分:3)

如果nginx正在检测来自FastCGI上游的输出,它将 即使上游(在这种情况下, php-fpm)触发了错误。

在PHP-FPM池中禁用display_errors可解决此问题。

php_admin_value[display_errors] = Off阻止PHP脚本  在屏幕上显示错误输出,进而导致nginx  正确引发HTTP 500内部服务器错误。

$  curl -i localhost:8080/test.php?time=`date +%s` HTTP/1.1 500
Internal Server Error Server: nginx ...

(未显示任何输出,响应为空)您仍然可以将所有错误记录到  文件,带有error_log指令。

php_admin_value[error_log] = /var/log/php-fpm/error.log
php_admin_flag[log_errors] = on

-Source

为了将HTTP状态代码从Nginx传递到PHP-FPM,还需要在PHP处理位置中放置以下内容:

fastcgi_intercept_errors on;

根据manual,此指令:

  

确定应将FastCGI服务器响应的代码大于或等于300传递给客户端,还是应将其拦截并重定向到nginx以使用error_page指令进行处理。

答案 1 :(得分:0)

这里的主要问题是默认情况下 php-fpm 不会返回状态代码 nginx 发生异常并启用 display_errors 时。

TLDR

使用一些全局错误处理程序来设置错误状态代码,如下所示:

http_response_code(500);

这将从 php-fpm 传递到 nginx 并附加到 nginx 响应。

如何测试这种行为

创建 index.php 文件:

<?php
// report all errors
error_reporting(E_ALL);

// do not display errors
ini_set("display_errors", 0);

// set http response code
// http_response_code(500);

// throw exception
throw new \Exception('TEST UNHANDLED EXCEPTION STATUS CODE');

default.conf创建nginx

server {
    listen       80;
    server_name  localhost;

    location / {
        root   /var/www/html;
        index  index.php index.html index.htm;
    }

    # pass the PHP scripts to FastCGI server listening on php:9000
    location ~ \.php$ {
        root           /var/www/html;
        fastcgi_pass   php:9000;
        fastcgi_index  index.php;
        fastcgi_param  SCRIPT_FILENAME  /var/www/html/$fastcgi_script_name;
        include        fastcgi_params;
    }
}

创建docker-compose.yml

version: "3.5"

services:
  php:
    image: php:fpm
    volumes:
      - ./index.php:/var/www/html/index.php

  nginx:
    depends_on:
      - php
    image: nginx:latest
    volumes:
      - ./index.php:/var/www/html/index.php
      - ./default.conf:/etc/nginx/conf.d/default.conf

运行项目

docker-compose up -d

php 容器内安装用于测试 php-fpm 的其他工具

要测试来自 php-fpm 的直接响应,我们需要安装 cgi-fcgi 二进制文件

docker-compose exec php bash -c 'apt update && apt install -y libfcgi0ldbl'

在禁用 display_errors 的情况下测试响应

  1. php 容器内,直接向 php-fpm 发出请求
    SCRIPT_NAME=/var/www/html/index.php SCRIPT_FILENAME=/var/www/html/index.php REQUEST_METHOD=GET cgi-fcgi -bind -connect localhost:9000
    
  2. 响应包含由 nginx 正确处理的状态代码 500:
    Status: 500 Internal Server Error
    X-Powered-By: PHP/8.0.2
    Content-type: text/html; charset=UTF-8
    
    
  3. 测试来自 nginx 的响应
    docker-compose exec nginx curl -i localhost
    
    回复:
    HTTP/1.1 500 Internal Server Error
    Server: nginx/1.19.6
    Date: Mon, 22 Feb 2021 11:45:56 GMT
    Content-Type: text/html; charset=UTF-8
    Transfer-Encoding: chunked
    Connection: keep-alive
    X-Powered-By: PHP/8.0.2
    
    
    

php-fpm 响应包含状态代码 500 并且没有正文。 Nginx 使用此代码作为响应。

在启用 display_errors 的情况下测试响应

  1. 让我们在 display_errors 中启用 index.php
    // do not display errors
    ini_set("display_errors", 1);
    
  2. php 容器内,直接向 php-fpm 发出请求
    SCRIPT_NAME=/var/www/html/index.php SCRIPT_FILENAME=/var/www/html/index.php REQUEST_METHOD=GET cgi-fcgi -bind -connect localhost:9000
    
    回复:
    X-Powered-By: PHP/8.0.2
    Content-type: text/html; charset=UTF-8
    
    <br />
    <b>Fatal error</b>:  Uncaught Exception: TEST UNHANDLED EXCEPTION STATUS CODE in /var/www/html/index.php:12
    Stack trace:
    #0 {main}
      thrown in <b>/var/www/html/index.php</b> on line <b>12</b><br />
    
  3. 测试来自 nginx 的响应
    docker-compose exec nginx curl -i localhost
    
    回复
    HTTP/1.1 200 OK
    Server: nginx/1.19.6
    Date: Mon, 22 Feb 2021 11:47:29 GMT
    Content-Type: text/html; charset=UTF-8
    Transfer-Encoding: chunked
    Connection: keep-alive
    X-Powered-By: PHP/8.0.2
    
    <br />
    <b>Fatal error</b>:  Uncaught Exception: TEST UNHANDLED EXCEPTION STATUS CODE in /var/www/html/index.php:12
    Stack trace:
    #0 {main}
      thrown in <b>/var/www/html/index.php</b> on line <b>12</b><br />
    
    

php-fpm 响应缺少状态代码 500 但有正文。 Nginx 将此视为正常响应 状态为 200。

在启用 display_errors 且标头明确设置为 500 的情况下测试响应

  1. 让我们在 display_errors 开启的情况下明确设置响应状态代码。

    // set http response code
    http_response_code(500);
    
  2. 测试 php-fpm 响应:

    SCRIPT_NAME=/var/www/html/index.php SCRIPT_FILENAME=/var/www/html/index.php REQUEST_METHOD=GET cgi-fcgi -bind -connect localhost:9000
    

    回复:

    Status: 500 Internal Server Error
    X-Powered-By: PHP/8.0.2
    Content-type: text/html; charset=UTF-8
    
    <br />
    <b>Fatal error</b>:  Uncaught Exception: TEST UNHANDLED EXCEPTION STATUS CODE in /var/www/html/index.php:12
    Stack trace:
    #0 {main}
      thrown in <b>/var/www/html/index.php</b> on line <b>12</b><br />
    
  3. 测试 Nginx 响应

    docker-compose exec nginx curl -i localhost
    

    回复

    HTTP/1.1 500 Internal Server Error
    Server: nginx/1.19.6
    Date: Mon, 22 Feb 2021 11:52:38 GMT
    Content-Type: text/html; charset=UTF-8
    Transfer-Encoding: chunked
    Connection: keep-alive
    X-Powered-By: PHP/8.0.2
    
    <br />
    <b>Fatal error</b>:  Uncaught Exception: TEST UNHANDLED EXCEPTION STATUS CODE in /var/www/html/index.php:12
    Stack trace:
    #0 {main}
      thrown in <b>/var/www/html/index.php</b> on line <b>12</b><br />
    

php-fpm 响应具有状态代码 500 和正文。 Nginx 使用来自 php-fpm 的正文和状态代码。

如何修复

我能想到的一个可能的解决方法是全局错误处理程序,它捕获每个未处理的错误并 明确设置正确的错误状态代码。