httpd Alternatives

httpd

Project Goals

The efforts emphasize portability, standardization, correctness, proactive security and integrated cryptography.
* Lean: Provide a small and monolithic architecture that supports the main standards and most important features of the web. Extensibility will never be implemented with plugins or loadable modules.
* Clean: Write readable and clean code following strict coding style(9) guidelines. "All code is beautiful".
* Secure: Implement secure code with strict validity checking, bounded buffer operations, and privilege separation to mitigate the security risks of possible bugs. Use strong cryptography with sane but secure defaults.
* Fast: Provide a fast implementation with a modern, event-based asynchronous I/O model. In fact, relayd uses the now popular async I/O model since 2007. Besides that, never sacrifice security for performance and do not use threads.
* Configurable: Make the configuration easy and nice with sane defaults, minimalistic configuration files and good documentation in the manual pages.

httpd fetaures

* Static files: Serves static files and directories via optional auto-indexing.
* FastCGI: Supports asynchronous and direct FastCGI via UNIX socket or TCP/IP.
Secure: Non-optional security by running chroot'ed and with privilege separation by default.
* SSL/TLS: Support secure connections via TLS powered by LibreSSL.
* Virtual servers: Flexible configuration with support for name- and IP-based virtual servers on IPv4 and IPv6.
* Reconfiguration: Reload the running configuration without interruption.
* Logging: Supports per-server logging via local access and error files or via syslog.