+ fastcgi_param REQUEST_METHOD $request_method;
This is a bug in php-fpm 0.5.9-rc2, will be fixed in next release.
--
Andrei Nigmatulin
GPG PUB KEY 6449830D
Now I lay me down to sleep(3)
Pray the OS my core to keep
If I die before I wake
Pray the Disk my core to take
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
and not have to set the SCRIPT_FILENAME for each server/location block
with the hardcoded docroot location manually :)
No need to wait ;-)
Have you tried adding "fastcgi_param REQUEST_METHOD $request_method;" ?
> On 18 août, 04:48, mike <mike...@gmail.com> wrote:
> > Also you can define this globally
> >
> > fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
> >
> > and not have to set the SCRIPT_FILENAME for each server/location block
> > with the hardcoded docroot location manually :)
>
> Same result with $document_root or no fastcgi_param.
--
>> Also you can define this globally
>>
>> fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
>>
>> and not have to set the SCRIPT_FILENAME for each server/location block
>> with the hardcoded docroot location manually :)
> Same result with $document_root or no fastcgi_param.
It won't change the behavior, it will just make configuration cleaner
and easier.
This is expected behavour.
The segmentation fault occured when fastcgi request have been formed without
REQUEST_METHOD parameter.
This is what you've got when you placed *only one* directive "fastcgi_param
SCRIPT_FILENAME" on location level.
Now you have moved the only fastcgi_param directive from location level to
http.
And from now *all* fastcgi_param directives from fastcgi.conf file are
inherited on the location level.
> Now you have moved the only fastcgi_param directive from location level to
> http.
>
> And from now *all* fastcgi_param directives from fastcgi.conf file are
> inherited on the location level.
This is the best, and can even include the SCRIPT_FILENAME. This is my
global fastcgi settings. I only need to change fastcgi_pass as needed.
Why create more configuration hassle right? :)
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 $document_root$fastcgi_script_name;
fastcgi_param SCRIPT_NAME $fastcgi_script_name;
fastcgi_param REQUEST_URI $request_uri;
fastcgi_param DOCUMENT_URI $document_uri;
fastcgi_param DOCUMENT_ROOT $document_root;
fastcgi_param SERVER_PROTOCOL $server_protocol;
fastcgi_param GATEWAY_INTERFACE CGI/1.1;
fastcgi_param SERVER_SOFTWARE nginx/$nginx_version;
fastcgi_param REMOTE_ADDR $remote_addr;
fastcgi_param REMOTE_PORT $remote_port;
fastcgi_param SERVER_ADDR $server_addr;
fastcgi_param SERVER_PORT $server_port;
fastcgi_param SERVER_NAME $http_host;
fastcgi_param REDIRECT_STATUS 200;
fastcgi_ignore_client_abort on;
Seems like so many people are reading nginx HOWTOs and it shows them
to define SCRIPT_FILENAME manually...