Skip to content

lighttpd1.5

PRE-RELEASE: lighttpd 1.4.23rc2-r2534 + new 1.5 snapshot

As a quick followup to release candidate #1 of 1.4.23, here comes #2.

You can get 1.4.23rc2-r2534 from these urls:
https://download.lighttpd.net/lighttpd/snapshots-1.4.x/lighttpd-1.4.23rc2-r2534.tar.gz
https://download.lighttpd.net/lighttpd/snapshots-1.4.x/lighttpd-1.4.23rc2-r2534.tar.bz2
Checksums:
https://download.lighttpd.net/lighttpd/snapshots-1.4.x/lighttpd-1.4.23rc2-r2534.sha256sum
https://download.lighttpd.net/lighttpd/snapshots-1.4.x/lighttpd-1.4.23rc2-r2534.sha1sum
https://download.lighttpd.net/lighttpd/snapshots-1.4.x/lighttpd-1.4.23rc2-r2534.md5sum

Please test it as much as possible and provide us with feedback.
A lot of testing ensures a good release.
If no showstoppers are encountered, there will be a final release soon.

Additionaly, we have created a new 1.5 snapshot 1.5.0snap-r2533.
It contains an important fix for a remote crash bug (only in 1.5) when ssl is used.

PRE-RELEASE: lighttpd-1.5.0-r1477.tar.gz

mod-proxy-core

Robert Jakabosky fixed and improved mod-proxy-core alot since the last pre-release:

POSIX Async IO

I added native support for POSIX AIO which might bring async io for more platforms. While Linux AIO is pretty stable the POSIX aio support is pretty experimental. Perhaps it compiles for you.

I tried to compile it on Linux and FreeBSD.

server.network-backend = "posix-aio"

PRE-RELEASE: lighttpd-1.5.0-r1454.tar.gz

Thanks to brave testers in #lighttpd the AIO-support is stabilizing very well and the corruptions that have been reported are fixed now.

Next to bugfixes, I implemented chunk-stealing and doubled the performance of aio for small files (100k) (16MByte/s instead of 9MByte/s).

lighty 1.5.0 and linux-aio

1.5.0 will be a big win for all users. It will be more flexible in the handling and will have huge improvement for static files thanks to async io.

The following benchmarks shows a increase of 80% for the new linux-aio-sendfile backend compared the classic linux-sendfile one.

1.4.12 becomes 1.5.0

moo poked me today and was so right: “With all the changes going into SVN we shouldn’t call the next release 1.4.12, but 1.5.0”. Lifting the restriction on ‘try to stay compatible to the 1.4.x plugin-API I started right away on ripping the internals apart and put them together sliglty different.

If you are developing a plugin for 1.4.x right now, be asured that it won’t work without changes in 1.5.0. Let me explain what is changing.