passenger 3.0.21 → 3.9.1.beta

data/doc/Users guide Apache.txt

@@ -1,52 +1,26 @@
-Phusion Passenger users guide
-=============================
+Phusion Passenger users guide, Apache version
+=============================================
 
 image:images/phusion_banner.png[link="http://www.phusion.nl/"]
 
-Phusion Passenger is an Apache module, which makes deploying Ruby and Ruby on
-Rails applications on Apache a breeze. It follows the usual Ruby on Rails
-conventions, such as "Don't-Repeat-Yourself" and ease of setup, while at the
-same time providing enough flexibility.
+Phusion Passenger is an application server which can directly integrate into Apache. It is designed to be easy to use, fast, stable and reliable and is used by link:http://trends.builtwith.com/Web-Server/Phusion-Passenger[hundreds of thousands of websites] all over the world.
+
+Phusion Passenger is a so-called polyglot application server because it supports applications written in multiple programming languages. At this time, Ruby and Python are supported.
 
 This users guide will teach you:
 
 - How to install Phusion Passenger.
 - How to configure Phusion Passenger.
-- How to deploy a Ruby on Rails application.
-- How to deploy a link:http://rack.rubyforge.org/[Rack]-based Ruby application.
+- How to deploy Ruby and Python applications.
 - How to solve common problems.
 
 This guide assumes that the reader is somewhat familiar with Apache and with
-using the commandline.
+using the command line.
 
 
 == Support information ==
 
-=== Supported operating systems ===
-
-Phusion Passenger works on any POSIX-compliant operating system. In other
-words: practically any operating system on earth, except Microsoft Windows.
-
-Phusion Passenger is confirmed on a large number of operating systems and Linux
-distributions, including, but not limited to, Ubuntu, Debian, CentOS/Fedora/RHEL,
-Gentoo, Mac OS X, FreeBSD and Solaris. Both 32-bit and 64-bit platforms are supported.
-
-The only POSIX-compliant operating system on which Phusion Passenger for Apache is
-known not to work at this time, is OpenBSD. Please use Phusion Passenger for Nginx
-instead.
-
-Please
-link:http://code.google.com/p/phusion-passenger/issues/list[report a bug]
-or
-link:http://groups.google.com/group/phusion-passenger[join our discussion forum]
-if it doesn't work on your POSIX-compliant operating system.
-
-=== Where to get support ===
-
-* link:http://code.google.com/p/phusion-passenger/issues/list[Issue tracker] - report
-  bugs here.
-* link:http://groups.google.com/group/phusion-passenger[Discussion forum] - post a
-  message here if you're experiencing problems.
+include::users_guide_snippets/support_information.txt[]
 
 
 == Installing, upgrading and uninstalling Phusion Passenger ==
@@ -58,8 +32,8 @@ if it doesn't work on your POSIX-compliant operating system.
 
 There are three ways to install Phusion Passenger:
 
-1. By installing the Phusion Passenger gem, as instructed on the
-   link:http://www.modrails.com/install.html[``Install'' page on the Phusion
+1. By installing the Phusion Passenger Ruby gem, as instructed on the
+   link:https://www.phusionpassenger.com/download[``Download'' page on the Phusion
    Passenger website].
 2. By downloading the source tarball from the Phusion Passenger website
    ('passenger-x.x.x.tar.gz').
@@ -219,12 +193,6 @@ Phusion Passenger.
 
 === Operating system-specific instructions and information ===
 
-==== MacOS X ====
-
-Ben Ruebenstein has written an excellent
-link:http://benr75.com/articles/2008/04/12/setup-mod_rails-phusion-mac-os-x-leopard[tutorial
-on installing Phusion Passenger on OS X].
-
 ==== Ubuntu Linux ====
 
 Ben Hughes has written an link:http://www.railsgarden.com/2008/04/12/configurating-passenger-mod_rails-on-slicehost-with-ubuntu-710/[article on installing Phusion Passenger on Ubuntu].
@@ -715,6 +683,114 @@ touch /webapps/rackapp/tmp/restart.txt
 include::users_guide_snippets/rackup_specifications.txt[]
 
 
+== Deploying a WSGI (Python) application
+
+Phusion Passenger supports all WSGI-compliant Python web applications. Suppose that you have a WSGI application in '/webapps/wsgiapp'. Then that folder must contain at least three entries:
+
+- 'passenger_wsgi.py', which Phusion Passenger will use as the main entry point for your application. This file must export a WSGI object called `application`.
+- 'public/', a folder containing public static web assets, like images and stylesheets.
+- 'tmp/', used for 'restart.txt' (our application restart mechanism). This will be explained in a following subsection.
+
+So '/webapps/wsgiapp' must, at minimum, look like this:
+----------------------
+/webapps/wsgiapp
+  |
+  +-- config.ru
+  |
+  +-- public/
+  |
+  +-- tmp/
+----------------------
+
+=== Tutorial/example: writing and deploying a Hello World WSGI application ===
+
+First we create a Phusion Passenger-compliant WSGI directory structure:
+
+-------------------------------------------
+$ mkdir /webapps/wsgi_example
+$ mkdir /webapps/wsgi_example/public
+$ mkdir /webapps/wsgi_example/tmp
+-------------------------------------------
+
+Next, we write a minimal "hello world" WSGI application:
+
+-------------------------------------------
+$ cd /webapps/wsgi_example
+$ some_awesome_editor passenger_wsgi.py
+...type in some source code...
+$ cat passenger_wsgi.py
+def application(environ, start_response):
+  start_response(200, [('Content-Type', 'text/plain')])
+  return ["hello world!\n"]
+-------------------------------------------
+
+Finally, we deploy it by adding the following configuration options to
+the Apache configuration file:
+
+-------------------------------------------
+<VirtualHost *:80>
+    ServerName www.wsgiexample.com
+    DocumentRoot /webapps/wsgi_example/public
+    <Directory /webapps/wsgi_example/public>
+        Allow from all
+        Options -MultiViews
+    </Directory>
+</VirtualHost>
+-------------------------------------------
+
+And we're done! After an Apache restart, the above WSGI application will be available
+under the URL 'http://www.wsgiexample.com/'.
+
+=== Deploying to a virtual host's root ===
+
+Add a virtual host entry to your Apache configuration file. Make sure that the
+following conditions are met:
+
+- The virtual host's document root must point to your WSGI application's
+  'public' folder.
+- The WSGI per-directory permissions must allow access to this folder.
+- MultiViews must be disabled for this folder.
+
+For example:
+-------------------------------------------
+<VirtualHost *:80>
+    ServerName www.wsgiapp.com
+    DocumentRoot /webapps/wsgiapp/public
+    <Directory /webapps/wsgiapp/public>
+        Allow from all
+        Options -MultiViews
+    </Directory>
+</VirtualHost>
+-------------------------------------------
+
+You may also need to tweak your file/folder permissions. Make sure that the
+following folders are readable and executable by Apache:
+
+ * this 'public' folder.
+ * the application's 'config' folder.
+ * all parent folders. That is, /webapps/wsgiapp and /webapps must also be readable and executable by Apache.
+
+Then restart Apache. The application has now been deployed.
+
+=== Redeploying (restarting the WSGI application) ===
+
+Deploying a new version of a WSGI application is as simple as
+re-uploading the application files, and restarting the application.
+
+There are two ways to restart the application:
+
+1. By restarting Apache.
+2. By creating or modifying the file 'tmp/restart.txt' in the WSGI
+   application's <<application_root,root folder>>. Phusion Passenger will
+   automatically restart the application.
+
+For example, to restart our example application, we type this in the
+command line:
+-------------------------------------------
+touch /webapps/wsgiapp/tmp/restart.txt
+-------------------------------------------
+
+
 == Configuring Phusion Passenger ==
 
 After installation, Phusion Passenger does not need any further configurations.
@@ -737,8 +813,14 @@ This required option may only occur once, in the global server configuration.
 === PassengerRuby <filename> ===
 This option allows one to specify the Ruby interpreter to use.
 
-This option may only occur once, in the global server configuration.
-The default is 'ruby'.
+This option may occur in the following places:
+
+ * In the global server configuration.
+ * In a virtual host configuration block.
+ * In a `<Directory>` or `<Location>` block.
+ * In '.htaccess', if `AllowOverride Options` is on.
+
+In each place, it may be specified at most once. The default value is 'ruby', meaning that the Ruby interpreter will be looked up according to the `PATH` environment variable.
 
 [[PassengerAppRoot]]
 === PassengerAppRoot <path/to/root> ===
@@ -793,22 +875,6 @@ This option may occur in the following places:
 
 In each place, it may be specified at most once. The default value is 'smart-lv2'.
 
-[[PassengerUseGlobalQueue]]
-=== PassengerUseGlobalQueue <on|off> ===
-Turns the use of global queuing on or off.
-
-This option may occur in the following places:
-
- * In the global server configuration.
- * In a virtual host configuration block.
-
-In each place, it may be specified at most once. The default value is 'on'.
-
-'This feature is sponsored by http://www.37signals.com/[37signals].'
-
-include::users_guide_snippets/global_queueing_explained.txt[]
-
-
 === PassengerEnabled <on|off> ===
 You can set this option to 'off' to completely disable Phusion Passenger for
 a certain location. This is useful if, for example, you want to integrate a PHP
@@ -1353,6 +1419,30 @@ applications, each which must be available at all times.
 This option may only occur once, in the global server configuration.
 The default value is '300'.
 
+==== PassengerMaxPreloaderIdleTime <integer> ====
+The ApplicationSpawner server (explained in <<spawning_methods_explained,Spawning
+methods explained>>) has an idle timeout, just like the backend processes spawned by
+Phusion Passenger do. That is, it will automatically shutdown if it hasn't done
+anything for a given period.
+
+This option allows you to set the ApplicationSpawner server's idle timeout, in
+seconds. A value of '0' means that it should never idle timeout.
+
+Setting a higher value will mean that the ApplicationSpawner server is kept around
+longer, which may slightly increase memory usage. But as long as the
+ApplicationSpawner server is running, the time to spawn a Ruby on Rails backend
+process only takes about 10% of the time that is normally needed, assuming that
+you're using the 'smart' or 'smart-lv2' <<PassengerSpawnMethod,spawning method>>. So if your
+system has enough memory, is it recommended that you set this option to a high
+value or to '0'.
+
+This option may occur in the following places:
+
+ * In the global server configuration.
+ * In a virtual host configuration block.
+
+In each place, it may be specified at most once. The default value is '300' (5 minutes).
+
 [[PassengerMaxRequests]]
 ==== PassengerMaxRequests <integer> ====
 The maximum number of requests an application process will process. After
@@ -1918,7 +2008,10 @@ This option may occur in the following places:
 In each place, it may be specified at most once. The default value is 'off'.
 
 
-=== Ruby on Rails-specific options ===
+=== Classic Ruby on Rails (<= 2.x)-specific options ===
+
+These options only have effect on classic Ruby on Rails 1.x and 2.x applications.
+Ruby on Rails >= 3.x applications are considered Rack applications.
 
 ==== RailsAutoDetect <on|off> ====
 Whether Phusion Passenger should automatically detect whether a virtual host's
@@ -1981,54 +2074,6 @@ This option may occur in the following places:
 
 In each place, it may be specified at most once. The default value is 'production'.
 
-==== RailsFrameworkSpawnerIdleTime <integer> ====
-The FrameworkSpawner server (explained in <<spawning_methods_explained,Spawning
-methods explained>>) has an idle timeout, just like the backend processes spawned by
-Phusion Passenger do. That is, it will automatically shutdown if it hasn't done
-anything for a given period.
-
-This option allows you to set the FrameworkSpawner server's idle timeout, in
-seconds. A value of '0' means that it should never idle timeout.
-
-Setting a higher value will mean that the FrameworkSpawner server is kept around
-longer, which may slightly increase memory usage. But as long as the
-FrameworkSpawner server is running, the time to spawn a Ruby on Rails backend
-process only takes about 40% of the time that is normally needed, assuming that
-you're using the 'smart' <<PassengerSpawnMethod,spawning method>>. So if your
-system has enough memory, is it recommended that you set this option to a high
-value or to '0'.
-
-This option may occur in the following places:
-
- * In the global server configuration.
- * In a virtual host configuration block.
-
-In each place, it may be specified at most once. The default value is '1800' (30 minutes).
-
-==== RailsAppSpawnerIdleTime <integer> ====
-The ApplicationSpawner server (explained in <<spawning_methods_explained,Spawning
-methods explained>>) has an idle timeout, just like the backend processes spawned by
-Phusion Passenger do. That is, it will automatically shutdown if it hasn't done
-anything for a given period.
-
-This option allows you to set the ApplicationSpawner server's idle timeout, in
-seconds. A value of '0' means that it should never idle timeout.
-
-Setting a higher value will mean that the ApplicationSpawner server is kept around
-longer, which may slightly increase memory usage. But as long as the
-ApplicationSpawner server is running, the time to spawn a Ruby on Rails backend
-process only takes about 10% of the time that is normally needed, assuming that
-you're using the 'smart' or 'smart-lv2' <<PassengerSpawnMethod,spawning method>>. So if your
-system has enough memory, is it recommended that you set this option to a high
-value or to '0'.
-
-This option may occur in the following places:
-
- * In the global server configuration.
- * In a virtual host configuration block.
-
-In each place, it may be specified at most once. The default value is '600' (10 minutes).
-
 === Rack and Rails >= 3 specific options ===
 
 ==== RackAutoDetect <on|off> ====

data/doc/Users guide Nginx.html

@@ -1,9 +1,9 @@
 <!DOCTYPE html>
-<html lang="en">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta name="generator" content="AsciiDoc 8.6.7">
-<title>Phusion Passenger users guide, Nginx version</title>
+<html lang="en">
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+<meta name="generator" content="AsciiDoc 8.6.7">
+<title>Phusion Passenger users guide, Nginx version</title>
 <style type="text/css">
 /* Shared CSS for AsciiDoc xhtml11 and html5 backends */
 
