Lighttpd

lighttpd (prescribed pronunciation: "lighty")^[2] is an open-source web server optimized for speed-critical environments while remaining standards-compliant, secure and flexible.^{[citation needed]} It was originally written by Jan Kneschke as a proof-of-concept of the c10k problem – how to handle 10,000 connections in parallel on one server,^[3] but has gained worldwide popularity.^[4] Its name is a portmanteau of "light" and "httpd".

lighttpd

Original author(s)	Jan Kneschke
Initial release	March 2003; 22 years ago (2003-03)
Stable release	1.4.79[1]  / 4 April 2025; 50 days ago (4 April 2025)
Preview release	1.4.79 (April 4, 2025; 50 days ago (2025-04-04)) [±]
Repository	git.lighttpd.net/lighttpd
Written in	C
Available in	English
Type	Web server
License	BSD-3-Clause
Website	www.lighttpd.net

Premise

The low memory footprint (compared to other web servers),^[5] small CPU load and speed optimizations^[6] make lighttpd suitable for servers that are suffering load problems, or for serving static media separately from dynamic content. lighttpd is free and open-source software and is distributed under the BSD license. It runs natively on Unix-like operating systems, with experimental support for Microsoft Windows.^[7]

Application support

lighttpd supports the FastCGI, SCGI and CGI interfaces to external programs, allowing web applications written in any programming language to be used with the server. As a particularly popular language, PHP performance has received special attention. Lighttpd's FastCGI can be configured to support PHP with opcode caches (like APC) properly and efficiently. Additionally, it has received attention from its popularity within the Python, Perl, Ruby and Lua communities. Lighttpd also supports WebDNA, the resilient in-memory database system designed to build database-driven websites. It is a popular web server for the Catalyst and Ruby on Rails web frameworks. Lighttpd does not support ISAPI.

Features

• Load balancing, CGI, FastCGI, SCGI, HTTP proxy, Servlet AJP, WebSocket tunnel support
• chroot support
• Web server event mechanism performance – select(), poll(), and epoll()^[8]
• Support for more efficient event notification schemes like kqueue and epoll
• Conditional URL rewriting (mod_rewrite)
• TLS/SSL with SNI support, via OpenSSL, GnuTLS, Mbed TLS, NSS, WolfSSL.^[9]
• Authentication against an LDAP or DBI server
• RRDtool statistics
• Rule-based downloading with possibility of a script handling only authentication
• Server Side Includes support (but not server-side CGI from SSI)^[10]
• Flexible virtual hosting
• Modules support
• Lua programming language scripts via mod_magnet^[11]
• WebDAV support
• HTTP compression using mod_deflate (zlib, brotli, zstd)
• Light-weight (less than 1 MB)^[12]
• Single-process design with only several threads. No processes or threads started per connection.
• HTTP/2 support since lighttpd 1.4.56
• HTTP/2 WebSocket support since lighttpd 1.4.65
• TLS Encrypted Client Hello (ECH) support since lighttpd 1.4.77^[13]

Limitations

• Versions below 1.4.40 do not officially support sending large files from CGI, FastCGI, or proxies^[14] unless X-Sendfile is used. This limitation has been removed in lighttpd 1.4.40.^[15]
• No HTTP/3 support

Usage

Lighttpd was used in the past by several high-traffic websites, including Bloglines, xkcd, Meebo, and YouTube.^{[16][better source needed]} The Wikimedia Foundation also once ran Lighttpd servers.^[17] Due to relatively small size it's often used in embedded devices like GL.iNet and Turris Omnia.

It's also used by git as a HTTP server daemon.

See also

• Free and open-source software portal

• Comparison of web server software
• Internet Cache Protocol
• Proxy server which discusses client-side proxies
• Reverse proxy which discusses origin-side proxies
• Traffic Server
• Web accelerator which discusses host-based HTTP acceleration