lighty's life

lighty developer blog

Flv Streaming With Lighttpd

1.4.11 got a new module for streaming Flash movie files called mod_flv_streaming. This module allows you to seek in FLV files using the high performance infrastructure of lighttpd.

Patches for 1.4.10

The wiki knows about bugs and their fixes in 1.4.10. Usually it covers small patches which fix problems discovered after the release.

But more interesting for the future is the section about patches for the current release.

  • mod_deflate for compressing dynamic content
  • mod_extforward to extract the Host from X-forwarded-for
  • the mysqlvhost patches for mod_fastcgi

They will be check in the next ‘feature’ release. If you want to try them out now and test them, feel free to contact the authors of the patches directly.

Lighttpd 1.4.10 Released

lighttpd 1.4.10 has been release and fixes the fastcgi and cgi problems of .9.

  • CGI should work again
  • fastcgi should not result in a crash under high load
  • load balancing in fastcgi should work as expected
  • broken digest request shouldn’t crash mod_auth

New is

  fastcgi.map-extensions = ( ".php3" => ".php" )
  fastcgi.server = ( ".php" => ... )

Links

In the News

I grep through the referer log from time to time to see where lighty is mentioned on the net.

This week I got attracted by these links:

That’s it for this week.

Simplify Your Configfiles With Includes

Or should it be named ‘virtual hosting made easy ?’ Anyway. If your vhosting setup looks a bit more complext like having different options (static only, php support, pre-installed rails apps, …) but a similar setup for each you can’t use the vhosting modules and have to write everything by hand. But there is rescue thanks to includes and variables.

Optimizing Lighty for High-concurrent, Large-file Downloads

In lighttpd 1.4.6 we have added some modifications for sites which have handle some 100 files in parallel with size of more than 100Mb each.

The problem in earlier releases was that lighttpd had to wait until the disk had seeked to the right place, read a few 100 kbyte to send it out. And this for each request as this scenario was completly trashing the disk-buffering. The IO-wait went sky-high and we were completly bound to the disk-io.