Comments on: Capistrano and Passenger http://tnux.net/2008/06/23/capistrano-and-passenger/ Blog of Tom Pesman Thu, 09 Sep 2010 12:37:32 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Tnux.net » Capistrano and Passenger part 2 http://tnux.net/2008/06/23/capistrano-and-passenger/comment-page-1/#comment-21 Tnux.net » Capistrano and Passenger part 2 Sat, 12 Dec 2009 13:52:24 +0000 http://tnux.net/?p=4#comment-21 [...] Karl Varga pointed out in his comment on my previous post on Capistrano and Passenger (here) my apache rewrite rules did not send back the proper HTTP status codes. Now with the improved and [...] [...] Karl Varga pointed out in his comment on my previous post on Capistrano and Passenger (here) my apache rewrite rules did not send back the proper HTTP status codes. Now with the improved and [...]

]]> By: Tom http://tnux.net/2008/06/23/capistrano-and-passenger/comment-page-1/#comment-20 Tom Tue, 08 Dec 2009 13:10:22 +0000 http://tnux.net/?p=4#comment-20 I do agree with the fact that your rewrite rules are an improvement over mine. I personally will not include the sitemap to the exceptions because my app will generate them automatically. Although I like the fact that your rules return the proper HTTP status codes. I do agree with the fact that your rewrite rules are an improvement over mine. I personally will not include the sitemap to the exceptions because my app will generate them automatically. Although I like the fact that your rules return the proper HTTP status codes.

]]> By: Karl Varga http://tnux.net/2008/06/23/capistrano-and-passenger/comment-page-1/#comment-19 Karl Varga Tue, 08 Dec 2009 09:38:47 +0000 http://tnux.net/?p=4#comment-19 My rewrite conditions are slightly different and dare I say better? The nice thing about this approach is you get the proper HTTP status code being returned with the maintenance page so that robots know it's just a temporary problem. Also, it allows robots to ready the robots files and any sitemaps you may have. I've also included images so that you can put images like logos and stuff in your maintenance page and have them display properly. ErrorDocument 503 /system/maintenance.html RewriteCond %{DOCUMENT_ROOT}/system/maintenance.html -f RewriteCond %{SCRIPT_FILENAME} !maintenance.html RewriteCond %{REQUEST_URI} !^/images/ RewriteCond %{REQUEST_URI} !^/robots.txt RewriteCond %{REQUEST_URI} !^/sitemap RewriteRule ^.*$ - [redirect=503,last] My rewrite conditions are slightly different and dare I say better? The nice thing about this approach is you get the proper HTTP status code being returned with the maintenance page so that robots know it’s just a temporary problem. Also, it allows robots to ready the robots files and any sitemaps you may have. I’ve also included images so that you can put images like logos and stuff in your maintenance page and have them display properly.

ErrorDocument 503 /system/maintenance.html
RewriteCond %{DOCUMENT_ROOT}/system/maintenance.html -f
RewriteCond %{SCRIPT_FILENAME} !maintenance.html
RewriteCond %{REQUEST_URI} !^/images/
RewriteCond %{REQUEST_URI} !^/robots.txt
RewriteCond %{REQUEST_URI} !^/sitemap
RewriteRule ^.*$ – [redirect=503,last]

]]>