Lighttpd

These interesting pages may help us solve this quiz!

http://drupal.org/node/20766 (Drupal and lighttpd rewrite rules)

http://digitalhandyman.info/articles/2005/08/14/gallery-url-rewriting-in-lighttpd (Gallery and lighttpd rerwrite rules)

http://www.xyooj.com/blog/plink/category/technical/lighttpd/ (Multi domain with multi sub-domains)

We have the configuration pieces... We miss a clever guy to put all pieces together in the right position!
Sorry Jan, I am not a clever guy and you are too alone in this brilliant project :)

-- oslookup

As far as I can tell, lighttpd still doesn't support flexible enough error-redirection (as in the 2nd part of oslookup's original post).

Suppose you have a CMS (blog, wiki, or such) that accepts clean URLs, but you also have some regular files whose locations, if requested directly by a web user, might be mistaken as clean URLs and rewritten by the CMS (actually the web server) to something like {{{/index.php?id=thefile}}}.

The web server ought to be able to say:

1. If the file specified by the URL exists, serve it;
2. If not (i.e. if a 404 would result), apply a set of rewrite rules, such as:

url.rewrite-once ( "^/(.*)$" => "/index.php?id=$1" )

One program which uses Apache rewrite rules to do this is DokuWiki.

Unless I'm missing something, lighttpd can't reproduce such rules.

-- anonymous2

That would require editing the application, right? If so, is there a reason to require applications to adapt to lighttpd, rather than lighttpd to adapt to applications which rely on certain Apache features (such as this one)? If lighttpd is to be a replacement for Apache, it seems to me it ought to have the same capabilities, even if it implements them differently.

Even if lighttpd is not to have the same capabilities as Apache, is there a reason to exclude this feature, or is it just a matter of time before it will be implemented?

-- anonymous2

This whole ticket looks awfully like disguised spam!

-- anonymous475987

typo

Yes, I agree with a person who wrote comment #8. Lighttpd should accept .htaccess files. However, I do not order Lighttpd to understand Apache's syntax (which is different), but I would like to add some lighty's configuration in .htaccess files. I'm telling it in mod_rewrite's context as it's very comfortable to have a seperate file (.htaccess) with rewrite rules - versus edition of lighttpd.conf.

-- Nowaker

we will not support the apache syntax in core any time soon. that said even if we support .htaccess alike files you still have to convert the syntax.
the example from the original comment uses -f/-d conditionals. those require mod_magnet in lighttpd. (see http://pixel.global-banlist.de/tags/mod_magnet http://trac.lighttpd.net/trac/wiki/Docs:ModMagnet)

mod_magnet scripts are reloaded when they have changed. that said you just need to convert your rules to mod_magnet scripts and get the features already.

lighthttpd looked like promising replaces for Apache to me. But when I found that .htaccess is not supported... Sorry, lighthttpd is no go. We have lots of sites with lots of .htaccess. And it is not a question to convert them manually.

May be, you guys, did a great job, I do not know. But your comments about .htaccess make me think that lighthttpd is just a hobby project for you ("we do only what we want to do, we do not care about business customers"). I doubt you can replace existing Apache installations with such attitude.

Anyway, good luck to your project.

Replying to anonymous:

lighthttpd looked like promising replaces for Apache to me. But when I found that .htaccess is not supported... Sorry, lighthttpd is no go. We have lots of sites with lots of .htaccess. And it is not a question to convert them manually.

May be, you guys, did a great job, I do not know. But your comments about .htaccess make me think that lighthttpd is just a hobby project for you ("we do only what we want to do, we do not care about business customers"). I doubt you can replace existing Apache installations with such attitude.

Anyway, good luck to your project.

Your comments make me think that English is just a hobby language for you

I tend to agree that it is a problem not to have something compatible with .htaccess.
Lots of php programs were written for Apache and use .htaccess to modify php behavior for just one site or directory.
After spending all night and more hours setting up lighttpd so it'll run php. I'm now stuck trying to figure out how to adapt .htaccess or make a fix, hack to replace it.
So how would someone convert the simple problem of making password protected directories without .htaccess using lighttpd?
Actually this question is not about rewrite rules but this forum popped up on google when I looked for .htaccess and lighttpd.

I'll answer my own post since I posted this in the wrong place.
I now found out that I should have been looking at mod_auth for directory access stuff. Although I didn't get that to work either. Maybe I'll wait until next year and keep on using Apache instead of wasting my time trying to reinvent the wheel just so lighttpd will work the way it's supposed to.