Skip to content

2010

PRE-RELEASE: lighttpd 1.4.27rc2-r2758

We would like to draw your attention to the latest pre-release of the stable 1.4 branch of lighttpd.

You can get the pre-release from these urls:
https://download.lighttpd.net/lighttpd/snapshots-1.4.x/lighttpd-1.4.27rc2-r2758.tar.gz
https://download.lighttpd.net/lighttpd/snapshots-1.4.x/lighttpd-1.4.27rc2-r2758.tar.bz2
SHA1 checksums:
https://download.lighttpd.net/lighttpd/snapshots-1.4.x/lighttpd-1.4.27rc2-r2758.sha1sum

Please test it as much as possible and provide us with feedback.
A lot of testing ensures a good release.

New changes since rc1:

We fixed a race condition with mod_cgi responses; and a similar problem in mod_proxy (forward response as soon at it is available).

There is a new fdevent handler “libev”; “linux-rtsig” got removed. The “libev” handler should support solaris ports, so it might be especially interesting on solaris.

And the last commit changes a small bit how we handle IPv6; we now disable the “dual-stack” IPv6 sockets in almost all cases, see IPv6-Config for details.

Changes already in rc1:

The most important change is the SSL_CTX_set_options fix, as lighttpd\ doesn’t start without it if you use a recent ssl library; most distributions included it with 1.4.26 for a while now.

We hope to have fixed some problems with mod_proxy and we really hope TLS SNI works now, and lighty doesn’t use the wrong certs anymore; it would be nice if you could test this :)

We fixed a segfault in mod_compress; if you disable etags, mod_compress won’t try to cache on disk anymore (and doesn’t set etag).

If no showstoppers are encountered, there will be a final release soon.

PRE-RELEASE: lighttpd 1.4.27rc1-r2724

We would like to draw your attention to the latest pre-release of the stable 1.4 branch of lighttpd.

You can get the pre-release from these urls:
https://download.lighttpd.net/lighttpd/snapshots-1.4.x/lighttpd-1.4.27rc1-r2724.tar.gz
https://download.lighttpd.net/lighttpd/snapshots-1.4.x/lighttpd-1.4.27rc1-r2724.tar.bz2
SHA1 checksums:
https://download.lighttpd.net/lighttpd/snapshots-1.4.x/lighttpd-1.4.27rc1-r2724.sha1sum

Please test it as much as possible and provide us with feedback.
A lot of testing ensures a good release.

The most important change is the SSL_CTX_set_options fix, as lighttpd doesn’t start without it if you use a recent ssl library; most distributions included it with 1.4.26 for a while now.

We hope to have fixed some problems with mod_proxy and we really hope TLS SNI works now, and lighty doesn’t use the wrong certs anymore; it would be nice if you could test this :)

We fixed a segfault in mod_compress; if you disable etags, mod_compress won’t try to cache on disk anymore (and doesn’t set etag).

If no showstoppers are encountered, there will be a final release soon.

  • in hosting
  • 1 min read

lighttpd.net moved to new host

In case you havn’t noticed: lighttpd.net moved to a new home. After several years running on sponsored hardware, we now run on our “own” server. Now including IPv6.

The transition went very smoothly thanks to the wonderful team. If you notice some issues, please ping us on IRC.

BTW, all your donations get used to keep the domain and server running. Thanks to all that make this possible. hint More support is always welcome.

PRE-RELEASE: lighttpd 1.4.26rc1-r2710

We would like to draw your attention to the latest pre-release of the stable 1.4 branch of lighttpd.

You can get the pre-release from these urls:
https://download.lighttpd.net/lighttpd/snapshots-1.4.x/lighttpd-1.4.26rc1-r2710.tar.gz
https://download.lighttpd.net/lighttpd/snapshots-1.4.x/lighttpd-1.4.26rc1-r2710.tar.bz2
SHA1 checksums:
https://download.lighttpd.net/lighttpd/snapshots-1.4.x/lighttpd-1.4.26rc1-r2710.sha1sum

Please test it as much as possible and provide us with feedback.
A lot of testing ensures a good release.

There have been some important bug fixes (request parser handling for splitted header data, a fd leak in mod_cgi, a segfault with broken configs in mod_rewrite/mod_redirect and of course the latest security issue with an OOM vulnerability)

If no showstoppers are encountered, there will be a final release soon.

PS: As it is often asked in the comments: We don’t plan to release 1.5, as we are working on 2.0; we can’t support too many different versions, so while we are still trying to keep 1.5 working, our main efforts will be keeping 1.4 stable and working on 2.0 for now.