The big thing of lighttpd 1.4.0 were the nested conditionals, but how can they be used ? And what are includes ?
From time to time we write code faster than documention. This basicly means that sometimes small gems are hidden and unknown to most users.
This time we want to put some focus on the new commandline options in lighttpd 1.4.0 and higher.
Just a few minutes ago lighttpd 1.4.1 has been released, shortly after lighttpd 1.4.0 which had some user-visible problems.
1.4.1 fixes those bugs, stabilizes the SSL support on OpenBSD and finishes the WebDAV support in mod_webdav to Class 1 (all options except LOCK/UNLOCK).
Xuefer pointed me to a thread on internals mailinglist on php.net. It starts nicely with the question if a upgrade to Apache2.x can solve the low-latency problem that arise when you want to use AJAX on a high-traffic site, talks about keep-alive and its problems until Andreas Korthus throws lighttpd into the game.
.15 is like a best-of album from your favourite band which contains all
the good song, a few remixes and one or two new songs, just to make sure
that you buy it.
We did the same: the core stuff got bugfixes and two new modules were
added which might interest you:
Changes ------- * added mod_cml * added mod_trigger_b4_dl * added encoding to mod_dirlisting * added ?auto to mod_status * relaxed handling of characters in URIs even more * fixed detection of sendfile() on Linux 2.4.x * fixed comparision of buffers for short strings * server.errorfile-prefix is now conditional * fixed mod_rrdtool to close STDERR
After the logo-contest went very well and we have seen very nice and professional proposals lighty finally has a logo.
Good work. Now we have a nice button which everyone can add to their sites and link back to lighttpd.net.
For a real big one, we have the big logo with a nice slogan:
For more information about the idea of the logo and more background on how lighttpd was started check the story of lighttpd on lighttpd.net.
After the release didn’t revealed any serious bugs the documentation was updated and the final release was roled.
Get it at www.lighttpd.net/download/ and spread the word.
I would like to see some comments on the loadbalancers in mod_proxy and the new mod_scgi.
The last release of lighttpd is now 3 month ago and several patches are waiting in the trac.lighttpd.net/trac/ for their release.
The first public pre-release has been upload and is meant for a wider testing than the svn-tree.
Please don’t put that on a production system yet even it contains mostly bugfixes.
Yeaha, what a impressive contest. So many nice ideas on how to interpret the word light. Even in the last days before the contest was closed we got some final submissions. I’m impressed and confused in the same way.
I can’t draw a decision on my own. I need your help. Think about the following questions and post yours answers in the comment.
- Which of the logos do you like the most ?
- Which of the logos would wear on a t-shirt and be proud of being a user of ?
- Which represents the idea of a light webserver the best way ?
I have some personal candidates, but can’t come to a final conclusion, perhaps you can help me ?