No announcement yet.

Lighttpd 1.4.40 Fixes Hundreds of Bugs

  • Filter
  • Time
  • Show
Clear All
new posts

  • Lighttpd 1.4.40 Fixes Hundreds of Bugs

    Phoronix: Lighttpd 1.4.40 Fixes Hundreds of Bugs

    Lighttpd, the lightweight open-source web server designed for high performance, is out with its major v1.4.40 update...

  • #2
    I used to be a big fan of Lighttpd when leaving the big giant Apache web server. Unfortunately probably due to mysterious memory leaking bug (which I did not found from all of my managed servers), the user base decline to around 1% and the majority join the nginx family.

    Less user will get less support like documentation, tricky configuration or weird bugs others might found, as a result I also switched to nginx since Debian 8 to strengthen the security.


    • #3
      How does Lighttpd compare to Mongoose?


      • #4
        dbpalan the hundreds of bugs fixed in lighttpd 1.4.40 (latest is currently lighttpd 1.4.41) includes addressing the memory resource management issue. The memory resource management issue was a result of caching entire backend (CGI, FastCGI, SCGI, proxy, etc) responses in memory, regardless of size. The issue was not-so-mysterious and was not a memory leak per se, but unfortunately was left alone for a long, long time and caused problems for those affected by it. Hopefully, the resolution of hundreds of open issues in the lighttpd release demonstrates that the current maintainers (including me) aim to address issues in a more timely fashion.

        zboson lighttpd and mongoose are both functional web servers, as are nginx, Apache, and many others. All are reasonable web serving solutions that meet the needs of many typical use cases. Which one is "better" for your needs depends on how you plan to use and maintain your system. While micro-benchmarks might show that one web server performs better than another for that specific micro-benchmark, there is not a significant difference between web servers in many real-world use cases, as long as the web server can do what you want it to do. If your use cases requires a feature that one web server has and another does not, then that is your answer.