We have been evaluating litespeedhttpd product with a _trail_ license and we found an issue we have been struggling on for 2 days now. We will greatly
appreciate your thoughts on it.

When the PHP extensions are set to be processed by the LSAPI App each
PHP process is executed with the owner of the docroot folder which is
exactly what we expect. This clones the "suexec" like behavior in apache.

However when we switch PHP extensions to be processed by the FastCGI
handler all PHP processes are executed with the user under which
litespeed is running on (nobody in our case).

We did a lot of research and all articles we read says that
fastcgi processed php scripts CAN be executed in "suexec" like mode. We tried all possible configurations. None of these helped.

When we strace/ltrace the litespeed processes it seems that when we are using fastcgi the fastcgi configured php is never executed via lscgid (the
daemon which handles the suexec like behavior in this product we
suppose). However when we switch to lsapi phps we can see that the
requests are passed to lscgid first and handled by the phps itself after
the lscgid setuid to the owner of the docroot folder.

We turned on the debug mode of the litespeed web server. Below you can
find the output from the processing a sample PHP script via lsapi php:

As you can see above none of the lines are showing "sexec" like behavior
for the php fastcgi processed scripts. Nothing here shows suphp/suexec like behavior which is observed when we running the phps via the lsapi.

We were wondering is this some kind of limitation imposed by the trial
license key we are using, something like a bug in the litespeedhttpd product or just a misconfiguration on our end.