Skip to content

Nginx fastcfi_params item deprecation  #28

@diraol

Description

@diraol

Since nginx 1.6.1-2 it seems that "fastcgi_params" has no more SCRIPT_FILENAME parameter.
https://github.com/nicolargo/varnish-nginx-wordpress/blob/master/nginx/global/php-fpm.conf#L12

I'm not sure if there is change that has to be made.

The nginx update log:

nginx-common (1.6.1-2) unstable; urgency=medium

  As of nginx-1.6.1-2 we have synced all configuration files with upstream and
  we plan to keep them in sync from now on.

  Unfortunately that might break existing configuration for some users. Please
  check the matrix below for more information:

  File            Changes
  -----------------------
  koi-win         whitespace
  koi-utf         whitespace
  mime-types      whitespace, changed js/rss mime type,
                  minor other changes & additions
  scgi_params     whitespace, added HTTPS
  uwsgi_params    whitespace, added HTTPS, removed UWSGI_SCHEME
  fastcgi_params  whitespace, removed SCRIPT_FILENAME
  fastcgi.conf    new upstream configuration file

  Fastcgi configuration issues
  ============================

  nginx shipped a modified `fastcgi_params`, which declared `SCRIPT_FILENAME`
  fastcgi_param. This line has now been removed. From now on we are also
  shipping fastcgi.conf from the upstream repository, which includes a sane
  `SCRIPT_FILENAME` parameter value.

  So, if you are using fastcgi_params, you can try switching to fastcgi.conf
  or manually set the relevant params.

  You might also want to read the documentation section before proceeding.

  http://nginx.org/en/docs/http/ngx_http_fastcgi_module.html
  section: $fastcgi_script_name variable.

 -- Christos Trochalakis <[email protected]>  Thu, 28 Aug 2014 14:23:42 +0300

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions