RubyGems - passenger - Versions diffs - 2.1.2 → 2.1.3 - Mend

passenger 2.1.2 → 2.1.3

Potentially problematic release.

This version of passenger might be problematic. Click here for more details.

Files changed (244) hide show

data/Rakefile +7 -5
data/doc/Architectural overview.html +729 -1
data/doc/Architectural overview.txt +0 -5
data/doc/Security of user switching support.html +605 -1
data/doc/Users guide.html +110 -106
data/doc/Users guide.txt +49 -0
data/doc/cxxapi/ApplicationPoolServer_8h-source.html +400 -372
data/doc/cxxapi/ApplicationPool_8h-source.html +1 -1
data/doc/cxxapi/Application_8h-source.html +1 -1
data/doc/cxxapi/Bucket_8h-source.html +1 -1
data/doc/cxxapi/CachedFileStat_8h-source.html +56 -65
data/doc/cxxapi/Configuration_8h-source.html +40 -32
data/doc/cxxapi/DirectoryMapper_8h-source.html +1 -1
data/doc/cxxapi/DummySpawnManager_8h-source.html +1 -1
data/doc/cxxapi/Exceptions_8h-source.html +1 -1
data/doc/cxxapi/FileChecker_8h-source.html +29 -30
data/doc/cxxapi/Hooks_8h-source.html +1 -1
data/doc/cxxapi/Logging_8h-source.html +1 -1
data/doc/cxxapi/MessageChannel_8h-source.html +1 -1
data/doc/cxxapi/PoolOptions_8h-source.html +1 -1
data/doc/cxxapi/SpawnManager_8h-source.html +225 -219
data/doc/cxxapi/StandardApplicationPool_8h-source.html +451 -445
data/doc/cxxapi/SystemTime_8h-source.html +1 -1
data/doc/cxxapi/Utils_8h-source.html +201 -140
data/doc/cxxapi/annotated.html +2 -2
data/doc/cxxapi/classClient-members.html +1 -1
data/doc/cxxapi/classClient.html +1 -1
data/doc/cxxapi/classHooks-members.html +1 -1
data/doc/cxxapi/classHooks.html +1 -1
data/doc/cxxapi/classPassenger_1_1Application-members.html +1 -1
data/doc/cxxapi/classPassenger_1_1Application.html +1 -1
data/doc/cxxapi/classPassenger_1_1ApplicationPool-members.html +1 -1
data/doc/cxxapi/classPassenger_1_1ApplicationPool.html +1 -1
data/doc/cxxapi/classPassenger_1_1ApplicationPoolServer-members.html +1 -1
data/doc/cxxapi/classPassenger_1_1ApplicationPoolServer.html +1 -1
data/doc/cxxapi/classPassenger_1_1ApplicationPool__inherit__graph.png +0 -0
data/doc/cxxapi/classPassenger_1_1Application_1_1Session-members.html +1 -1
data/doc/cxxapi/classPassenger_1_1Application_1_1Session.html +1 -1
data/doc/cxxapi/{classPassenger_1_1TempFile-members.html → classPassenger_1_1BufferedUpload-members.html} +5 -5
data/doc/cxxapi/{classPassenger_1_1TempFile.html → classPassenger_1_1BufferedUpload.html} +33 -43
data/doc/cxxapi/classPassenger_1_1BusyException-members.html +1 -1
data/doc/cxxapi/classPassenger_1_1BusyException.html +1 -1
data/doc/cxxapi/classPassenger_1_1ConfigurationException-members.html +1 -1
data/doc/cxxapi/classPassenger_1_1ConfigurationException.html +1 -1
data/doc/cxxapi/classPassenger_1_1DirectoryMapper-members.html +1 -1
data/doc/cxxapi/classPassenger_1_1DirectoryMapper.html +1 -1
data/doc/cxxapi/classPassenger_1_1DummySpawnManager-members.html +1 -1
data/doc/cxxapi/classPassenger_1_1DummySpawnManager.html +1 -1
data/doc/cxxapi/classPassenger_1_1FileChecker-members.html +1 -1
data/doc/cxxapi/classPassenger_1_1FileChecker.html +2 -2
data/doc/cxxapi/classPassenger_1_1FileNotFoundException-members.html +1 -1
data/doc/cxxapi/classPassenger_1_1FileNotFoundException.html +1 -1
data/doc/cxxapi/classPassenger_1_1FileNotFoundException__inherit__graph.png +0 -0
data/doc/cxxapi/classPassenger_1_1FileSystemException-members.html +1 -1
data/doc/cxxapi/classPassenger_1_1FileSystemException.html +1 -1
data/doc/cxxapi/classPassenger_1_1FileSystemException__inherit__graph.png +0 -0
data/doc/cxxapi/classPassenger_1_1IOException-members.html +1 -1
data/doc/cxxapi/classPassenger_1_1IOException.html +1 -1
data/doc/cxxapi/classPassenger_1_1IOException__inherit__graph.png +0 -0
data/doc/cxxapi/classPassenger_1_1MessageChannel-members.html +1 -1
data/doc/cxxapi/classPassenger_1_1MessageChannel.html +1 -1
data/doc/cxxapi/classPassenger_1_1RuntimeException-members.html +1 -1
data/doc/cxxapi/classPassenger_1_1RuntimeException.html +1 -1
data/doc/cxxapi/classPassenger_1_1SpawnException-members.html +1 -1
data/doc/cxxapi/classPassenger_1_1SpawnException.html +1 -1
data/doc/cxxapi/classPassenger_1_1SpawnManager-members.html +1 -1
data/doc/cxxapi/classPassenger_1_1SpawnManager.html +1 -1
data/doc/cxxapi/classPassenger_1_1StandardApplicationPool-members.html +1 -1
data/doc/cxxapi/classPassenger_1_1StandardApplicationPool.html +1 -1
data/doc/cxxapi/classPassenger_1_1StandardApplicationPool__inherit__graph.png +0 -0
data/doc/cxxapi/classPassenger_1_1SystemException-members.html +1 -1
data/doc/cxxapi/classPassenger_1_1SystemException.html +1 -1
data/doc/cxxapi/classPassenger_1_1SystemException__inherit__graph.png +0 -0
data/doc/cxxapi/classPassenger_1_1SystemTime-members.html +1 -1
data/doc/cxxapi/classPassenger_1_1SystemTime.html +1 -1
data/doc/cxxapi/definitions_8h-source.html +1 -1
data/doc/cxxapi/files.html +1 -1
data/doc/cxxapi/functions.html +12 -11
data/doc/cxxapi/functions_func.html +9 -7
data/doc/cxxapi/functions_type.html +1 -1
data/doc/cxxapi/functions_vars.html +2 -4
data/doc/cxxapi/graph_legend.html +1 -1
data/doc/cxxapi/graph_legend.png +0 -0
data/doc/cxxapi/group__Configuration.html +3 -3
data/doc/cxxapi/group__Configuration.png +0 -0
data/doc/cxxapi/group__Core.html +1 -1
data/doc/cxxapi/group__Core.png +0 -0
data/doc/cxxapi/group__Exceptions.html +1 -1
data/doc/cxxapi/group__Hooks.html +1 -1
data/doc/cxxapi/group__Hooks.png +0 -0
data/doc/cxxapi/group__Support.html +33 -16
data/doc/cxxapi/hierarchy.html +2 -2
data/doc/cxxapi/inherit__graph__0.png +0 -0
data/doc/cxxapi/inherit__graph__1.png +0 -0
data/doc/cxxapi/inherit__graph__10.map +1 -1
data/doc/cxxapi/inherit__graph__10.md5 +1 -1
data/doc/cxxapi/inherit__graph__10.png +0 -0
data/doc/cxxapi/inherit__graph__11.map +1 -1
data/doc/cxxapi/inherit__graph__11.md5 +1 -1
data/doc/cxxapi/inherit__graph__11.png +0 -0
data/doc/cxxapi/inherit__graph__12.map +1 -2
data/doc/cxxapi/inherit__graph__12.md5 +1 -1
data/doc/cxxapi/inherit__graph__12.png +0 -0
data/doc/cxxapi/inherit__graph__13.map +2 -1
data/doc/cxxapi/inherit__graph__13.md5 +1 -1
data/doc/cxxapi/inherit__graph__13.png +0 -0
data/doc/cxxapi/inherit__graph__14.map +1 -1
data/doc/cxxapi/inherit__graph__14.md5 +1 -1
data/doc/cxxapi/inherit__graph__14.png +0 -0
data/doc/cxxapi/inherit__graph__15.map +1 -1
data/doc/cxxapi/inherit__graph__15.md5 +1 -1
data/doc/cxxapi/inherit__graph__15.png +0 -0
data/doc/cxxapi/inherit__graph__16.map +1 -1
data/doc/cxxapi/inherit__graph__16.md5 +1 -1
data/doc/cxxapi/inherit__graph__16.png +0 -0
data/doc/cxxapi/inherit__graph__17.map +1 -1
data/doc/cxxapi/inherit__graph__17.md5 +1 -1
data/doc/cxxapi/inherit__graph__17.png +0 -0
data/doc/cxxapi/inherit__graph__18.map +1 -1
data/doc/cxxapi/inherit__graph__18.md5 +1 -1
data/doc/cxxapi/inherit__graph__18.png +0 -0
data/doc/cxxapi/inherit__graph__19.map +1 -2
data/doc/cxxapi/inherit__graph__19.md5 +1 -1
data/doc/cxxapi/inherit__graph__19.png +0 -0
data/doc/cxxapi/inherit__graph__2.png +0 -0
data/doc/cxxapi/inherit__graph__20.map +2 -1
data/doc/cxxapi/inherit__graph__20.md5 +1 -1
data/doc/cxxapi/inherit__graph__20.png +0 -0
data/doc/cxxapi/inherit__graph__21.map +1 -1
data/doc/cxxapi/inherit__graph__21.md5 +1 -1
data/doc/cxxapi/inherit__graph__21.png +0 -0
data/doc/cxxapi/inherit__graph__3.png +0 -0
data/doc/cxxapi/inherit__graph__4.png +0 -0
data/doc/cxxapi/inherit__graph__5.png +0 -0
data/doc/cxxapi/inherit__graph__6.png +0 -0
data/doc/cxxapi/inherit__graph__7.map +1 -1
data/doc/cxxapi/inherit__graph__7.md5 +1 -1
data/doc/cxxapi/inherit__graph__7.png +0 -0
data/doc/cxxapi/inherit__graph__8.map +1 -1
data/doc/cxxapi/inherit__graph__8.md5 +1 -1
data/doc/cxxapi/inherit__graph__8.png +0 -0
data/doc/cxxapi/inherit__graph__9.map +1 -1
data/doc/cxxapi/inherit__graph__9.md5 +1 -1
data/doc/cxxapi/inherit__graph__9.png +0 -0
data/doc/cxxapi/inherits.html +18 -18
data/doc/cxxapi/main.html +1 -1
data/doc/cxxapi/modules.html +1 -1
data/doc/cxxapi/structPassenger_1_1AnythingToString-members.html +1 -1
data/doc/cxxapi/structPassenger_1_1AnythingToString.html +1 -1
data/doc/cxxapi/structPassenger_1_1AnythingToString_3_01vector_3_01string_01_4_01_4-members.html +1 -1
data/doc/cxxapi/structPassenger_1_1AnythingToString_3_01vector_3_01string_01_4_01_4.html +1 -1
data/doc/cxxapi/structPassenger_1_1PoolOptions-members.html +1 -1
data/doc/cxxapi/structPassenger_1_1PoolOptions.html +1 -1
data/doc/cxxapi/tree.html +4 -4
data/doc/rdoc/classes/ConditionVariable.html +58 -58
data/doc/rdoc/classes/Exception.html +11 -11
data/doc/rdoc/classes/GC.html +4 -4
data/doc/rdoc/classes/IO.html +14 -14
data/doc/rdoc/classes/PhusionPassenger.html +11 -11
data/doc/rdoc/classes/PhusionPassenger/AdminTools.html +1 -1
data/doc/rdoc/classes/PhusionPassenger/AdminTools/ControlProcess.html +40 -39
data/doc/rdoc/classes/PhusionPassenger/Application.html +14 -14
data/doc/rdoc/classes/PhusionPassenger/HTMLTemplate.html +12 -12
data/doc/rdoc/classes/PhusionPassenger/Railz.html +1 -1
data/doc/rdoc/classes/PhusionPassenger/Utils.html +15 -8
data/doc/rdoc/classes/PlatformInfo.html +257 -253
data/doc/rdoc/classes/RakeExtensions.html +2 -2
data/doc/rdoc/classes/Signal.html +26 -26
data/doc/rdoc/created.rid +1 -1
data/doc/rdoc/files/DEVELOPERS_TXT.html +1 -1
data/doc/rdoc/files/README.html +1 -1
data/doc/rdoc/files/ext/phusion_passenger/native_support_c.html +1 -1
data/doc/rdoc/files/lib/phusion_passenger/abstract_request_handler_rb.html +1 -1
data/doc/rdoc/files/lib/phusion_passenger/abstract_server_collection_rb.html +1 -1
data/doc/rdoc/files/lib/phusion_passenger/abstract_server_rb.html +1 -1
data/doc/rdoc/files/lib/phusion_passenger/admin_tools/control_process_rb.html +1 -1
data/doc/rdoc/files/lib/phusion_passenger/admin_tools_rb.html +1 -1
data/doc/rdoc/files/lib/phusion_passenger/application_rb.html +1 -1
data/doc/rdoc/files/lib/phusion_passenger/console_text_template_rb.html +1 -1
data/doc/rdoc/files/lib/phusion_passenger/constants_rb.html +1 -1
data/doc/rdoc/files/lib/phusion_passenger/dependencies_rb.html +1 -1
data/doc/rdoc/files/lib/phusion_passenger/events_rb.html +1 -1
data/doc/rdoc/files/lib/phusion_passenger/exceptions_rb.html +1 -1
data/doc/rdoc/files/lib/phusion_passenger/html_template_rb.html +1 -1
data/doc/rdoc/files/lib/phusion_passenger/message_channel_rb.html +1 -1
data/doc/rdoc/files/lib/phusion_passenger/platform_info_rb.html +1 -1
data/doc/rdoc/files/lib/phusion_passenger/rack/application_spawner_rb.html +1 -1
data/doc/rdoc/files/lib/phusion_passenger/rack/request_handler_rb.html +1 -1
data/doc/rdoc/files/lib/phusion_passenger/railz/application_spawner_rb.html +1 -1
data/doc/rdoc/files/lib/phusion_passenger/railz/cgi_fixed_rb.html +1 -1
data/doc/rdoc/files/lib/phusion_passenger/railz/framework_spawner_rb.html +1 -1
data/doc/rdoc/files/lib/phusion_passenger/railz/request_handler_rb.html +1 -1
data/doc/rdoc/files/lib/phusion_passenger/simple_benchmarking_rb.html +1 -1
data/doc/rdoc/files/lib/phusion_passenger/spawn_manager_rb.html +1 -1
data/doc/rdoc/files/lib/phusion_passenger/utils_rb.html +9 -9
data/doc/rdoc/files/lib/phusion_passenger/wsgi/application_spawner_rb.html +1 -1
data/doc/rdoc/files/{lib → misc}/rake/extensions_rb.html +2 -2
data/doc/rdoc/fr_file_index.html +1 -1
data/doc/rdoc/fr_method_index.html +22 -22
data/ext/apache2/ApplicationPoolServer.h +43 -15
data/ext/apache2/ApplicationPoolServerExecutable.cpp +27 -52
data/ext/apache2/CachedFileStat.h +7 -16
data/ext/apache2/Configuration.h +9 -1
data/ext/apache2/FileChecker.h +4 -5
data/ext/apache2/Hooks.cpp +20 -22
data/ext/apache2/SpawnManager.h +6 -0
data/ext/apache2/StandardApplicationPool.h +6 -0
data/ext/apache2/Utils.cpp +174 -16
data/ext/apache2/Utils.h +99 -38
data/ext/boost/cstdint.hpp +2 -1
data/ext/oxt/system_calls.cpp +20 -2
data/ext/oxt/system_calls.hpp +2 -0
data/lib/phusion_passenger/abstract_request_handler.rb +5 -1
data/lib/phusion_passenger/admin_tools.rb +1 -1
data/lib/phusion_passenger/admin_tools/control_process.rb +2 -1
data/lib/phusion_passenger/dependencies.rb +7 -4
data/lib/phusion_passenger/platform_info.rb +8 -2
data/lib/phusion_passenger/rack/application_spawner.rb +1 -1
data/lib/phusion_passenger/templates/version_not_found.html.erb +9 -0
data/lib/phusion_passenger/utils.rb +13 -6
data/lib/phusion_passenger/wsgi/application_spawner.rb +1 -1
data/{lib → misc}/rake/cplusplus.rb +0 -0
data/{lib → misc}/rake/extensions.rb +0 -0
data/{lib → misc}/rake/gempackagetask.rb +0 -0
data/{lib → misc}/rake/packagetask.rb +0 -0
data/{lib → misc}/rake/rdoctask.rb +0 -0
data/misc/render_error_pages.rb +6 -5
data/test/CxxTestMain.cpp +109 -7
data/test/UtilsTest.cpp +61 -51
data/test/config.yml.example +6 -2
data/test/integration_tests.rb +4 -0
data/test/ruby/abstract_request_handler_spec.rb +9 -3
data/test/ruby/rack/application_spawner_spec.rb +3 -2
data/test/ruby/rails/application_spawner_spec.rb +15 -4
data/test/ruby/rails/framework_spawner_spec.rb +4 -2
data/test/ruby/rails/spawner_error_handling_spec.rb +4 -4
data/test/ruby/spawn_manager_spec.rb +22 -9
data/test/ruby/utils_spec.rb +18 -12
data/test/ruby/wsgi/application_spawner_spec.rb +16 -7
data/test/stub/apache2/httpd.conf.erb +1 -0
data/test/stub/wsgi/passenger_wsgi.pyc +0 -0
metadata +1064 -1090
data/doc/Users guide Apache.html +0 -3127
data/doc/Users guide Nginx.html +0 -1458

