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
Me too, I am looking forward for this extension for 1.4.x
current branch which is not working for recent versions:
https://github.com/zealot83/ngx_http_extended_status_module
it would be greatly appreciated if one of geeks to do it
Regards
On Th
On Thu, Jun 20, 2013 at 2:00 AM, Maxim Dounin wrote:
> Hello!
>
> On Wed, Jun 19, 2013 at 11:06:19AM -0700, Mark Moseley wrote:
>
> > TL;DR:
> > Any nginx setting to say 'if a vhost's ssl settings are broken, skip it
> and
> > don't fail to start' ?
> >
> > I've certainly RTFM'd this and peered a
Thanks for the feed back Reinis
I agree that the extended module (
http://wiki.nginx.org/Extended_status_module) is doing things right but it
is no more supported with nginx 1.3 or later and i think that patching
nginx core is not a good thing.
This way, the php-fpm status is a good alternative b
Ok, thanks !!! ;-)
2013/4/4 Reinis Rozitis
>
>> location / {
>> rewrite^/(.*)/(.*)$ /$1/index.php?url=$2;
>>}
>>
>
> I would suggest to use try_files:
>
> location / {
>try_files $uri $uri/ /index.php?url=$uri&$args;
> }
>
>
> Personally instead of pasing the uri
On 6/18/2013 5:55 PM, Francis Daly wrote:
> On Tue, Jun 18, 2013 at 03:22:04PM -0400, Ben Johnson wrote:
>
> Hi there,
Hi, Francis! I really appreciate your help and your time. Thanks for
replying in such detail.
>> The try_files directive is brilliant. The only problem I'm having is
>> that I
But according to me and my team (and many other admins as far as i can
see), something important is really missing to push it in production. This
is the "extended status" (i mean something like the apache server-status)
What are the "important" things in the "extended status" that you miss for
Hi Nginx Team,
I used nginx for a few years and until now, i used to deploy it for static
content. Right now, i 'd like to deploy it for dynamic content using
php-fpm. It works fine and performances are good.
But according to me and my team (and many other admins as far as i can
see), something i
Hello!
On Wed, Jun 19, 2013 at 11:06:19AM -0700, Mark Moseley wrote:
> TL;DR:
> Any nginx setting to say 'if a vhost's ssl settings are broken, skip it and
> don't fail to start' ?
>
> I've certainly RTFM'd this and peered at the source, but I figured I might
> as well throw it out there, in cas
13 matches
Mail list logo
