<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <meta http-equiv="Content-type" content="text/html; charset=utf-8" /> <meta http-equiv="Content-Language" content="en-us" /> <meta name="ROBOTS" content="ALL" /> <meta http-equiv="imagetoolbar" content="no" /> <meta name="MSSmartTagsPreventParsing" content="true" /> <meta name="Keywords" content="cherokee web server httpd http" /> <meta name="Description" content="Cherokee is a flexible, very fast, lightweight Web server. It is implemented entirely in C, and has no dependencies beyond a standard C library. It is embeddable and extensible with plug-ins. It supports on-the-fly configuration by reading files or strings, TLS/SSL (via GNUTLS or OpenSSL), virtual hosts, authentication, cache friendly features, PHP, custom error management, and much more." /> <link href="media/css/cherokee_doc.css" rel="stylesheet" type="text/css" media="all" /> </head> <body> <h2 id="_a_href_index_html_index_a_8594_a_href_modules_html_modules_a_8594_a_href_modules_handlers_html_handlers_a"><a href="index.html">Index</a> → <a href="modules.html">Modules</a> → <a href="modules_handlers.html">Handlers</a></h2> <div class="sectionbody"> </div> <h2 id="_handler_fastcgi">Handler: FastCGI</h2> <div class="sectionbody"> <div class="paragraph"><p>The fcgi handler makes queries to <strong>FastCGI</strong> servers, such as PHP, Ruby on Rails or Django in order to get the request response. FastCGI is scalable and language independent enhancement to CGI that provides high performance without limitations of server specific APIs and reduced overhead. It is basically the same thing as CGI but <strong>much faster</strong>.</p></div> <div class="paragraph"><p>This module accepts all the general <a href="modules_handlers_cgi.html">CGI</a> parameters. It needs a balancer to be configured besides that. It is the piece of configuration that points to the handler where to find the FastCGI servers.</p></div> <div class="paragraph"><p>For most of the cases there will be only one FastCGI server though. In that scenario the way to go would be to configure the handler to use a <a href="modules_balancers_round_robin.html">Round Robin</a> balancer and configure a single host or interpreter (it has no performance penalty).</p></div> <h3 id="parameters">Parameters</h3><div style="clear:left"></div> <div class="paragraph"><p>To set up the general gateway options, read about the common parameters shared with the <a href="modules_handlers_cgi.html">Common CGI options</a> handler. All of them apply with the exception of <tt>Check file</tt>, which will only be present if the manager is handling an extension. Be sure to understand what that parameter does. It is <a href="modules_handlers_cgi.html#check_file_warning">explained in detail</a> among the rest of CGI options, and depending of how you are using FastCGI it can make all the difference between succeeding and failing to run your application.</p></div> <div class="paragraph"><p>To set up the FastCGI specifics, read the <a href="modules_balancers.html">Balancers</a> section for general information and the <a href="config_info_sources.html">information sources</a> section for more details.</p></div> <h3 id="examples">Examples</h3><div style="clear:left"></div> <div class="paragraph"><p>Refer to the <a href="cookbook.html">Cookbook</a> if you want specific examples on how to configure this handler. The recipe about <a href="cookbook_php.html">setting up PHP</a> is a good starting point.</p></div> <div class="imageblock"> <div class="content"> <img src="media/images/admin_handler_fastcgi1.png" alt="media/images/admin_handler_fastcgi1.png" /> </div> </div> </div> <div id="footer"> <div id="footer-text"> </div> </div> </body> </html>