Difference between revisions of "FastCGI"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
| − | One of the main use-cases of FastCGI proxying within [[Nginx]] is for [[PHP]] processing. Unlike Apache, which can handle PHP processing directly with the use of the mod_php module, Nginx must rely on a separate PHP processor to handle PHP requests. Most often, this processing is handled with php-fpm, a PHP processor that has been extensively tested to work with Nginx. | + | One of the main use-cases of FastCGI proxying within [[Nginx]] is for [[PHP]] processing. Unlike Apache, which can handle PHP processing directly with the use of the mod_php module, Nginx must rely on a separate PHP processor to handle PHP requests. Most often, this processing is handled with <code>[[php-fpm]]</code>, a PHP processor that has been extensively tested to work with Nginx. |
Revision as of 11:00, 26 December 2019
One of the main use-cases of FastCGI proxying within Nginx is for PHP processing. Unlike Apache, which can handle PHP processing directly with the use of the mod_php module, Nginx must rely on a separate PHP processor to handle PHP requests. Most often, this processing is handled with php-fpm, a PHP processor that has been extensively tested to work with Nginx.
/etc/nginx/nginx.conf: fastcgi_pass
See also
- Web server: Nginx:
/etc/nginx/nginx.conf,nginx -t, Nginx logs, Nginx change log, PHP,php-fpm, Let's encrypt, Nginx directives, Reverse Proxy, Configure HTTP redirection Nginx, Return,proxy_pass (Reverse proxy),ngx_http_rewrite_module,/etc/nginx/sites-enabled/,error.log,access.log,/nginx status, AIO
Advertising:
