Comments on: Symfony and lighttpd

By: Laurent

Laurent — Wed, 07 Oct 2009 08:36:11 +0000

Interesting idea. I’d put the fastcgi.server line inside of a $HTTP["url"] conditional (I already have one fastcgi.server line per $HTTP["host"] and it works great).

By: brainfault

brainfault — Wed, 07 Oct 2009 07:25:49 +0000

what about disabling php execution in the upload folder ?

By: Tal Ater

Tal Ater — Fri, 08 May 2009 15:13:40 +0000

Maybe this will finally explain all the difficulties I’ve had working with querystrings that no one else was able to understand… I never thought to look in the lighttpd.conf … argh!

Thanks for the post.

By the way, I just released a new plugin for dealing with domains and subdomains in an elegant way straight from the routing system… It’s called sfDomainRoutePlugin (http://www.symfony-project.org/plugins/sfDomainRoutePlugin) and it lets you do some fancy things with subdomains, or domains in an elegant way. The kind of things that most of us had to resort to url rewrite hacks for.

For example, you can restrict rules to certain domains or subdomains (e.g. http://www.site.com and blog.site.com will go to different routes in the same application) , or even pass parameters in the subdomain (e.g. username.site.com) or even in the domain (e.g. PS2News.com vs. XboxNews.com).

By: Laurent

Laurent — Mon, 13 Apr 2009 14:58:02 +0000

Thanks for the information.
I always felt like the absence of a “file exists” rule was a feature of lighttpd. I don’t think it’s that a good idea . But it will make hosting some applications much easier; I’ve seen some horrific rewriting examples ;-).

By: Jamie

Jamie — Mon, 13 Apr 2009 10:58:25 +0000

Lighttpd 1.4.23 will include a handy helper to do a rewrite based on whether or not a file exists, which means you will be able to take all those static file rules out. See: http://redmine.lighttpd.net/issues/985