With lighttpd 1.4.3 it is possible to do a graceful shutdown by sending a SIGINT to the process. It will only shutdown the server after the client connections are closed successfully without interrupting the connections.
But can this be used to implement “reload config on signal” or “graceful restart”?
lighttpd isn’t beautiful when it shows the user that a file is not available.
When I wrote it I want to make sure to don’t show any information that might be used for XSS attacks like displaying the URL unencoded, show local paths, … something like that. I used the simplest approach: Just show the status.
This is not pretty, but works. But I assume you want something more sexy.
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.
The big thing of lighttpd 1.4.0 were the nested conditionals, but how can they be used ? And what are includes ?
Xuefer pointed me to a thread on internals mailinglist on php.net. It starts nicely with the question if a upgrade to Apache 2.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.
After the logo-contest went very well and we have seen very nice and professional proposals lighty finally has a logo.
The winning entry is based on the paper airplane submitted by Phu from endturn. It was modified by Paul from openartist.net.
Good work. Now we have a nice button which everyone can add to their sites and link back to https://www.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.
Xuefer opened a ticket to document the history of lighty.
As we have a new logo now I wrote everything up, why I started it, why I continued and were we will head to.
If you want, add your date when you started using lighty to the comments.
After poking I was poked several times to publish a benchmark between lighttpd and Apache2 I added it to the benchmark page.
More impressive than scientific benchmarks are real-world tests like the oen Jason has done: Taking a full frontal slashdot lighttpdly at textdrive. :)
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.
I have some personal candidates, but can’t come to a final conclusion, perhaps you can help me ?
Only 7 days are left for the lighttpd logo contest. In the last week 3 artists have sent in there submissions with one of them being so creative to submit 8 logos at once.
Please take a look at the new submissions and leave your comment under this article.