A lot of Lighttpd users converting from Apache ask if Lighttpd has any substitutes for .htaccess files, which were made popular by Apache and are now a de-facto Standard used by many web servers. Instead, Lighttpd has its own configuration syntax, so all the old .htaccess files won't work with Lighttpd.
There is no perfect solution to this problem, but as the most used feature of .htaccess files is authentication, we can at least solve that. Let's have a look at the authentication directive format in Apache and Lighttpd:
Apache just assumes that the path required for authentication is the path where the
.htaccessfile resides, while Lighttpd needs to add this explicitly.The
httpd.confadds some more stuff, which is given as default fromhttpd.conf. In thelighttpd.confexample, we do not assume such defaults.
Note that the Lighttpd configuration gets a little more complicated if we have multiple backends or user files. In this case, we need to use a selector to limit the reach of...