Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues with fastcgi_params #499

Closed
vincentbernat opened this issue Nov 8, 2014 · 2 comments
Closed

Issues with fastcgi_params #499

vincentbernat opened this issue Nov 8, 2014 · 2 comments

Comments

@vincentbernat
Copy link
Contributor

Hi!

The shipped fastcgi_params file is not generic enough. It would be nice to change SCRIPT_FILENAME to $document_root$fastcgi_script_name for better flexibility. However, this change may be disruptive. This is how the file shipped with nginx is.

Currently, SCRIPT_FILENAME is not correct for many setup and it may not be overridable because the order of the fastcgi_param directives are important. For stuff like php-fpm, the last entry wins, so it is easy to override SCRIPT_FILENAME. However, for fcgiwrap, this is the first one that will win.

vincentbernat added a commit to vincentbernat/puppet-nginx that referenced this issue Nov 8, 2014
This is a risky change for `SCRIPT_FILENAME` but it handles more
situation than fastcgi_params. Upstream still ships the previous
fastcgi_params file.

Fixes: voxpupuli#499
@lesinigo
Copy link

lesinigo commented May 4, 2016

I've been bitten by exactly this issue. Trying to find out why a setup with fcgiwrap did not work, I've found that my SCRIPT_FILENAME (from fastcgi_param) was being ignored in favor of the one included in the file referenced from fastcgi_params. As referenced in #682, the only workaround at the moment is to create and reference an empty file for fastcgi_param.

@wyardley
Copy link
Collaborator

I'm going to close this; please follow #862 to keep track of resolution of this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants