1.4.17 - for the sake of the server.error-handler-404
August 29, 2007
Ok. We broke it. And yes it took longer than expected to fix it.
Anyway. It was worth to wait. We fixed lots of bugs in this release. For a complete list of changes see below.
The final fix for bug #948 changed the behavior of the server.error-handler-404. In the past lighttpd tried to send 404 responses generated by CGI/FastCGI/SCGI applications to the configured handler. With the current design of the plugin handling the 404 handler this failed, if the subrequest used the same backend as the original request (FastCGI -> FastCGI 404 handler). Starting with 1.4.17, only the original request will trigger the 404 handler. That means your application has to generate the content for the 404 response itself. You can no longer rely on the 404 handler for dynamically generated 404 responses.
Thanks for using lighttpd! :)