Fix FPM tester default env vars change

This broke cloexec test

Fix GH-13563: Setting bool values via env in FPM config fails

Closes GH-13786

Fix GH-11086: FPM: config test runs twice in daemonised mode

The previous check for STDERR did not work so this fixes it.

Closes GH-13357

Add FPM tester logs printing for all errors

Closes GH-12902

Separate setting of SO_KEEPALIVE in FPM tests

Closes GH-12640

Fix bug #76922: FastCGI terminates conn after FCGI_GET_VALUES

Closes GH-12387

Fix GH-12232: FPM: segfault dynamically loading extension without opcache

Also fixes incorrect assertion in ini init that php_dl is always
temporary.

Closes GH-12277

Fix GH-12077: Check lsof functionality in socket on close test

Closes GH-12084

FPM tester FastCGI client transport (#11764)

This improves FastCGI client by separating transport functions and adding support for more low level socket transport that is useful for debuggin

FPM tester FastCGI client transport (#11764)

This improves FastCGI client by separating transport functions and adding support for more low level socket transport that is useful for debugging in some cases.

In addition to that it introduces an option for delaying of fcgi request writing.

show more ...

Set CLOEXEC on listened/accepted sockets in the FPM children

Closes GH-11708

Co-authored-by: Jakub Zelenka <bukka@php.net>

Warn when fpm socket was not registered on the expected path

This might happen if the UDS length limit is exceeded.

Co-authored-by: Jakub Zelenka <bukka@php.net>

Closes GH-

Warn when fpm socket was not registered on the expected path

This might happen if the UDS length limit is exceeded.

Co-authored-by: Jakub Zelenka <bukka@php.net>

Closes GH-11066

show more ...

When running FPM tests, pass -n option to php-fpm

"make test" was failing for me, because I was running it prior to
install, and there was an old installed version which was incompatible

When running FPM tests, pass -n option to php-fpm

"make test" was failing for me, because I was running it prior to
install, and there was an old installed version which was incompatible.
The FPM tests were using the installed php.ini which referenced
installed dynamically linked extensions.

So, pass -n to php-fpm.

FPM\Tester::start() has $extensions, $iniEntries and
TEST_FPM_EXTENSION_DIR but they are not actually set by anything. Rather
than rely on the installed php.ini to be correct, it seems safer to pass
-n, and any tests that need specific config can pass $iniEntries.

Closes GH-11373

show more ...

Fix bug #64539: FPM status - query_string not properly JSON encoded

Closes GH-11050

Fix FPM tester $scriptName logic

Add extra option to FPM tester for handling script filename

Introduce max_multipart_body_parts INI

This fixes GHSA-54hq-v5wp-fqgv DOS vulnerabality by limitting number of
parsed multipart body parts as currently all parts were always parsed.

Fix bug #68591: Configuration test does not perform UID lookups

Addition check in fpm config test to verify existence of user, group,
listen.owner and listen.group.

Closes GH-10

Fix bug #68591: Configuration test does not perform UID lookups

Addition check in fpm config test to verify existence of user, group,
listen.owner and listen.group.

Closes GH-10165

show more ...

Fix bug #80669: FPM numeric user fails to set groups

Fix bug #68207: Setting fastcgi.error_header can result in a WARNING

Introduce TEST_FPM_EXTENSION_DIR for FPM tests with shared extensions

Fix GH-9754: SaltStack hangs when running php-fpm 8.1.11

SaltStack uses Python subprocess and redirects stderr to stdout which is
then piped to the returned output. If php-fpm starts in

Fix GH-9754: SaltStack hangs when running php-fpm 8.1.11

SaltStack uses Python subprocess and redirects stderr to stdout which is
then piped to the returned output. If php-fpm starts in daemonized mode,
it should close stderr. However a fix introduced in GH-8913 keeps stderr
around so it can be later restored. That causes the issue reported in
GH-9754. The solution is to keep stderr around only when php-fpm runs in
foreground as the issue is most likely visible only there. Basically
there is no need to restore stderr when php-fpm is daemonized.

show more ...

Rework FPM tests logging for better debugging

Fix FPM tester conflict

Fix bug #77780: "Headers already sent" when previous connection was aborted

This change primarily splits SAPI deactivation to module and destroy
parts. The reason is that currently some

Fix bug #77780: "Headers already sent" when previous connection was aborted

This change primarily splits SAPI deactivation to module and destroy
parts. The reason is that currently some SAPIs might bail out
on deactivation. One of those SAPI is PHP-FPM that can bail out on
request end if for example the connection is closed by the client
(web sever). The problem is that in such case the resources are not
freed and some values reset. The most visible impact can have not
resetting the PG(headers_sent) which can cause erorrs in the next
request. One such issue is described in #77780 bug which this fixes
and is also cover by a test in this commit. It seems reasonable
to separate deactivation and destroying of the resource which means
that the bail out will not impact it.

show more ...

Fix GH-8885: access.log with stderr writes logs to error_log after reload

This fix allows restoring the the original stderr so the logs are
correctly written.