Thank you! I got it working.
It seemed to be an issue with using $document_root$fastcgi_script_name as
my SCRIPT_FILENAME. I changed it to: $request_filename, and it works fine
now.
Thanks!
On Thu, Jun 20, 2013 at 11:02 PM, Steve Holdoway wrote:
> fastcgi_param QUERY_STRING$query
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_FILENAME $request_filename;
fastcgi_param
I don't know why, but it is simply not working for me. I tried changing my
SCRIPT_FILENAME to match yours exactly, and I changed my location block to
"location ~ ^/fpm-status$ {}" - as opposed to using "=". Same problems.
I also tried toggling fastcgi_intercept_errors to see if that did anything.
On Thu, 2013-06-20 at 22:31 -0400, Schiz0 wrote:
> Hello list,
>
>
> I use php-fpm via fastcgi to handle my PHP scripts. I have that
> working successfully. PHP-FPM has a feature where it displays a status
> page, as mentioned here:
> http://php.net/manual/en/install.fpm.configuration.php#pm.stat
Hello list,
I use php-fpm via fastcgi to handle my PHP scripts. I have that working
successfully. PHP-FPM has a feature where it displays a status page, as
mentioned here:
http://php.net/manual/en/install.fpm.configuration.php#pm.status-path
I'd like to be able to access this through nginx. I tri
