Comments on: lighttpd configuration files for multiple rails apps http://serbiancafe.wordpress.com/2005/12/05/lighttpd-configuration-files-for-multiple-rails-apps/ Mon, 03 Aug 2009 20:21:04 +0000 http://wordpress.com/ hourly 1 By: greenpossum http://serbiancafe.wordpress.com/2005/12/05/lighttpd-configuration-files-for-multiple-rails-apps/#comment-325 greenpossum Wed, 21 Jan 2009 02:48:53 +0000 http://serbiancafe.wordpress.com/2005/12/05/lighttpd-configuration-files-for-multiple-rails-apps/#comment-325 Thanks for this tip. But I found that I had to use the $HTTP["host"] matching against the virtual host name instead of $HTTP["url'] matching against the first part of the path to make it work. Otherwise I got a 404 like Ryan did. Looking at the logs, it seems that aside from the top page, and maybe static pages (I don't know), the other requests went to the main host, not the virtual host. The condition log showed some requests for dispatch.cgi which were not matched by the virtual host. I don't know if the lighttpd version has anything to do with it, I'm running 1.4.20. I could have sworn it was working with "url" before a recent update. If you use "host" matching, then be sure to specify "ProxyPreserveHost on" on the Apache side, otherwise lighttpd doesn't get the original Host: header. Thanks for this tip.

But I found that I had to use the $HTTP["host"] matching against the virtual host name instead of $HTTP["url'] matching against the first part of the path to make it work. Otherwise I got a 404 like Ryan did. Looking at the logs, it seems that aside from the top page, and maybe static pages (I don’t know), the other requests went to the main host, not the virtual host. The condition log showed some requests for dispatch.cgi which were not matched by the virtual host.

I don’t know if the lighttpd version has anything to do with it, I’m running 1.4.20. I could have sworn it was working with “url” before a recent update.

If you use “host” matching, then be sure to specify “ProxyPreserveHost on” on the Apache side, otherwise lighttpd doesn’t get the original Host: header.

]]> By: Joe’s Amazing Technicolor Weblog » Blog Archive » Deploying my first rails app http://serbiancafe.wordpress.com/2005/12/05/lighttpd-configuration-files-for-multiple-rails-apps/#comment-68 Joe’s Amazing Technicolor Weblog » Blog Archive » Deploying my first rails app Wed, 10 Jan 2007 04:19:16 +0000 http://serbiancafe.wordpress.com/2005/12/05/lighttpd-configuration-files-for-multiple-rails-apps/#comment-68 [...] to this lighttpd configuration guide for pointing out that alias.url needs to be set as well for the public/ directory to be properly [...] [...] to this lighttpd configuration guide for pointing out that alias.url needs to be set as well for the public/ directory to be properly [...]

]]> By: Ryan http://serbiancafe.wordpress.com/2005/12/05/lighttpd-configuration-files-for-multiple-rails-apps/#comment-3 Ryan Tue, 13 Jun 2006 20:32:44 +0000 http://serbiancafe.wordpress.com/2005/12/05/lighttpd-configuration-files-for-multiple-rails-apps/#comment-3 This get's me to being able to access my static index.html in my app's public directory, but I just get 404 when I try to reacha controller. This get’s me to being able to access my static index.html in my app’s public directory, but I just get 404 when I try to reacha controller.

]]> By: freebsd + lighttpd + Typo^H^H^H^HWordPress http://serbiancafe.wordpress.com/2005/12/05/lighttpd-configuration-files-for-multiple-rails-apps/#comment-2 freebsd + lighttpd + Typo^H^H^H^HWordPress Sat, 01 Apr 2006 21:27:14 +0000 http://serbiancafe.wordpress.com/2005/12/05/lighttpd-configuration-files-for-multiple-rails-apps/#comment-2 [...] First were my problems with lighttpd.conf and trying to get rails working with directory aliasing. After looking in a few places (here and here), thanks to technorati I finally found something else here that worked. [...] [...] First were my problems with lighttpd.conf and trying to get rails working with directory aliasing. After looking in a few places (here and here), thanks to technorati I finally found something else here that worked. [...]

]]>