PRE-RELEASE: lighttpd-1.4.12-r1303
A new pre-release has been uploaded with more fixes than the last release and with a new, hot module: mod_magnet . It is the promised replacement for mod_cml.
Update replaced r1303 with r1309
lighty developer blog¶
forum is on the new host
The forum just got migrated to the new lighty-server. As long as the DNS is not update and as fallback, the old lighty server is proxying to the new host.
As a side-effect, registering a account in the forum works again. The trac on the new host also sends out notifications on ticket updates again.
PRE-RELEASE: lighttpd-1.4.12-20060901-1232.tar.gz
The 1.4.11 release need a maintainance package. This pre-release is taking the 1.4.11 code and fixes:
- SSL upload hangs
- SSL download breaks
- cygwin path traversal
and adds:
- LOCK/UNLOCK support for webdav
bsdtalk061 - Interview with lighttpd developer Jan Kneschke
bsdtalk061 - Interview with lighttpd developer Jan Kneschke
- What is lighty
- Event-based vs. Threads and Processes
- What is coming up version 1.5.x
- X-sendfile and hash-balancing
- Why is it using the BSD license
- vi or emacs :)
- and much more.
Thanks to Will (bitgeist) for doing the interview.
BTW: sorry for my bad microphone.
the docs are dead, long live the docs
… oh not again.
The Docs are now in the wiki instead of a dead, boring manual, see https://www.lighttpd.net points to the new location already. If you want, the docs are editable for everyone now. It is an easy way to improve the docs, check if they are right, fix typos, rephrase the wording, add more examples, …
Thanks go to hoffie and the others who helped to move the docs to the wiki.
Expect: header handling is in
Just a short one: Handling for HTTP/1.1 Expect: 100-continue has been
added. With the new infrastructure it was only a few lines to get it in.
curl and some WebDAV clients were using it to verify that the server
speaks HTTP/1.1.
How to spawn a backend process
I’m not completly sure yet how I will add the spawning of processes to the new mod_proxy_core. The current idea is mod_spawn described as below. If you have specific needs or ideas how to implement it, add your comment please.
mod_cml is dead, long live mod_cml
Yep, mod_cml will vanish from the distribution of lighttpd 1.5.0. It will get a new name and will get a full blown set of functions to manipulate the execution of a request in lighty.
It reason to rename mod_cml is that the focus of this module has changed from the its first implementation. It is not about checking if a request is a cache-hit or not. It is about deciding how to handle a request. Any status code can be returned, any content source will be able to be queried to assemble the content (files, memcache).
The main reason is to allow us to change the names like ‘trigger_handler’ and ‘CACHE_HIT’ to something more appropriate. In the end no big change, but a neccesary one to make the use of this powerful module more obvious. … Perhaps the new name will be mod_cml … what would be the new meaning of this abbreviation ? Any suggestions ?
mod_uploadprogress is back
In my ongoing efforts in restructuring the core of lighttpd for the 1.5.0 release I brought mod_uploadprogress back to life.
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.