Bozohttpd is a small and secure http version 1.1 server. it's main feature
is the lack of features, reducing the code size and improving verifiability.
It supports CGI/1.1, HTTP/1.1, HTTP/1.0, HTTP/0.9, ~user translations,
virtual hosting support, as well as multiple IP-based servers on a single
machine. It is capable of services pages via the IPv6 protocol. It has no
configuration file by design. Recently added features are htpasswd, SSL,
and dynamic redirection, that can be easily disabled.
Starlet is a standalone HTTP/1.0 server.
The server supports several features, and is suitable for running HTTP
application servers behind a reverse proxy.
HTTP::Daemon::SSL - a simple http server class with SSL support.
Instances of the HTTP::Daemon::SSL class are HTTP/1.1 servers
that listen on a socket for incoming requests.
CGI::Application::Dispatch::Server
A simple HTTP server for developing apps that use CGI::Application::Dispatch
CGI::Application::Server
A simple HTTP server for developing with CGI::Application.
libmicrohttpd is a small C library for embedding HTTP server functionality
into other applications. It is reentrant, fast, supports HTTP 1.1, and
permits listening on multiple ports. The API is simple and still powerful
enough to allow programmers to use the entire HTTP feature set.
This is a simple http server for purely static content. You can
use it to serve the content of a ftp server via http for example.
It is also nice to export some files quickly by starting an http
server in a few seconds without editing a config file first.
Features/Design:
================
* single process: select() + non-blocking I/O
* automatically generates directory listings when asked for a
directory (check for index.html available as option), caches
the listings.
* no config file, just a few switches. Try "webfsd -h" for a
list.
* Uses ${PREFIX}/etc/webfsd/mime.types to map file extentions
to mime/types (not included).
* supports keep-alive and pipelined requests.
* serves byte ranges.
* optional logging in common log file format.
This is a pure-Tcl implementation of an HTTP protocol server. It runs as
a script on top of a vanilla Tcl interpreter using tcllib scripts and,
optionally, two binary libraries (crypt and limit).
The Tcl I/O system provides event-driven I/O facilities and a primitive
that copies data from one I/O channel to another. The server does the
HTTP protocol handling and then simply directs the I/O system to blast
data from disk to a network socket. The server has suprisingly good
performance because of Tcl's sophisticated I/O system.
The HTTP protocol is perhaps the least interesting aspect of the server.
The cool stuff is the framework for generating dynamic page content, and
the support for embedding the server directly into legacy applications
to "web-enable" them.
A Tcl-based web server is ideal for embedding because Tcl was designed
to support embedding into other applications. The interpreted nature of
Tcl allows dynamic reconfiguration of the server. Once the core
interface between the web server and the hosting application is defined,
it is possible to manage the web server, upload Safe-Tcl control
scripts, download logging information, and otherwise debug the Tcl part
of the application without restarting the hosting application.
Unicorn is an HTTP server for Rack applications designed to only serve fast
clients on low-latency, high-bandwidth connections and take advantage of
features in Unix/Unix-like kernels. Slow clients should only be served by
placing a reverse proxy capable of fully buffering both the request and
response in between Unicorn and slow clients.
Server Spy indicates what brand of HTTP server (e.g. Apache, IIS, etc.)
runs on the visited sites.