5 messages in ru.sysoev.nginxRe: [nginx-announce] nginx-0.8.30| From | Sent On | Attachments |
|---|---|---|
| Michael Shadle | Dec 15, 2009 2:36 pm | |
| merlin corey | Dec 15, 2009 5:48 pm | |
| Michael Shadle | Dec 15, 2009 6:36 pm | |
| merlin corey | Dec 17, 2009 12:31 pm | |
| Michael Shadle | Dec 17, 2009 2:04 pm |
| Subject: | Re: [nginx-announce] nginx-0.8.30 | |
|---|---|---|
| From: | merlin corey (merl...@dc949.org) | |
| Date: | Dec 15, 2009 5:48:29 pm | |
| List: | ru.sysoev.nginx | |
On Tue, Dec 15, 2009 at 2:36 PM, Michael Shadle <mike...@gmail.com> wrote:
On Tue, Dec 15, 2009 at 7:21 AM, Igor Sysoev <ig...@sysoev.ru> wrote:
*) Feature: the conf/fastcgi.conf for simple FastCGI configurations.
What's the reasoning for this? Right now it's identical to fastcgi_params besides for no
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
Which I think should be kept as default, as it's probably the most standard way people use it, and they can overrfastide it manually in the server config if they choose to host PHP in some wacky place...
_______________________________________________ nginx mailing list ngi...@nginx.org http://nginx.org/mailman/listinfo/nginx
Because it's not just for PHP. Most other people don't NEED SCRIPT_FILENAME (or at least in my experience) and I think it's a good thing to not needlessly pass along a value made of variables that must be resolved.
That said I'll be including fastcgi.conf instead of fastcgi_params on my PHP boxes now :).
-- Merlin
_______________________________________________ nginx mailing list ngi...@nginx.org http://nginx.org/mailman/listinfo/nginx