Open trwnh opened 5 years ago
https://blog.martinfjordvald.com/2013/04/nginx-config-history-fastcgi_params-versus-fastcgi-conf/
i can't seem to find any downsides to just using $request_filename 100% of the time over $document_root$fastcgi_script_name for SCRIPT_FILENAME. $request_filename just seems to be less likely to break -- it takes alias into account,
$request_filename
$document_root$fastcgi_script_name
SCRIPT_FILENAME
Also https://www.nginx.com/resources/wiki/start/topics/tutorials/config_pitfalls/#use-request-filename-for-script-filename
And if you use $request_filename, you should set index using index directive, fastcgi_index will not work.
which seems to be the only pitfall, per se.
seems to work fine in testing. maybe make the switch
actually maybe snippets/phpsub.conf can just replace snippets/php.conf? since that's basically what the change boils down to
https://blog.martinfjordvald.com/2013/04/nginx-config-history-fastcgi_params-versus-fastcgi-conf/
i can't seem to find any downsides to just using
$request_filename
100% of the time over$document_root$fastcgi_script_name
forSCRIPT_FILENAME
.$request_filename
just seems to be less likely to break -- it takes alias into account,Also https://www.nginx.com/resources/wiki/start/topics/tutorials/config_pitfalls/#use-request-filename-for-script-filename
which seems to be the only pitfall, per se.