Cherokee (web server)

Cherokee (web server)
source
Name	Cherokee
Developer	GrupoW
Released	2001
Operating system	Unix-like, Windows (partial)
Genre	Web server
License	GNU GPL, proprietary modules

Cherokee (web server) is an open-source web server designed for high performance and ease of configuration. It targets use cases ranging from lightweight content delivery to dynamic application hosting and has been compared to Apache HTTP Server, Nginx, Lighttpd, Microsoft Internet Information Services, and Caddy (web server). The project originated in the early 2000s and has seen participation from contributors associated with GrupoW, Open Source Initiative, Debian, Ubuntu, Fedora Project, and other distributions.

History

Cherokee was created in 2001 by developers from GrupoW, influenced by work on Apache HTTP Server modules, efforts in lightweight software by authors linked to Lighttpd, and scalability research associated with Nginx and Event-driven programming. Early releases targeted Linux kernel platforms and were packaged for Debian and Gentoo Linux; subsequent adoption included FreeBSD, NetBSD, and OpenBSD ports. Over time the project incorporated ideas from FastCGI efforts, lessons from CGI work on Perl, Python, and PHP, and operational practices from Sysadmin communities active around Slashdot and Stack Overflow.

Architecture and Features

Cherokee implements a multithreaded and event-driven architecture inspired by designs in Nginx and Lighttpd, using asynchronous I/O models found in epoll implementations on Linux kernel and kqueue on FreeBSD. Feature-wise it provides virtual hosts, URL rewriting, reverse proxying, TLS termination comparable to OpenSSL deployments, and support for application backends via FastCGI, SCGI, and WSGI interfaces used by Python frameworks like Django and Flask. The server includes static file serving optimized with sendfile semantics present in Linux kernel and FreeBSD to reduce context switches, and native gzip compression similar to modules in Apache HTTP Server and Nginx. Its modular design allows optional components for authentication interoperable with LDAP, Kerberos, and OAuth ecosystems, and integration points for content management systems such as WordPress, Drupal, and Joomla! when paired with PHP runtimes.

Configuration and Administration

Cherokee emphasizes ease of administration through a graphical management interface influenced by workflows used in cPanel, Plesk, and Webmin, alongside a human-readable configuration format akin to styles in Nginx and HAProxy. Administrators can define virtual hosts, rewrite rules, access controls, and backend pools via the web-based UI or plain-text files managed by tools from systemd, upstart, and OpenRC service managers. Logging is compatible with analysis tools like logrotate, Splunk, and ELK Stack components such as Elasticsearch, Logstash, and Kibana for observability in production deployments common in Amazon Web Services, Google Cloud Platform, and Microsoft Azure environments.

Performance and Security

Performance characteristics draw on non-blocking I/O patterns championed by Nginx and tuning strategies from Linux kernel network stack research, allowing high concurrency for static and proxied content similar to benchmarks seen with Lighttpd and Apache HTTP Server under certain workloads. Security features include TLS support leveraging OpenSSL and alternative stacks used by LibreSSL, configuration options for HTTP/2 comparable to IETF recommendations, and access controls integrating with PAM and SELinux mechanisms present in distributions like Red Hat Enterprise Linux and CentOS. Operational security practices for Cherokee deployments echo guidance from OWASP and incident response patterns observed in CERT/CC advisories.

Platforms and Packaging

Cherokee is portable across Unix-like systems with ports and packages maintained for Debian, Ubuntu, Fedora Project, CentOS, Arch Linux, Gentoo, FreeBSD, OpenBSD, and NetBSD. Binary builds and source tarballs have been distributed historically through project archives and mirrored by community package maintainers who coordinate with GNU Automake and CMake build systems; Windows support has been limited compared to native IIS options and relies on compatibility layers similar to Cygwin or ports for MinGW toolchains.

Reception and Usage

The server received attention from sysadmin and developer communities represented on Stack Overflow, Server Fault, and Slashdot threads for its user-friendly administration UI and lightweight footprint relative to Apache HTTP Server in small-to-medium deployments. Adoption included use in academic settings linked to University of Cambridge, Massachusetts Institute of Technology, and research labs that favored compact servers for static content delivery, as well as by hosting providers and small enterprises that compared it against Nginx and Lighttpd in benchmark discussions on Phoronix and LWN.net.

Development and Community

Development has been coordinated by contributors associated with GrupoW and volunteers from distributions such as Debian and Gentoo, with discussion occurring on mailing lists, issue trackers, and community platforms like GitHub and SourceForge in earlier phases. Community interaction reflects collaboration patterns found in other open-source projects such as FreeBSD ports and OpenSSL maintenance, and contributors often cross-participate in events like FOSDEM, LinuxCon, and DebConf.

Category:Web servers