phpinfo() changes the status code of nginx response in a weird way

Question

I have a php code that should always end up being "http 500 code" as I have a call to undefined func status_code("OK");

code:

<?
# phpinfo();
echo 'error_log = ' . ini_get('error_log') . "\n";
status_code("OK");
echo "OK";
?>

With example above:

➜ curl -I http://localhost:8080/kkk
HTTP/1.1 500 Internal Server Error
Server: nginx/1.20.1
Date: Sat, 29 Oct 2022 18:48:25 GMT
Content-Type: text/html
Content-Length: 5597
Connection: close
ETag: "635c9b20-15dd"

and in stdout output:

2022/10/29 18:50:32 [error] 29#29: *30 FastCGI sent in stderr: "PHP message: PHP Fatal error:  Uncaught Error: Call to undefined function status_code() in /legacy/app/index.php:4
Stack trace:
#0 {main}
  thrown in /legacy/app/index.php on line 4" while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "HEAD /kkk HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "localhost:8080"
172.17.0.1 - - [29/Oct/2022:18:50:32 +0000] 500 "HEAD /kkk HTTP/1.1" 0 "-" "curl/7.82.0" "-"

However if I uncomment #phpinfo(); line I get 200 OK:

➜ curl -I http://localhost:8080/kkk
HTTP/1.1 200 OK
Server: nginx/1.20.1
Date: Sat, 29 Oct 2022 18:52:25 GMT
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
X-Powered-By: PHP/7.1.33

and in stdout:

172.17.0.1 - - [29/Oct/2022:18:52:25 +0000] 200 "HEAD /kkk HTTP/1.1" 0 "-" "curl/7.82.0" "-"

I'm running nginx and it has the following configuration:

location ~ \.php$ {
    root /legacy/app;
    fastcgi_pass 127.0.0.1:9000;
    fastcgi_read_timeout 10s;
    fastcgi_split_path_info ^(.+\.php)(/.+)$;
    fastcgi_index index.php;
    fastcgi_intercept_errors on;
    fastcgi_buffer_size 16k;
    fastcgi_buffers 4 16k;
}

location / {
    # make sure you have a custom html page placed in app folder
    # i.e. /legacy/app/app/50x.html
    try_files _ /index.php?$query_string;

}

status code as well as headers must be set before any output is produced — Paolo
– Paolo, Commented Oct 29, 2022 at 20:54

Chris · Accepted Answer · 2022-10-29 21:11:05Z

2

You should use builtin function http_response_code() to change the response code.

But, as well as header(), you must call http_response_code() before phpinfo() because any output produced in your response will imply header with 200 status code that you can't change anymore. (see Call header() after output is sent)

Just tested with Apache (I don't think it makes a difference).

This works (display php info with 500 status code):

http_response_code(500);
phpinfo();

This doesn't works (display php info with 200 status code):

phpinfo();
http_response_code(500);

This doesn't works (display php info with 200 status code):

phpinfo();
undefined_function(); // generates an error in error.log

edited Oct 29, 2022 at 21:11

answered Oct 29, 2022 at 20:49

Chris

8,65710 gold badges36 silver badges51 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

DmitrySemenov Over a year ago

thanks @Chris, it's interesting I have expected that there is a call to undefined_function(); - php fastcgi reports back as error and waits for all data from the index.php before starting the response to nginx.

Collectives™ on Stack Overflow

phpinfo() changes the status code of nginx response in a weird way

1 Answer 1

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related