lighttpd

1.4.17 - for the sake of the server.error-handler-404

August 29th, 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.

Download

  • lighttpd-1.4.17.tar.gz
    (sha1sum: f86684db6979c363d74689a51c3e8a7af066025e
    md5sum: 7172c39c2a166fe7f9ab6df30fa4298f     )
  • lighttpd-1.4.17.tar.bz2
    (sha1sum: e7684d29b2a42bc0628dc59b05741fc5fb5f699b
    md5sum: 85c99c2d6baf8ad9e38e6267efe7d9aa    )

Thanks for using lighttpd! :)

  • added dir-listing.set-footer in mod_dirlisting (#1277)
  • added sending UID and PID for SIGTERM and SIGINT to the logs
  • fixed hardcoded font-sizes in mod_dirlisting (#1267)
  • fixed different ETag length on 32/64 platforms (#1279)
  • fixed compression of files < 128 bytes by disabling compression (#1241)
  • fixed mysql server reconnects (#518)
  • fixed disabled keep-alive for dynamic content with HTTP/1.0 (#1166)
  • fixed crash on mixed EOL sequences in mod_cgi
  • fixed key compare (#1287)
  • fixed invalid char in header values (#1286)
  • fixed invalid "304 Not Modified" on broken timestamps
  • fixed endless loop on shrinked files with sendfile() on BSD (#1289)
  • fixed counter overrun in ?auto in mod_status (#909)
  • fixed too aggresive caching of nested conditionals (#41)
  • fixed possible overflow in unix-socket path checks on BSD (#713)
  • fixed extra Content-Length header on 1xx, 204 and 304 (#1002)
  • fixed handling of duplicate If-Modified-Since to return 304
  • fixed extracting status code from NPH scripts (#1125)
  • fixed prctl() usage (#1310)
  • removed config-check if passwd files exist (#1188)
  • fixed crash when etags are disabled but the client sends one (#1322)
  • fixed crash when freeing the config in mod_alias
  • fixed server.error-handler-404 breakage from 1.4.16 (#1270)
  • fixed entering 404-handler from dynamic content (#948)
  • added more debug infos for FAM based stat-cache
  • use more LSB like paths in the sample config (#1242)

13 Responses to “1.4.17 - for the sake of the server.error-handler-404”

  1. sleets Says:
    August 29th, 2007 at 01:49 AM I hope you make it work with lua kepler or can use lua with sqlite & mysql & other cool stuff.
  2. Servertweak.com Says:
    August 29th, 2007 at 04:04 AM Bravo, thanks for this update guys! :D
  3. SAP Guru Says:
    August 29th, 2007 at 06:53 AM Great thanks, been waiting fo this fix.
  4. ste Says:
    August 29th, 2007 at 09:26 AM Thanks for the update, lighttpd on RHEL 4 seems to be working fine
  5. darix Says:
    August 29th, 2007 at 09:28 AM uhm. sleets i dont see a reason why kepler shouldnt work with lighttpd. are you seeing any issues with it?
  6. arch Says:
    August 29th, 2007 at 04:21 PM I've generally been happy with lighttpd but I think the response time for fixing the 404 problem has been rather poor. This is a really big problem for sites running Ruby on Rails - which has done a LOT for pushing lighttpd into the spotlight. Not to say I appreciate bug fixes, but please try to address critical problems faster without the wait. I mean are you guys worried about running out of version numbers or something? :) Perhaps releasing a bit more often might also help things.
  7. grandcat Says:
    August 29th, 2007 at 08:38 PM Thanks, that's really great =)
  8. Free SMS Says:
    August 29th, 2007 at 09:32 PM Thank you, for your work! greetz
  9. CoffeeDregs Says:
    August 30th, 2007 at 04:14 AM Woohoo! Thanks for the fix. Waiting on Debian to push it downstream to me. apt-get update... apt-get update... apt-get update...
  10. q250 Says:
    August 30th, 2007 at 03:28 PM Hiya, Im running huge forum on average web server. On 1.4.16 i have no problems with server overload (maximum 8.0) but when i installed 1.4.17 i got server load 52.0 and everything was freezed... something is screwed in this release i think
  11. jrabbit Says:
    August 30th, 2007 at 05:43 PM Can we have an update to the mod_deflate patch for 1.4.17 - I've been unable to update my server since 1.4.13 as it would mean I loose dynamic compression.
  12. Motoshi Says:
    September 5th, 2007 at 12:34 AM Tested it and it looks like its having some freeze issues, getting a lot of server.max-write-idle errors, pages are not being processed that quickly compared to 1.4.16, it can take up to a minute sometimes. Config files remained the same.
  13. tinkertim Says:
    September 7th, 2007 at 02:26 AM This is a nice laundry list taken care of, thanks guys! I'm not going to throw this version into production, I'll do some stress testing first. I'm looking forward to the next milestone release, this server is really maturing. It seems a little more 'heavy handed' than previously, is there something possibly overlooked in keep-alives / http 1.0?

Sorry, comments are closed for this article.