Are fastcgi_params case-sensitive

Server NGINX
1

I have spent a few hours trying to debug ‘No input file specified’
errors
until I realized that the script_filename must be specified in upper
case

ie,

fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;

rather than

fastcgi_param script_filename $document_root$fastcgi_script_name;

Has it always been this way?

–
Frank C.

=======================
http://devblog.brahmancreations.com

2

On Tue, 02 Nov 2010 18:17:54 -0400, Frank C. wrote:

I have spent a few hours trying to debug ‘No input file specified’
errors
until I realized that the script_filename must be specified in upper
case
Has it always been this way?

On the one hand, it appears to be a bug. On the other, I don’t think
it’s a bug in nginx. The FastCGI is just receiving the variables over
the socket, including SCRIPT_FILENAME. It would therefore be a bug in
the program receiving from the CGI side (I’m guessing PHP?). By the
way, SCRIPT_FILENAME is not a standard CGI meta-variable.

4.1. Request Meta-Variables

Meta-variables contain data about the request passed from the server
to the script, and are accessed by the script in a system-defined
manner. Meta-variables are identified by case-insensitive names[.]

helen

Posted at Nginx Forum:

3

Hello!

On Tue, Nov 02, 2010 at 10:17:54PM +0000, Frank C. wrote:

Has it always been this way?

nginx doesn’t care what you wrote, it just passes key-value pairs
you specified to your fastcgi application (backend).

Maxim D.

4

On 2 November 2010 22:17, Frank C. [email protected] wrote:

Has it always been this way?

–
Frank C.

=======================
http://devblog.brahmancreations.com

From the responses I suspect that the php-cgi is looking for arrays with
case-sensitive keys.

I will check when time allows.

Thanks

–
Frank C.

=======================
http://devblog.brahmancreations.com

5

Shouldn’t that be Os-dependant?
Has anyone tested on Windows?

–
Mars 2 Stay!

/etc