Hiawatha is a secure and advanced Web server for Unix. It has been written with security as its main goal. It features advanced access control, prevention of SQL injection and cross-site scripting, banning of clients who try such exploits, the ability to run CGIs under any UID/GID you want, and many other features. These features make Hiawatha an interesting Web server for those who need more security than what the other available Web servers are offering. Hiawatha is also fast and easy to configure.
Loomes' Nested Set is a class that can be used to manage a tree of information stored in a database. It can perform several types of operations to manipulate a hierarchy of nodes that are stored in a database as table records. Currently, it can insert a root node, insert a node that is child of a given parent, delete a branch of nodes under a given node, delete a single node, rename a node, move nodes, check whether the root node exists, and retrieve the whole tree of nodes.
Tiny Bash Server (TBS) is a small HTTP server. It allows CGI style scripting with .htsh files, which may contain Bash code embedded within normal HTML. TBS uses netcat to bind itself to open port(s). Multiple instances of the server may be run (on different ports and with different docroots) using separate configuration files. TBS comes with all the basic features you expect of a Web server: serving HTML/CSS, handling POST/GET forms, etc. It also passes selected environment variables for use with CGI scripting in .htsh files. However, it is highly not recommended to run TBS on any sort of production system. This is because, as a server, TBS is relatively slow, potentially insecure, and has fewer features than full-fledged servers like Apache HTTPD. A potential use for TBS is to develop browser-based frontends to bash scripts for local usage.
gweb++ is an asynchronous event-driven Web server and reverse proxy. It is written in C++, but it doesn't make use of the STL or of any additional libraries. It supports the following event notification mechanisms: epoll (edge-triggered, Linux), kqueue (FreeBSD), port (Solaris), poll, and select. It has the following main features: HTTP/1.1, reverse proxy, FastCGI, configurable via an XML file, MIME types support, pipelining, virtual hosts, Keep-Alive, directory listing (with an optional footer file), handling of the If-Modified-Since header, HTTP ranges, logs, configurable access logs, and log rotation.
Alaya is a primitive chrooting Web server with basic WebDAV support. It can serve HTTPS and HTTP, and can authenticate using PAM, /etc/shadow, /etc/passwd, or using its own authentication files that allow for 'native' users that only have access to alaya content. It's intended to be a simple method of sharing content over WebDAV, and though it can be configured with a config file, it's easy to configure by command-line switches alone. Alaya always chroots to ensure that malicious users can't use '..' within a URL to access unintended documents, and that users can't accidentally leave documents in places outside of the chroot. It has a 'ChHome' mode that chroots users into their home directory and serves content from there. It supports .cgi scripts out of a trusted path (so not from within the chrooted WebDAV share) and read-only shared directories that are outside of the chroot (allowing access to shared content when in ChHome mode).
Jkaptive is a simple captive portal without RADIUS (and thus without total security, but at the same time without too much hassle). The reason behind this is because a lot of site administrators don't need tight security; their site is just a café that offers free Internet access on an unsecured WLAN access point connected to the Internet, and they need a ticketing system to make it cumbersome for average people to use this offering without actually buying a single coffee. Jkaptive itself just presents the login page and checks the token. The blocking of unticketed traffic is done through Linux' netfilter. As no proxy server is involved, jkaptive has no performance penalty, nor does it create problems with non-HTTP traffic. Once the token is accepted, jkaptive is out of the way of any network packets completely. For presenting the login page, jkaptive has a built-in Web server, so no additional Web server application is needed.