@@ -603,7 +603,7 @@ div.exampleblock > div.content, div.sidebarblock > div.content, div.listingblock
 div.verseblock { border-left-width: 0; margin-left: 3em; }
 div.quoteblock { border-left-width: 3px; margin-left: 0; margin-right: 0;}
 div.admonitionblock td.content { border-left: 3px solid #E8E8E8; }
-</style>
+</style>
 <script type="text/javascript">
 /*<![CDATA[*/
 var asciidoc = {  // Namespace.
@@ -795,14 +795,11 @@ install: function(toclevels) {
 }
 
 }
-asciidoc.install();
+asciidoc.install(3);
 /*]]>*/
-</script>
-<style type="text/css">
+</script><style type="text/css">
 body {
-	margin: 1em auto 1em auto;
-	padding: 0 1em 0 1em;
-	max-width: 800px;
+	margin: 1em 10% 1em 10%;
 }
 
 a.image {
@@ -881,10 +878,6 @@ a.image {
 	margin: 2em;
 }
 
-pre {
-	overflow: auto;
-}
-
 @media print {
 	body {
 		font-size: 18pt;
@@ -1045,40 +1038,27 @@ pre {
 	border-bottom-right-radius: 0;
 }
 
-/* http://nicolasgallagher.com/jump-links-and-viewport-positioning/ */
-.anchor_helper {
-	position: relative;
-	display: block;
-	top: -50px;
-	width: 1px;
-	height: 1px;
-}
-
 </style>
-</head>
+</head>
 <body class="article">
 <div id="topbar" style="display: none">
 	<div class="title">
-		<img src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAsAAAAKCAYAAAEV95QVAAAAAXNSR0IArs4c6QAAAAZiS0dEAP8A/wD/oL2nkwAAAAlwSFlzAAALEwAACxMBAJqcGAAAAAd0SU1FB9sGCRMSACDxkZwAAAAidEVYdENvbW1lbnQAQ3JlYXRlZCB3aXRoIEdJTVAgb24gYSBNYWOHqHdDAAAAZUlEQVQY032PSxbAIAjEIlfygL6ePF3UUvpzNjgSYWwqAMEhUQnANnsC7TQPeJpsVWzMuh2sog4vDTUbqP081zECrW4dtdaQGSIKlWluPyjK+VXxAz5XfcKufCzA130AfQHWB30HZxlPaP080xsAAAAASUVORK5CYII=" width="11" height="10" alt="">
-		<a href="javascript:void(Mizuho.smoothlyScrollToToc())">Phusion Passenger users guide, Nginx version</a>
+		<img src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAsAAAAKCAYAAAEV95QVAAAAAXNSR0IArs4c6QAAAAZiS0dEAP8A/wD/oL2nkwAAAAlwSFlzAAALEwAACxMBAJqcGAAAAAd0SU1FB9sGCRMSACDxkZwAAAAidEVYdENvbW1lbnQAQ3JlYXRlZCB3aXRoIEdJTVAgb24gYSBNYWOHqHdDAAAAZUlEQVQY032PSxbAIAjEIlfygL6ePF3UUvpzNjgSYWwqAMEhUQnANnsC7TQPeJpsVWzMuh2sog4vDTUbqP081zECrW4dtdaQGSIKlWluPyjK+VXxAz5XfcKufCzA130AfQHWB30HZxlPaP080xsAAAAASUVORK5CYII=" width="11" height="10" alt=""><a href="javascript:void(Mizuho.smoothlyScrollToToc())">Phusion Passenger users guide, Nginx version</a>
 	</div>
 	<a href="javascript:void(0)" id="current_section"></a>
 </div>
 <div id="header">
-<h1>Phusion Passenger users guide, Nginx version</h1>
+<h1>Phusion Passenger users guide, Nginx version</h1>
 <div id="preamble">
 <div class="sectionbody">
 <div class="paragraph"><p><span class="image">
 <a class="image" href="http://www.phusion.nl/">
-<img src="images/phusion_banner.png" alt="images/phusion_banner.png">
-</a>
+<img src="images/phusion_banner.png" alt="images/phusion_banner.png"></a>
 </span></p></div>
-<div class="paragraph"><p>Phusion Passenger is an Nginx module, which makes deploying Ruby and Ruby on
-Rails applications on Nginx a breeze. It follows the usual Ruby on Rails
-conventions, such as "Don’t-Repeat-Yourself" and ease of setup, while at the
-same time providing enough flexibility.</p></div>
+<div class="paragraph"><p>Phusion Passenger is an application server which can directly integrate into Nginx. It is designed to be easy to use, fast, stable and reliable and is used by <a href="http://trends.builtwith.com/Web-Server/Phusion-Passenger">hundreds of thousands of websites</a> all over the world.</p></div>
+<div class="paragraph"><p>Phusion Passenger is a so-called polyglot application server because it supports applications written in multiple programming languages. At this time, Ruby and Python are supported.</p></div>
 <div class="paragraph"><p>This users guide will teach you:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 How to install Nginx with Phusion Passenger support.
@@ -1091,12 +1071,7 @@ How to configure Phusion Passenger.
 </li>
 <li>
 <p>
-How to deploy a Ruby on Rails application.
-</p>
-</li>
-<li>
-<p>
-How to deploy a <a href="http://rack.rubyforge.org/">Rack</a>-based Ruby application.
+How to deploy Ruby and Python applications.
 </p>
 </li>
 <li>
@@ -1106,145 +1081,35 @@ How to solve common problems.
 </li>
 </ul></div>
 <div class="paragraph"><p>This guide assumes that the reader is somewhat familiar with Nginx and with
-using the commandline.</p></div>
+using the command line.</p></div>
+</div>
 </div>
-</div>
 <div id="toc">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><div id="toctitle">Table of Contents</div>
-<div class="foo toclevel2"><a href="#_support_information">1. Support information</a></div>
-<div class="foo toclevel3"><a href="#_supported_operating_systems">1.1. Supported operating systems</a></div>
-<div class="foo toclevel3"><a href="#_where_to_get_support">1.2. Where to get support</a></div>
-<div class="foo toclevel2"><a href="#_installing_phusion_passenger">2. Installing Phusion Passenger</a></div>
-<div class="foo toclevel3"><a href="#_overview">2.1. Overview</a></div>
-<div class="foo toclevel3"><a href="#specifying_ruby_installation">2.2. Specifying the correct Ruby installation</a></div>
-<div class="foo toclevel3"><a href="#_installing_phusion_passenger_for_nginx_through_the_installer">2.3. Installing Phusion Passenger for Nginx through the installer</a></div>
-<div class="foo toclevel4"><a href="#_obtaining_the_phusion_passenger_files_and_running_the_installer">2.3.1. Obtaining the Phusion Passenger files and running the installer</a></div>
-<div class="foo toclevel4"><a href="#_non_interactive_automatic_installation">2.3.2. Non-interactive/automatic installation</a></div>
-<div class="foo toclevel3"><a href="#_installing_phusion_passenger_for_nginx_manually">2.4. Installing Phusion Passenger for Nginx manually</a></div>
-<div class="foo toclevel3"><a href="#_upgrading_or_downgrading_phusion_passenger_or_nginx_itself">2.5. Upgrading or downgrading Phusion Passenger or Nginx itself</a></div>
-<div class="foo toclevel3"><a href="#_unloading_disabling_phusion_passenger_from_nginx_without_uninstalling_it">2.6. Unloading (disabling) Phusion Passenger from Nginx without uninstalling it</a></div>
-<div class="foo toclevel3"><a href="#_uninstalling_phusion_passenger">2.7. Uninstalling Phusion Passenger</a></div>
-<div class="foo toclevel2"><a href="#deploying_a_ror_app">3. Deploying a Ruby on Rails 1.x or 2.x (but NOT Rails &gt;= 3) application</a></div>
-<div class="foo toclevel3"><a href="#_deploying_to_a_virtual_host_8217_s_root">3.1. Deploying to a virtual host’s root</a></div>
-<div class="foo toclevel3"><a href="#deploying_rails_to_sub_uri">3.2. Deploying to a sub URI</a></div>
-<div class="foo toclevel3"><a href="#_redeploying_restarting_the_ruby_on_rails_application">3.3. Redeploying (restarting the Ruby on Rails application)</a></div>
-<div class="foo toclevel3"><a href="#_migrations">3.4. Migrations</a></div>
-<div class="foo toclevel3"><a href="#_capistrano_integration">3.5. Capistrano integration</a></div>
-<div class="foo toclevel2"><a href="#deploying_a_rack_app">4. Deploying a Rack-based Ruby application (including Rails &gt;= 3)</a></div>
-<div class="foo toclevel3"><a href="#_tutorial_example_writing_and_deploying_a_hello_world_rack_application">4.1. Tutorial/example: writing and deploying a Hello World Rack application</a></div>
-<div class="foo toclevel3"><a href="#_deploying_to_a_virtual_host_8217_s_root_2">4.2. Deploying to a virtual host’s root</a></div>
-<div class="foo toclevel3"><a href="#deploying_rack_to_sub_uri">4.3. Deploying to a sub URI</a></div>
-<div class="foo toclevel3"><a href="#_redeploying_restarting_the_rack_application">4.4. Redeploying (restarting the Rack application)</a></div>
-<div class="foo toclevel3"><a href="#_rackup_specifications_for_various_web_frameworks">4.5. Rackup specifications for various web frameworks</a></div>
-<div class="foo toclevel4"><a href="#_camping">4.5.1. Camping</a></div>
-<div class="foo toclevel4"><a href="#_halcyon">4.5.2. Halcyon</a></div>
-<div class="foo toclevel4"><a href="#_mack">4.5.3. Mack</a></div>
-<div class="foo toclevel4"><a href="#_merb">4.5.4. Merb</a></div>
-<div class="foo toclevel4"><a href="#_ramaze">4.5.5. Ramaze</a></div>
-<div class="foo toclevel4"><a href="#_sinatra">4.5.6. Sinatra</a></div>
-<div class="foo toclevel2"><a href="#_configuring_phusion_passenger">5. Configuring Phusion Passenger</a></div>
-<div class="foo toclevel3"><a href="#_passenger_root_lt_directory_gt">5.1. passenger_root &lt;directory&gt;</a></div>
-<div class="foo toclevel3"><a href="#_passenger_ruby_lt_filename_gt">5.2. passenger_ruby &lt;filename&gt;</a></div>
-<div class="foo toclevel3"><a href="#PassengerSpawnMethod">5.3. passenger_spawn_method &lt;string&gt;</a></div>
-<div class="foo toclevel3"><a href="#PassengerRollingRestarts">5.4. passenger_rolling_restarts &lt;on|off&gt;</a></div>
-<div class="foo toclevel3"><a href="#_passenger_resist_deployment_errors_lt_on_off_gt">5.5. passenger_resist_deployment_errors &lt;on|off&gt;</a></div>
-<div class="foo toclevel3"><a href="#_important_deployment_options">5.6. Important deployment options</a></div>
-<div class="foo toclevel4"><a href="#_passenger_enabled_lt_on_off_gt">5.6.1. passenger_enabled &lt;on|off&gt;</a></div>
-<div class="foo toclevel4"><a href="#PassengerBaseURI">5.6.2. passenger_base_uri &lt;uri&gt;</a></div>
-<div class="foo toclevel3"><a href="#_connection_handling_options">5.7. Connection handling options</a></div>
-<div class="foo toclevel4"><a href="#PassengerUseGlobalQueue">5.7.1. passenger_use_global_queue &lt;on|off&gt;</a></div>
-<div class="foo toclevel4"><a href="#_passenger_ignore_client_abort_lt_on_off_gt">5.7.2. passenger_ignore_client_abort &lt;on|off&gt;</a></div>
-<div class="foo toclevel4"><a href="#_passenger_set_cgi_param_lt_cgi_environment_name_gt_lt_value_gt">5.7.3. passenger_set_cgi_param &lt;CGI environment name&gt; &lt;value&gt;</a></div>
-<div class="foo toclevel4"><a href="#_passenger_pass_header_lt_header_name_gt">5.7.4. passenger_pass_header &lt;header name&gt;</a></div>
-<div class="foo toclevel4"><a href="#_passenger_buffer_response_lt_on_off_gt">5.7.5. passenger_buffer_response &lt;on|off&gt;</a></div>
-<div class="foo toclevel4"><a href="#_passenger_buffer_size">5.7.6. passenger_buffer_size</a></div>
-<div class="foo toclevel4"><a href="#_passenger_buffers">5.7.7. passenger_buffers</a></div>
-<div class="foo toclevel4"><a href="#_passenger_busy_buffer_size">5.7.8. passenger_busy_buffer_size</a></div>
-<div class="foo toclevel3"><a href="#_security_options">5.8. Security options</a></div>
-<div class="foo toclevel4"><a href="#PassengerUserSwitching">5.8.1. passenger_user_switching &lt;on|off&gt;</a></div>
-<div class="foo toclevel4"><a href="#_passenger_user_lt_username_gt">5.8.2. passenger_user &lt;username&gt;</a></div>
-<div class="foo toclevel4"><a href="#_passenger_group_lt_group_name_gt">5.8.3. passenger_group &lt;group name&gt;</a></div>
-<div class="foo toclevel4"><a href="#PassengerDefaultUser">5.8.4. passenger_default_user &lt;username&gt;</a></div>
-<div class="foo toclevel4"><a href="#PassengerDefaultGroup">5.8.5. Passenger_default_group &lt;group name&gt;</a></div>
-<div class="foo toclevel4"><a href="#_passenger_friendly_error_pages_lt_on_off_gt">5.8.6. passenger_friendly_error_pages &lt;on|off&gt;</a></div>
-<div class="foo toclevel3"><a href="#_resource_control_and_optimization_options">5.9. Resource control and optimization options</a></div>
-<div class="foo toclevel4"><a href="#PassengerMaxPoolSize">5.9.1. passenger_max_pool_size &lt;integer&gt;</a></div>
-<div class="foo toclevel4"><a href="#PassengerMinInstances">5.9.2. passenger_min_instances &lt;integer&gt;</a></div>
-<div class="foo toclevel4"><a href="#_passenger_max_instances_lt_integer_gt">5.9.3. passenger_max_instances &lt;integer&gt;</a></div>
-<div class="foo toclevel4"><a href="#_passenger_max_instances_per_app_lt_integer_gt">5.9.4. passenger_max_instances_per_app &lt;integer&gt;</a></div>
-<div class="foo toclevel4"><a href="#PassengerPoolIdleTime">5.9.5. passenger_pool_idle_time &lt;integer&gt;</a></div>
-<div class="foo toclevel4"><a href="#PassengerMaxRequests">5.9.6. passenger_max_requests &lt;integer&gt;</a></div>
-<div class="foo toclevel4"><a href="#PassengerMaxRequestTime">5.9.7. passenger_max_request_time &lt;seconds&gt;</a></div>
-<div class="foo toclevel4"><a href="#PassengerMemoryLimit">5.9.8. passenger_memory_limit &lt;integer&gt;</a></div>
-<div class="foo toclevel4"><a href="#PassengerPreStart">5.9.9. passenger_pre_start &lt;url&gt;</a></div>
-<div class="foo toclevel3"><a href="#_logging_and_debugging_options">5.10. Logging and debugging options</a></div>
-<div class="foo toclevel4"><a href="#_passenger_log_level_lt_integer_gt">5.10.1. passenger_log_level &lt;integer&gt;</a></div>
-<div class="foo toclevel4"><a href="#_passenger_debug_log_file_lt_filename_gt">5.10.2. passenger_debug_log_file &lt;filename&gt;</a></div>
-<div class="foo toclevel4"><a href="#_passenger_debugger_lt_on_off_gt">5.10.3. passenger_debugger &lt;on|off&gt;</a></div>
-<div class="foo toclevel3"><a href="#_ruby_on_rails_specific_options">5.11. Ruby on Rails-specific options</a></div>
-<div class="foo toclevel4"><a href="#RailsEnv">5.11.1. rails_env &lt;string&gt;</a></div>
-<div class="foo toclevel4"><a href="#_rails_framework_spawner_idle_time_lt_integer_gt">5.11.2. rails_framework_spawner_idle_time &lt;integer&gt;</a></div>
-<div class="foo toclevel4"><a href="#_rails_app_spawner_idle_time_lt_integer_gt">5.11.3. rails_app_spawner_idle_time &lt;integer&gt;</a></div>
-<div class="foo toclevel3"><a href="#_rack_and_rails_gt_3_specific_options">5.12. Rack and Rails &gt;= 3 specific options</a></div>
-<div class="foo toclevel4"><a href="#RackEnv">5.12.1. rack_env &lt;string&gt;</a></div>
-<div class="foo toclevel3"><a href="#_deprecated_options">5.13. Deprecated options</a></div>
-<div class="foo toclevel4"><a href="#_rails_spawn_method">5.13.1. rails_spawn_method</a></div>
-<div class="foo toclevel2"><a href="#_analysis_and_system_maintenance">6. Analysis and system maintenance</a></div>
-<div class="foo toclevel3"><a href="#_inspecting_memory_usage">6.1. Inspecting memory usage</a></div>
-<div class="foo toclevel3"><a href="#_inspecting_phusion_passenger_8217_s_internal_status">6.2. Inspecting Phusion Passenger’s internal status</a></div>
-<div class="foo toclevel3"><a href="#debugging_frozen">6.3. Debugging frozen applications</a></div>
-<div class="foo toclevel3"><a href="#_accessing_individual_application_processes">6.4. Accessing individual application processes</a></div>
-<div class="foo toclevel3"><a href="#_attaching_an_irb_console_to_an_application_process">6.5. Attaching an IRB console to an application process</a></div>
-<div class="foo toclevel2"><a href="#_tips">7. Tips</a></div>
-<div class="foo toclevel3"><a href="#user_switching">7.1. User switching (security)</a></div>
-<div class="foo toclevel3"><a href="#reducing_memory_usage">7.2. Reducing memory consumption of Ruby on Rails applications by 33%</a></div>
-<div class="foo toclevel3"><a href="#capistrano">7.3. Capistrano recipe</a></div>
-<div class="foo toclevel3"><a href="#bundler_support">7.4. Bundler support</a></div>
-<div class="foo toclevel3"><a href="#moving_phusion_passenger">7.5. Moving Phusion Passenger to a different directory</a></div>
-<div class="foo toclevel3"><a href="#_installing_multiple_ruby_on_rails_versions">7.6. Installing multiple Ruby on Rails versions</a></div>
-<div class="foo toclevel3"><a href="#_making_the_application_restart_after_each_request">7.7. Making the application restart after each request</a></div>
-<div class="foo toclevel3"><a href="#sub_uri_deployment_uri_fix">7.8. How to fix broken images/CSS/JavaScript URIs in sub-URI deployments</a></div>
-<div class="foo toclevel2"><a href="#_under_the_hood">8. Under the hood</a></div>
-<div class="foo toclevel3"><a href="#_page_caching_support">8.1. Page caching support</a></div>
-<div class="foo toclevel3"><a href="#application_detection">8.2. How Phusion Passenger detects whether a virtual host is a web application</a></div>
-<div class="foo toclevel2"><a href="#_appendix_a_about_this_document">9. Appendix A: About this document</a></div>
-<div class="foo toclevel2"><a href="#_appendix_b_terminology">10. Appendix B: Terminology</a></div>
-<div class="foo toclevel3"><a href="#application_root">10.1. Application root</a></div>
-<div class="foo toclevel3"><a href="#idle_process">10.2. Idle process</a></div>
-<div class="foo toclevel3"><a href="#inactive_process">10.3. Inactive process</a></div>
-<div class="foo toclevel2"><a href="#spawning_methods_explained">11. Appendix C: Spawning methods explained</a></div>
-<div class="foo toclevel3"><a href="#_the_most_straightforward_and_traditional_way_conservative_spawning">11.1. The most straightforward and traditional way: conservative spawning</a></div>
-<div class="foo toclevel3"><a href="#_the_smart_spawning_method">11.2. The smart spawning method</a></div>
-<div class="foo toclevel4"><a href="#_how_it_works">11.2.1. How it works</a></div>
-<div class="foo toclevel4"><a href="#_summary_of_benefits">11.2.2. Summary of benefits</a></div>
-<div class="foo toclevel3"><a href="#_smart_spawning_gotcha_1_unintentional_file_descriptor_sharing">11.3. Smart spawning gotcha #1: unintentional file descriptor sharing</a></div>
-<div class="foo toclevel4"><a href="#_example_1_memcached_connection_sharing_harmful">11.3.1. Example 1: Memcached connection sharing (harmful)</a></div>
-<div class="foo toclevel4"><a href="#_example_2_log_file_sharing_not_harmful">11.3.2. Example 2: Log file sharing (not harmful)</a></div>
-<div class="foo toclevel3"><a href="#_smart_spawning_gotcha_2_the_need_to_revive_threads">11.4. Smart spawning gotcha #2: the need to revive threads</a></div>
-<div class="foo toclevel3"><a href="#_smart_spawning_gotcha_3_code_load_order">11.5. Smart spawning gotcha #3: code load order</a></div>
-</div>
+  <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><div id="toctitle">Table of Contents</div>
+  <noscript><p><b>JavaScript must be enabled in your browser to display the table of contents.</b></p></noscript>
+</div>
 </div>
 <div id="content">
 
 <div class="sect1">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_support_information"></span><h2 data-comment-topic="support-information-nl5gdn" data-anchor="_support_information">1. Support information</h2>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h2 id="_support_information" data-comment-topic="support-information-nl5gdn">1. Support information</h2>
 <div class="sectionbody">
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_supported_operating_systems"></span><h3 data-comment-topic="supported-operating-systems-a5n2x4" data-anchor="_supported_operating_systems">1.1. Supported operating systems</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_supported_operating_systems" data-comment-topic="supported-operating-systems-a5n2x4">1.1. Supported operating systems</h3>
 <div class="paragraph"><p>Phusion Passenger works on any POSIX-compliant operating system. In other
 words: practically any operating system on earth, except Microsoft Windows.</p></div>
 <div class="paragraph"><p>Phusion Passenger is confirmed on a large number of operating systems and Linux
 distributions, including, but not limited to, Ubuntu, Debian, CentOS/Fedora/RHEL,
-Gentoo, Mac OS X, FreeBSD and Solaris. Both 32-bit and 64-bit platforms are supported.
-Please
+Gentoo, Mac OS X, FreeBSD and Solaris. Both 32-bit and 64-bit platforms are supported.</p></div>
+<div class="paragraph"><p>Please
 <a href="http://code.google.com/p/phusion-passenger/issues/list">report a bug</a>
 or
 <a href="http://groups.google.com/group/phusion-passenger">join our discussion forum</a>
 if it doesn’t work on your POSIX-compliant operating system.</p></div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_where_to_get_support"></span><h3 data-comment-topic="where-to-get-support-2s9na5" data-anchor="_where_to_get_support">1.2. Where to get support</h3>
-<div class="ulist"><ul>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_where_to_get_support" data-comment-topic="where-to-get-support-2s9na5">1.2. Where to get support</h3>
+<div class="ulist"><ul>
 <li>
 <p>
 <a href="http://code.google.com/p/phusion-passenger/issues/list">Issue tracker</a> - report
@@ -1257,20 +1122,26 @@ if it doesn’t work on your POSIX-compliant operating system.</p></div>
   message here if you’re experiencing problems.
 </p>
 </li>
+<li>
+<p>
+<a href="https://www.phusionpassenger.com/commercial_support">Commercial support contracts</a> are also available.
+</p>
+</li>
 </ul></div>
+<div class="paragraph"><p>Please consult <a href="https://www.phusionpassenger.com/support">the Phusion Passenger website</a> for a full list of support resources.</p></div>
 </div>
 </div>
 </div>
 <div class="sect1">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_installing_phusion_passenger"></span><h2 data-comment-topic="installing-phusion-passenger-hn03ac" data-anchor="_installing_phusion_passenger">2. Installing Phusion Passenger</h2>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h2 id="_installing_phusion_passenger" data-comment-topic="installing-phusion-passenger-hn03ac">2. Installing Phusion Passenger</h2>
 <div class="sectionbody">
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_overview"></span><h3 data-comment-topic="overview-kvhzi4" data-anchor="_overview">2.1. Overview</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_overview" data-comment-topic="overview-kvhzi4">2.1. Overview</h3>
 <div class="paragraph"><p>As you might already know, Nginx does not support loadable modules, in contrast
 to most other web servers (e.g. Apache). Therefore, to install Phusion Passenger
 for Nginx, one must recompile and reinstall Nginx with Phusion Passenger support.
 There are two ways to do this:</p></div>
-<div class="olist arabic"><ol class="arabic">
+<div class="olist arabic"><ol class="arabic">
 <li>
 <p>
 By running the Phusion Passenger installer for Nginx. This installer will
@@ -1290,18 +1161,18 @@ By manually configuring and compiling Nginx with Phusion Passenger support,
 </li>
 </ol></div>
 <div class="admonitionblock">
-<table><tr>
+<table><tr>
 <td class="icon">
-<img src="./images/icons/tip.png" alt="Tip">
+<img src="./images/icons/tip.png" alt="Tip">
 </td>
 <td class="content">You might have to run the installation commands in the following sections
 as <em>root</em>. If the installer fails because of permission errors, it will tell
 you.</td>
-</tr></table>
+</tr></table>
 </div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="specifying_ruby_installation"></span><h3 data-comment-topic="specifying-the-correct-ruby-installation-jvqdv6" data-anchor="specifying_ruby_installation">2.2. Specifying the correct Ruby installation</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="specifying_ruby_installation" data-comment-topic="specifying-the-correct-ruby-installation-jvqdv6">2.2. Specifying the correct Ruby installation</h3>
 <div class="paragraph"><p>If your system has multiple Ruby installations — which is likely the case on
 MacOS X, or if you’ve also installed
 <a href="http://www.rubyenterpriseedition.com">Ruby Enterprise Edition</a> — then you
@@ -1312,7 +1183,7 @@ Passenger will automatically detect it.</p></div>
 <div class="paragraph"><p>To specify a Ruby installation, prepend your Ruby installation’s <span class="monospaced">bin</span>
 directory to the <span class="monospaced">PATH</span> environment variable. For example, if you have the
 following Ruby installations:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 /usr/bin/ruby
@@ -1332,9 +1203,9 @@ following Ruby installations:</p></div>
 </div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_installing_phusion_passenger_for_nginx_through_the_installer"></span><h3 data-comment-topic="installing-phusion-passenger-for-nginx-through-the-installer-1lqxes1" data-anchor="_installing_phusion_passenger_for_nginx_through_the_installer">2.3. Installing Phusion Passenger for Nginx through the installer</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_installing_phusion_passenger_for_nginx_through_the_installer" data-comment-topic="installing-phusion-passenger-for-nginx-through-the-installer-1lqxes1">2.3. Installing Phusion Passenger for Nginx through the installer</h3>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_obtaining_the_phusion_passenger_files_and_running_the_installer"></span><h4 data-comment-topic="obtaining-the-phusion-passenger-files-and-running-the-installer-6l6ula" data-anchor="_obtaining_the_phusion_passenger_files_and_running_the_installer">2.3.1. Obtaining the Phusion Passenger files and running the installer</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_obtaining_the_phusion_passenger_files_and_running_the_installer" data-comment-topic="obtaining-the-phusion-passenger-files-and-running-the-installer-6l6ula">2.3.1. Obtaining the Phusion Passenger files and running the installer</h4>
 <div class="paragraph"><p>You must obtain the Phusion Passenger files in order to run the installer.
 This can be done either by installing the Phusion Passenger gem, or by
 downloading the source tarball.</p></div>
@@ -1375,18 +1246,18 @@ tar xzvf ~/YourDownloadsFolder/passenger-x.x.x.tar.gz</pre>
 </div>
 <div class="paragraph"><p>Please follow the instructions given by the installer.</p></div>
 <div class="admonitionblock">
-<table><tr>
+<table><tr>
 <td class="icon">
-<img src="./images/icons/important.png" alt="Important">
+<img src="./images/icons/important.png" alt="Important">
 </td>
 <td class="content">Please do not remove the passenger-x.x.x folder after installation.
 Furthermore, the passenger-x.x.x folder must be accessible by Nginx.</td>
-</tr></table>
+</tr></table>
 </div>
 </div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_non_interactive_automatic_installation"></span><h4 data-comment-topic="non-interactive-automatic-installation-1u97717" data-anchor="_non_interactive_automatic_installation">2.3.2. Non-interactive/automatic installation</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_non_interactive_automatic_installation" data-comment-topic="non-interactive-automatic-installation-1u97717">2.3.2. Non-interactive/automatic installation</h4>
 <div class="paragraph"><p>By default, the installer is interactive. If you want to automate installation,
 then you can do so by passing various answers to the installer through command
 line options.</p></div>
@@ -1395,7 +1266,7 @@ options.</p></div>
 </div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_installing_phusion_passenger_for_nginx_manually"></span><h3 data-comment-topic="installing-phusion-passenger-for-nginx-manually-1qg1e2x" data-anchor="_installing_phusion_passenger_for_nginx_manually">2.4. Installing Phusion Passenger for Nginx manually</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_installing_phusion_passenger_for_nginx_manually" data-comment-topic="installing-phusion-passenger-for-nginx-manually-1qg1e2x">2.4. Installing Phusion Passenger for Nginx manually</h3>
 <div class="paragraph"><p>You can also install Phusion Passenger the way you install any other Nginx module.
 To do this, run Nginx’s configure script with <span class="monospaced">--add-module=/path-to-passenger-root/ext/nginx</span>.</p></div>
 <div class="paragraph"><p>If you installed Phusion Passenger via the gem, then <em>path-to-passenger-root</em>
@@ -1421,7 +1292,7 @@ line into your Nginx configuration file:</p></div>
 <div class="paragraph"><p>After having done so, restart Nginx.</p></div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_upgrading_or_downgrading_phusion_passenger_or_nginx_itself"></span><h3 data-comment-topic="upgrading-or-downgrading-phusion-passenger-or-nginx-itself-8dulxz" data-anchor="_upgrading_or_downgrading_phusion_passenger_or_nginx_itself">2.5. Upgrading or downgrading Phusion Passenger or Nginx itself</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_upgrading_or_downgrading_phusion_passenger_or_nginx_itself" data-comment-topic="upgrading-or-downgrading-phusion-passenger-or-nginx-itself-8dulxz">2.5. Upgrading or downgrading Phusion Passenger or Nginx itself</h3>
 <div class="paragraph"><p>Whether you’re upgrading/downgrading Phusion Passenger or Nginx itself (or perhaps both),
 Nginx will have to be recompiled and reinstalled. The procedure is exactly the same as
 a normal installation so just follow the instructions in section 2.3 or 2.4.</p></div>
@@ -1441,7 +1312,7 @@ removed, otherwise Phusion Passenger may malfunction.</p></div>
 <div class="paragraph"><p>When you’re done, restart Nginx.</p></div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_unloading_disabling_phusion_passenger_from_nginx_without_uninstalling_it"></span><h3 data-comment-topic="unloading-disabling-phusion-passenger-from-nginx-without-uninstalling-it-v447e0" data-anchor="_unloading_disabling_phusion_passenger_from_nginx_without_uninstalling_it">2.6. Unloading (disabling) Phusion Passenger from Nginx without uninstalling it</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_unloading_disabling_phusion_passenger_from_nginx_without_uninstalling_it" data-comment-topic="unloading-disabling-phusion-passenger-from-nginx-without-uninstalling-it-v447e0">2.6. Unloading (disabling) Phusion Passenger from Nginx without uninstalling it</h3>
 <div class="paragraph"><p>You can temporarily unload (disable) Phusion Passenger from Nginx, without
 uninstalling the Phusion Passenger files, so that Nginx behaves as if Phusion
 Passenger was never installed in the first place. This might be useful to you if,
@@ -1469,7 +1340,6 @@ http {
         listen 80;
         root /webapps/foo/public;
         passenger_enabled on;
-        passenger_use_global_queue on;
     }
 }</pre>
 </div>
@@ -1499,11 +1369,11 @@ http {
 <div class="paragraph"><p>After you’ve done this, save the file and restart Nginx.</p></div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_uninstalling_phusion_passenger"></span><h3 data-comment-topic="uninstalling-phusion-passenger-wuycvb" data-anchor="_uninstalling_phusion_passenger">2.7. Uninstalling Phusion Passenger</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_uninstalling_phusion_passenger" data-comment-topic="uninstalling-phusion-passenger-wuycvb">2.7. Uninstalling Phusion Passenger</h3>
 <div class="paragraph"><p>To uninstall Phusion Passenger, please first remove all Phusion Passenger
 configuration directives from your Nginx configuration file(s). After you’ve
 done this, you need to remove the Phusion Passenger files.</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 If you installed Phusion Passenger via a gem, then type <span class="monospaced">gem uninstall passenger</span>.
@@ -1525,7 +1395,7 @@ Nginx binary.</p></div>
 </div>
 </div>
 <div class="sect1">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="deploying_a_ror_app"></span><h2 data-comment-topic="deploying-a-ruby-on-rails-1-x-or-2-x-but-not-rails-3-application-b69gqa" data-anchor="deploying_a_ror_app">3. Deploying a Ruby on Rails 1.x or 2.x (but NOT Rails &gt;= 3) application</h2>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h2 id="deploying_a_ror_app" data-comment-topic="deploying-a-ruby-on-rails-1-x-or-2-x-but-not-rails-3-application-b69gqa">3. Deploying a Ruby on Rails 1.x or 2.x (but NOT Rails &gt;= 3) application</h2>
 <div class="sectionbody">
 <div class="paragraph"><p>Suppose you have a Ruby on Rails application in <em>/webapps/mycook</em>, and you own
 the domain <em>www.mycook.com</em>. You can either deploy your application to the
@@ -1533,17 +1403,17 @@ virtual host’s root (i.e. the application will be accessible from the root URL
 <em>http://www.mycook.com/</em>), or in a sub URI (i.e. the application will be
 accessible from a sub URL, such as <em>http://www.mycook.com/railsapplication</em>).</p></div>
 <div class="admonitionblock">
-<table><tr>
+<table><tr>
 <td class="icon">
-<img src="./images/icons/note.png" alt="Note">
+<img src="./images/icons/note.png" alt="Note">
 </td>
 <td class="content">The default <span class="monospaced">RAILS_ENV</span> environment in which deployed Rails applications
 are run, is “production”. You can change this by changing the
 <a href="#RailsEnv">rails_env</a> configuration option.</td>
-</tr></table>
+</tr></table>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_deploying_to_a_virtual_host_8217_s_root"></span><h3 data-comment-topic="deploying-to-a-virtual-host-s-root-1mh24z5" data-anchor="_deploying_to_a_virtual_host_8217_s_root">3.1. Deploying to a virtual host’s root</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_deploying_to_a_virtual_host_8217_s_root" data-comment-topic="deploying-to-a-virtual-host-s-root-1mh24z5">3.1. Deploying to a virtual host’s root</h3>
 <div class="paragraph"><p>Add a <em>server</em> virtual host entry to your Nginx configuration file. The virtual
 host’s root must point to your Ruby on Rails application’s <em>public</em> folder.</p></div>
 <div class="paragraph"><p>Inside the <em>server</em> block, set <em>passenger_enabled on</em>.</p></div>
@@ -1567,7 +1437,7 @@ host’s root must point to your Ruby on Rails application’s <em>public</em> f
 <div class="paragraph"><p>Then restart Nginx. The application has now been deployed.</p></div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="deploying_rails_to_sub_uri"></span><h3 data-comment-topic="deploying-to-a-sub-uri-1il2qj7" data-anchor="deploying_rails_to_sub_uri">3.2. Deploying to a sub URI</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="deploying_rails_to_sub_uri" data-comment-topic="deploying-to-a-sub-uri-1il2qj7">3.2. Deploying to a sub URI</h3>
 <div class="paragraph"><p>Suppose that you already have a <em>server</em> virtual host entry:</p></div>
 <div class="listingblock">
 <div class="content monospaced">
@@ -1614,9 +1484,9 @@ option to the <em>server</em> block:</p></div>
 </div>
 <div class="paragraph"><p>Then restart Nginx. The application has now been deployed.</p></div>
 <div class="admonitionblock">
-<table><tr>
+<table><tr>
 <td class="icon">
-<img src="./images/icons/tip.png" alt="Tip">
+<img src="./images/icons/tip.png" alt="Tip">
 </td>
 <td class="content">
 <div class="paragraph"><p>You can deploy multiple Rails applications under a virtual host, by specifying
@@ -1632,15 +1502,15 @@ option to the <em>server</em> block:</p></div>
 </div>
 </div>
 </td>
-</tr></table>
+</tr></table>
 </div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_redeploying_restarting_the_ruby_on_rails_application"></span><h3 data-comment-topic="redeploying-restarting-the-ruby-on-rails-application--1eso761" data-anchor="_redeploying_restarting_the_ruby_on_rails_application">3.3. Redeploying (restarting the Ruby on Rails application)</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_redeploying_restarting_the_ruby_on_rails_application" data-comment-topic="redeploying-restarting-the-ruby-on-rails-application--1eso761">3.3. Redeploying (restarting the Ruby on Rails application)</h3>
 <div class="paragraph"><p>Deploying a new version of a Ruby on Rails application is as simple as
 re-uploading the application files, and restarting the application.</p></div>
 <div class="paragraph"><p>There are two ways to restart the application:</p></div>
-<div class="olist arabic"><ol class="arabic">
+<div class="olist arabic"><ol class="arabic">
 <li>
 <p>
 By restarting Nginx.
@@ -1667,27 +1537,27 @@ of this file has changed in order to determine whether the application should
 be restarted.</p></div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_migrations"></span><h3 data-comment-topic="migrations-9yyb8w" data-anchor="_migrations">3.4. Migrations</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_migrations" data-comment-topic="migrations-9yyb8w">3.4. Migrations</h3>
 <div class="paragraph"><p>Phusion Passenger is not related to Ruby on Rails migrations in any way. To
 run migrations on your deployment server, please login to your deployment
 server (e.g. with <em>ssh</em>) and type <span class="monospaced">rake db:migrate RAILS_ENV=production</span> in
 a shell console, just like one would normally run migrations.</p></div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_capistrano_integration"></span><h3 data-comment-topic="capistrano-integration-1ktunm6" data-anchor="_capistrano_integration">3.5. Capistrano integration</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_capistrano_integration" data-comment-topic="capistrano-integration-1ktunm6">3.5. Capistrano integration</h3>
 <div class="paragraph"><p>See <a href="#capistrano">Capistrano recipe</a>.</p></div>
 </div>
 </div>
 </div>
 <div class="sect1">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="deploying_a_rack_app"></span><h2 data-comment-topic="deploying-a-rack-based-ruby-application-including-rails-3--12benx3" data-anchor="deploying_a_rack_app">4. Deploying a Rack-based Ruby application (including Rails &gt;= 3)</h2>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h2 id="deploying_a_rack_app" data-comment-topic="deploying-a-rack-based-ruby-application-including-rails-3--12benx3">4. Deploying a Rack-based Ruby application (including Rails &gt;= 3)</h2>
 <div class="sectionbody">
 <div class="paragraph"><p>Phusion Passenger supports arbitrary Ruby web applications that follow the
 <a href="http://rack.rubyforge.org/">Rack</a> interface.</p></div>
 <div class="paragraph"><p>Phusion Passenger assumes that Rack application directories have a certain layout.
 Suppose that you have a Rack application in <em>/webapps/rackapp</em>. Then that
 folder must contain at least three entries:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 <em>config.ru</em>, a Rackup file for starting the Rack application. This file must contain
@@ -1723,17 +1593,17 @@ to the virtual host’s root (i.e. the application will be accessible from the r
 <em>http://www.rackapp.com/</em>), or in a sub URI (i.e. the application will be
 accessible from a sub URL, such as <em>http://www.rackapp.com/rackapp</em>).</p></div>
 <div class="admonitionblock">
-<table><tr>
+<table><tr>
 <td class="icon">
-<img src="./images/icons/note.png" alt="Note">
+<img src="./images/icons/note.png" alt="Note">
 </td>
 <td class="content">The default <span class="monospaced">RACK_ENV</span> environment in which deployed Rack applications
 are run, is “production”. You can change this by changing the
 <a href="#RackEnv">rack_env</a> configuration option.</td>
-</tr></table>
+</tr></table>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_tutorial_example_writing_and_deploying_a_hello_world_rack_application"></span><h3 data-comment-topic="tutorial-example-writing-and-deploying-a-hello-world-rack-application-1wstx99" data-anchor="_tutorial_example_writing_and_deploying_a_hello_world_rack_application">4.1. Tutorial/example: writing and deploying a Hello World Rack application</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_tutorial_example_writing_and_deploying_a_hello_world_rack_application" data-comment-topic="tutorial-example-writing-and-deploying-a-hello-world-rack-application-1wstx99">4.1. Tutorial/example: writing and deploying a Hello World Rack application</h3>
 <div class="paragraph"><p>First we create a Phusion Passenger-compliant Rack directory structure:</p></div>
 <div class="listingblock">
 <div class="content monospaced">
@@ -1775,7 +1645,7 @@ the Nginx configuration file:</p></div>
 under the URL <em>http://www.rackexample.com/</em>.</p></div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_deploying_to_a_virtual_host_8217_s_root_2"></span><h3 data-comment-topic="deploying-to-a-virtual-host-s-root-f02erj" data-anchor="_deploying_to_a_virtual_host_8217_s_root_2">4.2. Deploying to a virtual host’s root</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_deploying_to_a_virtual_host_8217_s_root_2" data-comment-topic="deploying-to-a-virtual-host-s-root-f02erj">4.2. Deploying to a virtual host’s root</h3>
 <div class="paragraph"><p>Add a <em>server</em> virtual host entry to your Nginx configuration file. The virtual host’s
 root must point to your Rack application’s <em>public</em> folder. You must also set
 <em>passenger_enabled on</em> in the <em>server</em> block.</p></div>
@@ -1797,7 +1667,7 @@ root must point to your Rack application’s <em>public</em> folder. You must al
 <div class="paragraph"><p>Then restart Nginx. The application has now been deployed.</p></div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="deploying_rack_to_sub_uri"></span><h3 data-comment-topic="deploying-to-a-sub-uri-37q0ou" data-anchor="deploying_rack_to_sub_uri">4.3. Deploying to a sub URI</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="deploying_rack_to_sub_uri" data-comment-topic="deploying-to-a-sub-uri-37q0ou">4.3. Deploying to a sub URI</h3>
 <div class="paragraph"><p>Suppose that you already have a virtual host:</p></div>
 <div class="listingblock">
 <div class="content monospaced">
@@ -1845,9 +1715,9 @@ option to the <em>server</em> block:</p></div>
 </div>
 <div class="paragraph"><p>Then restart Nginx. The application has now been deployed.</p></div>
 <div class="admonitionblock">
-<table><tr>
+<table><tr>
 <td class="icon">
-<img src="./images/icons/tip.png" alt="Tip">
+<img src="./images/icons/tip.png" alt="Tip">
 </td>
 <td class="content">
 <div class="paragraph"><p>You can deploy multiple Rack applications under a virtual host, by specifying
@@ -1863,15 +1733,15 @@ option to the <em>server</em> block:</p></div>
 </div>
 </div>
 </td>
-</tr></table>
+</tr></table>
 </div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_redeploying_restarting_the_rack_application"></span><h3 data-comment-topic="redeploying-restarting-the-rack-application--xnbfam" data-anchor="_redeploying_restarting_the_rack_application">4.4. Redeploying (restarting the Rack application)</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_redeploying_restarting_the_rack_application" data-comment-topic="redeploying-restarting-the-rack-application--xnbfam">4.4. Redeploying (restarting the Rack application)</h3>
 <div class="paragraph"><p>Deploying a new version of a Rack application is as simple as
 re-uploading the application files, and restarting the application.</p></div>
 <div class="paragraph"><p>There are two ways to restart the application:</p></div>
-<div class="olist arabic"><ol class="arabic">
+<div class="olist arabic"><ol class="arabic">
 <li>
 <p>
 By restarting Nginx.
@@ -1894,10 +1764,10 @@ command line:</p></div>
 </div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_rackup_specifications_for_various_web_frameworks"></span><h3 data-comment-topic="rackup-specifications-for-various-web-frameworks-1a2cs41" data-anchor="_rackup_specifications_for_various_web_frameworks">4.5. Rackup specifications for various web frameworks</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_rackup_specifications_for_various_web_frameworks" data-comment-topic="rackup-specifications-for-various-web-frameworks-1a2cs41">4.5. Rackup specifications for various web frameworks</h3>
 <div class="paragraph"><p>This subsection shows example <em>config.ru</em> files for various web frameworks.</p></div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_camping"></span><h4 data-comment-topic="camping-16vz2yb" data-anchor="_camping">4.5.1. Camping</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_camping" data-comment-topic="camping-16vz2yb">4.5.1. Camping</h4>
 <div class="listingblock">
 <div class="content monospaced">
 <pre>require 'rubygems'
@@ -1916,7 +1786,7 @@ run Rack::Adapter::Camping.new(Blog)</pre>
 <div class="paragraph"><p>For Camping versions 2.0 and up, using <span class="monospaced">run Blog</span> as the final line will do.</p></div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_halcyon"></span><h4 data-comment-topic="halcyon-1benlfl" data-anchor="_halcyon">4.5.2. Halcyon</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_halcyon" data-comment-topic="halcyon-1benlfl">4.5.2. Halcyon</h4>
 <div class="listingblock">
 <div class="content monospaced">
 <pre>require 'rubygems'
@@ -1928,7 +1798,7 @@ run Halcyon::Runner.new</pre>
 </div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_mack"></span><h4 data-comment-topic="mack-1ezijq6" data-anchor="_mack">4.5.3. Mack</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_mack" data-comment-topic="mack-1ezijq6">4.5.3. Mack</h4>
 <div class="listingblock">
 <div class="content monospaced">
 <pre>ENV["MACK_ENV"] = ENV["RACK_ENV"]
@@ -1940,7 +1810,7 @@ run Mack::Utils::Server.build_app</pre>
 </div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_merb"></span><h4 data-comment-topic="merb-ddsh55" data-anchor="_merb">4.5.4. Merb</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_merb" data-comment-topic="merb-ddsh55">4.5.4. Merb</h4>
 <div class="listingblock">
 <div class="content monospaced">
 <pre>require 'rubygems'
@@ -1959,7 +1829,7 @@ run Merb::Rack::Application.new</pre>
 </div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_ramaze"></span><h4 data-comment-topic="ramaze-1p2zod" data-anchor="_ramaze">4.5.5. Ramaze</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_ramaze" data-comment-topic="ramaze-1p2zod">4.5.5. Ramaze</h4>
 <div class="listingblock">
 <div class="content monospaced">
 <pre>require "rubygems"
@@ -1972,7 +1842,7 @@ run Ramaze::Adapter::Base</pre>
 </div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_sinatra"></span><h4 data-comment-topic="sinatra-a7u9ag" data-anchor="_sinatra">4.5.6. Sinatra</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_sinatra" data-comment-topic="sinatra-a7u9ag">4.5.6. Sinatra</h4>
 <div class="listingblock">
 <div class="content monospaced">
 <pre>require 'rubygems'
@@ -1987,14 +1857,139 @@ run Sinatra::Application</pre>
 </div>
 </div>
 <div class="sect1">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_configuring_phusion_passenger"></span><h2 data-comment-topic="configuring-phusion-passenger-1g1svey" data-anchor="_configuring_phusion_passenger">5. Configuring Phusion Passenger</h2>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h2 id="_deploying_a_wsgi_python_application" data-comment-topic="deploying-a-wsgi-python-application-1or2efo">5. Deploying a WSGI (Python) application</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>Phusion Passenger supports all WSGI-compliant Python web applications. Suppose that you have a WSGI application in <em>/webapps/wsgiapp</em>. Then that folder must contain at least three entries:</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+<em>passenger_wsgi.py</em>, which Phusion Passenger will use as the main entry point for your application. This file must export a WSGI object called <span class="monospaced">application</span>.
+</p>
+</li>
+<li>
+<p>
+<em>public/</em>, a folder containing public static web assets, like images and stylesheets.
+</p>
+</li>
+<li>
+<p>
+<em>tmp/</em>, used for <em>restart.txt</em> (our application restart mechanism). This will be explained in a following subsection.
+</p>
+</li>
+</ul></div>
+<div class="paragraph"><p>So <em>/webapps/wsgiapp</em> must, at minimum, look like this:</p></div>
+<div class="listingblock">
+<div class="content monospaced">
+<pre>/webapps/wsgiapp
+  |
+  +-- config.ru
+  |
+  +-- public/
+  |
+  +-- tmp/</pre>
+</div>
+</div>
+<div class="sect2">
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_tutorial_example_writing_and_deploying_a_hello_world_wsgi_application" data-comment-topic="tutorial-example-writing-and-deploying-a-hello-world-wsgi-application-k5ron2">5.1. Tutorial/example: writing and deploying a Hello World WSGI application</h3>
+<div class="paragraph"><p>First we create a Phusion Passenger-compliant WSGI directory structure:</p></div>
+<div class="listingblock">
+<div class="content monospaced">
+<pre>$ mkdir /webapps/wsgi_example
+$ mkdir /webapps/wsgi_example/public
+$ mkdir /webapps/wsgi_example/tmp</pre>
+</div>
+</div>
+<div class="paragraph"><p>Next, we write a minimal "hello world" WSGI application:</p></div>
+<div class="listingblock">
+<div class="content monospaced">
+<pre>$ cd /webapps/wsgi_example
+$ some_awesome_editor passenger_wsgi.py
+...type in some source code...
+$ cat passenger_wsgi.py
+def application(environ, start_response):
+  start_response(200, [('Content-Type', 'text/plain')])
+  return ["hello world!\n"]</pre>
+</div>
+</div>
+<div class="paragraph"><p>Finally, we deploy it by adding the following configuration options to
+the Nginx configuration file:</p></div>
+<div class="listingblock">
+<div class="content monospaced">
+<pre>http {
+    ...
+    server {
+        listen 80;
+        server_name www.wsgiexample.com;
+        root /webapps/wsgi_example/public;
+        passenger_enabled on;
+    }
+    ...
+}</pre>
+</div>
+</div>
+<div class="paragraph"><p>And we’re done! After an Nginx restart, the above WSGI application will be available
+under the URL <em>http://www.wsgiexample.com/</em>.</p></div>
+</div>
+<div class="sect2">
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_deploying_to_a_virtual_host_8217_s_root_3" data-comment-topic="deploying-to-a-virtual-host-s-root-1chcpbj">5.2. Deploying to a virtual host’s root</h3>
+<div class="paragraph"><p>Add a <em>server</em> virtual host entry to your Nginx configuration file. The virtual host’s
+root must point to your WSGI application’s <em>public</em> folder. You must also set
+<em>passenger_enabled on</em> in the <em>server</em> block.</p></div>
+<div class="paragraph"><p>For example:</p></div>
+<div class="listingblock">
+<div class="content monospaced">
+<pre>http {
+    ...
+    server {
+        listen 80;
+        server_name www.wsgiapp.com;
+        root /webapps/wsgiapp/public;
+        passenger_enabled on;
+    }
+    ...
+}</pre>
+</div>
+</div>
+<div class="paragraph"><p>Then restart Nginx. The application has now been deployed.</p></div>
+</div>
+<div class="sect2">
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_redeploying_restarting_the_wsgi_application" data-comment-topic="redeploying-restarting-the-wsgi-application--10zdh2k">5.3. Redeploying (restarting the WSGI application)</h3>
+<div class="paragraph"><p>Deploying a new version of a WSGI application is as simple as
+re-uploading the application files, and restarting the application.</p></div>
+<div class="paragraph"><p>There are two ways to restart the application:</p></div>
+<div class="olist arabic"><ol class="arabic">
+<li>
+<p>
+By restarting Nginx.
+</p>
+</li>
+<li>
+<p>
+By creating or modifying the file <em>tmp/restart.txt</em> in the WSGI
+   application’s <a href="#application_root">root folder</a>. Phusion Passenger will
+   automatically restart the application.
+</p>
+</li>
+</ol></div>
+<div class="paragraph"><p>For example, to restart our example application, we type this in the
+command line:</p></div>
+<div class="listingblock">
+<div class="content monospaced">
+<pre>touch /webapps/wsgiapp/tmp/restart.txt</pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h2 id="_configuring_phusion_passenger" data-comment-topic="configuring-phusion-passenger-1g1svey">6. Configuring Phusion Passenger</h2>
 <div class="sectionbody">
 <div class="paragraph"><p>After installation, Phusion Passenger does not need any further configurations.
 Nevertheless, the system administrator may be interested in changing
 Phusion Passenger’s behavior. Phusion Passenger supports the following configuration
 options in the Nginx configuration file:</p></div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_passenger_root_lt_directory_gt"></span><h3 data-comment-topic="passenger-root-directory--bqvhhz" data-anchor="_passenger_root_lt_directory_gt">5.1. passenger_root &lt;directory&gt;</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_passenger_root_lt_directory_gt" data-comment-topic="passenger-root-directory--bqvhhz">6.1. passenger_root &lt;directory&gt;</h3>
 <div class="paragraph"><p>The location to the Phusion Passenger root directory. This configuration option
 is essential to Phusion Passenger, and allows Phusion Passenger to locate its own
 data files. The correct value is given by the installer.</p></div>
@@ -2004,17 +1999,38 @@ this option as well. Please read
 <div class="paragraph"><p>This required option may only occur once, in the <em>http</em> configuration block.</p></div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_passenger_ruby_lt_filename_gt"></span><h3 data-comment-topic="passenger-ruby-filename--1gnok5k" data-anchor="_passenger_ruby_lt_filename_gt">5.2. passenger_ruby &lt;filename&gt;</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_passenger_ruby_lt_filename_gt" data-comment-topic="passenger-ruby-filename--1gnok5k">6.2. passenger_ruby &lt;filename&gt;</h3>
 <div class="paragraph"><p>This option allows one to specify the Ruby interpreter to use.</p></div>
-<div class="paragraph"><p>This option may only occur once, in the <em>http</em> configuration block.
-The default is <em>ruby</em>.</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+In the <em>http</em> configuration block.
+</p>
+</li>
+<li>
+<p>
+In a <em>server</em> configuration block.
+</p>
+</li>
+<li>
+<p>
+In a <em>location</em> configuration block.
+</p>
+</li>
+<li>
+<p>
+In an <em>if</em> configuration scope.
+</p>
+</li>
+</ul></div>
+<div class="paragraph"><p>In each place, it may be specified at most once. The default value is <em>ruby</em>, meaning that the Ruby interpreter will be looked up according to the <span class="monospaced">PATH</span> environment variable.</p></div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerSpawnMethod"></span><h3 data-comment-topic="passenger-spawn-method-string--1sc6njl" data-anchor="PassengerSpawnMethod">5.3. passenger_spawn_method &lt;string&gt;</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="PassengerSpawnMethod" data-comment-topic="passenger-spawn-method-string--1sc6njl">6.3. passenger_spawn_method &lt;string&gt;</h3>
 <div class="admonitionblock">
-<table><tr>
+<table><tr>
 <td class="icon">
-<img src="./images/icons/tip.png" alt="Tip">
+<img src="./images/icons/tip.png" alt="Tip">
 </td>
 <td class="content">
 <div class="title">"What spawn method should I use?"</div>
@@ -2023,76 +2039,62 @@ understand it, as it’s mostly a technical detail. You can basically follow thi
 <div class="sidebarblock">
 <div class="content">
 <div class="paragraph"><p>If your application works on Mongrel, but not on Phusion Passenger, then set
-<span class="monospaced">passenger_spawn_method</span> to <em>conservative</em>. Otherwise, leave it at <em>smart-lv2</em> (the default).</p></div>
+<span class="monospaced">passenger_spawn_method</span> to <em>direct</em>. Otherwise, leave it at <em>smart</em> (the default).</p></div>
 </div>
 </div>
-<div class="paragraph"><p>However, we do recommend you to try to understand it. The <em>smart</em> and <em>smart-lv2</em> spawn
-methods bring many benefits.</p></div>
+<div class="paragraph"><p>However, we do recommend you to try to understand it. The <em>smart</em> spawn
+method brings many benefits.</p></div>
 </td>
-</tr></table>
+</tr></table>
 </div>
 <div class="paragraph"><p>Internally, Phusion Passenger spawns multiple Ruby application processes in order to handle
 requests. But there are multiple ways with which processes can be spawned, each having
 its own set of pros and cons. Supported spawn methods are:</p></div>
-<div class="dlist"><dl>
+<div class="dlist"><dl>
 <dt class="hdlist1">
 <em>smart</em>
 </dt>
 <dd>
 <p>
-When this spawn method is used, Phusion Passenger will attempt to cache any
-framework code (e.g. Ruby on Rails itself) and application code for a limited
-period of time. Please read <a href="#spawning_methods_explained">Spawning methods explained</a>
-for a more detailed explanation of what smart spawning exactly does.
-</p>
-<div class="paragraph"><p><strong>Pros:</strong>
-This can significantly decrease spawn time (by as much as 90%). And, when Ruby Enterprise
-Edition is used, <a href="#reducing_memory_usage">memory usage can be reduced by 33% on average</a>.</p></div>
-<div class="paragraph"><p><strong>Cons:</strong>
-Some applications and libraries are not compatible with smart spawning.
-If that’s the case for your application, then you should use <em>conservative</em> as
-spawning method. Please read <a href="#spawning_methods_explained">Spawning methods explained</a>
-for possible compatibility issues.</p></div>
-</dd>
-<dt class="hdlist1">
-<em>smart-lv2</em>
-</dt>
-<dd>
-<p>
-This spawning method is similar to <em>smart</em> but it skips the framework spawner
-and uses the application spawner directly. This means the framework code is not
-cached between multiple applications, although it is still cached within
+This spawning method caches code using the app preloader. Framework code is not
+cached between multiple applications, although it is cached within
 instances of the same application. Please read
 <a href="#spawning_methods_explained">Spawning methods explained</a> for a more detailed
-explanation of what smart-lv2 spawning exactly does.
+explanation of what smart spawning exactly does.
 </p>
-<div class="paragraph"><p><strong>Pros:</strong> It is compatible with a larger number of applications when compared to
-the <em>smart</em> method, and still performs some caching.</p></div>
-<div class="paragraph"><p><strong>Cons:</strong> It is slower than smart spawning if you have many applications which
-use the same framework version. It is therefore advised that shared hosts use the
-<em>smart</em> method instead.</p></div>
+<div class="paragraph"><p><strong>Pros:</strong>
+Smart spawning caches code where possible to speed up the respawn process
+and is compatible with most applications</p></div>
+<div class="paragraph"><p><strong>Cons:</strong>
+It is possible that it may be incompatible with some applications</p></div>
 </dd>
 <dt class="hdlist1">
-<em>conservative</em>
+<em>direct</em>
 </dt>
 <dd>
 <p>
 This spawning method is similar to the one used in Mongrel Cluster. It does not
 perform any code caching at all. Please read
 <a href="#spawning_methods_explained">Spawning methods explained</a> for a more detailed
-explanation of what conservative spawning exactly does.
+explanation of what direct spawning exactly does.
 </p>
 <div class="paragraph"><p><strong>Pros:</strong>
-Conservative spawning is guaranteed to be compatible with all applications
+Direct spawning is guaranteed to be compatible with all applications
 and libraries.</p></div>
 <div class="paragraph"><p><strong>Cons:</strong>
 Much slower than smart spawning. Every spawn action will be equally slow, though no slower than
-the startup time of a single server in Mongrel Cluster. Conservative spawning will also
+the startup time of a single server in Mongrel Cluster. Direct spawning will also
 render <a href="#reducing_memory_usage">Ruby Enterprise Edition’s memory reduction technology</a> useless.</p></div>
 </dd>
 </dl></div>
+<div class="sidebarblock">
+<div class="content">
+<div class="paragraph"><p>As of Passenger 3.2, <em>conservative</em> spawning was renamed to <em>direct</em> and <em>smart-lv2</em> was renamed
+to <em>smart</em>. The old <em>smart</em> spawning has been removed in favor of the new version.</p></div>
+</div>
+</div>
 <div class="paragraph"><p>This option may occur in the following places:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 In the <em>http</em> configuration block.
@@ -2114,10 +2116,10 @@ In an <em>if</em> configuration scope.
 </p>
 </li>
 </ul></div>
-<div class="paragraph"><p>In each place, it may be specified at most once. The default value is <em>smart-lv2</em>.</p></div>
+<div class="paragraph"><p>In each place, it may be specified at most once. The default value is <em>smart</em>.</p></div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerRollingRestarts"></span><h3 data-comment-topic="passenger-rolling-restarts" data-anchor="PassengerRollingRestarts">5.4. passenger_rolling_restarts &lt;on|off&gt;</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="PassengerRollingRestarts" data-comment-topic="passenger-rolling-restarts">6.4. passenger_rolling_restarts &lt;on|off&gt;</h3>
 <div class="paragraph"><p><strong>This feature is only available in <a href="https://www.phusionpassenger.com/enterprise">Phusion Passenger Enterprise</a>. It was introduced in version 3.0.0. <a href="https://www.phusionpassenger.com/download">Buy Phusion Passenger Enterprise here.</a></strong></p></div>
 <div class="paragraph"><p>Enables or disables support for rolling restarts. Normally when you
 restart an application (by touching restart.txt), Phusion Passenger would
@@ -2126,7 +2128,7 @@ of a new application process could take a while, and any requests that
 come in during this time will be blocked until this first application
 process has spawned.</p></div>
 <div class="paragraph"><p>But when rolling restarts are enabled, Phusion Passenger Enterprise will:</p></div>
-<div class="olist arabic"><ol class="arabic">
+<div class="olist arabic"><ol class="arabic">
 <li>
 <p>
 Spawn a new process in the background.
@@ -2145,7 +2147,7 @@ Step 1 and 2 are repeated until all processes have been replaced.
 </ol></div>
 <div class="paragraph"><p>This way, visitors will not experience any delays when you are restarting your application. This allows you to, for example, upgrade your application often without degrading user experience.</p></div>
 <div class="paragraph"><p>Rolling restarts have a few caveat however that you should be aware of:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 Upgrading an application sometimes involves upgrading the database schema.
@@ -2165,7 +2167,7 @@ Because there’s no telling which process will serve a request, users may
 </li>
 </ul></div>
 <div class="paragraph"><p>This option may occur in the following places:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 In the <em>http</em> configuration block.
@@ -2190,12 +2192,12 @@ In an <em>if</em> configuration scope.
 <div class="paragraph"><p>In each place, it may be specified at most once. The default value is <em>off</em>.</p></div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_passenger_resist_deployment_errors_lt_on_off_gt"></span><h3 data-comment-topic="passenger-resist-deployment-errors-on-off--k9yf1" data-anchor="_passenger_resist_deployment_errors_lt_on_off_gt">5.5. passenger_resist_deployment_errors &lt;on|off&gt;</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_passenger_resist_deployment_errors_lt_on_off_gt" data-comment-topic="passenger-resist-deployment-errors-on-off--k9yf1">6.5. passenger_resist_deployment_errors &lt;on|off&gt;</h3>
 <div class="paragraph"><p><strong>This feature is only available in <a href="https://www.phusionpassenger.com/enterprise">Phusion Passenger Enterprise</a>. It was introduced in version 3.0.0. <a href="https://www.phusionpassenger.com/download">Buy Phusion Passenger Enterprise here.</a></strong></p></div>
 <div class="paragraph"><p>Enables or disables resistance against deployment errors.</p></div>
 <div class="paragraph"><p>Suppose you’ve upgraded your application and you’ve issues a command to restart it (by touching restart.txt), but the application code contains an error that prevents Phusion Passenger from successfully spawning a process (e.g. a syntax error). Phusion Passenger would normally display an error message in response to this.</p></div>
 <div class="paragraph"><p>By enabling deployment error resistance, Phusion Passenger Enterprise would instead do this:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 It passes the request to one of the existing application processes (that belong to the previous version of the application). The visitor will not see a Phusion Passenger process spawning error message.
@@ -2215,7 +2217,7 @@ It sets an internal flag so that no processes for this application will be spawn
 <div class="paragraph"><p>This way, visitors will suffer minimally from deployment errors. Phusion Passenger will attempt to restart the application again next time restart.txt is touched.</p></div>
 <div class="paragraph"><p>Enabling deployment error resistance only works if <a href="#PassengerRollingRestarts">rolling restart</a> is also enabled.</p></div>
 <div class="paragraph"><p>This option may occur in the following places:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 In the <em>http</em> configuration block.
@@ -2240,9 +2242,9 @@ In an <em>if</em> configuration scope.
 <div class="paragraph"><p>In each place, it may be specified at most once. The default value is <em>off</em>.</p></div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_important_deployment_options"></span><h3 data-comment-topic="important-deployment-options-av567" data-anchor="_important_deployment_options">5.6. Important deployment options</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_important_deployment_options" data-comment-topic="important-deployment-options-av567">6.6. Important deployment options</h3>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_passenger_enabled_lt_on_off_gt"></span><h4 data-comment-topic="passenger-enabled-on-off--1rpb2t7" data-anchor="_passenger_enabled_lt_on_off_gt">5.6.1. passenger_enabled &lt;on|off&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_passenger_enabled_lt_on_off_gt" data-comment-topic="passenger-enabled-on-off--1rpb2t7">6.6.1. passenger_enabled &lt;on|off&gt;</h4>
 <div class="paragraph"><p>This option may be specified in the <em>http</em> configuration block, a
 <em>server</em> configuration block, a <em>location</em> configuration block or
 an <em>if</em> configuration scope, to enable or disable Phusion Passenger
@@ -2254,7 +2256,7 @@ and <a href="#deploying_a_rack_app">Deploying a Rack-based Ruby application</a>
 for examples.</p></div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerBaseURI"></span><h4 data-comment-topic="passenger-base-uri-uri--1xtuo50" data-anchor="PassengerBaseURI">5.6.2. passenger_base_uri &lt;uri&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="PassengerBaseURI" data-comment-topic="passenger-base-uri-uri--1xtuo50">6.6.2. passenger_base_uri &lt;uri&gt;</h4>
 <div class="paragraph"><p>Used to specify that the given URI is an distinct application that should
 be served by Phusion Passenger. This option can be used for both Rails and
 Rack applications. See <a href="#deploying_rails_to_sub_uri">Deploying Rails to a sub URI</a>
@@ -2262,7 +2264,7 @@ for an example.</p></div>
 <div class="paragraph"><p>It is allowed to specify this option multiple times. Do this to deploy multiple
 applications in different sub-URIs under the same virtual host.</p></div>
 <div class="paragraph"><p>This option may occur in the following places:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 In the <em>http</em> configuration block.
@@ -2287,116 +2289,9 @@ In an <em>if</em> configuration scope.
 </div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_connection_handling_options"></span><h3 data-comment-topic="connection-handling-options-8jgq90" data-anchor="_connection_handling_options">5.7. Connection handling options</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_connection_handling_options" data-comment-topic="connection-handling-options-8jgq90">6.7. Connection handling options</h3>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerUseGlobalQueue"></span><h4 data-comment-topic="passenger-use-global-queue-on-off--14h9n22" data-anchor="PassengerUseGlobalQueue">5.7.1. passenger_use_global_queue &lt;on|off&gt;</h4>
-<div class="paragraph"><p>Turns the use of global queuing on or off.</p></div>
-<div class="paragraph"><p>This option may occur in the following places:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-In the <em>http</em> configuration block.
-</p>
-</li>
-<li>
-<p>
-In a <em>server</em> configuration block.
-</p>
-</li>
-<li>
-<p>
-In a <em>location</em> configuration block.
-</p>
-</li>
-<li>
-<p>
-In an <em>if</em> configuration scope.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>In each place, it may be specified at most once. The default value is <em>on</em>.</p></div>
-<div class="paragraph"><p><em>This feature is sponsored by <a href="http://www.37signals.com/">37signals</a>.</em></p></div>
-<div class="paragraph">
-<div class="title">What does this option do?</div>
-<p>Recall that Phusion Passenger spawns multiple backend processes (e.g. multiple
-Ruby on Rails processes), each which processes HTTP requests serially. One of
-Phusion Passenger’s jobs is to forward HTTP requests to a suitable backend
-process. A backend process may take an arbitrary amount of time to process a
-specific HTTP request. If the websites are (temporarily) under high load, and
-the backend processes cannot process the requests fast enough, then some
-requests may have to be queued.</p>
-</div>
-<div class="paragraph"><p>If global queuing is turned off, then Phusion Passenger will use <em>fair load
-balancing</em>. This means that each backend process will have its own private
-queue. Phusion Passenger will forward an HTTP request to the backend process
-that has the least amount of requests in its queue.</p></div>
-<div class="paragraph"><p>If global queuing is turned on, then Phusion Passenger will use a global queue
-that’s shared between all backend processes. If an HTTP request comes in, and
-all the backend processes are still busy, then Phusion Passenger will wait until
-at least one backend process is done, and will then forward the request to that
-process.</p></div>
-<div class="paragraph">
-<div class="title">When to turn on global queuing?</div>
-<p>You should turn on global queuing if one of your web applications may have
-long-running requests.</p>
-</div>
-<div class="paragraph"><p>For example suppose that:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-global queuing is turned off.
-</p>
-</li>
-<li>
-<p>
-we’re currently in a state where all backend processes have 3 requests in
-  their queue, except for a single backend process, which has 1 request in its
-  queue.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>The situation looks like this:</p></div>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>Backend process A:  [*     ]  (1 request in queue)
-Backend process B:  [***   ]  (3 requests in queue)
-Backend process C:  [***   ]  (3 requests in queue)
-Backend process D:  [***   ]  (3 requests in queue)</pre>
-</div>
-</div>
-<div class="paragraph"><p>Each process is currently serving short-running requests.</p></div>
-<div class="paragraph"><p>Phusion Passenger will forward the next request to backend process A. A will
-now have 2 items in its queue. We’ll mark this new request with an X:</p></div>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>Backend process A:  [*X    ]  (2 request in queue)
-Backend process B:  [***   ]  (3 requests in queue)
-Backend process C:  [***   ]  (3 requests in queue)
-Backend process D:  [***   ]  (3 requests in queue)</pre>
-</div>
-</div>
-<div class="paragraph"><p>Assuming that B, C and D still aren’t done with their current request, the next
-HTTP request - let’s call this Y - will be forwarded to backend process A as
-well, because it has the least number of items in its queue:</p></div>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>Backend process A:  [*XY   ]  (3 requests in queue)
-Backend process B:  [***   ]  (3 requests in queue)
-Backend process C:  [***   ]  (3 requests in queue)
-Backend process D:  [***   ]  (3 requests in queue)</pre>
-</div>
-</div>
-<div class="paragraph"><p>But if request X happens to be a long-running request that needs 60 seconds to
-complete, then we’ll have a problem. Y won’t be processed for at least 60
-seconds. It would have been a better idea if Y was forward to processes B, C or
-D instead, because they only have short-living requests in their queues.</p></div>
-<div class="paragraph"><p>This problem will be avoided entirely if you turn global queuing on. With global
-queuing, all backend processes will share the same queue. The first backend
-process that becomes available will take from the queue, and so this
-“queuing-behind-long-running-request” problem will never occur.</p></div>
-</div>
-<div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_passenger_ignore_client_abort_lt_on_off_gt"></span><h4 data-comment-topic="passenger-ignore-client-abort" data-anchor="_passenger_ignore_client_abort_lt_on_off_gt">5.7.2. passenger_ignore_client_abort &lt;on|off&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_passenger_ignore_client_abort_lt_on_off_gt" data-comment-topic="passenger-ignore-client-abort">6.7.1. passenger_ignore_client_abort &lt;on|off&gt;</h4>
 <div class="paragraph"><p>Normally, when the HTTP client aborts the connection (e.g. when the user clicked on "Stop"
 in the browser), the connection with the application process will be closed too. If the
 application process continues to send its response, then that will result in EPIPE errors
@@ -2407,7 +2302,7 @@ read the application process’s response while discarding all the read data. Th
 EPIPE errors but it’ll also mean the backend process will be unavailable for new requests
 until it is done sending its response.</p></div>
 <div class="paragraph"><p>This option may occur in the following places:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 In the <em>http</em> configuration block.
@@ -2432,7 +2327,7 @@ In an <em>if</em> configuration scope.
 <div class="paragraph"><p>In each place, it may be specified at most once. The default value is <em>off</em>.</p></div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_passenger_set_cgi_param_lt_cgi_environment_name_gt_lt_value_gt"></span><h4 data-comment-topic="passenger-set-cgi-param-cgi-environment-name-value--rx9gc0" data-anchor="_passenger_set_cgi_param_lt_cgi_environment_name_gt_lt_value_gt">5.7.3. passenger_set_cgi_param &lt;CGI environment name&gt; &lt;value&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_passenger_set_cgi_param_lt_cgi_environment_name_gt_lt_value_gt" data-comment-topic="passenger-set-cgi-param-cgi-environment-name-value--rx9gc0">6.7.2. passenger_set_cgi_param &lt;CGI environment name&gt; &lt;value&gt;</h4>
 <div class="paragraph"><p>Allows one to define additional CGI environment variables to pass to the backend
 application. This is equivalent to ngx_http_fastcgi_module’s <em>fastcgi_param</em>
 directive, and is comparable to ngx_http_proxy_module’s <em>proxy_set_header</em> option.
@@ -2459,7 +2354,7 @@ passenger_set_cgi_param HTTP_X_FORWARDED_FOR 127.0.0.2;</pre>
 </div>
 </div>
 <div class="paragraph"><p>This option may occur in the following places:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 In the <em>http</em> configuration block.
@@ -2483,7 +2378,7 @@ In an <em>if</em> configuration scope.
 </ul></div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_passenger_pass_header_lt_header_name_gt"></span><h4 data-comment-topic="passenger-pass-header-header-name--1cg31je" data-anchor="_passenger_pass_header_lt_header_name_gt">5.7.4. passenger_pass_header &lt;header name&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_passenger_pass_header_lt_header_name_gt" data-comment-topic="passenger-pass-header-header-name--1cg31je">6.7.3. passenger_pass_header &lt;header name&gt;</h4>
 <div class="paragraph"><p>Some headers generated by backend applications are not forwarded to the HTTP client,
 e.g. <em>X-Accel-Redirect</em> which is directly processed by Nginx and then discarded from
 the final response. This directive allows one to force Nginx to pass those headers
@@ -2497,7 +2392,7 @@ anyway, similar to how <em>proxy_pass_header</em> works.</p></div>
 </div>
 </div>
 <div class="paragraph"><p>This option may occur in the following places:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 In the <em>http</em> configuration block.
@@ -2521,7 +2416,7 @@ In an <em>if</em> configuration scope.
 </ul></div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_passenger_buffer_response_lt_on_off_gt"></span><h4 data-comment-topic="passenger-buffer-response" data-anchor="_passenger_buffer_response_lt_on_off_gt">5.7.5. passenger_buffer_response &lt;on|off&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_passenger_buffer_response_lt_on_off_gt" data-comment-topic="passenger-buffer-response">6.7.4. passenger_buffer_response &lt;on|off&gt;</h4>
 <div class="paragraph"><p>When turned on, application-generated responses are buffered in memory and also on
 disk if the response is larger than a certain threshold. By buffering responses,
 protection is provided against slow HTTP clients that can not read your response
@@ -2569,7 +2464,7 @@ after which it receives the entire response at once.
 When response buffering is turned off, it works as expected: the client
 receives an "entry X" message every second for 10 seconds.</p></div>
 <div class="paragraph"><p>This option may occur in the following places:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 In the <em>http</em> configuration block.
@@ -2594,34 +2489,34 @@ In an <em>if</em> configuration scope.
 <div class="paragraph"><p>In each place, it may be specified at most once. The default value is <em>on</em>.</p></div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_passenger_buffer_size"></span><h4 data-comment-topic="passenger-buffer-size-1jfkq87" data-anchor="_passenger_buffer_size">5.7.6. passenger_buffer_size</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_passenger_buffer_size" data-comment-topic="passenger-buffer-size-1jfkq87">6.7.5. passenger_buffer_size</h4>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_passenger_buffers"></span><h4 data-comment-topic="passenger-busy-buffers" data-anchor="_passenger_buffers">5.7.7. passenger_buffers</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_passenger_buffers" data-comment-topic="passenger-busy-buffers">6.7.6. passenger_buffers</h4>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_passenger_busy_buffer_size"></span><h4 data-comment-topic="passenger-busy-buffer-size-124sj61" data-anchor="_passenger_busy_buffer_size">5.7.8. passenger_busy_buffer_size</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_passenger_busy_buffer_size" data-comment-topic="passenger-busy-buffer-size-124sj61">6.7.7. passenger_busy_buffer_size</h4>
 <div class="paragraph"><p>These options have the same effect as proxy_module’s similarly named options.
 They can be used to modify the maximum allowed HTTP header size.</p></div>
 </div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_security_options"></span><h3 data-comment-topic="security-options-1bv93g4" data-anchor="_security_options">5.8. Security options</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_security_options" data-comment-topic="security-options-1bv93g4">6.8. Security options</h3>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerUserSwitching"></span><h4 data-comment-topic="passenger-user-switching-on-off--1p37u3l" data-anchor="PassengerUserSwitching">5.8.1. passenger_user_switching &lt;on|off&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="PassengerUserSwitching" data-comment-topic="passenger-user-switching-on-off--1p37u3l">6.8.1. passenger_user_switching &lt;on|off&gt;</h4>
 <div class="paragraph"><p>Whether to enable <a href="#user_switching">user switching support</a>.</p></div>
 <div class="paragraph"><p>This option may only occur once, in the <em>http</em> configuration block.
 The default value is <em>on</em>.</p></div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_passenger_user_lt_username_gt"></span><h4 data-comment-topic="passenger-user-username--b06ur7" data-anchor="_passenger_user_lt_username_gt">5.8.2. passenger_user &lt;username&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_passenger_user_lt_username_gt" data-comment-topic="passenger-user-username--b06ur7">6.8.2. passenger_user &lt;username&gt;</h4>
 <div class="paragraph"><p>If <a href="#user_switching">user switching support</a> is enabled, then Phusion Passenger will
 by default run the web application as the owner of the file <em>config/environment.rb</em>
 (for Rails apps) or <em>config.ru</em> (for Rack apps). This option allows you to override
 that behavior and explicitly set a user to run the web application as, regardless
 of the ownership of <em>environment.rb</em>/<em>config.ru</em>.</p></div>
 <div class="paragraph"><p>This option may occur in the following places:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 In the <em>http</em> configuration block.
@@ -2646,7 +2541,7 @@ In an <em>if</em> configuration scope.
 <div class="paragraph"><p>In each place, it may be specified at most once.</p></div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_passenger_group_lt_group_name_gt"></span><h4 data-comment-topic="passenger-user-group-name--1fco4j7" data-anchor="_passenger_group_lt_group_name_gt">5.8.3. passenger_group &lt;group name&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_passenger_group_lt_group_name_gt" data-comment-topic="passenger-user-group-name--1fco4j7">6.8.3. passenger_group &lt;group name&gt;</h4>
 <div class="paragraph"><p>If <a href="#user_switching">user switching support</a> is enabled, then Phusion Passenger will
 by default run the web application as the primary group of the owner of the file
 <em>config/environment.rb</em> (for Rails apps) or <em>config.ru</em> (for Rack apps). This option
@@ -2655,7 +2550,7 @@ as, regardless of the ownership of <em>environment.rb</em>/<em>config.ru</em>.</
 <div class="paragraph"><p><em>&lt;group name&gt;</em> may also be set to the special value <em>!STARTUP_FILE!</em>, in which case
 the web application’s group will be set to <em>environment.rb</em>/<em>config.ru</em>'s group.</p></div>
 <div class="paragraph"><p>This option may occur in the following places:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 In the <em>http</em> configuration block.
@@ -2680,7 +2575,7 @@ In an <em>if</em> configuration scope.
 <div class="paragraph"><p>In each place, it may be specified at most once.</p></div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerDefaultUser"></span><h4 data-comment-topic="passenger-default-user-username--1h6cdmf" data-anchor="PassengerDefaultUser">5.8.4. passenger_default_user &lt;username&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="PassengerDefaultUser" data-comment-topic="passenger-default-user-username--1h6cdmf">6.8.4. passenger_default_user &lt;username&gt;</h4>
 <div class="paragraph"><p>Phusion Passenger enables <a href="#user_switching">user switching support</a> by default.
 This configuration option allows one to specify the user that applications must
 run as, if user switching fails or is disabled.</p></div>
@@ -2688,7 +2583,7 @@ run as, if user switching fails or is disabled.</p></div>
 The default value is <em>nobody</em>.</p></div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerDefaultGroup"></span><h4 data-comment-topic="passenger-default-group-group-name--1qxn2qa" data-anchor="PassengerDefaultGroup">5.8.5. Passenger_default_group &lt;group name&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="PassengerDefaultGroup" data-comment-topic="passenger-default-group-group-name--1qxn2qa">6.8.5. Passenger_default_group &lt;group name&gt;</h4>
 <div class="paragraph"><p>Phusion Passenger enables <a href="#user_switching">user switching support</a> by default.
 This configuration option allows one to specify the group that applications must
 run as, if user switching fails or is disabled.</p></div>
@@ -2697,7 +2592,7 @@ The default value is the primary group of the user specifified by
 <a href="#PassengerDefaultUser">passenger_default_user</a>.</p></div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_passenger_friendly_error_pages_lt_on_off_gt"></span><h4 data-comment-topic="passenger-friendly-error-pages-on-off--1ti1a0e" data-anchor="_passenger_friendly_error_pages_lt_on_off_gt">5.8.6. passenger_friendly_error_pages &lt;on|off&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_passenger_friendly_error_pages_lt_on_off_gt" data-comment-topic="passenger-friendly-error-pages-on-off--1ti1a0e">6.8.6. passenger_friendly_error_pages &lt;on|off&gt;</h4>
 <div class="paragraph"><p>Phusion Passenger can display friendly error pages whenever an application fails
 to start. This friendly error page presents the startup error message, some
 suggestions for solving the problem, and a backtrace. This feature is very useful
@@ -2706,7 +2601,7 @@ but the page might reveal potentially sensitive information, depending on the
 application. Experienced system administrators who are using Phusion Passenger
 on serious production servers should consider turning this feature off.</p></div>
 <div class="paragraph"><p>This option may occur in the following places:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 In the <em>http</em> configuration block.
@@ -2732,9 +2627,9 @@ In an <em>if</em> configuration scope.
 </div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_resource_control_and_optimization_options"></span><h3 data-comment-topic="resource-control-and-optimization-options-xd7evs" data-anchor="_resource_control_and_optimization_options">5.9. Resource control and optimization options</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_resource_control_and_optimization_options" data-comment-topic="resource-control-and-optimization-options-xd7evs">6.9. Resource control and optimization options</h3>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerMaxPoolSize"></span><h4 data-comment-topic="passenger-max-pool-size-integer--3jzefs" data-anchor="PassengerMaxPoolSize">5.9.1. passenger_max_pool_size &lt;integer&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="PassengerMaxPoolSize" data-comment-topic="passenger-max-pool-size-integer--3jzefs">6.9.1. passenger_max_pool_size &lt;integer&gt;</h4>
 <div class="paragraph"><p>The maximum number of <a href="#application_process">application processes</a> that may
 simultanously exist. A larger number results in higher memory usage,
 but improved ability to handle concurrent HTTP clients.</p></div>
@@ -2751,24 +2646,24 @@ hardware or getting more servers.)</p></div>
 <div class="paragraph"><p>This option may only occur once, in the <em>http</em> configuration bock.
 The default value is <em>6</em>.</p></div>
 <div class="admonitionblock">
-<table><tr>
+<table><tr>
 <td class="icon">
-<img src="./images/icons/tip.png" alt="Tip">
+<img src="./images/icons/tip.png" alt="Tip">
 </td>
 <td class="content">We strongly recommend you to <a href="#reducing_memory_usage">use Ruby Enterprise Edition</a>. This allows you to reduce the memory usage of your Ruby on Rails applications
 by about 33%, and it’s not hard to install.</td>
-</tr></table>
+</tr></table>
 </div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerMinInstances"></span><h4 data-comment-topic="passenger-min-instances-integer--uclykt" data-anchor="PassengerMinInstances">5.9.2. passenger_min_instances &lt;integer&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="PassengerMinInstances" data-comment-topic="passenger-min-instances-integer--uclykt">6.9.2. passenger_min_instances &lt;integer&gt;</h4>
 <div class="paragraph"><p>This specifies the minimum number of application processes that should exist for a
 given application. You should set this option to a
 non-zero value if you want to avoid potentially long startup times after a website
 has been <a href="#idle_process">idle</a> for an extended period.</p></div>
 <div class="paragraph"><p>Please note that this option does <strong>not</strong> pre-start application processes during Nginx
 startup. It just makes sure that when the application is first accessed:</p></div>
-<div class="olist arabic"><ol class="arabic">
+<div class="olist arabic"><ol class="arabic">
 <li>
 <p>
 at least the given number of processes will be spawned.
@@ -2811,7 +2706,7 @@ simultanously. Phusion Passenger will start 12 more application processes. After
 timeout of 10 seconds have passed, Phusion Passenger will clean up 12 application
 processes, keeping 3 processes around.</p></div>
 <div class="paragraph"><p>The passenger_min_instances option may occur in the following places:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 In the <em>http</em> configuration block.
@@ -2836,7 +2731,7 @@ In an <em>if</em> configuration scope.
 <div class="paragraph"><p>In each place, it may be specified at most once. The default value is <em>1</em>.</p></div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_passenger_max_instances_lt_integer_gt"></span><h4 data-comment-topic="passenger-max-instances" data-anchor="_passenger_max_instances_lt_integer_gt">5.9.3. passenger_max_instances &lt;integer&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_passenger_max_instances_lt_integer_gt" data-comment-topic="passenger-max-instances">6.9.3. passenger_max_instances &lt;integer&gt;</h4>
 <div class="paragraph"><p><strong>This feature is only available in <a href="https://www.phusionpassenger.com/enterprise">Phusion Passenger Enterprise</a>. It was introduced in version 3.0.0. <a href="https://www.phusionpassenger.com/download">Buy Phusion Passenger Enterprise here.</a></strong></p></div>
 <div class="paragraph"><p>The maximum number of application processes that may simultaneously exist
 for an application. This helps to make sure that a single application
@@ -2846,7 +2741,7 @@ means that there is no limit placed on the number of processes a single applicat
 may spawn, i.e. only the global limit of <a href="#PassengerMaxPoolSize">passenger_max_pool_size</a>
 will be enforced.</p></div>
 <div class="paragraph"><p>This option may occur in the following places:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 In the <em>http</em> configuration block.
@@ -2870,9 +2765,9 @@ In an <em>if</em> configuration scope.
 </ul></div>
 <div class="paragraph"><p>In each place, it may be specified at most once. The default value is <em>0</em>.</p></div>
 <div class="admonitionblock">
-<table><tr>
+<table><tr>
 <td class="icon">
-<img src="./images/icons/tip.png" alt="Tip">
+<img src="./images/icons/tip.png" alt="Tip">
 </td>
 <td class="content">
 <div class="title">Practical usage example</div>
@@ -2883,11 +2778,11 @@ to 10. The e-commerce website is more important to you. You can then set
 than 3 processes, even if it suddenly gets a lot of traffic. Your e-commerce website
 on the other hand will be free to spawn up to 10 processes if it gets a lot of traffic.</p></div>
 </td>
-</tr></table>
+</tr></table>
 </div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_passenger_max_instances_per_app_lt_integer_gt"></span><h4 data-comment-topic="passenger-max-instances-per-app-integer--1xhbbne" data-anchor="_passenger_max_instances_per_app_lt_integer_gt">5.9.4. passenger_max_instances_per_app &lt;integer&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_passenger_max_instances_per_app_lt_integer_gt" data-comment-topic="passenger-max-instances-per-app-integer--1xhbbne">6.9.4. passenger_max_instances_per_app &lt;integer&gt;</h4>
 <div class="paragraph"><p>The maximum number of application processes that may simultaneously exist
 for a single application. This helps to make sure that a single application
 will not occupy all available slots in the application pool.</p></div>
@@ -2899,7 +2794,7 @@ will be enforced.</p></div>
 The default value is <em>0</em>.</p></div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerPoolIdleTime"></span><h4 data-comment-topic="passenger-pool-idle-time-integer--xcw65o" data-anchor="PassengerPoolIdleTime">5.9.5. passenger_pool_idle_time &lt;integer&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="PassengerPoolIdleTime" data-comment-topic="passenger-pool-idle-time-integer--xcw65o">6.9.5. passenger_pool_idle_time &lt;integer&gt;</h4>
 <div class="paragraph"><p>The maximum number of seconds that an application process may be idle. That is,
 if an application process hasn’t received any traffic after the given number of
 seconds, then it will be shutdown in order to conserve memory.</p></div>
@@ -2921,7 +2816,116 @@ applications, each which must be available at all times.</p></div>
 The default value is <em>300</em>.</p></div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerMaxRequests"></span><h4 data-comment-topic="passenger-max-requests" data-anchor="PassengerMaxRequests">5.9.6. passenger_max_requests &lt;integer&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_passenger_max_preloader_idle_time_lt_integer_gt" data-comment-topic="rails-app-spawner-idle-time-integer--1xjqe4b">6.9.6. passenger_max_preloader_idle_time &lt;integer&gt;</h4>
+<div class="paragraph"><p>The ApplicationSpawner server (explained in <a href="#spawning_methods_explained">Spawning methods explained</a>) has an idle timeout, just like the backend processes spawned by
+Phusion Passenger do. That is, it will automatically shutdown if it hasn’t done
+anything for a given period.</p></div>
+<div class="paragraph"><p>This option allows you to set the ApplicationSpawner server’s idle timeout, in
+seconds. A value of <em>0</em> means that it should never idle timeout.</p></div>
+<div class="paragraph"><p>Setting a higher value will mean that the ApplicationSpawner server is kept around
+longer, which may slightly increase memory usage. But as long as the
+ApplicationSpawner server is running, the time to spawn a Ruby on Rails backend
+process only takes about 10% of the time that is normally needed, assuming that
+you’re using the <em>smart</em> or <em>smart-lv2</em> <a href="#RailsSpawnMethod">spawning method</a>. So if your
+system has enough memory, is it recommended that you set this option to a high
+value or to <em>0</em>.</p></div>
+<div class="paragraph"><p>This option may occur in the following places:</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+In the <em>http</em> configuration block.
+</p>
+</li>
+<li>
+<p>
+In a <em>server</em> configuration block.
+</p>
+</li>
+<li>
+<p>
+In a <em>location</em> configuration block.
+</p>
+</li>
+<li>
+<p>
+In an <em>if</em> configuration scope.
+</p>
+</li>
+</ul></div>
+<div class="paragraph"><p>In each place, it may be specified at most once. The default value is <em>300</em> (5 minutes).</p></div>
+</div>
+<div class="sect3">
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="PassengerConcurrencyModel" data-comment-topic="passenger-max-requests">6.9.7. passenger_concurrency_model &lt;process|thread&gt;</h4>
+<div class="paragraph"><p><strong>This feature is only available in <a href="https://www.phusionpassenger.com/enterprise">Phusion Passenger Enterprise</a>. It was introduced in version 4.0.0. <a href="https://www.phusionpassenger.com/download">Buy Phusion Passenger Enterprise here.</a></strong></p></div>
+<div class="paragraph"><p>Specifies the I/O concurrency model that should be used for application processes. Phusion Passenger supports two concurrency models:</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+<em>process</em> - single-threaded, multi-processed I/O concurrency. Each application process only has a single thread and can only handle 1 request at a time. This is the concurrency model that Ruby applications traditionally used. It has excellent compatiblity (can work with applications that are not designed to be thread-safe) but is unsuitable workloads in which the application has to wait for a lot of external I/O (e.g. HTTP API calls), and uses more memory because each process has a large memory overhead.
+</p>
+</li>
+<li>
+<p>
+<em>thread</em> - multi-threaded, multi-processed I/O concurrency. Each application process has multiple threads (customizable via <a href="#PassengerThreadCount">passenger_thread_count</a>). This model provides much better I/O concurrency and uses less memory because threads share memory with each other within the same process. However, using this model may cause compatibility problems if the application is not designed to be thread-safe.
+</p>
+</li>
+</ul></div>
+<div class="paragraph"><p>This option may occur in the following places:</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+In the <em>http</em> configuration block.
+</p>
+</li>
+<li>
+<p>
+In a <em>server</em> configuration block.
+</p>
+</li>
+<li>
+<p>
+In a <em>location</em> configuration block.
+</p>
+</li>
+<li>
+<p>
+In an <em>if</em> configuration scope.
+</p>
+</li>
+</ul></div>
+<div class="paragraph"><p>In each place, it may be specified at most once. The default value is <em>process</em>.</p></div>
+</div>
+<div class="sect3">
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="PassengerThreadCount" data-comment-topic="passenger-max-request-time-seconds--1qod9kg">6.9.8. passenger_thread_count &lt;number&gt;</h4>
+<div class="paragraph"><p><strong>This feature is only available in <a href="https://www.phusionpassenger.com/enterprise">Phusion Passenger Enterprise</a>. It was introduced in version 4.0.0. <a href="https://www.phusionpassenger.com/download">Buy Phusion Passenger Enterprise here.</a></strong></p></div>
+<div class="paragraph"><p>Specifies the number of threads that Phusion Passenger should spawn per application process. This option only has effect if <a href="#PassengerConcurrencyModel">passenger_concurrency_model</a> is <em>thread</em>.</p></div>
+<div class="paragraph"><p>This option may occur in the following places:</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+In the <em>http</em> configuration block.
+</p>
+</li>
+<li>
+<p>
+In a <em>server</em> configuration block.
+</p>
+</li>
+<li>
+<p>
+In a <em>location</em> configuration block.
+</p>
+</li>
+<li>
+<p>
+In an <em>if</em> configuration scope.
+</p>
+</li>
+</ul></div>
+<div class="paragraph"><p>In each place, it may be specified at most once. The default value is <em>1</em>.</p></div>
+</div>
+<div class="sect3">
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="PassengerMaxRequests" data-comment-topic="passenger-max-requests-integer--sgzint">6.9.9. passenger_max_requests &lt;integer&gt;</h4>
 <div class="paragraph"><p>The maximum number of requests an application process will process. After
 serving that many requests, the application process will be shut down and
 Phusion Passenger will restart it. A value of 0 means that there is no maximum:
@@ -2931,7 +2935,7 @@ reached.</p></div>
 it down after a certain number of requests, all of its memory is guaranteed
 to be freed by the operating system.</p></div>
 <div class="paragraph"><p>This option may occur in the following places:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 In the <em>http</em> configuration block.
@@ -2955,9 +2959,9 @@ In an <em>if</em> configuration scope.
 </ul></div>
 <div class="paragraph"><p>In each place, it may be specified at most once. The default value is <em>0</em>.</p></div>
 <div class="admonitionblock">
-<table><tr>
+<table><tr>
 <td class="icon">
-<img src="./images/icons/caution.png" alt="Caution">
+<img src="./images/icons/caution.png" alt="Caution">
 </td>
 <td class="content">
 <div class="paragraph"><p>The <a href="#PassengerMaxRequests">passenger_max_requests</a> directive should be considered
@@ -2965,11 +2969,11 @@ as a workaround for misbehaving applications. It is advised that you fix the
 problem in your application rather than relying on these directives as a
 measure to avoid memory leaks.</p></div>
 </td>
-</tr></table>
+</tr></table>
 </div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerMaxRequestTime"></span><h4 data-comment-topic="passenger-max-request-time-seconds--1qod9kg" data-anchor="PassengerMaxRequestTime">5.9.7. passenger_max_request_time &lt;seconds&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="PassengerMaxRequestTime" data-comment-topic="passenger-pre-start-url--1f2phk7">6.9.10. passenger_max_request_time &lt;seconds&gt;</h4>
 <div class="paragraph"><p><strong>This feature is only available in <a href="https://www.phusionpassenger.com/enterprise">Phusion Passenger Enterprise</a>. It was introduced in version 3.0.0. <a href="https://www.phusionpassenger.com/download">Buy Phusion Passenger Enterprise here.</a></strong></p></div>
 <div class="paragraph"><p>The maximum amount of time, in seconds, that an application process may take
 to process a request. If the request takes longer than this amount of time,
@@ -2978,7 +2982,7 @@ restarted upon the next request. A value of 0 means that there is no time limit.
 <div class="paragraph"><p>This option is useful for preventing your application from freezing for an
 indefinite period of time.</p></div>
 <div class="paragraph"><p>This option may occur in the following places:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 In the <em>http</em> configuration block.
@@ -3026,9 +3030,9 @@ to 10 seconds. You can then configure Phusion Passenger as follows:</p>
 or if a request to any other URI takes more than 2 seconds,
 then the corresponding application process will be forced to shutdown.</p></div>
 <div class="admonitionblock">
-<table><tr>
+<table><tr>
 <td class="icon">
-<img src="./images/icons/caution.png" alt="Caution">
+<img src="./images/icons/caution.png" alt="Caution">
 </td>
 <td class="content">
 <div class="paragraph"><p>The <a href="#PassengerMaxRequestTime">passenger_max_request_time</a> directive should be
@@ -3036,11 +3040,11 @@ considered as a workaround for misbehaving applications. It is advised that you
 fix the problem in your application rather than relying on these directives as a
 measure to avoid freezing applications.</p></div>
 </td>
-</tr></table>
+</tr></table>
 </div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerMemoryLimit"></span><h4 data-comment-topic="passenger-memory-limit-integer--1ry7dwx" data-anchor="PassengerMemoryLimit">5.9.8. passenger_memory_limit &lt;integer&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="PassengerMemoryLimit" data-comment-topic="passenger-memory-limit-integer--1ry7dwx">6.9.11. passenger_memory_limit &lt;integer&gt;</h4>
 <div class="paragraph"><p><strong>This feature is only available in <a href="https://www.phusionpassenger.com/enterprise">Phusion Passenger Enterprise</a>. It was introduced in version 3.0.0. <a href="https://www.phusionpassenger.com/download">Buy Phusion Passenger Enterprise here.</a></strong></p></div>
 <div class="paragraph"><p>The maximum amount of memory that an application process may use, in megabytes.
 Once an application process has surpassed its memory limit, it will process
@@ -3050,7 +3054,7 @@ will not be checked.</p></div>
 <div class="paragraph"><p>This option is useful if your application is leaking memory. By shutting
 it down, all of its memory is guaranteed to be freed by the operating system.</p></div>
 <div class="paragraph"><p>This option may occur in the following places:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 In the <em>http</em> configuration block.
@@ -3074,9 +3078,9 @@ In an <em>if</em> configuration scope.
 </ul></div>
 <div class="paragraph"><p>In each place, it may be specified at most once. The default value is <em>200</em>.</p></div>
 <div class="admonitionblock">
-<table><tr>
+<table><tr>
 <td class="icon">
-<img src="./images/icons/note.png" alt="Note">
+<img src="./images/icons/note.png" alt="Note">
 </td>
 <td class="content">
 <div class="title">A word about permissions</div>
@@ -3089,12 +3093,12 @@ tight permissions on <span class="monospaced">/proc</span>, this directive may n
 this directive and your <span class="monospaced">/proc</span> permissions are too tight, then please consider
 untightening the permissions.</p></div>
 </td>
-</tr></table>
+</tr></table>
 </div>
 <div class="admonitionblock">
-<table><tr>
+<table><tr>
 <td class="icon">
-<img src="./images/icons/tip.png" alt="Tip">
+<img src="./images/icons/tip.png" alt="Tip">
 </td>
 <td class="content">
 <div class="title">FreeBSD and <span class="monospaced">/proc</span>
@@ -3108,12 +3112,12 @@ which is very fast. If you mount <span class="monospaced">/proc</span> with a di
 Phusion Passenger must resort to querying memory information from the <span class="monospaced">ps</span> command,
 which is a lot slower.</p></div>
 </td>
-</tr></table>
+</tr></table>
 </div>
 <div class="admonitionblock">
-<table><tr>
+<table><tr>
 <td class="icon">
-<img src="./images/icons/caution.png" alt="Caution">
+<img src="./images/icons/caution.png" alt="Caution">
 </td>
 <td class="content">
 <div class="paragraph"><p>The <a href="#PassengerMaxRequests">passenger_max_requests</a> and
@@ -3122,25 +3126,25 @@ as workarounds for misbehaving applications. It is advised that you fix the
 problem in your application rather than relying on these directives as a
 measure to avoid memory leaks.</p></div>
 </td>
-</tr></table>
+</tr></table>
 </div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerPreStart"></span><h4 data-comment-topic="passenger-pre-start-url--1f2phk7" data-anchor="PassengerPreStart">5.9.9. passenger_pre_start &lt;url&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="PassengerPreStart" data-comment-topic="passenger-pre-start-url--npldeb">6.9.12. passenger_pre_start &lt;url&gt;</h4>
 <div class="paragraph"><p>By default, Phusion Passenger does not start any application processes until said
 web application is first accessed. The result is that the first visitor of said
 web application might experience a small delay as Phusion Passenger is starting
 the web application on demand. If that is undesirable, then this directive can be
 used to pre-started application processes during Nginx startup.</p></div>
 <div class="paragraph"><p>A few things to be careful of:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 This directive accepts the <strong>URL</strong> of the web application you want to pre-start,
   not a on/off value! This might seem a bit weird, but read on for rationale. As
   for the specifics of the URL:
 </p>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 The domain part of the URL must be equal to the value of the <em>server_name</em>
@@ -3341,14 +3345,14 @@ the request ending up at a different web server in the cluster.</p></div>
 </div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_logging_and_debugging_options"></span><h3 data-comment-topic="logging-and-debugging-options-14e91ni" data-anchor="_logging_and_debugging_options">5.10. Logging and debugging options</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_logging_and_debugging_options" data-comment-topic="logging-and-debugging-options-14e91ni">6.10. Logging and debugging options</h3>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_passenger_log_level_lt_integer_gt"></span><h4 data-comment-topic="passenger-log-level-integer--17snhon" data-anchor="_passenger_log_level_lt_integer_gt">5.10.1. passenger_log_level &lt;integer&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_passenger_log_level_lt_integer_gt" data-comment-topic="passenger-log-level-integer--17snhon">6.10.1. passenger_log_level &lt;integer&gt;</h4>
 <div class="paragraph"><p>This option allows one to specify how much information Phusion Passenger should
 write to the Nginx error log file. A higher log level value means that more
 information will be logged.</p></div>
 <div class="paragraph"><p>Possible values are:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 <em>0</em>: Show only errors and warnings.
@@ -3376,14 +3380,14 @@ information will be logged.</p></div>
 The default is <em>0</em>.</p></div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_passenger_debug_log_file_lt_filename_gt"></span><h4 data-comment-topic="passenger-debug-log-file-filename--21ubaj" data-anchor="_passenger_debug_log_file_lt_filename_gt">5.10.2. passenger_debug_log_file &lt;filename&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_passenger_debug_log_file_lt_filename_gt" data-comment-topic="passenger-debug-log-file-filename--21ubaj">6.10.2. passenger_debug_log_file &lt;filename&gt;</h4>
 <div class="paragraph"><p>By default Phusion Passenger debugging and error messages are written to the global
 web server error log. This option allows one to specify the file that debugging and
 error messages should be written to instead.</p></div>
 <div class="paragraph"><p>This option may only occur once, in the <em>http</em> configuration block.</p></div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_passenger_debugger_lt_on_off_gt"></span><h4 data-comment-topic="passenger-debugger-on-off--1wkuq85" data-anchor="_passenger_debugger_lt_on_off_gt">5.10.3. passenger_debugger &lt;on|off&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_passenger_debugger_lt_on_off_gt" data-comment-topic="passenger-debugger-on-off--1wkuq85">6.10.3. passenger_debugger &lt;on|off&gt;</h4>
 <div class="paragraph"><p><strong>This feature is only available in <a href="https://www.phusionpassenger.com/enterprise">Phusion Passenger Enterprise</a>. It was introduced in version 3.0.0. <a href="https://www.phusionpassenger.com/download">Buy Phusion Passenger Enterprise here.</a></strong></p></div>
 <div class="paragraph"><p>Turns support for application debugging on or off. In case of Ruby applications,
 turning this option on will cause them to load the <span class="monospaced">ruby-debug</span> gem (when on Ruby 1.8)
@@ -3397,7 +3401,7 @@ gem 'debugger', :platforms =&gt; :ruby_19</pre>
 </div>
 <div class="paragraph"><p>Once debugging is turned on, you can use the command <span class="monospaced">passenger-irb --debug &lt;PID&gt;</span> to attach an rdebug console to the application process with the given PID. Attaching will succeed once the application process executes a <span class="monospaced">debugger</span> command.</p></div>
 <div class="paragraph"><p>This option may occur in the following places:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 In the <em>http</em> configuration block.
@@ -3423,12 +3427,12 @@ In an <em>if</em> configuration scope.
 </div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_ruby_on_rails_specific_options"></span><h3 data-comment-topic="ruby-on-rails-specific-options-12vfokt" data-anchor="_ruby_on_rails_specific_options">5.11. Ruby on Rails-specific options</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_ruby_on_rails_specific_options" data-comment-topic="ruby-on-rails-specific-options-12vfokt">6.11. Ruby on Rails-specific options</h3>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="RailsEnv"></span><h4 data-comment-topic="rails-env-string--jlh7v9" data-anchor="RailsEnv">5.11.1. rails_env &lt;string&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="RailsEnv" data-comment-topic="rails-env-string--jlh7v9">6.11.1. rails_env &lt;string&gt;</h4>
 <div class="paragraph"><p>This option allows one to specify the default <span class="monospaced">RAILS_ENV</span> value.</p></div>
 <div class="paragraph"><p>This option may occur in the following places:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 In the <em>http</em> configuration block.
@@ -3452,92 +3456,14 @@ In an <em>if</em> configuration scope.
 </ul></div>
 <div class="paragraph"><p>In each place, it may be specified at most once. The default value is <em>production</em>.</p></div>
 </div>
-<div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_rails_framework_spawner_idle_time_lt_integer_gt"></span><h4 data-comment-topic="rails-framework-spawner-idle-time-integer--q5ljd5" data-anchor="_rails_framework_spawner_idle_time_lt_integer_gt">5.11.2. rails_framework_spawner_idle_time &lt;integer&gt;</h4>
-<div class="paragraph"><p>The FrameworkSpawner server (explained in <a href="#spawning_methods_explained">Spawning methods explained</a>) has an idle timeout, just like the backend processes spawned by
-Phusion Passenger do. That is, it will automatically shutdown if it hasn’t done
-anything for a given period.</p></div>
-<div class="paragraph"><p>This option allows you to set the FrameworkSpawner server’s idle timeout, in
-seconds. A value of <em>0</em> means that it should never idle timeout.</p></div>
-<div class="paragraph"><p>Setting a higher value will mean that the FrameworkSpawner server is kept around
-longer, which may slightly increase memory usage. But as long as the
-FrameworkSpawner server is running, the time to spawn a Ruby on Rails backend
-process only takes about 40% of the time that is normally needed, assuming that
-you’re using the <em>smart</em> <a href="#RailsSpawnMethod">spawning method</a>. So if your
-system has enough memory, is it recommended that you set this option to a high
-value or to <em>0</em>.</p></div>
-<div class="paragraph"><p>This option may occur in the following places:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-In the <em>http</em> configuration block.
-</p>
-</li>
-<li>
-<p>
-In a <em>server</em> configuration block.
-</p>
-</li>
-<li>
-<p>
-In a <em>location</em> configuration block.
-</p>
-</li>
-<li>
-<p>
-In an <em>if</em> configuration scope.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>In each place, it may be specified at most once. The default value is <em>1800</em> (30 minutes).</p></div>
-</div>
-<div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_rails_app_spawner_idle_time_lt_integer_gt"></span><h4 data-comment-topic="rails-app-spawner-idle-time-integer--1xjqe4b" data-anchor="_rails_app_spawner_idle_time_lt_integer_gt">5.11.3. rails_app_spawner_idle_time &lt;integer&gt;</h4>
-<div class="paragraph"><p>The ApplicationSpawner server (explained in <a href="#spawning_methods_explained">Spawning methods explained</a>) has an idle timeout, just like the backend processes spawned by
-Phusion Passenger do. That is, it will automatically shutdown if it hasn’t done
-anything for a given period.</p></div>
-<div class="paragraph"><p>This option allows you to set the ApplicationSpawner server’s idle timeout, in
-seconds. A value of <em>0</em> means that it should never idle timeout.</p></div>
-<div class="paragraph"><p>Setting a higher value will mean that the ApplicationSpawner server is kept around
-longer, which may slightly increase memory usage. But as long as the
-ApplicationSpawner server is running, the time to spawn a Ruby on Rails backend
-process only takes about 10% of the time that is normally needed, assuming that
-you’re using the <em>smart</em> or <em>smart-lv2</em> <a href="#RailsSpawnMethod">spawning method</a>. So if your
-system has enough memory, is it recommended that you set this option to a high
-value or to <em>0</em>.</p></div>
-<div class="paragraph"><p>This option may occur in the following places:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-In the <em>http</em> configuration block.
-</p>
-</li>
-<li>
-<p>
-In a <em>server</em> configuration block.
-</p>
-</li>
-<li>
-<p>
-In a <em>location</em> configuration block.
-</p>
-</li>
-<li>
-<p>
-In an <em>if</em> configuration scope.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>In each place, it may be specified at most once. The default value is <em>600</em> (10 minutes).</p></div>
-</div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_rack_and_rails_gt_3_specific_options"></span><h3 data-comment-topic="rack-specific-options-13yvdxs" data-anchor="_rack_and_rails_gt_3_specific_options">5.12. Rack and Rails &gt;= 3 specific options</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_rack_and_rails_gt_3_specific_options" data-comment-topic="rack-specific-options-13yvdxs">6.12. Rack and Rails &gt;= 3 specific options</h3>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="RackEnv"></span><h4 data-comment-topic="rack-env-string--tqmrt0" data-anchor="RackEnv">5.12.1. rack_env &lt;string&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="RackEnv" data-comment-topic="rack-env-string--tqmrt0">6.12.1. rack_env &lt;string&gt;</h4>
 <div class="paragraph"><p>This option allows one to specify the default <span class="monospaced">RACK_ENV</span> value.</p></div>
 <div class="paragraph"><p>This option may occur in the following places:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 In the <em>http</em> configuration block.
@@ -3563,23 +3489,23 @@ In an <em>if</em> configuration scope.
 </div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_deprecated_options"></span><h3 data-comment-topic="deprecated-options-1dtzo0g" data-anchor="_deprecated_options">5.13. Deprecated options</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_deprecated_options" data-comment-topic="deprecated-options-1dtzo0g">6.13. Deprecated options</h3>
 <div class="paragraph"><p>The following options have been deprecated, but are still supported for backwards
 compatibility reasons.</p></div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_rails_spawn_method"></span><h4 data-comment-topic="rails-spawn-method-17vdnpt" data-anchor="_rails_spawn_method">5.13.1. rails_spawn_method</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_rails_spawn_method" data-comment-topic="rails-spawn-method-17vdnpt">6.13.1. rails_spawn_method</h4>
 <div class="paragraph"><p>Deprecated in favor of <a href="#PassengerSpawnMethod">passenger_spawn_method</a>.</p></div>
 </div>
 </div>
 </div>
 </div>
 <div class="sect1">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_analysis_and_system_maintenance"></span><h2 data-comment-topic="analysis-and-system-maintenance-1nnlnj8" data-anchor="_analysis_and_system_maintenance">6. Analysis and system maintenance</h2>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h2 id="_analysis_and_system_maintenance" data-comment-topic="analysis-and-system-maintenance-1nnlnj8">7. Analysis and system maintenance</h2>
 <div class="sectionbody">
 <div class="paragraph"><p>Phusion Passenger provides a set of tools, which are useful for system analysis,
 maintenance and troubleshooting.</p></div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_inspecting_memory_usage"></span><h3 data-comment-topic="inspecting-memory-usage-1k6y8v0" data-anchor="_inspecting_memory_usage">6.1. Inspecting memory usage</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_inspecting_memory_usage" data-comment-topic="inspecting-memory-usage-1k6y8v0">7.1. Inspecting memory usage</h3>
 <div class="paragraph"><p>Process inspection tools such as <span class="monospaced">ps</span> and <span class="monospaced">top</span> are useful, but they
 <a href="http://groups.google.com/group/phusion-passenger/msg/1fd1c233456d3180">rarely show the correct memory usage</a>.
 The real memory usage is usually lower than what <span class="monospaced">ps</span> and <span class="monospaced">top</span> report.</p></div>
@@ -3621,18 +3547,18 @@ we see that all the Apache worker processes only take less than 1 MB memory each
 This is a lot less than the 50 MB-ish memory usage as shown in the <em>VMSize</em> column
 (which is what a lot of people think is the real memory usage, but is actually not).</p></div>
 <div class="admonitionblock">
-<table><tr>
+<table><tr>
 <td class="icon">
-<img src="./images/icons/note.png" alt="Note">
+<img src="./images/icons/note.png" alt="Note">
 </td>
 <td class="content">Private dirty RSS reporting only works on Linux. Unfortunately other operating systems
 don’t provide facilities for determining processes' private dirty RSS. On non-Linux systems,
 the Resident Set Size is reported instead.</td>
-</tr></table>
+</tr></table>
 </div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_inspecting_phusion_passenger_8217_s_internal_status"></span><h3 data-comment-topic="inspecting-phusion-passenger-s-internal-status-v36wbc" data-anchor="_inspecting_phusion_passenger_8217_s_internal_status">6.2. Inspecting Phusion Passenger’s internal status</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_inspecting_phusion_passenger_8217_s_internal_status" data-comment-topic="inspecting-phusion-passenger-s-internal-status-v36wbc">7.2. Inspecting Phusion Passenger’s internal status</h3>
 <div class="paragraph"><p>One can inspect Phusion Passenger’s internal status with the tool <span class="monospaced">passenger-status</span>.
 This tool must typically be run as root. For example:</p></div>
 <div class="listingblock">
@@ -3650,7 +3576,7 @@ inactive = 1
 </div>
 </div>
 <div class="paragraph"><p>The <em>general information</em> section shows the following information:</p></div>
-<div class="dlist"><dl>
+<div class="dlist"><dl>
 <dt class="hdlist1">
 max
 </dt>
@@ -3694,7 +3620,7 @@ time). The value of <em>inactive</em> equals <span class="monospaced">count - ac
 </dl></div>
 <div class="paragraph"><p>The <em>domains</em> section shows, for each application directory, information about running
 application instances:</p></div>
-<div class="dlist"><dl>
+<div class="dlist"><dl>
 <dt class="hdlist1">
 Sessions
 </dt>
@@ -3747,7 +3673,7 @@ sessions compared to the others, then there might be a problem:</p></div>
 </div>
 </div>
 <div class="paragraph"><p>Possible reasons why spikes can occur:</p></div>
-<div class="olist arabic"><ol class="arabic">
+<div class="olist arabic"><ol class="arabic">
 <li>
 <p>
 Your application is busy processing a request that takes a very long time.
@@ -3764,7 +3690,7 @@ Your application is frozen, i.e. has stopped responding. See
 </ol></div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="debugging_frozen"></span><h3 data-comment-topic="debugging-frozen-applications-qoctl8" data-anchor="debugging_frozen">6.3. Debugging frozen applications</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="debugging_frozen" data-comment-topic="debugging-frozen-applications-qoctl8">7.3. Debugging frozen applications</h3>
 <div class="paragraph"><p>If one of your application instances is frozen (stopped responding), then you
 can figure out where it is frozen by killing it with <em>SIGABRT</em>. This will cause the
 application to raise an exception, with a backtrace.</p></div>
@@ -3776,22 +3702,22 @@ This is the case with Ruby on Rails. So if you kill a Ruby on Rails application
 running it in a <em>production</em> environment). If you don’t see a backtrace there, check
 the Apache error log.</p></div>
 <div class="admonitionblock">
-<table><tr>
+<table><tr>
 <td class="icon">
-<img src="./images/icons/note.png" alt="Note">
+<img src="./images/icons/note.png" alt="Note">
 </td>
 <td class="content">It is safe to kill application instances, even in live environments. Phusion Passenger
 will restart killed application instances, as if nothing bad happened.</td>
-</tr></table>
+</tr></table>
 </div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_accessing_individual_application_processes"></span><h3 data-comment-topic="accessing-individual-application-processes-1qe4fqk" data-anchor="_accessing_individual_application_processes">6.4. Accessing individual application processes</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_accessing_individual_application_processes" data-comment-topic="accessing-individual-application-processes-1qe4fqk">7.4. Accessing individual application processes</h3>
 <div class="paragraph"><p>When a request is sent to the web server, Phusion Passenger will automatically forward
 the request to the most suitable application process, but sometimes it is desirable to
 be able to directly access the individual application processes. Use cases include, but
 are not limited to:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 One wants to debug a memory leak or memory bloat problem that only seems to appear on
@@ -3852,17 +3778,16 @@ through the <em>X-Passenger-Connect-Password</em> HTTP header, like this:</p></d
 </div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_attaching_an_irb_console_to_an_application_process"></span><h3 data-comment-topic="attaching-an-irb-console-to-an-application-process-d36enw" data-anchor="_attaching_an_irb_console_to_an_application_process">6.5. Attaching an IRB console to an application process</h3>
-<div class="paragraph"><p><strong>Available in Phusion Passenger Enterprise since version 3.0.0.</strong></p></div>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_attaching_an_irb_console_to_an_application_process" data-comment-topic="attaching-an-irb-console-to-an-application-process-d36enw">7.5. Attaching an IRB console to an application process</h3>
 <div class="paragraph"><p>You can attach an IRB console to any application process and inspect its state by executing arbitrary Ruby code. Do this by invoking <span class="monospaced">passenger-irb &lt;PID&gt;</span> where <em>&lt;PID&gt;</em> is the PID of the application process you wish to inspect. Note that the IRB console is currently only available for Ruby apps, not for apps in any other languages.</p></div>
 </div>
 </div>
 </div>
 <div class="sect1">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_tips"></span><h2 data-comment-topic="tips-n4c22d" data-anchor="_tips">7. Tips</h2>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h2 id="_tips" data-comment-topic="tips-n4c22d">8. Tips</h2>
 <div class="sectionbody">
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="user_switching"></span><h3 data-comment-topic="user-switching-security--zmsy9o" data-anchor="user_switching">7.1. User switching (security)</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="user_switching" data-comment-topic="user-switching-security--zmsy9o">8.1. User switching (security)</h3>
 <div class="paragraph"><p>There is a problem that plagues most PHP web hosts, namely the fact that all PHP
 applications are run in the same user context as the web server. So for
 example, Joe’s PHP application will be able to read Jane’s PHP application’s
@@ -3874,7 +3799,7 @@ So if <em>/home/webapps/foo/config/environment.rb</em> is owned by <em>joe</em>,
 Passenger will launch the corresponding Rails application as <em>joe</em> as well.</p></div>
 <div class="paragraph"><p>This behavior is the default, and you don’t need to configure anything. But
 there are things that you should keep in mind:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 The owner of <em>environment.rb</em>/<em>config.ru</em> must have read access to the application’s
@@ -3902,14 +3827,14 @@ Under no circumstances will applications be run as <em>root</em>. If
 option.</p></div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="reducing_memory_usage"></span><h3 data-comment-topic="reducing-memory-consumption-of-ruby-on-rails-applications-by-33--1o3z66q" data-anchor="reducing_memory_usage">7.2. Reducing memory consumption of Ruby on Rails applications by 33%</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="reducing_memory_usage" data-comment-topic="reducing-memory-consumption-of-ruby-on-rails-applications-by-33--1o3z66q">8.2. Reducing memory consumption of Ruby on Rails applications by 33%</h3>
 <div class="paragraph"><p>Is it possible to reduce memory consumption of your Rails applications by 33% on average,
 by using <a href="http://www.rubyenterpriseedition.com/">Ruby Enterprise Edition</a>.
 Please visit the website for details.</p></div>
 <div class="paragraph"><p>Note that this feature does not apply to Rack applications.</p></div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="capistrano"></span><h3 data-comment-topic="capistrano-recipe-pfn4qu" data-anchor="capistrano">7.3. Capistrano recipe</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="capistrano" data-comment-topic="capistrano-recipe-pfn4qu">8.3. Capistrano recipe</h3>
 <div class="paragraph"><p>Phusion Passenger can be combined with <a href="http://capify.org/">Capistrano</a>.
 The following Capistrano recipe demonstrates Phusion Passenger support.
 It assumes that you’re using Git as version control system.</p></div>
@@ -3944,10 +3869,10 @@ end</pre>
 </div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="bundler_support"></span><h3 data-comment-topic="bundler-support-19v1h43" data-anchor="bundler_support">7.4. Bundler support</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="bundler_support" data-comment-topic="bundler-support-19v1h43">8.4. Bundler support</h3>
 <div class="paragraph"><p>Phusion Passenger has automatic support for <a href="http://gembundler.com/git.html">Bundler</a>.
 It works as follows:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 If you have a <em>.bundle/environment.rb</em> in your application root, then Phusion
@@ -3977,10 +3902,10 @@ the application startup file. In this file you can do whatever you need to setup
 or a similar system.</p></div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="moving_phusion_passenger"></span><h3 data-comment-topic="moving-phusion-passenger-to-a-different-directory-1hel5cp" data-anchor="moving_phusion_passenger">7.5. Moving Phusion Passenger to a different directory</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="moving_phusion_passenger" data-comment-topic="moving-phusion-passenger-to-a-different-directory-1hel5cp">8.5. Moving Phusion Passenger to a different directory</h3>
 <div class="paragraph"><p>It is possible to relocate the Phusion Passenger files to a different directory. It
 involves two steps:</p></div>
-<div class="olist arabic"><ol class="arabic">
+<div class="olist arabic"><ol class="arabic">
 <li>
 <p>
 Moving the directory.
@@ -3994,7 +3919,7 @@ Updating the “PassengerRoot” configuration option in Apache.
 </ol></div>
 <div class="paragraph"><p>For example, if Phusion Passenger is located in <em>/opt/passenger/</em>, and you’d like to
 move it to <em>/usr/local/passenger/</em>, then do this:</p></div>
-<div class="olist arabic"><ol class="arabic">
+<div class="olist arabic"><ol class="arabic">
 <li>
 <p>
 Run the following command:
@@ -4018,7 +3943,7 @@ Edit your Apache configuration file, and set:
 </ol></div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_installing_multiple_ruby_on_rails_versions"></span><h3 data-comment-topic="installing-multiple-ruby-on-rails-versions-1bp1fff" data-anchor="_installing_multiple_ruby_on_rails_versions">7.6. Installing multiple Ruby on Rails versions</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_installing_multiple_ruby_on_rails_versions" data-comment-topic="installing-multiple-ruby-on-rails-versions-1bp1fff">8.6. Installing multiple Ruby on Rails versions</h3>
 <div class="paragraph"><p>Each Ruby on Rails applications that are going to be deployed may require a
 specific Ruby on Rails version. You can install a specific version with
 this command:</p></div>
@@ -4032,7 +3957,7 @@ this command:</p></div>
 other. Phusion Passenger will automatically make use of the correct version.</p></div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_making_the_application_restart_after_each_request"></span><h3 data-comment-topic="making-the-application-restart-after-each-request-vimy48" data-anchor="_making_the_application_restart_after_each_request">7.7. Making the application restart after each request</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_making_the_application_restart_after_each_request" data-comment-topic="making-the-application-restart-after-each-request-vimy48">8.7. Making the application restart after each request</h3>
 <div class="paragraph"><p>In some situations it might be desirable to restart the web application after
 each request, for example when developing a non-Rails application that doesn’t
 support code reloading, or when developing a web framework.</p></div>
@@ -4041,9 +3966,9 @@ application’s root folder. Unlike <em>restart.txt</em>, Phusion Passenger does
 check for this file’s timestamp: Phusion Passenger will always restart the
 application, as long as <em>always_restart.txt</em> exists.</p></div>
 <div class="admonitionblock">
-<table><tr>
+<table><tr>
 <td class="icon">
-<img src="./images/icons/note.png" alt="Note">
+<img src="./images/icons/note.png" alt="Note">
 </td>
 <td class="content">If you’re just developing a Rails application then you probably don’t need
 this feature. If you set <em>RailsEnv development</em> in your Apache configuration,
@@ -4051,11 +3976,11 @@ then Rails will automatically reload your application code after each request.
 <em>always_restart.txt</em> is only useful if you’re working on Ruby on Rails itself,
 or when you’re not developing a Rails application and your web framework
 does not support code reloading.</td>
-</tr></table>
+</tr></table>
 </div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="sub_uri_deployment_uri_fix"></span><h3 data-comment-topic="how-to-fix-broken-images-css-javascript-uris-in-sub-uri-deployments-11mzwt6" data-anchor="sub_uri_deployment_uri_fix">7.8. How to fix broken images/CSS/JavaScript URIs in sub-URI deployments</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="sub_uri_deployment_uri_fix" data-comment-topic="how-to-fix-broken-images-css-javascript-uris-in-sub-uri-deployments-11mzwt6">8.8. How to fix broken images/CSS/JavaScript URIs in sub-URI deployments</h3>
 <div class="paragraph"><p>Some people experience broken images and other broken static assets when they
 deploy their application to a sub-URI (i.e. <em>http://mysite.com/railsapp/</em>).
 The reason for this usually is that you used a
@@ -4095,13 +4020,13 @@ please refer to
 </div>
 </div>
 <div class="sect1">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_under_the_hood"></span><h2 data-comment-topic="under-the-hood-8uney" data-anchor="_under_the_hood">8. Under the hood</h2>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h2 id="_under_the_hood" data-comment-topic="under-the-hood-8uney">9. Under the hood</h2>
 <div class="sectionbody">
 <div class="paragraph"><p>Phusion Passenger hides a lot of complexity for the end user (i.e. the web server
 system administrator), but sometimes it is desirable to know what is going on.
 This section describes a few things that Phusion Passenger does under the hood.</p></div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_page_caching_support"></span><h3 data-comment-topic="page-caching-support-nafhf6" data-anchor="_page_caching_support">8.1. Page caching support</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_page_caching_support" data-comment-topic="page-caching-support-nafhf6">9.1. Page caching support</h3>
 <div class="paragraph"><p>For each HTTP request, Phusion Passenger will automatically look for a corresponding
 page cache file, and serve that if it exists. It does this by appending ".html" to
 the filename that the URI normally maps to, and checking whether that file exists.
@@ -4109,7 +4034,7 @@ This check occurs after checking whether the original mapped filename exists (as
 of static asset serving). All this is done without the need for special mod_rewrite
 rules.</p></div>
 <div class="paragraph"><p>For example, suppose that the browser requests <em>/foo/bar</em>.</p></div>
-<div class="olist arabic"><ol class="arabic">
+<div class="olist arabic"><ol class="arabic">
 <li>
 <p>
 Phusion Passenger will first check whether this URI maps to a static file, i.e.
@@ -4137,7 +4062,7 @@ the <em>public</em> directory. In that case you’ll need to use mod_rewrite to
 page cache files.</p></div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="application_detection"></span><h3 data-comment-topic="how-phusion-passenger-detects-whether-a-virtual-host-is-a-web-application-13qbmhn" data-anchor="application_detection">8.2. How Phusion Passenger detects whether a virtual host is a web application</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="application_detection" data-comment-topic="how-phusion-passenger-detects-whether-a-virtual-host-is-a-web-application-13qbmhn">9.2. How Phusion Passenger detects whether a virtual host is a web application</h3>
 <div class="paragraph"><p>After you’ve read the deployment instructions you might wonder how Phusion Passenger
 knows that the server root points to a web application that Phusion Passenger is
 able to serve, and how it knows what kind of web application it is (e.g. Rails or Rack).</p></div>
@@ -4150,7 +4075,7 @@ whether the following file exists:</p></div>
 </div>
 <div class="paragraph"><p>If you’re not a programmer and don’t understand the above pseudo-code snippet, it means
 that Phusion Passenger will:</p></div>
-<div class="olist arabic"><ol class="arabic">
+<div class="olist arabic"><ol class="arabic">
 <li>
 <p>
 Extract the parent directory filename from the value of the “root” directive.
@@ -4178,30 +4103,28 @@ Phusion Passenger will look for <em>config.ru</em> instead of <em>config/environ
 </div>
 </div>
 <div class="sect1">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_appendix_a_about_this_document"></span><h2 data-comment-topic="appendix-a-about-this-document-zfvixm" data-anchor="_appendix_a_about_this_document">9. Appendix A: About this document</h2>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h2 id="_appendix_a_about_this_document" data-comment-topic="appendix-a-about-this-document-zfvixm">10. Appendix A: About this document</h2>
 <div class="sectionbody">
 <div class="paragraph"><p>The text of this document is licensed under the
 <a href="http://creativecommons.org/licenses/by-sa/3.0/">Creative Commons
 Attribution-Share Alike 3.0 Unported License</a>.</p></div>
 <div class="paragraph"><p><span class="image">
 <a class="image" href="http://creativecommons.org/licenses/by-sa/3.0/">
-<img src="images/by_sa.png" alt="images/by_sa.png">
-</a>
+<img src="images/by_sa.png" alt="images/by_sa.png"></a>
 </span></p></div>
 <div class="paragraph"><p>Phusion Passenger is brought to you by <a href="http://www.phusion.nl/">Phusion</a>.</p></div>
 <div class="paragraph"><p><span class="image">
 <a class="image" href="http://www.phusion.nl/">
-<img src="images/phusion_banner.png" alt="images/phusion_banner.png">
-</a>
+<img src="images/phusion_banner.png" alt="images/phusion_banner.png"></a>
 </span></p></div>
 <div class="paragraph"><p>Phusion Passenger is a trademark of Hongli Lai &amp; Ninh Bui.</p></div>
 </div>
 </div>
 <div class="sect1">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_appendix_b_terminology"></span><h2 data-comment-topic="appendix-b-terminology-wzv5ro" data-anchor="_appendix_b_terminology">10. Appendix B: Terminology</h2>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h2 id="_appendix_b_terminology" data-comment-topic="appendix-b-terminology-wzv5ro">11. Appendix B: Terminology</h2>
 <div class="sectionbody">
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="application_root"></span><h3 data-comment-topic="application-root-1fd6bqv" data-anchor="application_root">10.1. Application root</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="application_root" data-comment-topic="application-root-1fd6bqv">11.1. Application root</h3>
 <div class="paragraph"><p>The root directory of an application that’s served by Phusion Passenger.</p></div>
 <div class="paragraph"><p>In case of Ruby on Rails applications, this is the directory that contains
 <em>Rakefile</em>, <em>app/</em>, <em>config/</em>, <em>public/</em>, etc. In other words, the directory
@@ -4263,17 +4186,17 @@ For example, take the following directory structure:</p></div>
 </div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="idle_process"></span><h3 data-comment-topic="idle-process-13byfw9" data-anchor="idle_process">10.2. Idle process</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="idle_process" data-comment-topic="idle-process-13byfw9">11.2. Idle process</h3>
 <div class="paragraph"><p>An "idle process" refers to a process that hasn’t processed any requests for a while.</p></div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="inactive_process"></span><h3 data-comment-topic="inactive-process-1d2h0po" data-anchor="inactive_process">10.3. Inactive process</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="inactive_process" data-comment-topic="inactive-process-1d2h0po">11.3. Inactive process</h3>
 <div class="paragraph"><p>An "inactive process" refers to a process that’s current not processing any requests. An idle process is always inactive, but an inactive process is not always considered idle.</p></div>
 </div>
 </div>
 </div>
 <div class="sect1">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="spawning_methods_explained"></span><h2 data-comment-topic="appendix-c-spawning-methods-explained-tcp8e6" data-anchor="spawning_methods_explained">11. Appendix C: Spawning methods explained</h2>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h2 id="spawning_methods_explained" data-comment-topic="appendix-c-spawning-methods-explained-tcp8e6">12. Appendix C: Spawning methods explained</h2>
 <div class="sectionbody">
 <div class="paragraph"><p>At its core, Phusion Passenger is an HTTP proxy and process manager. It spawns
 Ruby on Rails/Rack/WSGI worker processes (which may also be referred to as
@@ -4283,7 +4206,7 @@ processes.</p></div>
 Let’s go over the different spawning methods. For simplicity’s sake, let’s
 assume that we’re only talking about Ruby on Rails applications.</p></div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_the_most_straightforward_and_traditional_way_conservative_spawning"></span><h3 data-comment-topic="the-most-straightforward-and-traditional-way-conservative-spawning-civ29z" data-anchor="_the_most_straightforward_and_traditional_way_conservative_spawning">11.1. The most straightforward and traditional way: conservative spawning</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_the_most_straightforward_and_traditional_way_direct_spawning" data-comment-topic="the-most-straightforward-and-traditional-way-conservative-spawning-civ29z">12.1. The most straightforward and traditional way: direct spawning</h3>
 <div class="paragraph"><p>Phusion Passenger could create a new Ruby process, which will then load the
 Rails application along with the entire Rails framework. This process will then
 enter an request handling main loop.</p></div>
@@ -4292,7 +4215,7 @@ familiar with the Mongrel application server, then this approach is exactly
 what mongrel_cluster performs: it creates N worker processes, each which loads
 a full copy of the Rails application and the Rails framework in memory. The Thin
 application server employs pretty much the same approach.</p></div>
-<div class="paragraph"><p>Note that Phusion Passenger’s version of conservative spawning differs slightly
+<div class="paragraph"><p>Note that Phusion Passenger’s version of direct spawning differs slightly
 from mongrel_cluster. Mongrel_cluster creates entirely new Ruby processes. In
 programmers jargon, mongrel_cluster creates new Ruby processes by forking the
 current process and exec()-ing a new Ruby interpreter. Phusion Passenger on the
@@ -4300,31 +4223,29 @@ other hand creates processes that reuse the already loaded Ruby interpreter. In
 programmers jargon, Phusion Passenger calls fork(), but not exec().</p></div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_the_smart_spawning_method"></span><h3 data-comment-topic="the-smart-spawning-method-7nhgtj" data-anchor="_the_smart_spawning_method">11.2. The smart spawning method</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_the_smart_spawning_method" data-comment-topic="the-smart-spawning-method-7nhgtj">12.2. The smart spawning method</h3>
 <div class="admonitionblock">
-<table><tr>
+<table><tr>
 <td class="icon">
-<img src="./images/icons/note.png" alt="Note">
+<img src="./images/icons/note.png" alt="Note">
 </td>
 <td class="content">Smart spawning is supported for all Ruby applications but not for WSGI applications.</td>
-</tr></table>
+</tr></table>
 </div>
-<div class="paragraph"><p>While conservative spawning works well, it’s not as efficient as it could be
+<div class="paragraph"><p>While direct spawning works well, it’s not as efficient as it could be
 because each worker process has its own private copy of the Rails application
 as well as the Rails framework. This wastes memory as well as startup time.</p></div>
 <div class="paragraph"><p><span class="image">
-<img src="images/conservative_spawning.png" alt="Worker processes and conservative spawning">
-</span><br>
-<em>Figure: Worker processes and conservative spawning. Each worker process has its
+<img src="images/direct_spawning.png" alt="Worker processes and direct spawning"></span><br><em>Figure: Worker processes and direct spawning. Each worker process has its
 own private copy of the application code and Rails framework code.</em></p></div>
 <div class="paragraph"><p>It is possible to make the different worker processes share the memory occupied
 by application and Rails framework code, by utilizing so-called
 copy-on-write semantics of the virtual memory system on modern operating
 systems. As a side effect, the startup time is also reduced. This is technique
-is exploited by Phusion Passenger’s <em>smart</em> and <em>smart-lv2</em> spawn methods.</p></div>
+is exploited by Phusion Passenger’s <em>smart</em> spawn method.</p></div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_how_it_works"></span><h4 data-comment-topic="how-it-works-f9umga" data-anchor="_how_it_works">11.2.1. How it works</h4>
-<div class="paragraph"><p>When the <em>smart-lv2</em> spawn method is being used, Phusion Passenger will first
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_how_it_works" data-comment-topic="how-it-works-f9umga">12.2.1. How it works</h4>
+<div class="paragraph"><p>When the <em>smart</em> spawn method is being used, Phusion Passenger will first
 create a so-called <em>ApplicationSpawner server</em> process. This process loads the
 entire Rails application along with the Rails framework, by loading
 <em>environment.rb</em>. Then, whenever Phusion Passenger needs a new worker process,
@@ -4339,24 +4260,13 @@ processes will share as much common
 memory as possible. That is, they will all share the same application and Rails
 framework code.</p></div>
 <div class="paragraph"><p><span class="image">
-<img src="images/smart-lv2.png" alt="images/smart-lv2.png">
-</span><br>
-<em>Figure: Worker processes and the smart-lv2 spawn method. All worker processes,
+<img src="images/smart.png" alt="images/smart.png"></span><br><em>Figure: Worker processes and the smart spawn method. All worker processes,
 as well as the ApplicationSpawner, share the same application code and Rails
 framework code.</em></p></div>
-<div class="paragraph"><p>The <em>smart</em> spawn method goes even further, by caching the Rails framework in
-another process called the <em>FrameworkSpawner server</em>. This process only loads
-the Rails framework, not the application. When a FrameworkSpawner server is
-instructed to create a new worker process, it will create a new
-ApplicationSpawner to which the instruction will be delegated. All those
-ApplicationSpawner servers, as well as all worker processes created by those
-ApplicationSpawner servers, will share the same Rails framework code.</p></div>
-<div class="paragraph"><p>The <em>smart-lv2</em> method allows different worker processes that belong to the same
-application to share memory. The <em>smart</em> method allows different worker
-processes - that happen to use the same Rails version - to share memory, even if
-they don’t belong to the same application.</p></div>
+<div class="paragraph"><p>The <em>smart</em> method allows different worker processes that belong to the same
+application to share memory.</p></div>
 <div class="paragraph"><p>Notes:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 Vendored Rails frameworks cannot be shared by different applications, even if
@@ -4366,53 +4276,32 @@ Vendored Rails frameworks cannot be shared by different applications, even if
 </li>
 <li>
 <p>
-ApplicationSpawner and FrameworkSpawner servers have an idle timeout just
-  like worker processes. If an ApplicationSpawner/FrameworkSpawner server hasn’t
-  been instructed to do anything for a while, it will be shutdown in order to
-  conserve memory. This idle timeout is configurable.
+ApplicationSpawner servers have an idle timeout just like worker processes.
+  If an ApplicationSpawner/FrameworkSpawner server hasn’t been instructed to do
+  anything for a while, it will be shutdown in order to conserve memory. This
+  idle timeout is configurable.
 </p>
 </li>
 </ul></div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_summary_of_benefits"></span><h4 data-comment-topic="summary-of-benefits-qovyvk" data-anchor="_summary_of_benefits">11.2.2. Summary of benefits</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_summary_of_benefits" data-comment-topic="summary-of-benefits-qovyvk">12.2.2. Summary of benefits</h4>
 <div class="paragraph"><p>Suppose that Phusion Passenger needs a new worker process for an application
 that uses Rails 2.2.1.</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-If the <em>smart-lv2</em> spawning method is used, and an ApplicationSpawner server
-  for this application is already running, then worker process creation time is
-  about 10 times faster than conservative spawning. This worker process will also
-  share application and Rails framework code memory with the ApplicationSpawner
-  server and the worker processes that had been spawned by this ApplicationSpawner
-  server.
-</p>
-</li>
-<li>
-<p>
-If the <em>smart</em> spawning method is used, and a FrameworkSpawner server for
-  Rails 2.2.1 is already running, but no ApplicationSpawner server for this
-  application is running, then worker process creation time is about 2 times
-  faster than conservative spawning. If there is an ApplicationSpawner server
-  for this application running, then worker process creation time is about 10
-  times faster. This worker process will also share application and Rails
-  framework code memory with the ApplicationSpawner and FrameworkSpawner
-  servers.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>You could compare ApplicationSpawner and FrameworkSpawner servers with stem
-cells, that have the ability to quickly change into more specific cells (worker
-process).</p></div>
-<div class="paragraph"><p>In practice, the smart spawning methods could mean a memory saving of about 33%,
+<div class="paragraph"><p>If the <em>smart</em> spawning method is used, and an ApplicationSpawner server
+for this application is already running, then worker process creation time is
+about 10 times faster than direct spawning. This worker process will also
+share application and Rails framework code memory with the ApplicationSpawner
+server and the worker processes that had been spawned by this ApplicationSpawner
+server.</p></div>
+<div class="paragraph"><p>In practice, the smart spawning method could mean a memory saving of about 33%,
 assuming that your Ruby interpreter is <a href="#reducing_memory_usage">copy-on-write friendly</a>.</p></div>
 <div class="paragraph"><p>Of course, smart spawning is not without gotchas. But if you understand the
 gotchas you can easily reap the benefits of smart spawning.</p></div>
 </div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_smart_spawning_gotcha_1_unintentional_file_descriptor_sharing"></span><h3 data-comment-topic="smart-spawning-gotcha-1-unintentional-file-descriptor-sharing-cebw6q" data-anchor="_smart_spawning_gotcha_1_unintentional_file_descriptor_sharing">11.3. Smart spawning gotcha #1: unintentional file descriptor sharing</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_smart_spawning_gotcha_1_unintentional_file_descriptor_sharing" data-comment-topic="smart-spawning-gotcha-1-unintentional-file-descriptor-sharing-cebw6q">12.3. Smart spawning gotcha #1: unintentional file descriptor sharing</h3>
 <div class="paragraph"><p>Because worker processes are created by forking from an ApplicationSpawner
 server, it will share all file descriptors that are opened by the
 ApplicationSpawner server. (This is part of the semantics of the Unix
@@ -4438,7 +4327,7 @@ http://www.gnu.org/software/src-highlite -->
             <span style="font-style: italic"><span style="color: #9A1900"># We're in smart spawning mode.</span></span>
             <span style="color: #990000">...</span> code to reestablish socket connections here <span style="color: #990000">...</span>
         <span style="font-weight: bold"><span style="color: #0000FF">else</span></span>
-            <span style="font-style: italic"><span style="color: #9A1900"># We're in conservative spawning mode. We don't need to do anything.</span></span>
+            <span style="font-style: italic"><span style="color: #9A1900"># We're in direct spawning mode. We don't need to do anything.</span></span>
         <span style="font-weight: bold"><span style="color: #0000FF">end</span></span>
     <span style="font-weight: bold"><span style="color: #0000FF">end</span></span>
 <span style="font-weight: bold"><span style="color: #0000FF">end</span></span></tt></pre>
@@ -4448,7 +4337,7 @@ http://www.gnu.org/software/src-highlite -->
 database upon creating a new worker process, which is why you normally do not
 encounter any database issues when using smart spawning mode.</p></div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_example_1_memcached_connection_sharing_harmful"></span><h4 data-comment-topic="example-1-memcached-connection-sharing-harmful--1wfs3ad" data-anchor="_example_1_memcached_connection_sharing_harmful">11.3.1. Example 1: Memcached connection sharing (harmful)</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_example_1_memcached_connection_sharing_harmful" data-comment-topic="example-1-memcached-connection-sharing-harmful--1wfs3ad">12.3.1. Example 1: Memcached connection sharing (harmful)</h4>
 <div class="paragraph"><p>Suppose we have a Rails application that connects to a Memcached server in
 <em>environment.rb</em>. This causes the ApplicationSpawner to have a socket connection
 (file descriptor) to the Memcached server, as shown in the following figure:</p></div>
@@ -4539,7 +4428,7 @@ http://www.gnu.org/software/src-highlite -->
             <span style="font-style: italic"><span style="color: #9A1900"># We're in smart spawning mode.</span></span>
             reestablish_connection_to_memcached
         <span style="font-weight: bold"><span style="color: #0000FF">else</span></span>
-            <span style="font-style: italic"><span style="color: #9A1900"># We're in conservative spawning mode. We don't need to do anything.</span></span>
+            <span style="font-style: italic"><span style="color: #9A1900"># We're in direct spawning mode. We don't need to do anything.</span></span>
         <span style="font-weight: bold"><span style="color: #0000FF">end</span></span>
     <span style="font-weight: bold"><span style="color: #0000FF">end</span></span>
 <span style="font-weight: bold"><span style="color: #0000FF">end</span></span></tt></pre>
@@ -4547,7 +4436,7 @@ http://www.gnu.org/software/src-highlite -->
 </div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_example_2_log_file_sharing_not_harmful"></span><h4 data-comment-topic="example-2-log-file-sharing-not-harmful--ox4yfy" data-anchor="_example_2_log_file_sharing_not_harmful">11.3.2. Example 2: Log file sharing (not harmful)</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_example_2_log_file_sharing_not_harmful" data-comment-topic="example-2-log-file-sharing-not-harmful--ox4yfy">12.3.2. Example 2: Log file sharing (not harmful)</h4>
 <div class="paragraph"><p>There are also cases in which unintentional file descriptor sharing is not harmful.
 One such case is log file file descriptor sharing. Even if two processes write
 to the log file at the same time, the worst thing that can happen is that the
@@ -4559,7 +4448,7 @@ Memcached example, doesn’t help.</p></div>
 </div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_smart_spawning_gotcha_2_the_need_to_revive_threads"></span><h3 data-comment-topic="smart-spawning-gotcha-2-the-need-to-revive-threads-1ey176o" data-anchor="_smart_spawning_gotcha_2_the_need_to_revive_threads">11.4. Smart spawning gotcha #2: the need to revive threads</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_smart_spawning_gotcha_2_the_need_to_revive_threads" data-comment-topic="smart-spawning-gotcha-2-the-need-to-revive-threads-1ey176o">12.4. Smart spawning gotcha #2: the need to revive threads</h3>
 <div class="paragraph"><p>Another part of the <em>fork()</em> system call’s semantics is the fact that threads
 disappear after a fork call. So if you’ve created any threads in environment.rb,
 then those threads will no longer be running in newly created worker process.
@@ -4577,7 +4466,7 @@ http://www.gnu.org/software/src-highlite -->
             <span style="font-style: italic"><span style="color: #9A1900"># We're in smart spawning mode.</span></span>
             <span style="color: #990000">...</span> code to revive threads here <span style="color: #990000">...</span>
         <span style="font-weight: bold"><span style="color: #0000FF">else</span></span>
-            <span style="font-style: italic"><span style="color: #9A1900"># We're in conservative spawning mode. We don't need to do anything.</span></span>
+            <span style="font-style: italic"><span style="color: #9A1900"># We're in direct spawning mode. We don't need to do anything.</span></span>
         <span style="font-weight: bold"><span style="color: #0000FF">end</span></span>
     <span style="font-weight: bold"><span style="color: #0000FF">end</span></span>
 <span style="font-weight: bold"><span style="color: #0000FF">end</span></span></tt></pre>
@@ -4585,7 +4474,7 @@ http://www.gnu.org/software/src-highlite -->
 </div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_smart_spawning_gotcha_3_code_load_order"></span><h3 data-comment-topic="smart-spawning-gotcha-3-code-load-order-12ydsn8" data-anchor="_smart_spawning_gotcha_3_code_load_order">11.5. Smart spawning gotcha #3: code load order</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_smart_spawning_gotcha_3_code_load_order" data-comment-topic="smart-spawning-gotcha-3-code-load-order-12ydsn8">12.5. Smart spawning gotcha #3: code load order</h3>
 <div class="paragraph"><p>This gotcha is only applicable to the <em>smart</em> spawn method, not the <em>smart-lv2</em>
 spawn method.</p></div>
 <div class="paragraph"><p>If your application expects the Rails framework to be not loaded during the
@@ -4607,7 +4496,9 @@ has no effect.</p></div>
 </div>
 <div id="footnotes"><hr></div>
 <div id="footer">
-
+<div id="footer-text">
+Last updated 2012-10-24 16:27:54 CEST
+</div>
 </div>
 <script>/*! jQuery v1.7.1 jquery.com | jquery.org/license */
 (function(a,b){function cy(a){return f.isWindow(a)?a:a.nodeType===9?a.defaultView||a.parentWindow:!1}function cv(a){if(!ck[a]){var b=c.body,d=f("<"+a+">").appendTo(b),e=d.css("display");d.remove();if(e==="none"||e===""){cl||(cl=c.createElement("iframe"),cl.frameBorder=cl.width=cl.height=0),b.appendChild(cl);if(!cm||!cl.createElement)cm=(cl.contentWindow||cl.contentDocument).document,cm.write((c.compatMode==="CSS1Compat"?"<!doctype html>":"")+"<html><body>"),cm.close();d=cm.createElement(a),cm.body.appendChild(d),e=f.css(d,"display"),b.removeChild(cl)}ck[a]=e}return ck[a]}function cu(a,b){var c={};f.each(cq.concat.apply([],cq.slice(0,b)),function(){c[this]=a});return c}function ct(){cr=b}function cs(){setTimeout(ct,0);return cr=f.now()}function cj(){try{return new a.ActiveXObject("Microsoft.XMLHTTP")}catch(b){}}function ci(){try{return new a.XMLHttpRequest}catch(b){}}function cc(a,c){a.dataFilter&&(c=a.dataFilter(c,a.dataType));var d=a.dataTypes,e={},g,h,i=d.length,j,k=d[0],l,m,n,o,p;for(g=1;g<i;g++){if(g===1)for(h in a.converters)typeof h=="string"&&(e[h.toLowerCase()]=a.converters[h]);l=k,k=d[g];if(k==="*")k=l;else if(l!=="*"&&l!==k){m=l+" "+k,n=e[m]||e["* "+k];if(!n){p=b;for(o in e){j=o.split(" ");if(j[0]===l||j[0]==="*"){p=e[j[1]+" "+k];if(p){o=e[o],o===!0?n=p:p===!0&&(n=o);break}}}}!n&&!p&&f.error("No conversion from "+m.replace(" "," to ")),n!==!0&&(c=n?n(c):p(o(c)))}}return c}function cb(a,c,d){var e=a.contents,f=a.dataTypes,g=a.responseFields,h,i,j,k;for(i in g)i in d&&(c[g[i]]=d[i]);while(f[0]==="*")f.shift(),h===b&&(h=a.mimeType||c.getResponseHeader("content-type"));if(h)for(i in e)if(e[i]&&e[i].test(h)){f.unshift(i);break}if(f[0]in d)j=f[0];else{for(i in d){if(!f[0]||a.converters[i+" "+f[0]]){j=i;break}k||(k=i)}j=j||k}if(j){j!==f[0]&&f.unshift(j);return d[j]}}function ca(a,b,c,d){if(f.isArray(b))f.each(b,function(b,e){c||bE.test(a)?d(a,e):ca(a+"["+(typeof e=="object"||f.isArray(e)?b:"")+"]",e,c,d)});else if(!c&&b!=null&&typeof b=="object")for(var e in b)ca(a+"["+e+"]",b[e],c,d);else d(a,b)}function b_(a,c){var d,e,g=f.ajaxSettings.flatOptions||{};for(d in c)c[d]!==b&&((g[d]?a:e||(e={}))[d]=c[d]);e&&f.extend(!0,a,e)}function b$(a,c,d,e,f,g){f=f||c.dataTypes[0],g=g||{},g[f]=!0;var h=a[f],i=0,j=h?h.length:0,k=a===bT,l;for(;i<j&&(k||!l);i++)l=h[i](c,d,e),typeof l=="string"&&(!k||g[l]?l=b:(c.dataTypes.unshift(l),l=b$(a,c,d,e,l,g)));(k||!l)&&!g["*"]&&(l=b$(a,c,d,e,"*",g));return l}function bZ(a){return function(b,c){typeof b!="string"&&(c=b,b="*");if(f.isFunction(c)){var d=b.toLowerCase().split(bP),e=0,g=d.length,h,i,j;for(;e<g;e++)h=d[e],j=/^\+/.test(h),j&&(h=h.substr(1)||"*"),i=a[h]=a[h]||[],i[j?"unshift":"push"](c)}}}function bC(a,b,c){var d=b==="width"?a.offsetWidth:a.offsetHeight,e=b==="width"?bx:by,g=0,h=e.length;if(d>0){if(c!=="border")for(;g<h;g++)c||(d-=parseFloat(f.css(a,"padding"+e[g]))||0),c==="margin"?d+=parseFloat(f.css(a,c+e[g]))||0:d-=parseFloat(f.css(a,"border"+e[g]+"Width"))||0;return d+"px"}d=bz(a,b,b);if(d<0||d==null)d=a.style[b]||0;d=parseFloat(d)||0;if(c)for(;g<h;g++)d+=parseFloat(f.css(a,"padding"+e[g]))||0,c!=="padding"&&(d+=parseFloat(f.css(a,"border"+e[g]+"Width"))||0),c==="margin"&&(d+=parseFloat(f.css(a,c+e[g]))||0);return d+"px"}function bp(a,b){b.src?f.ajax({url:b.src,async:!1,dataType:"script"}):f.globalEval((b.text||b.textContent||b.innerHTML||"").replace(bf,"/*$0*/")),b.parentNode&&b.parentNode.removeChild(b)}function bo(a){var b=c.createElement("div");bh.appendChild(b),b.innerHTML=a.outerHTML;return b.firstChild}function bn(a){var b=(a.nodeName||"").toLowerCase();b==="input"?bm(a):b!=="script"&&typeof a.getElementsByTagName!="undefined"&&f.grep(a.getElementsByTagName("input"),bm)}function bm(a){if(a.type==="checkbox"||a.type==="radio")a.defaultChecked=a.checked}function bl(a){return typeof a.getElementsByTagName!="undefined"?a.getElementsByTagName("*"):typeof a.querySelectorAll!="undefined"?a.querySelectorAll("*"):[]}function bk(a,b){var c;if(b.nodeType===1){b.clearAttributes&&b.clearAttributes(),b.mergeAttributes&&b.mergeAttributes(a),c=b.nodeName.toLowerCase();if(c==="object")b.outerHTML=a.outerHTML;else if(c!=="input"||a.type!=="checkbox"&&a.type!=="radio"){if(c==="option")b.selected=a.defaultSelected;else if(c==="input"||c==="textarea")b.defaultValue=a.defaultValue}else a.checked&&(b.defaultChecked=b.checked=a.checked),b.value!==a.value&&(b.value=a.value);b.removeAttribute(f.expando)}}function bj(a,b){if(b.nodeType===1&&!!f.hasData(a)){var c,d,e,g=f._data(a),h=f._data(b,g),i=g.events;if(i){delete h.handle,h.events={};for(c in i)for(d=0,e=i[c].length;d<e;d++)f.event.add(b,c+(i[c][d].namespace?".":"")+i[c][d].namespace,i[c][d],i[c][d].data)}h.data&&(h.data=f.extend({},h.data))}}function bi(a,b){return f.nodeName(a,"table")?a.getElementsByTagName("tbody")[0]||a.appendChild(a.ownerDocument.createElement("tbody")):a}function U(a){var b=V.split("|"),c=a.createDocumentFragment();if(c.createElement)while(b.length)c.createElement(b.pop());return c}function T(a,b,c){b=b||0;if(f.isFunction(b))return f.grep(a,function(a,d){var e=!!b.call(a,d,a);return e===c});if(b.nodeType)return f.grep(a,function(a,d){return a===b===c});if(typeof b=="string"){var d=f.grep(a,function(a){return a.nodeType===1});if(O.test(b))return f.filter(b,d,!c);b=f.filter(b,d)}return f.grep(a,function(a,d){return f.inArray(a,b)>=0===c})}function S(a){return!a||!a.parentNode||a.parentNode.nodeType===11}function K(){return!0}function J(){return!1}function n(a,b,c){var d=b+"defer",e=b+"queue",g=b+"mark",h=f._data(a,d);h&&(c==="queue"||!f._data(a,e))&&(c==="mark"||!f._data(a,g))&&setTimeout(function(){!f._data(a,e)&&!f._data(a,g)&&(f.removeData(a,d,!0),h.fire())},0)}function m(a){for(var b in a){if(b==="data"&&f.isEmptyObject(a[b]))continue;if(b!=="toJSON")return!1}return!0}function l(a,c,d){if(d===b&&a.nodeType===1){var e="data-"+c.replace(k,"-$1").toLowerCase();d=a.getAttribute(e);if(typeof d=="string"){try{d=d==="true"?!0:d==="false"?!1:d==="null"?null:f.isNumeric(d)?parseFloat(d):j.test(d)?f.parseJSON(d):d}catch(g){}f.data(a,c,d)}else d=b}return d}function h(a){var b=g[a]={},c,d;a=a.split(/\s+/);for(c=0,d=a.length;c<d;c++)b[a[c]]=!0;return b}var c=a.document,d=a.navigator,e=a.location,f=function(){function J(){if(!e.isReady){try{c.documentElement.doScroll("left")}catch(a){setTimeout(J,1);return}e.ready()}}var e=function(a,b){return new e.fn.init(a,b,h)},f=a.jQuery,g=a.$,h,i=/^(?:[^#<]*(<[\w\W]+>)[^>]*$|#([\w\-]*)$)/,j=/\S/,k=/^\s+/,l=/\s+$/,m=/^<(\w+)\s*\/?>(?:<\/\1>)?$/,n=/^[\],:{}\s]*$/,o=/\\(?:["\\\/bfnrt]|u[0-9a-fA-F]{4})/g,p=/"[^"\\\n\r]*"|true|false|null|-?\d+(?:\.\d*)?(?:[eE][+\-]?\d+)?/g,q=/(?:^|:|,)(?:\s*\[)+/g,r=/(webkit)[ \/]([\w.]+)/,s=/(opera)(?:.*version)?[ \/]([\w.]+)/,t=/(msie) ([\w.]+)/,u=/(mozilla)(?:.*? rv:([\w.]+))?/,v=/-([a-z]|[0-9])/ig,w=/^-ms-/,x=function(a,b){return(b+"").toUpperCase()},y=d.userAgent,z,A,B,C=Object.prototype.toString,D=Object.prototype.hasOwnProperty,E=Array.prototype.push,F=Array.prototype.slice,G=String.prototype.trim,H=Array.prototype.indexOf,I={};e.fn=e.prototype={constructor:e,init:function(a,d,f){var g,h,j,k;if(!a)return this;if(a.nodeType){this.context=this[0]=a,this.length=1;return this}if(a==="body"&&!d&&c.body){this.context=c,this[0]=c.body,this.selector=a,this.length=1;return this}if(typeof a=="string"){a.charAt(0)!=="<"||a.charAt(a.length-1)!==">"||a.length<3?g=i.exec(a):g=[null,a,null];if(g&&(g[1]||!d)){if(g[1]){d=d instanceof e?d[0]:d,k=d?d.ownerDocument||d:c,j=m.exec(a),j?e.isPlainObject(d)?(a=[c.createElement(j[1])],e.fn.attr.call(a,d,!0)):a=[k.createElement(j[1])]:(j=e.buildFragment([g[1]],[k]),a=(j.cacheable?e.clone(j.fragment):j.fragment).childNodes);return e.merge(this,a)}h=c.getElementById(g[2]);if(h&&h.parentNode){if(h.id!==g[2])return f.find(a);this.length=1,this[0]=h}this.context=c,this.selector=a;return this}return!d||d.jquery?(d||f).find(a):this.constructor(d).find(a)}if(e.isFunction(a))return f.ready(a);a.selector!==b&&(this.selector=a.selector,this.context=a.context);return e.makeArray(a,this)},selector:"",jquery:"1.7.1",length:0,size:function(){return this.length},toArray:function(){return F.call(this,0)},get:function(a){return a==null?this.toArray():a<0?this[this.length+a]:this[a]},pushStack:function(a,b,c){var d=this.constructor();e.isArray(a)?E.apply(d,a):e.merge(d,a),d.prevObject=this,d.context=this.context,b==="find"?d.selector=this.selector+(this.selector?" ":"")+c:b&&(d.selector=this.selector+"."+b+"("+c+")");return d},each:function(a,b){return e.each(this,a,b)},ready:function(a){e.bindReady(),A.add(a);return this},eq:function(a){a=+a;return a===-1?this.slice(a):this.slice(a,a+1)},first:function(){return this.eq(0)},last:function(){return this.eq(-1)},slice:function(){return this.pushStack(F.apply(this,arguments),"slice",F.call(arguments).join(","))},map:function(a){return this.pushStack(e.map(this,function(b,c){return a.call(b,c,b)}))},end:function(){return this.prevObject||this.constructor(null)},push:E,sort:[].sort,splice:[].splice},e.fn.init.prototype=e.fn,e.extend=e.fn.extend=function(){var a,c,d,f,g,h,i=arguments[0]||{},j=1,k=arguments.length,l=!1;typeof i=="boolean"&&(l=i,i=arguments[1]||{},j=2),typeof i!="object"&&!e.isFunction(i)&&(i={}),k===j&&(i=this,--j);for(;j<k;j++)if((a=arguments[j])!=null)for(c in a){d=i[c],f=a[c];if(i===f)continue;l&&f&&(e.isPlainObject(f)||(g=e.isArray(f)))?(g?(g=!1,h=d&&e.isArray(d)?d:[]):h=d&&e.isPlainObject(d)?d:{},i[c]=e.extend(l,h,f)):f!==b&&(i[c]=f)}return i},e.extend({noConflict:function(b){a.$===e&&(a.$=g),b&&a.jQuery===e&&(a.jQuery=f);return e},isReady:!1,readyWait:1,holdReady:function(a){a?e.readyWait++:e.ready(!0)},ready:function(a){if(a===!0&&!--e.readyWait||a!==!0&&!e.isReady){if(!c.body)return setTimeout(e.ready,1);e.isReady=!0;if(a!==!0&&--e.readyWait>0)return;A.fireWith(c,[e]),e.fn.trigger&&e(c).trigger("ready").off("ready")}},bindReady:function(){if(!A){A=e.Callbacks("once memory");if(c.readyState==="complete")return setTimeout(e.ready,1);if(c.addEventListener)c.addEventListener("DOMContentLoaded",B,!1),a.addEventListener("load",e.ready,!1);else if(c.attachEvent){c.attachEvent("onreadystatechange",B),a.attachEvent("onload",e.ready);var b=!1;try{b=a.frameElement==null}catch(d){}c.documentElement.doScroll&&b&&J()}}},isFunction:function(a){return e.type(a)==="function"},isArray:Array.isArray||function(a){return e.type(a)==="array"},isWindow:function(a){return a&&typeof a=="object"&&"setInterval"in a},isNumeric:function(a){return!isNaN(parseFloat(a))&&isFinite(a)},type:function(a){return a==null?String(a):I[C.call(a)]||"object"},isPlainObject:function(a){if(!a||e.type(a)!=="object"||a.nodeType||e.isWindow(a))return!1;try{if(a.constructor&&!D.call(a,"constructor")&&!D.call(a.constructor.prototype,"isPrototypeOf"))return!1}catch(c){return!1}var d;for(d in a);return d===b||D.call(a,d)},isEmptyObject:function(a){for(var b in a)return!1;return!0},error:function(a){throw new Error(a)},parseJSON:function(b){if(typeof b!="string"||!b)return null;b=e.trim(b);if(a.JSON&&a.JSON.parse)return a.JSON.parse(b);if(n.test(b.replace(o,"@").replace(p,"]").replace(q,"")))return(new Function("return "+b))();e.error("Invalid JSON: "+b)},parseXML:function(c){var d,f;try{a.DOMParser?(f=new DOMParser,d=f.parseFromString(c,"text/xml")):(d=new ActiveXObject("Microsoft.XMLDOM"),d.async="false",d.loadXML(c))}catch(g){d=b}(!d||!d.documentElement||d.getElementsByTagName("parsererror").length)&&e.error("Invalid XML: "+c);return d},noop:function(){},globalEval:function(b){b&&j.test(b)&&(a.execScript||function(b){a.eval.call(a,b)})(b)},camelCase:function(a){return a.replace(w,"ms-").replace(v,x)},nodeName:function(a,b){return a.nodeName&&a.nodeName.toUpperCase()===b.toUpperCase()},each:function(a,c,d){var f,g=0,h=a.length,i=h===b||e.isFunction(a);if(d){if(i){for(f in a)if(c.apply(a[f],d)===!1)break}else for(;g<h;)if(c.apply(a[g++],d)===!1)break}else if(i){for(f in a)if(c.call(a[f],f,a[f])===!1)break}else for(;g<h;)if(c.call(a[g],g,a[g++])===!1)break;return a},trim:G?function(a){return a==null?"":G.call(a)}:function(a){return a==null?"":(a+"").replace(k,"").replace(l,"")},makeArray:function(a,b){var c=b||[];if(a!=null){var d=e.type(a);a.length==null||d==="string"||d==="function"||d==="regexp"||e.isWindow(a)?E.call(c,a):e.merge(c,a)}return c},inArray:function(a,b,c){var d;if(b){if(H)return H.call(b,a,c);d=b.length,c=c?c<0?Math.max(0,d+c):c:0;for(;c<d;c++)if(c in b&&b[c]===a)return c}return-1},merge:function(a,c){var d=a.length,e=0;if(typeof c.length=="number")for(var f=c.length;e<f;e++)a[d++]=c[e];else while(c[e]!==b)a[d++]=c[e++];a.length=d;return a},grep:function(a,b,c){var d=[],e;c=!!c;for(var f=0,g=a.length;f<g;f++)e=!!b(a[f],f),c!==e&&d.push(a[f]);return d},map:function(a,c,d){var f,g,h=[],i=0,j=a.length,k=a instanceof e||j!==b&&typeof j=="number"&&(j>0&&a[0]&&a[j-1]||j===0||e.isArray(a));if(k)for(;i<j;i++)f=c(a[i],i,d),f!=null&&(h[h.length]=f);else for(g in a)f=c(a[g],g,d),f!=null&&(h[h.length]=f);return h.concat.apply([],h)},guid:1,proxy:function(a,c){if(typeof c=="string"){var d=a[c];c=a,a=d}if(!e.isFunction(a))return b;var f=F.call(arguments,2),g=function(){return a.apply(c,f.concat(F.call(arguments)))};g.guid=a.guid=a.guid||g.guid||e.guid++;return g},access:function(a,c,d,f,g,h){var i=a.length;if(typeof c=="object"){for(var j in c)e.access(a,j,c[j],f,g,d);return a}if(d!==b){f=!h&&f&&e.isFunction(d);for(var k=0;k<i;k++)g(a[k],c,f?d.call(a[k],k,g(a[k],c)):d,h);return a}return i?g(a[0],c):b},now:function(){return(new Date).getTime()},uaMatch:function(a){a=a.toLowerCase();var b=r.exec(a)||s.exec(a)||t.exec(a)||a.indexOf("compatible")<0&&u.exec(a)||[];return{browser:b[1]||"",version:b[2]||"0"}},sub:function(){function a(b,c){return new a.fn.init(b,c)}e.extend(!0,a,this),a.superclass=this,a.fn=a.prototype=this(),a.fn.constructor=a,a.sub=this.sub,a.fn.init=function(d,f){f&&f instanceof e&&!(f instanceof a)&&(f=a(f));return e.fn.init.call(this,d,f,b)},a.fn.init.prototype=a.fn;var b=a(c);return a},browser:{}}),e.each("Boolean Number String Function Array Date RegExp Object".split(" "),function(a,b){I["[object "+b+"]"]=b.toLowerCase()}),z=e.uaMatch(y),z.browser&&(e.browser[z.browser]=!0,e.browser.version=z.version),e.browser.webkit&&(e.browser.safari=!0),j.test(" ")&&(k=/^[\s\xA0]+/,l=/[\s\xA0]+$/),h=e(c),c.addEventListener?B=function(){c.removeEventListener("DOMContentLoaded",B,!1),e.ready()}:c.attachEvent&&(B=function(){c.readyState==="complete"&&(c.detachEvent("onreadystatechange",B),e.ready())});return e}(),g={};f.Callbacks=function(a){a=a?g[a]||h(a):{};var c=[],d=[],e,i,j,k,l,m=function(b){var d,e,g,h,i;for(d=0,e=b.length;d<e;d++)g=b[d],h=f.type(g),h==="array"?m(g):h==="function"&&(!a.unique||!o.has(g))&&c.push(g)},n=function(b,f){f=f||[],e=!a.memory||[b,f],i=!0,l=j||0,j=0,k=c.length;for(;c&&l<k;l++)if(c[l].apply(b,f)===!1&&a.stopOnFalse){e=!0;break}i=!1,c&&(a.once?e===!0?o.disable():c=[]:d&&d.length&&(e=d.shift(),o.fireWith(e[0],e[1])))},o={add:function(){if(c){var a=c.length;m(arguments),i?k=c.length:e&&e!==!0&&(j=a,n(e[0],e[1]))}return this},remove:function(){if(c){var b=arguments,d=0,e=b.length;for(;d<e;d++)for(var f=0;f<c.length;f++)if(b[d]===c[f]){i&&f<=k&&(k--,f<=l&&l--),c.splice(f--,1);if(a.unique)break}}return this},has:function(a){if(c){var b=0,d=c.length;for(;b<d;b++)if(a===c[b])return!0}return!1},empty:function(){c=[];return this},disable:function(){c=d=e=b;return this},disabled:function(){return!c},lock:function(){d=b,(!e||e===!0)&&o.disable();return this},locked:function(){return!d},fireWith:function(b,c){d&&(i?a.once||d.push([b,c]):(!a.once||!e)&&n(b,c));return this},fire:function(){o.fireWith(this,arguments);return this},fired:function(){return!!e}};return o};var i=[].slice;f.extend({Deferred:function(a){var b=f.Callbacks("once memory"),c=f.Callbacks("once memory"),d=f.Callbacks("memory"),e="pending",g={resolve:b,reject:c,notify:d},h={done:b.add,fail:c.add,progress:d.add,state:function(){return e},isResolved:b.fired,isRejected:c.fired,then:function(a,b,c){i.done(a).fail(b).progress(c);return this},always:function(){i.done.apply(i,arguments).fail.apply(i,arguments);return this},pipe:function(a,b,c){return f.Deferred(function(d){f.each({done:[a,"resolve"],fail:[b,"reject"],progress:[c,"notify"]},function(a,b){var c=b[0],e=b[1],g;f.isFunction(c)?i[a](function(){g=c.apply(this,arguments),g&&f.isFunction(g.promise)?g.promise().then(d.resolve,d.reject,d.notify):d[e+"With"](this===i?d:this,[g])}):i[a](d[e])})}).promise()},promise:function(a){if(a==null)a=h;else for(var b in h)a[b]=h[b];return a}},i=h.promise({}),j;for(j in g)i[j]=g[j].fire,i[j+"With"]=g[j].fireWith;i.done(function(){e="resolved"},c.disable,d.lock).fail(function(){e="rejected"},b.disable,d.lock),a&&a.call(i,i);return i},when:function(a){function m(a){return function(b){e[a]=arguments.length>1?i.call(arguments,0):b,j.notifyWith(k,e)}}function l(a){return function(c){b[a]=arguments.length>1?i.call(arguments,0):c,--g||j.resolveWith(j,b)}}var b=i.call(arguments,0),c=0,d=b.length,e=Array(d),g=d,h=d,j=d<=1&&a&&f.isFunction(a.promise)?a:f.Deferred(),k=j.promise();if(d>1){for(;c<d;c++)b[c]&&b[c].promise&&f.isFunction(b[c].promise)?b[c].promise().then(l(c),j.reject,m(c)):--g;g||j.resolveWith(j,b)}else j!==a&&j.resolveWith(j,d?[a]:[]);return k}}),f.support=function(){var b,d,e,g,h,i,j,k,l,m,n,o,p,q=c.createElement("div"),r=c.documentElement;q.setAttribute("className","t"),q.innerHTML="   <link/><table></table><a href='/a' style='top:1px;float:left;opacity:.55;'>a</a><input type='checkbox'/>",d=q.getElementsByTagName("*"),e=q.getElementsByTagName("a")[0];if(!d||!d.length||!e)return{};g=c.createElement("select"),h=g.appendChild(c.createElement("option")),i=q.getElementsByTagName("input")[0],b={leadingWhitespace:q.firstChild.nodeType===3,tbody:!q.getElementsByTagName("tbody").length,htmlSerialize:!!q.getElementsByTagName("link").length,style:/top/.test(e.getAttribute("style")),hrefNormalized:e.getAttribute("href")==="/a",opacity:/^0.55/.test(e.style.opacity),cssFloat:!!e.style.cssFloat,checkOn:i.value==="on",optSelected:h.selected,getSetAttribute:q.className!=="t",enctype:!!c.createElement("form").enctype,html5Clone:c.createElement("nav").cloneNode(!0).outerHTML!=="<:nav></:nav>",submitBubbles:!0,changeBubbles:!0,focusinBubbles:!1,deleteExpando:!0,noCloneEvent:!0,inlineBlockNeedsLayout:!1,shrinkWrapBlocks:!1,reliableMarginRight:!0},i.checked=!0,b.noCloneChecked=i.cloneNode(!0).checked,g.disabled=!0,b.optDisabled=!h.disabled;try{delete q.test}catch(s){b.deleteExpando=!1}!q.addEventListener&&q.attachEvent&&q.fireEvent&&(q.attachEvent("onclick",function(){b.noCloneEvent=!1}),q.cloneNode(!0).fireEvent("onclick")),i=c.createElement("input"),i.value="t",i.setAttribute("type","radio"),b.radioValue=i.value==="t",i.setAttribute("checked","checked"),q.appendChild(i),k=c.createDocumentFragment(),k.appendChild(q.lastChild),b.checkClone=k.cloneNode(!0).cloneNode(!0).lastChild.checked,b.appendChecked=i.checked,k.removeChild(i),k.appendChild(q),q.innerHTML="",a.getComputedStyle&&(j=c.createElement("div"),j.style.width="0",j.style.marginRight="0",q.style.width="2px",q.appendChild(j),b.reliableMarginRight=(parseInt((a.getComputedStyle(j,null)||{marginRight:0}).marginRight,10)||0)===0);if(q.attachEvent)for(o in{submit:1,change:1,focusin:1})n="on"+o,p=n in q,p||(q.setAttribute(n,"return;"),p=typeof q[n]=="function"),b[o+"Bubbles"]=p;k.removeChild(q),k=g=h=j=q=i=null,f(function(){var a,d,e,g,h,i,j,k,m,n,o,r=c.getElementsByTagName("body")[0];!r||(j=1,k="position:absolute;top:0;left:0;width:1px;height:1px;margin:0;",m="visibility:hidden;border:0;",n="style='"+k+"border:5px solid #000;padding:0;'",o="<div "+n+"><div></div></div>"+"<table "+n+" cellpadding='0' cellspacing='0'>"+"<tr><td></td></tr></table>",a=c.createElement("div"),a.style.cssText=m+"width:0;height:0;position:static;top:0;margin-top:"+j+"px",r.insertBefore(a,r.firstChild),q=c.createElement("div"),a.appendChild(q),q.innerHTML="<table><tr><td style='padding:0;border:0;display:none'></td><td>t</td></tr></table>",l=q.getElementsByTagName("td"),p=l[0].offsetHeight===0,l[0].style.display="",l[1].style.display="none",b.reliableHiddenOffsets=p&&l[0].offsetHeight===0,q.innerHTML="",q.style.width=q.style.paddingLeft="1px",f.boxModel=b.boxModel=q.offsetWidth===2,typeof q.style.zoom!="undefined"&&(q.style.display="inline",q.style.zoom=1,b.inlineBlockNeedsLayout=q.offsetWidth===2,q.style.display="",q.innerHTML="<div style='width:4px;'></div>",b.shrinkWrapBlocks=q.offsetWidth!==2),q.style.cssText=k+m,q.innerHTML=o,d=q.firstChild,e=d.firstChild,h=d.nextSibling.firstChild.firstChild,i={doesNotAddBorder:e.offsetTop!==5,doesAddBorderForTableAndCells:h.offsetTop===5},e.style.position="fixed",e.style.top="20px",i.fixedPosition=e.offsetTop===20||e.offsetTop===15,e.style.position=e.style.top="",d.style.overflow="hidden",d.style.position="relative",i.subtractsBorderForOverflowNotVisible=e.offsetTop===-5,i.doesNotIncludeMarginInBodyOffset=r.offsetTop!==j,r.removeChild(a),q=a=null,f.extend(b,i))});return b}();var j=/^(?:\{.*\}|\[.*\])$/,k=/([A-Z])/g;f.extend({cache:{},uuid:0,expando:"jQuery"+(f.fn.jquery+Math.random()).replace(/\D/g,""),noData:{embed:!0,object:"clsid:D27CDB6E-AE6D-11cf-96B8-444553540000",applet:!0},hasData:function(a){a=a.nodeType?f.cache[a[f.expando]]:a[f.expando];return!!a&&!m(a)},data:function(a,c,d,e){if(!!f.acceptData(a)){var g,h,i,j=f.expando,k=typeof c=="string",l=a.nodeType,m=l?f.cache:a,n=l?a[j]:a[j]&&j,o=c==="events";if((!n||!m[n]||!o&&!e&&!m[n].data)&&k&&d===b)return;n||(l?a[j]=n=++f.uuid:n=j),m[n]||(m[n]={},l||(m[n].toJSON=f.noop));if(typeof c=="object"||typeof c=="function")e?m[n]=f.extend(m[n],c):m[n].data=f.extend(m[n].data,c);g=h=m[n],e||(h.data||(h.data={}),h=h.data),d!==b&&(h[f.camelCase(c)]=d);if(o&&!h[c])return g.events;k?(i=h[c],i==null&&(i=h[f.camelCase(c)])):i=h;return i}},removeData:function(a,b,c){if(!!f.acceptData(a)){var d,e,g,h=f.expando,i=a.nodeType,j=i?f.cache:a,k=i?a[h]:h;if(!j[k])return;if(b){d=c?j[k]:j[k].data;if(d){f.isArray(b)||(b in d?b=[b]:(b=f.camelCase(b),b in d?b=[b]:b=b.split(" ")));for(e=0,g=b.length;e<g;e++)delete d[b[e]];if(!(c?m:f.isEmptyObject)(d))return}}if(!c){delete j[k].data;if(!m(j[k]))return}f.support.deleteExpando||!j.setInterval?delete j[k]:j[k]=null,i&&(f.support.deleteExpando?delete a[h]:a.removeAttribute?a.removeAttribute(h):a[h]=null)}},_data:function(a,b,c){return f.data(a,b,c,!0)},acceptData:function(a){if(a.nodeName){var b=f.noData[a.nodeName.toLowerCase()];if(b)return b!==!0&&a.getAttribute("classid")===b}return!0}}),f.fn.extend({data:function(a,c){var d,e,g,h=null;if(typeof a=="undefined"){if(this.length){h=f.data(this[0]);if(this[0].nodeType===1&&!f._data(this[0],"parsedAttrs")){e=this[0].attributes;for(var i=0,j=e.length;i<j;i++)g=e[i].name,g.indexOf("data-")===0&&(g=f.camelCase(g.substring(5)),l(this[0],g,h[g]));f._data(this[0],"parsedAttrs",!0)}}return h}if(typeof a=="object")return this.each(function(){f.data(this,a)});d=a.split("."),d[1]=d[1]?"."+d[1]:"";if(c===b){h=this.triggerHandler("getData"+d[1]+"!",[d[0]]),h===b&&this.length&&(h=f.data(this[0],a),h=l(this[0],a,h));return h===b&&d[1]?this.data(d[0]):h}return this.each(function(){var b=f(this),e=[d[0],c];b.triggerHandler("setData"+d[1]+"!",e),f.data(this,a,c),b.triggerHandler("changeData"+d[1]+"!",e)})},removeData:function(a){return this.each(function(){f.removeData(this,a)})}}),f.extend({_mark:function(a,b){a&&(b=(b||"fx")+"mark",f._data(a,b,(f._data(a,b)||0)+1))},_unmark:function(a,b,c){a!==!0&&(c=b,b=a,a=!1);if(b){c=c||"fx";var d=c+"mark",e=a?0:(f._data(b,d)||1)-1;e?f._data(b,d,e):(f.removeData(b,d,!0),n(b,c,"mark"))}},queue:function(a,b,c){var d;if(a){b=(b||"fx")+"queue",d=f._data(a,b),c&&(!d||f.isArray(c)?d=f._data(a,b,f.makeArray(c)):d.push(c));return d||[]}},dequeue:function(a,b){b=b||"fx";var c=f.queue(a,b),d=c.shift(),e={};d==="inprogress"&&(d=c.shift()),d&&(b==="fx"&&c.unshift("inprogress"),f._data(a,b+".run",e),d.call(a,function(){f.dequeue(a,b)},e)),c.length||(f.removeData(a,b+"queue "+b+".run",!0),n(a,b,"queue"))}}),f.fn.extend({queue:function(a,c){typeof a!="string"&&(c=a,a="fx");if(c===b)return f.queue(this[0],a);return this.each(function(){var b=f.queue(this,a,c);a==="fx"&&b[0]!=="inprogress"&&f.dequeue(this,a)})},dequeue:function(a){return this.each(function(){f.dequeue(this,a)})},delay:function(a,b){a=f.fx?f.fx.speeds[a]||a:a,b=b||"fx";return this.queue(b,function(b,c){var d=setTimeout(b,a);c.stop=function(){clearTimeout(d)}})},clearQueue:function(a){return this.queue(a||"fx",[])},promise:function(a,c){function m(){--h||d.resolveWith(e,[e])}typeof a!="string"&&(c=a,a=b),a=a||"fx";var d=f.Deferred(),e=this,g=e.length,h=1,i=a+"defer",j=a+"queue",k=a+"mark",l;while(g--)if(l=f.data(e[g],i,b,!0)||(f.data(e[g],j,b,!0)||f.data(e[g],k,b,!0))&&f.data(e[g],i,f.Callbacks("once memory"),!0))h++,l.add(m);m();return d.promise()}});var o=/[\n\t\r]/g,p=/\s+/,q=/\r/g,r=/^(?:button|input)$/i,s=/^(?:button|input|object|select|textarea)$/i,t=/^a(?:rea)?$/i,u=/^(?:autofocus|autoplay|async|checked|controls|defer|disabled|hidden|loop|multiple|open|readonly|required|scoped|selected)$/i,v=f.support.getSetAttribute,w,x,y;f.fn.extend({attr:function(a,b){return f.access(this,a,b,!0,f.attr)},removeAttr:function(a){return this.each(function(){f.removeAttr(this,a)})},prop:function(a,b){return f.access(this,a,b,!0,f.prop)},removeProp:function(a){a=f.propFix[a]||a;return this.each(function(){try{this[a]=b,delete this[a]}catch(c){}})},addClass:function(a){var b,c,d,e,g,h,i;if(f.isFunction(a))return this.each(function(b){f(this).addClass(a.call(this,b,this.className))});if(a&&typeof a=="string"){b=a.split(p);for(c=0,d=this.length;c<d;c++){e=this[c];if(e.nodeType===1)if(!e.className&&b.length===1)e.className=a;else{g=" "+e.className+" ";for(h=0,i=b.length;h<i;h++)~g.indexOf(" "+b[h]+" ")||(g+=b[h]+" ");e.className=f.trim(g)}}}return this},removeClass:function(a){var c,d,e,g,h,i,j;if(f.isFunction(a))return this.each(function(b){f(this).removeClass(a.call(this,b,this.className))});if(a&&typeof a=="string"||a===b){c=(a||"").split(p);for(d=0,e=this.length;d<e;d++){g=this[d];if(g.nodeType===1&&g.className)if(a){h=(" "+g.className+" ").replace(o," ");for(i=0,j=c.length;i<j;i++)h=h.replace(" "+c[i]+" "," ");g.className=f.trim(h)}else g.className=""}}return this},toggleClass:function(a,b){var c=typeof a,d=typeof b=="boolean";if(f.isFunction(a))return this.each(function(c){f(this).toggleClass(a.call(this,c,this.className,b),b)});return this.each(function(){if(c==="string"){var e,g=0,h=f(this),i=b,j=a.split(p);while(e=j[g++])i=d?i:!h.hasClass(e),h[i?"addClass":"removeClass"](e)}else if(c==="undefined"||c==="boolean")this.className&&f._data(this,"__className__",this.className),this.className=this.className||a===!1?"":f._data(this,"__className__")||""})},hasClass:function(a){var b=" "+a+" ",c=0,d=this.length;for(;c<d;c++)if(this[c].nodeType===1&&(" "+this[c].className+" ").replace(o," ").indexOf(b)>-1)return!0;return!1},val:function(a){var c,d,e,g=this[0];{if(!!arguments.length){e=f.isFunction(a);return this.each(function(d){var g=f(this),h;if(this.nodeType===1){e?h=a.call(this,d,g.val()):h=a,h==null?h="":typeof h=="number"?h+="":f.isArray(h)&&(h=f.map(h,function(a){return a==null?"":a+""})),c=f.valHooks[this.nodeName.toLowerCase()]||f.valHooks[this.type];if(!c||!("set"in c)||c.set(this,h,"value")===b)this.value=h}})}if(g){c=f.valHooks[g.nodeName.toLowerCase()]||f.valHooks[g.type];if(c&&"get"in c&&(d=c.get(g,"value"))!==b)return d;d=g.value;return typeof d=="string"?d.replace(q,""):d==null?"":d}}}}),f.extend({valHooks:{option:{get:function(a){var b=a.attributes.value;return!b||b.specified?a.value:a.text}},select:{get:function(a){var b,c,d,e,g=a.selectedIndex,h=[],i=a.options,j=a.type==="select-one";if(g<0)return null;c=j?g:0,d=j?g+1:i.length;for(;c<d;c++){e=i[c];if(e.selected&&(f.support.optDisabled?!e.disabled:e.getAttribute("disabled")===null)&&(!e.parentNode.disabled||!f.nodeName(e.parentNode,"optgroup"))){b=f(e).val();if(j)return b;h.push(b)}}if(j&&!h.length&&i.length)return f(i[g]).val();return h},set:function(a,b){var c=f.makeArray(b);f(a).find("option").each(function(){this.selected=f.inArray(f(this).val(),c)>=0}),c.length||(a.selectedIndex=-1);return c}}},attrFn:{val:!0,css:!0,html:!0,text:!0,data:!0,width:!0,height:!0,offset:!0},attr:function(a,c,d,e){var g,h,i,j=a.nodeType;if(!!a&&j!==3&&j!==8&&j!==2){if(e&&c in f.attrFn)return f(a)[c](d);if(typeof a.getAttribute=="undefined")return f.prop(a,c,d);i=j!==1||!f.isXMLDoc(a),i&&(c=c.toLowerCase(),h=f.attrHooks[c]||(u.test(c)?x:w));if(d!==b){if(d===null){f.removeAttr(a,c);return}if(h&&"set"in h&&i&&(g=h.set(a,d,c))!==b)return g;a.setAttribute(c,""+d);return d}if(h&&"get"in h&&i&&(g=h.get(a,c))!==null)return g;g=a.getAttribute(c);return g===null?b:g}},removeAttr:function(a,b){var c,d,e,g,h=0;if(b&&a.nodeType===1){d=b.toLowerCase().split(p),g=d.length;for(;h<g;h++)e=d[h],e&&(c=f.propFix[e]||e,f.attr(a,e,""),a.removeAttribute(v?e:c),u.test(e)&&c in a&&(a[c]=!1))}},attrHooks:{type:{set:function(a,b){if(r.test(a.nodeName)&&a.parentNode)f.error("type property can't be changed");else if(!f.support.radioValue&&b==="radio"&&f.nodeName(a,"input")){var c=a.value;a.setAttribute("type",b),c&&(a.value=c);return b}}},value:{get:function(a,b){if(w&&f.nodeName(a,"button"))return w.get(a,b);return b in a?a.value:null},set:function(a,b,c){if(w&&f.nodeName(a,"button"))return w.set(a,b,c);a.value=b}}},propFix:{tabindex:"tabIndex",readonly:"readOnly","for":"htmlFor","class":"className",maxlength:"maxLength",cellspacing:"cellSpacing",cellpadding:"cellPadding",rowspan:"rowSpan",colspan:"colSpan",usemap:"useMap",frameborder:"frameBorder",contenteditable:"contentEditable"},prop:function(a,c,d){var e,g,h,i=a.nodeType;if(!!a&&i!==3&&i!==8&&i!==2){h=i!==1||!f.isXMLDoc(a),h&&(c=f.propFix[c]||c,g=f.propHooks[c]);return d!==b?g&&"set"in g&&(e=g.set(a,d,c))!==b?e:a[c]=d:g&&"get"in g&&(e=g.get(a,c))!==null?e:a[c]}},propHooks:{tabIndex:{get:function(a){var c=a.getAttributeNode("tabindex");return c&&c.specified?parseInt(c.value,10):s.test(a.nodeName)||t.test(a.nodeName)&&a.href?0:b}}}}),f.attrHooks.tabindex=f.propHooks.tabIndex,x={get:function(a,c){var d,e=f.prop(a,c);return e===!0||typeof e!="boolean"&&(d=a.getAttributeNode(c))&&d.nodeValue!==!1?c.toLowerCase():b},set:function(a,b,c){var d;b===!1?f.removeAttr(a,c):(d=f.propFix[c]||c,d in a&&(a[d]=!0),a.setAttribute(c,c.toLowerCase()));return c}},v||(y={name:!0,id:!0},w=f.valHooks.button={get:function(a,c){var d;d=a.getAttributeNode(c);return d&&(y[c]?d.nodeValue!=="":d.specified)?d.nodeValue:b},set:function(a,b,d){var e=a.getAttributeNode(d);e||(e=c.createAttribute(d),a.setAttributeNode(e));return e.nodeValue=b+""}},f.attrHooks.tabindex.set=w.set,f.each(["width","height"],function(a,b){f.attrHooks[b]=f.extend(f.attrHooks[b],{set:function(a,c){if(c===""){a.setAttribute(b,"auto");return c}}})}),f.attrHooks.contenteditable={get:w.get,set:function(a,b,c){b===""&&(b="false"),w.set(a,b,c)}}),f.support.hrefNormalized||f.each(["href","src","width","height"],function(a,c){f.attrHooks[c]=f.extend(f.attrHooks[c],{get:function(a){var d=a.getAttribute(c,2);return d===null?b:d}})}),f.support.style||(f.attrHooks.style={get:function(a){return a.style.cssText.toLowerCase()||b},set:function(a,b){return a.style.cssText=""+b}}),f.support.optSelected||(f.propHooks.selected=f.extend(f.propHooks.selected,{get:function(a){var b=a.parentNode;b&&(b.selectedIndex,b.parentNode&&b.parentNode.selectedIndex);return null}})),f.support.enctype||(f.propFix.enctype="encoding"),f.support.checkOn||f.each(["radio","checkbox"],function(){f.valHooks[this]={get:function(a){return a.getAttribute("value")===null?"on":a.value}}}),f.each(["radio","checkbox"],function(){f.valHooks[this]=f.extend(f.valHooks[this],{set:function(a,b){if(f.isArray(b))return a.checked=f.inArray(f(a).val(),b)>=0}})});var z=/^(?:textarea|input|select)$/i,A=/^([^\.]*)?(?:\.(.+))?$/,B=/\bhover(\.\S+)?\b/,C=/^key/,D=/^(?:mouse|contextmenu)|click/,E=/^(?:focusinfocus|focusoutblur)$/,F=/^(\w*)(?:#([\w\-]+))?(?:\.([\w\-]+))?$/,G=function(a){var b=F.exec(a);b&&(b[1]=(b[1]||"").toLowerCase(),b[3]=b[3]&&new RegExp("(?:^|\\s)"+b[3]+"(?:\\s|$)"));return b},H=function(a,b){var c=a.attributes||{};return(!b[1]||a.nodeName.toLowerCase()===b[1])&&(!b[2]||(c.id||{}).value===b[2])&&(!b[3]||b[3].test((c["class"]||{}).value))},I=function(a){return f.event.special.hover?a:a.replace(B,"mouseenter$1 mouseleave$1")};
@@ -4944,7 +4835,6 @@ Mizuho.initializeTopBar = $.proxy(function() {
 	var isMobileDevice = this.isMobileDevice();
 	var timerId;
 	
-	// Create the floating table of contents used in the top bar.
 	var $floattoc = $('<div id="floattoc"></div>').html($('#toc').html());
 	$floattoc.find('#toctitle').remove();
 	$floattoc.find('.comments').remove();
@@ -4963,8 +4853,6 @@ Mizuho.initializeTopBar = $.proxy(function() {
 		self.internalLinkClicked(this, event);
 	});
 	
-	// Callback for when the user clicks on the Table of Contents
-	// button on the top bar.
 	function showFloatingToc() {
 		var scrollUpdateTimerId;
 		
@@ -5057,9 +4945,6 @@ Mizuho.initializeTopBar = $.proxy(function() {
 		$window.bind('scroll', onScroll);
 	}
 	
-	// Called whenever the user scrolls. Updates the title of the
-	// Table of Contents button in the top bar to the section that
-	// the user is currently reading.
 	function update() {
 		if ($title.offset().top + $title.height() < $document.scrollTop()) {
 			if (!$topbar.is(':visible')) {
@@ -5103,7 +4988,6 @@ Mizuho.initializeTopBar = $.proxy(function() {
 		}, 100);
 	}
 	
-	
 	if (isMobileDevice) {
 		// Mobile devices don't support position fixed.
 		$topbar.css('position', 'absolute');
@@ -5287,5 +5171,5 @@ Mizuho.topicListReceived = $.proxy(function(result) {
 $(document).ready(Mizuho.initializeCommenting);
 
 </script>
-</body>
+</body>
 </html>