@@ -3,7 +3,7 @@
 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
-<meta name="generator" content="AsciiDoc 8.3.4" />
+<meta name="generator" content="AsciiDoc 8.4.2" />
 <title>Phusion Passenger users guide</title>
 <style type="text/css">
 /* Debug borders */
@@ -118,7 +118,6 @@ div#preamble {
 div.tableblock, div.imageblock, div.exampleblock, div.verseblock,
 div.quoteblock, div.literalblock, div.listingblock, div.sidebarblock,
 div.admonitionblock {
-  margin-right: 10%;
   margin-top: 1.5em;
   margin-bottom: 1.5em;
 }
@@ -160,9 +159,6 @@ div.sidebarblock > div.content {
   padding: 0.5em;
 }
-div.listingblock {
-  margin-right: 0%;
-}
 div.listingblock > div.content {
   border: 1px solid silver;
   background: #f4f4f4;
@@ -171,6 +167,7 @@ div.listingblock > div.content {
 div.quoteblock {
   padding-left: 2.0em;
+  margin-right: 10%;
 }
 div.quoteblock > div.attribution {
   padding-top: 0.5em;
@@ -179,6 +176,7 @@ div.quoteblock > div.attribution {
 div.verseblock {
   padding-left: 2.0em;
+  margin-right: 10%;
 }
 div.verseblock > div.content {
   white-space: pre;
@@ -341,47 +339,6 @@ div.toclevel4 {
   margin-left: 6em;
   font-size: 0.9em;
 }
-/* Workarounds for IE6's broken and incomplete CSS2. */
-div.sidebar-content {
-  background: #ffffee;
-  border: 1px solid silver;
-  padding: 0.5em;
-}
-div.sidebar-title, div.image-title {
-  color: #527bbd;
-  font-family: sans-serif;
-  font-weight: bold;
-  margin-top: 0.0em;
-  margin-bottom: 0.5em;
-}
-div.listingblock div.content {
-  border: 1px solid silver;
-  background: #f4f4f4;
-  padding: 0.5em;
-}
-div.quoteblock-attribution {
-  padding-top: 0.5em;
-  text-align: right;
-}
-div.verseblock-content {
-  white-space: pre;
-}
-div.verseblock-attribution {
-  padding-top: 0.75em;
-  text-align: left;
-}
-div.exampleblock-content {
-  border-left: 2px solid silver;
-  padding-left: 0.5em;
-}
-/* IE6 sets dynamically generated links as visited. */
-div#toc a:visited { color: blue; }
 </style>
 <script type="text/javascript">
 /*<![CDATA[*/
@@ -585,7 +542,7 @@ if it doesn&#8217;t.</p></div>
 </div>
 <h2 id="_installing_phusion_passenger">2. Installing Phusion Passenger</h2>
 <div class="sectionbody">
-<h3 id="_generic_installation_instructions">2.1. Generic installation instructions</h3><div style="clear:left"></div>
+<h3 id="_generic_installation_instructions">2.1. Generic installation instructions</h3>
 <h4 id="install_passenger">2.1.1. Overview of download and installation methods</h4>
 <div class="paragraph"><p>There are two ways to install Phusion Passenger:</p></div>
 <div class="olist arabic"><ol class="arabic">
@@ -732,7 +689,7 @@ tar xzvf ~/YourDownloadsFolder/passenger-x.x.x.tar.gz</tt></pre>
 installation. Furthermore, the <em>passenger-x.x.x</em> folder must be accessible by Apache.</td>
 </tr></table>
 </div>
-<h3 id="_operating_system_specific_instructions_and_information">2.2. Operating system-specific instructions and information</h3><div style="clear:left"></div>
+<h3 id="_operating_system_specific_instructions_and_information">2.2. Operating system-specific instructions and information</h3>
 <h4 id="_macos_x">2.2.1. MacOS X</h4>
 <div class="paragraph"><p>Ben Ruebenstein has written an excellent
 <a href="http://benr75.com/articles/2008/04/12/setup-mod_rails-phusion-mac-os-x-leopard">tutorial
@@ -757,7 +714,7 @@ are run, is &#8220;production&#8221;. You can change this by changing the
 <a href="#rails_env"><em>RailsEnv</em></a> configuration option.</td>
 </tr></table>
 </div>
-<h3 id="_deploying_to_a_virtual_host_8217_s_root">3.1. Deploying to a virtual host&#8217;s root</h3><div style="clear:left"></div>
+<h3 id="_deploying_to_a_virtual_host_8217_s_root">3.1. Deploying to a virtual host&#8217;s root</h3>
 <div class="paragraph"><p>Add a virtual host entry to your Apache configuration file. The virtual host&#8217;s
 document root must point to your Ruby on Rails application&#8217;s <em>public</em> folder.
 For example:</p></div>
@@ -769,7 +726,7 @@ For example:</p></div>
 &lt;/VirtualHost&gt;</tt></pre>
 </div></div>
 <div class="paragraph"><p>Then restart Apache. The application has now been deployed.</p></div>
-<h3 id="deploying_rails_to_sub_uri">3.2. Deploying to a sub URI</h3><div style="clear:left"></div>
+<h3 id="deploying_rails_to_sub_uri">3.2. 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">
@@ -799,6 +756,18 @@ folder to a directory in the document root. For example:</p></div>
 <div class="admonitionblock">
 <table><tr>
 <td class="icon">
+<img src="./images/icons/note.png" alt="Note" />
+</td>
+<td class="content">If you&#8217;re deploying to a sub-URI then please make sure that your view
+templates correctly handles references to sub-URI static assets! Otherwise
+you may find broken links to images, CSS files, JavaScripts, etc. Please read
+<a href="#sub_uri_deployment_uri_fix">How to fix broken images/CSS/JavaScript URIs in sub-URI deployments</a>
+for more information.</td>
+</tr></table>
+</div>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
 <img src="./images/icons/tip.png" alt="Tip" />
 </td>
 <td class="content">
@@ -816,7 +785,7 @@ folder to a directory in the document root. For example:</p></div>
 </td>
 </tr></table>
 </div>
-<h3 id="_redeploying_restarting_the_ruby_on_rails_application">3.3. Redeploying (restarting the Ruby on Rails application)</h3><div style="clear:left"></div>
+<h3 id="_redeploying_restarting_the_ruby_on_rails_application">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>
@@ -840,12 +809,12 @@ command line:</p></div>
 <div class="content">
 <pre><tt>touch /webapps/mycook/tmp/restart.txt</tt></pre>
 </div></div>
-<h3 id="_migrations">3.4. Migrations</h3><div style="clear:left"></div>
+<h3 id="_migrations">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 <tt>rake db:migrate RAILS_ENV=production</tt> in
 a shell console, just like one would normally run migrations.</p></div>
-<h3 id="_capistrano_integration">3.5. Capistrano integration</h3><div style="clear:left"></div>
+<h3 id="_capistrano_integration">3.5. Capistrano integration</h3>
 <div class="paragraph"><p>See <a href="#capistrano">Capistrano recipe</a>.</p></div>
 </div>
 <h2 id="_deploying_a_rack_based_ruby_application">4. Deploying a Rack-based Ruby application</h2>
@@ -899,7 +868,7 @@ are run, is &#8220;production&#8221;. You can change this by changing the
 <a href="#rack_env"><em>RackEnv</em></a> configuration option.</td>
 </tr></table>
 </div>
-<h3 id="_tutorial_example_writing_and_deploying_a_hello_world_rack_application">4.1. Tutorial/example: writing and deploying a Hello World Rack application</h3><div style="clear:left"></div>
+<h3 id="_tutorial_example_writing_and_deploying_a_hello_world_rack_application">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">
@@ -930,7 +899,7 @@ the Apache configuration file:</p></div>
 </div></div>
 <div class="paragraph"><p>And we&#8217;re done! After an Apache restart, the above Rack application will be available
 under the URL <em>http://www.rackexample.com/</em>.</p></div>
-<h3 id="_deploying_to_a_virtual_host_8217_s_root_2">4.2. Deploying to a virtual host&#8217;s root</h3><div style="clear:left"></div>
+<h3 id="_deploying_to_a_virtual_host_8217_s_root_2">4.2. Deploying to a virtual host&#8217;s root</h3>
 <div class="paragraph"><p>Add a virtual host entry to your Apache configuration file. The virtual host&#8217;s
 document root must point to your Rack application&#8217;s <em>public</em> folder.
 For example:</p></div>
@@ -942,7 +911,7 @@ For example:</p></div>
 &lt;/VirtualHost&gt;</tt></pre>
 </div></div>
 <div class="paragraph"><p>Then restart Apache. The application has now been deployed.</p></div>
-<h3 id="deploying_rack_to_sub_uri">4.3. Deploying to a sub URI</h3><div style="clear:left"></div>
+<h3 id="deploying_rack_to_sub_uri">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">
@@ -989,7 +958,7 @@ folder to a directory in the document root. For example:</p></div>
 </td>
 </tr></table>
 </div>
-<h3 id="_redeploying_restarting_the_rack_application">4.4. Redeploying (restarting the Rack application)</h3><div style="clear:left"></div>
+<h3 id="_redeploying_restarting_the_rack_application">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>
@@ -1013,7 +982,7 @@ command line:</p></div>
 <div class="content">
 <pre><tt>touch /webapps/rackapp/tmp/restart.txt</tt></pre>
 </div></div>
-<h3 id="_rackup_specifications_for_various_web_frameworks">4.5. Rackup specifications for various web frameworks</h3><div style="clear:left"></div>
+<h3 id="_rackup_specifications_for_various_web_frameworks">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>
 <h4 id="_camping">4.5.1. Camping</h4>
 <div class="listingblock">
@@ -1095,12 +1064,12 @@ run Sinatra::Application</tt></pre>
 Nevertheless, the system administrator may be interested in changing
 Phusion Passenger&#8217;s behavior. Phusion Passenger&#8217;s Apache module supports the
 following configuration options:</p></div>
-<h3 id="_passengerroot_lt_directory_gt">5.1. PassengerRoot &lt;directory&gt;</h3><div style="clear:left"></div>
+<h3 id="_passengerroot_lt_directory_gt">5.1. PassengerRoot &lt;directory&gt;</h3>
 <div class="paragraph"><p>The location to the Phusion Passenger root directory. This configuration option
 is essential to Phusion Passenger. The correct value is given by the installer,
 and should usually not be changed manually.</p></div>
 <div class="paragraph"><p>This required option may only occur once, in the global server configuration.</p></div>
-<h3 id="_passengerloglevel_lt_integer_gt">5.2. PassengerLogLevel &lt;integer&gt;</h3><div style="clear:left"></div>
+<h3 id="_passengerloglevel_lt_integer_gt">5.2. PassengerLogLevel &lt;integer&gt;</h3>
 <div class="paragraph"><p>This option allows one to specify how much information Phusion Passenger should
 write to the Apache error log file. A higher log level value means that more
 information will be logged.</p></div>
@@ -1131,11 +1100,11 @@ information will be logged.</p></div>
 </ul></div>
 <div class="paragraph"><p>This option may only occur once, in the global server configuration.
 The default is <em>0</em>.</p></div>
-<h3 id="PassengerRuby">5.3. PassengerRuby &lt;filename&gt;</h3><div style="clear:left"></div>
+<h3 id="PassengerRuby">5.3. PassengerRuby &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 global server configuration.
 The default is <em>ruby</em>.</p></div>
-<h3 id="PassengerAppRoot">5.4. PassengerAppRoot &lt;path/to/root&gt;</h3><div style="clear:left"></div>
+<h3 id="PassengerAppRoot">5.4. PassengerAppRoot &lt;path/to/root&gt;</h3>
 <div class="paragraph"><p>By default, Phusion Passenger assumes that the application&#8217;s root directory
 is the parent directory of the <em>public</em> directory. This option allows one to
 specify the application&#8217;s root independently from the DocumentRoot, which
@@ -1174,7 +1143,7 @@ In <em>.htaccess</em>, if <tt>AllowOverride Options</tt> is on.
                                        #     root is "/var/rails/zena/sites/example.com"
 &lt;/VirtualHost&gt;</tt></pre>
 </div></div>
-<h3 id="PassengerUseGlobalQueue">5.5. PassengerUseGlobalQueue &lt;on|off&gt;</h3><div style="clear:left"></div>
+<h3 id="PassengerUseGlobalQueue">5.5. PassengerUseGlobalQueue &lt;on|off&gt;</h3>
 <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>
@@ -1263,17 +1232,17 @@ process that becomes available will take from the queue, and so this
 <div class="paragraph"><p>Turning global queuing off will yield a minor performance improvement (about 5%,
 depending on how fast/slow your web application is), which is why it&#8217;s off by
 default.</p></div>
-<h3 id="PassengerUserSwitching">5.6. PassengerUserSwitching &lt;on|off&gt;</h3><div style="clear:left"></div>
+<h3 id="PassengerUserSwitching">5.6. PassengerUserSwitching &lt;on|off&gt;</h3>
 <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 global server configuration.
 The default value is <em>on</em>.</p></div>
-<h3 id="PassengerDefaultUser">5.7. PassengerDefaultUser &lt;username&gt;</h3><div style="clear:left"></div>
+<h3 id="PassengerDefaultUser">5.7. PassengerDefaultUser &lt;username&gt;</h3>
 <div class="paragraph"><p>Passenger enables <a href="#user_switching">user switching support</a> by default.
 This configuration option allows one to specify which user Rails/Rack
 applications must run as, if user switching fails or is disabled.</p></div>
 <div class="paragraph"><p>This option may only occur once, in the global server configuration.
 The default value is <em>nobody</em>.</p></div>
-<h3 id="PassengerHighPerformance">5.8. PassengerHighPerformance &lt;on|off&gt;</h3><div style="clear:left"></div>
+<h3 id="PassengerHighPerformance">5.8. PassengerHighPerformance &lt;on|off&gt;</h3>
 <div class="paragraph"><p>By default, Phusion Passenger is compatible with mod_rewrite and most other
 Apache modules. However, a lot of effort is required in order to be compatible.
 If you turn <em>PassengerHighPerformance</em> to <em>on</em>, then Phusion Passenger will be
@@ -1349,7 +1318,7 @@ then you can enable high performance mode for a certain URL only. For example:</
 </div></div>
 <div class="paragraph"><p>This enables high performance mode for
 <a href="http://www.foo.com/chatroom/ajax_update_poll">http://www.foo.com/chatroom/ajax_update_poll</a> only.</p></div>
-<h3 id="_passengerenabled_lt_on_off_gt">5.9. PassengerEnabled &lt;on|off&gt;</h3><div style="clear:left"></div>
+<h3 id="_passengerenabled_lt_on_off_gt">5.9. PassengerEnabled &lt;on|off&gt;</h3>
 <div class="paragraph"><p>You can set this option to <em>off</em> to completely disable Phusion Passenger for
 a certain location. This is useful if, for example, you want to integrate a PHP
 application into the same virtual host as a Rails application.</p></div>
@@ -1393,7 +1362,7 @@ In <em>.htaccess</em>.
 </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>
-<h3 id="_passengertempdir_lt_directory_gt">5.10. PassengerTempDir &lt;directory&gt;</h3><div style="clear:left"></div>
+<h3 id="_passengertempdir_lt_directory_gt">5.10. PassengerTempDir &lt;directory&gt;</h3>
 <div class="paragraph"><p>Specifies the directory that Phusion Passenger should use for storing temporary
 files. This includes things such as Unix socket files, buffered file uploads,
 etc.</p></div>
@@ -1416,7 +1385,7 @@ environment variable, like this:</p></div>
 sudo -E passenger-status
 # The -E option tells 'sudo' to preserve environment variables.</tt></pre>
 </div></div>
-<h3 id="_passengerrestartdir_lt_directory_gt">5.11. PassengerRestartDir &lt;directory&gt;</h3><div style="clear:left"></div>
+<h3 id="_passengerrestartdir_lt_directory_gt">5.11. PassengerRestartDir &lt;directory&gt;</h3>
 <div class="paragraph"><p>As described in the deployment chapters of this document, Phusion Passenger
 checks the file <em>tmp/restart.txt</em> in the applications'
 <a href="#application_root">root directory</a> for restarting applications. Sometimes it
@@ -1484,7 +1453,7 @@ security flaw which allows an attacker to touch restart.txt, then that will
 allow the attacker to cause a Denial-of-Service.</p></div>
 <div class="paragraph"><p>You can prevent this from happening by pointing PassengerRestartDir to a
 directory that&#8217;s readable by Apache, but only writable by administrators.</p></div>
-<h3 id="_resource_control_and_optimization_options">5.12. Resource control and optimization options</h3><div style="clear:left"></div>
+<h3 id="_resource_control_and_optimization_options">5.12. Resource control and optimization options</h3>
 <h4 id="_passengermaxpoolsize_lt_integer_gt">5.12.1. PassengerMaxPoolSize &lt;integer&gt;</h4>
 <div class="paragraph"><p>The maximum number of Ruby on Rails or Rack application instances that may
 be simultaneously active. A larger number results in higher memory usage,
@@ -1636,7 +1605,7 @@ In <em>.htaccess</em>, if <tt>AllowOverride Limits</tt> is on.
 </li>
 </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>
-<h3 id="_ruby_on_rails_specific_options">5.13. Ruby on Rails-specific options</h3><div style="clear:left"></div>
+<h3 id="_ruby_on_rails_specific_options">5.13. Ruby on Rails-specific options</h3>
 <h4 id="_railsautodetect_lt_on_off_gt">5.13.1. RailsAutoDetect &lt;on|off&gt;</h4>
 <div class="paragraph"><p>Whether Phusion Passenger should automatically detect whether a virtual host&#8217;s
 document root is a Ruby on Rails application. The default is <em>on</em>.</p></div>
@@ -1730,7 +1699,7 @@ In <em>.htaccess</em>, if <tt>AllowOverride Options</tt> is on.
 <div class="paragraph"><p>This subsection attempts to describe spawn methods, but it&#8217;s okay if you don&#8217;t (want to)
 understand it, as it&#8217;s mostly a technical detail. You can basically follow this rule of thumb:</p></div>
 <div class="sidebarblock">
-<div class="sidebar-content">
+<div class="content">
 <div class="paragraph"><p>If your application works on Mongrel, but not on Phusion Passenger, then set
 <tt>RailsSpawnMethod</tt> to <em>conservative</em>. Otherwise, leave it at <em>smart-lv2</em> (the default).</p></div>
 </div></div>
@@ -1842,7 +1811,7 @@ 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 only occur in the global server configuration, and may occur at
 most once. The default value is <em>600</em> (10 minutes).</p></div>
-<h3 id="_rack_specific_options">5.14. Rack-specific options</h3><div style="clear:left"></div>
+<h3 id="_rack_specific_options">5.14. Rack-specific options</h3>
 <h4 id="_rackautodetect_lt_on_off_gt">5.14.1. RackAutoDetect &lt;on|off&gt;</h4>
 <div class="paragraph"><p>Whether Phusion Passenger should automatically detect whether a virtual host&#8217;s
 document root is a Rack application. The default is <em>on</em>.</p></div>
@@ -1927,7 +1896,7 @@ In <em>.htaccess</em>, if <tt>AllowOverride Options</tt> is on.
 </li>
 </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>
-<h3 id="_deprecated_options">5.15. Deprecated options</h3><div style="clear:left"></div>
+<h3 id="_deprecated_options">5.15. Deprecated options</h3>
 <div class="paragraph"><p>The following options have been deprecated, but are still supported for backwards
 compatibility reasons.</p></div>
 <h4 id="_railsruby">5.15.1. RailsRuby</h4>
@@ -1941,11 +1910,11 @@ compatibility reasons.</p></div>
 </div>
 <h2 id="_troubleshooting">6. Troubleshooting</h2>
 <div class="sectionbody">
-<h3 id="_operating_system_specific_problems">6.1. Operating system-specific problems</h3><div style="clear:left"></div>
+<h3 id="_operating_system_specific_problems">6.1. Operating system-specific problems</h3>
 <h4 id="_macos_x_the_installer_cannot_locate_mamp_8217_s_apache">6.1.1. MacOS X: The installer cannot locate MAMP&#8217;s Apache</h4>
 <div class="sidebarblock">
-<div class="sidebar-content">
-<div class="sidebar-title">Symptoms</div>
+<div class="content">
+<div class="title">Symptoms</div>
 <div class="paragraph"><p>The installer finds Apache 2 development headers at <tt>/Applications/MAMP/Library/bin/apxs</tt>.
 However, Apache cannot be found. The installer also outputs the following error:</p></div>
 <div class="listingblock">
@@ -1958,11 +1927,11 @@ No such file or directory at /Applications/MAMP/Library/bin/apxs line 218.</tt><
 Please read <a href="http://forum.mamp.info/viewtopic.php?t=1866">this forum topic</a> to learn how
 to fix this problem.</p></div>
 <div class="paragraph"><p>See also <a href="http://code.google.com/p/phusion-passenger/issues/detail?id=12">this bug report</a>.</p></div>
-<h3 id="_problems_during_installation">6.2. Problems during installation</h3><div style="clear:left"></div>
+<h3 id="_problems_during_installation">6.2. Problems during installation</h3>
 <h4 id="installing_ruby_dev">6.2.1. Ruby development headers aren&#8217;t installed</h4>
 <div class="sidebarblock">
-<div class="sidebar-content">
-<div class="sidebar-title">Symptoms</div>
+<div class="content">
+<div class="title">Symptoms</div>
 <div class="paragraph"><p>Installing Phusion Passenger fails because of one of the following errors:</p></div>
 <div class="ulist"><ul>
 <li>
@@ -2054,8 +2023,8 @@ which Ruby installation you want to use. Please read
 </div>
 <h4 id="_apache_development_headers_aren_8217_t_installed">6.2.2. Apache development headers aren&#8217;t installed</h4>
 <div class="sidebarblock">
-<div class="sidebar-content">
-<div class="sidebar-title">Symptoms</div>
+<div class="content">
+<div class="title">Symptoms</div>
 <div class="paragraph"><p>Installing Phusion Passenger fails because of one of the following errors:</p></div>
 <div class="ulist"><ul>
 <li>
@@ -2139,8 +2108,8 @@ Other operating systems
 </dl></div>
 <h4 id="_apr_development_headers_aren_8217_t_installed">6.2.3. APR development headers aren&#8217;t installed</h4>
 <div class="sidebarblock">
-<div class="sidebar-content">
-<div class="sidebar-title">Symptoms</div>
+<div class="content">
+<div class="title">Symptoms</div>
 <div class="paragraph"><p>Installing Phusion Passenger fails because one of the following errors:</p></div>
 <div class="ulist"><ul>
 <li>
@@ -2221,7 +2190,7 @@ Other operating systems
 <div class="paragraph"><p>Please <a href="#specifying_correct_apache_install">Specifying the correct Apache installation</a>, and re-run the Phusion Passenger installer.</p></div>
 <h4 id="_phusion_passenger_is_using_the_wrong_ruby_during_installation">6.2.5. Phusion Passenger is using the wrong Ruby during installation</h4>
 <div class="paragraph"><p>Please <a href="#specifying_ruby_installation">Specifying the correct Ruby installation</a>, and re-run the Phusion Passenger installer.</p></div>
-<h3 id="_problems_after_installation">6.3. Problems after installation</h3><div style="clear:left"></div>
+<h3 id="_problems_after_installation">6.3. Problems after installation</h3>
 <div class="admonitionblock">
 <table><tr>
 <td class="icon">
@@ -2239,8 +2208,8 @@ inside the Apache error logs. It will tell you what exactly went wrong.</p></div
 <div class="paragraph"><p>Please try setting <a href="#RailsSpawnMethod">RailsSpawnMethod</a> to <em>conservative</em>.</p></div>
 <h4 id="_phusion_passenger_has_been_compiled_against_the_wrong_apache_installation">6.3.2. Phusion Passenger has been compiled against the wrong Apache installation</h4>
 <div class="sidebarblock">
-<div class="sidebar-content">
-<div class="sidebar-title">Symptoms</div>
+<div class="content">
+<div class="title">Symptoms</div>
 <div class="paragraph"><p>Apache crashes during startup (after being daemonized). The Apache error log
 says &#8220;<em>seg fault or similar nasty error detected in the parent process&#8221;</em>.</p></div>
 </div></div>
@@ -2352,7 +2321,7 @@ following command to give your Rails application folder that context:</p></div>
 <div class="content">
 <pre><tt>chcon -R -h -t httpd_sys_content_t /path/to/your/rails/app</tt></pre>
 </div></div>
-<h3 id="conflicting_apache_modules">6.4. Conflicting Apache modules</h3><div style="clear:left"></div>
+<h3 id="conflicting_apache_modules">6.4. Conflicting Apache modules</h3>
 <h4 id="_mod_userdir">6.4.1. mod_userdir</h4>
 <div class="paragraph"><p><em>mod_userdir</em> is not compatible with Phusion Passenger at the moment.</p></div>
 <h4 id="_virtualdocumentroot">6.4.2. VirtualDocumentRoot</h4>
@@ -2362,7 +2331,7 @@ following command to give your Rails application folder that context:</p></div>
 <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>
-<h3 id="_inspecting_memory_usage">7.1. Inspecting memory usage</h3><div style="clear:left"></div>
+<h3 id="_inspecting_memory_usage">7.1. Inspecting memory usage</h3>
 <div class="paragraph"><p>Process inspection tools such as <tt>ps</tt> and <tt>top</tt> 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 <tt>ps</tt> and <tt>top</tt> report.</p></div>
@@ -2411,7 +2380,7 @@ This is a lot less than the 50 MB-ish memory usage as shown in the <em>VMSize</e
 provide facilities for determining processes' private dirty RSS.</td>
 </tr></table>
 </div>
-<h3 id="_inspecting_phusion_passenger_8217_s_internal_status">7.2. Inspecting Phusion Passenger&#8217;s internal status</h3><div style="clear:left"></div>
+<h3 id="_inspecting_phusion_passenger_8217_s_internal_status">7.2. Inspecting Phusion Passenger&#8217;s internal status</h3>
 <div class="paragraph"><p>One can inspect Phusion Passenger&#8217;s internal status with the tool <tt>passenger-status</tt>.
 This tool must typically be run as root. For example:</p></div>
 <div class="listingblock">
@@ -2537,7 +2506,7 @@ Your application is frozen, i.e. has stopped responding. See
 </p>
 </li>
 </ol></div>
-<h3 id="debugging_frozen">7.3. Debugging frozen applications</h3><div style="clear:left"></div>
+<h3 id="debugging_frozen">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>
@@ -2560,7 +2529,7 @@ will restart killed application instances, as if nothing bad happened.</td>
 </div>
 <h2 id="_tips">8. Tips</h2>
 <div class="sectionbody">
-<h3 id="user_switching">8.1. User switching (security)</h3><div style="clear:left"></div>
+<h3 id="user_switching">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&#8217;s PHP application will be able to read Jane&#8217;s PHP application&#8217;s
@@ -2598,12 +2567,12 @@ Under no circumstances will applications be run as <em>root</em>. If
 </ul></div>
 <div class="paragraph"><p>User switching can be disabled with the
 <a href="#PassengerUserSwitching">PassengerUserSwitching</a> option.</p></div>
-<h3 id="reducing_memory_usage">8.2. Reducing memory consumption of Ruby on Rails applications by 33%</h3><div style="clear:left"></div>
+<h3 id="reducing_memory_usage">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>
-<h3 id="capistrano">8.3. Capistrano recipe</h3><div style="clear:left"></div>
+<h3 id="capistrano">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&#8217;re using Git as version control system.</p></div>
@@ -2659,7 +2628,7 @@ command is as follows:</p></div>
 </div></div>
 <div class="paragraph"><p>Killing the spawn server is completely safe, because Phusion Passenger will restart the
 spawn server if it has been terminated.</p></div>
-<h3 id="_moving_phusion_passenger_to_a_different_directory">8.4. Moving Phusion Passenger to a different directory</h3><div style="clear:left"></div>
+<h3 id="_moving_phusion_passenger_to_a_different_directory">8.4. 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">
@@ -2696,7 +2665,7 @@ Edit your Apache configuration file, and set:
 </div></div>
 </li>
 </ol></div>
-<h3 id="_installing_multiple_ruby_on_rails_versions">8.5. Installing multiple Ruby on Rails versions</h3><div style="clear:left"></div>
+<h3 id="_installing_multiple_ruby_on_rails_versions">8.5. 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>
@@ -2707,14 +2676,14 @@ this command:</p></div>
 <div class="paragraph"><p>where <em>X.X.X</em> is the version number of Ruby on Rails.</p></div>
 <div class="paragraph"><p>All of these versions will exist in parallel, and will not conflict with each
 other. Phusion Passenger will automatically make use of the correct version.</p></div>
-<h3 id="_x_sendfile_support">8.6. X-Sendfile support</h3><div style="clear:left"></div>
+<h3 id="_x_sendfile_support">8.6. X-Sendfile support</h3>
 <div class="paragraph"><p>Phusion Passenger does not provide X-Sendfile support by itself. Please install
 <a href="http://tn123.ath.cx/mod_xsendfile/">mod_xsendfile</a> for X-Sendfile support.</p></div>
-<h3 id="_upload_progress">8.7. Upload progress</h3><div style="clear:left"></div>
+<h3 id="_upload_progress">8.7. Upload progress</h3>
 <div class="paragraph"><p>Phusion Passenger does not provide upload progress support by itself. Please
 try drogus&#8217;s <a href="http://github.com/drogus/apache-upload-progress-module/tree/master">
 Apache upload progress module</a> instead.</p></div>
-<h3 id="_making_the_application_restart_after_each_request">8.8. Making the application restart after each request</h3><div style="clear:left"></div>
+<h3 id="_making_the_application_restart_after_each_request">8.8. 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&#8217;t
 support code reloading, or when developing a web framework.</p></div>
@@ -2735,6 +2704,41 @@ or when you&#8217;re not developing a Rails application and your web framework
 does not support code reloading.</td>
 </tr></table>
 </div>
+<h3 id="sub_uri_deployment_uri_fix">8.9. 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
+static URI for your image in the views. This means your <em>img</em> source probably refers
+to something like <em>/images/foo.jpg</em>. The leading slash means that it&#8217;s an absolute URI:
+you&#8217;re telling the browser to always load <em>http://mysite.com/images/foo.jpg</em> no
+matter what. The problem is that the image is actually at
+<em>http://mysite.com/railsapp/images/foo.jpg</em>. There are two ways to fix this.</p></div>
+<div class="paragraph"><p>The first way (not recommended) is to change your view templates to refer to
+<em>images/foo.jpg</em>. This is a relative URI: note the lack of a leading slash). What
+this does is making the path relative to the current URI. The problem is that if you
+use restful URIs, then your images will probably break again when you add a level to
+the URI.
+For example, when you&#8217;re at <em>http://mysite.com/railsapp</em> the browser will look for
+<em>http://mysite.com/railsapp/images/foo.jpg</em>. But when you&#8217;re at
+<em>http://mysite.com/railsapp/controller</em>. the browser will look for
+<em>http://mysite.com/railsapp/controller/images/foo.jpg</em>.
+So relative URIs usually don&#8217;t work well with layout templates.</p></div>
+<div class="paragraph"><p>The second and highly recommended way is to always use Rails helper methods to
+output tags for static assets. These helper methods automatically take care
+of prepending the base URI that you&#8217;ve deployed the application to. For images
+there is <tt>image_tag</tt>, for JavaScript there is <tt>javascript_include_tag</tt> and for
+CSS there is <tt>stylesheet_link_tag</tt>. In the above example you would simply remove
+the <em>&lt;img&gt;</em> HTML tag and replace it with inline Ruby like this:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><tt>&lt;%= image_tag("foo.jpg") %&gt;</tt></pre>
+</div></div>
+<div class="paragraph"><p>This will generate the proper image tag to <tt>$RAILS_ROOT/public/images/foo.jpg</tt>
+so that your images will always work no matter what sub-URI you&#8217;ve deployed to.</p></div>
+<div class="paragraph"><p>These helper methods are more valuable than you may think. For example they also
+append a timestamp to the URI to better facilitate HTTP caching. For more information,
+please refer to
+<a href="http://api.rubyonrails.org/classes/ActionView/Helpers/AssetTagHelper.html">the Rails API docs</a>.</p></div>
 </div>
 <h2 id="_appendix_a_about_this_document">9. Appendix A: About this document</h2>
 <div class="sectionbody">
@@ -2756,7 +2760,7 @@ Attribution-Share Alike 3.0 Unported License</a>.</p></div>
 </div>
 <h2 id="_appendix_b_terminology">10. Appendix B: Terminology</h2>
 <div class="sectionbody">
-<h3 id="application_root">10.1. Application root</h3><div style="clear:left"></div>
+<h3 id="application_root">10.1. Application root</h3>
 <div class="paragraph"><p>The root directory of an application that&#8217;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
@@ -2823,7 +2827,7 @@ processes.</p></div>
 <div class="paragraph"><p>While this may sound simple, there&#8217;s not just one way to spawn worker processes.
 Let&#8217;s go over the different spawning methods. For simplicity&#8217;s sake, let&#8217;s
 assume that we&#8217;re only talking about Ruby on Rails applications.</p></div>
-<h3 id="_the_most_straightforward_and_traditional_way_conservative_spawning">11.1. The most straightforward and traditional way: conservative spawning</h3><div style="clear:left"></div>
+<h3 id="_the_most_straightforward_and_traditional_way_conservative_spawning">11.1. The most straightforward and traditional way: conservative 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>
@@ -2838,7 +2842,7 @@ programmers jargon, mongrel_cluster creates new Ruby processes by forking the
 current process and exec()-ing a new Ruby interpreter. Phusion Passenger on the
 other hand creates processes that reuse the already loaded Ruby interpreter. In
 programmers jargon, Phusion Passenger calls fork(), but not exec().</p></div>
-<h3 id="_the_smart_spawning_method">11.2. The smart spawning method</h3><div style="clear:left"></div>
+<h3 id="_the_smart_spawning_method">11.2. The smart spawning method</h3>
 <div class="admonitionblock">
 <table><tr>
 <td class="icon">
@@ -2945,7 +2949,7 @@ process).</p></div>
 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>
-<h3 id="_smart_spawning_gotcha_1_unintential_file_descriptor_sharing">11.3. Smart spawning gotcha #1: unintential file descriptor sharing</h3><div style="clear:left"></div>
+<h3 id="_smart_spawning_gotcha_1_unintential_file_descriptor_sharing">11.3. Smart spawning gotcha #1: unintential 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
@@ -3076,7 +3080,7 @@ data in the log file is interleaved.</p></div>
 must synchronize write access via an inter-process synchronization mechanism,
 such as file locks. Reopening the log file, like you would have done in the
 Memcached example, doesn&#8217;t help.</p></div>
-<h3 id="_smart_spawning_gotcha_2_the_need_to_revive_threads">11.4. Smart spawning gotcha #2: the need to revive threads</h3><div style="clear:left"></div>
+<h3 id="_smart_spawning_gotcha_2_the_need_to_revive_threads">11.4. Smart spawning gotcha #2: the need to revive threads</h3>
 <div class="paragraph"><p>Another part of the <em>fork()</em> system call&#8217;s semantics is the fact that threads
 disappear after a fork call. So if you&#8217;ve created any threads in environment.rb,
 then those threads will no longer be running in newly created worker process.
@@ -3097,7 +3101,7 @@ http://www.gnu.org/software/src-highlite -->
         <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></div></div>
-<h3 id="_smart_spawning_gotcha_3_code_load_order">11.5. Smart spawning gotcha #3: code load order</h3><div style="clear:left"></div>
+<h3 id="_smart_spawning_gotcha_3_code_load_order">11.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
@@ -3116,7 +3120,7 @@ has no effect.</p></div>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2009-03-13 17:14:24 CEST
+Last updated 2009-03-31 13:58:42 CEST
 </div>
 </div>
 </body>