-
-
Notifications
You must be signed in to change notification settings - Fork 881
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
Comments
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
|
I've been bitten by exactly this issue. Trying to find out why a setup with |
|
I'm going to close this; please follow #862 to keep track of resolution of this. |
Hi!
The shipped
fastcgi_paramsfile is not generic enough. It would be nice to changeSCRIPT_FILENAMEto$document_root$fastcgi_script_namefor better flexibility. However, this change may be disruptive. This is how the file shipped with nginx is.Currently,
SCRIPT_FILENAMEis not correct for many setup and it may not be overridable because the order of thefastcgi_paramdirectives are important. For stuff likephp-fpm, the last entry wins, so it is easy to overrideSCRIPT_FILENAME. However, forfcgiwrap, this is the first one that will win.The text was updated successfully, but these errors were encountered: