Opened 9 years ago
Closed 9 years ago
#50019 closed defect (fixed)
nginx: use fastcgi.conf instead of fastcgi_params
Reported by: | ryandesign (Ryan Carsten Schmidt) | Owned by: | neverpanic (Clemens Lang) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.3.4 |
Keywords: | Cc: | Schamschula (Marius Schamschula) | |
Port: | nginx |
Description
The nginx portfile says:
set nginx_all_confs {fastcgi.conf fastcgi_params mime.types nginx.conf scgi_params uwsgi_params} set auto_activate_confs {nginx.conf mime.types fastcgi_params}
Why is the old fastcgi_params in the auto-activated confs but its modern replacement fastcgi.conf isn't? According to this blog post from 2013, people should be using fastcgi.conf these days, not fastcgi_params.
If you make this change, you also need to patch nginx.conf.default to reference fastcgi.conf instead of fastcgi_params.
Change History (1)
comment:1 Changed 9 years ago by neverpanic (Clemens Lang)
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
r143534.