Free http servers software for linux

httptype is a program that returns the http host software of a website. It is written in Perl.
httptype reads a list of http hosts and optionally the port number for each of these. It queries each host, displaying the type of HTTP server running on that host. It reads the http_proxy and no_proxy environment variables to determine whether to use a proxy or not.
httptype reads a list of http servers and, optionally, the port number for each of these. It then queries each of the hosts and displays the HTTP server software of the host.
Input may be read from a host file if specified using the --hosts switch:
httptype --hosts [hostfile]
If hostfile is omitted or `-, httptype reads from standard input. See Format of host file for more info.
A single host may be queried by passing its name on the command line:
httptype host [port]
If port is omitted, 80 is used.
If no host file is specified through the --hosts file and no host is specified on the command line, httptype will read the list from standard input. See Format of host file for more info.
httptype will read the http_proxy environment variable and try to determine if a proxy server is being used. This setting may be overridden using the --proxy switch:
httptype --proxy proxyhost[:proxyport]
If proxyport is omitted, 80 is used.
If the proxy server is `none, no proxy is used. This is typically used to prevent httptype from using the proxy server specified by http_proxy. The --noproxy switch can be used to achieve the same.
Additionally, you may use the no_proxy environment variable to specify a comma delimited list of hosts for which httptype should not use the proxy. If httptype comes across any of these hosts, it will make a direct connection to them.
Enhancements:
- made 1.3.8 stable and renamed to 1.2.3

Dwarf HTTP Server is a full-featured and ready-to-use web server with the Java Servlet API 2.2 and Java Server Pages 1.1 implementation.
Dwarf HTTP Server can be used either standalone or embed in a larger hosting application, free of charge for the binary redistribution
Since the server is based on the Dwarf framework, it shares its common design principles and features - simplicity, high modularity and extensibility, authentication and authorization, XML-based configuration, logging and remote management.
Main features:
- multi-threaded design
- dynamically adjusted number of active threads
- Java Servlet API 2.2 implementation
- Java Server Pages 1.1 (by Apache Tomcat/Jasper)
- HTTP/1.1 and CGI/1.1 implementation
- WebDAV Class 1 implementation
- built-in SSL/TLS support
- IP-based and name-based virtual hosts
- customizable authentication and authorization
- standard and custom HTTP log formats
- extensible session management
- Basic and Form-based HTTP authentication
- automatic deploying of WAR archives
- runtime server configuration
- full documentation with guides and tutorials
- web application examples with source code

DeniX Server OS is an independent Linux based distribution built from scratch by Denis Salmanovich. They aim to offer a user-friendly full-featured server operating system, pre-configured, well structured and easy to work with, and filled with the latest stable versions of Linux apps.
Its easy to install and configure. Every package is downloaded from the authors source and compiled when installed.
Main features:
- Domain Controller
- ADSL/CABLE Router (PPPoE)
- Network Firewall
- Anti Virus Gateway
- Anti Spam Gateway
- Mail Server (local & external) + Web Mail
- Calendar Sharing Support
- Network File Server
- DHCP Server
- TFTP BOOT Server
- WINS Server
- FTP Server
- VPN Server
- DNS Server
- DDNS Server
- MySQL Server
- HTTP Apache Server
- Remote Backup Solutions
- Remote control and administration
- Print Queue Server
- Proxy Server

GN gopher server provides a fast gopher and HTTP server.

GN is a fast, light and (for 1995 standards) secure gopher server. An effort is underway to fix the known buffer overflows and bring GN up to par with todays standards.

To use these scripts with the sample sample setup as descibed in the installation guide you need to run mkcache in this (/docs/examples) directory or run mkcache -r in the /docs directory.

To use the image clicking capabilities involving "imagemap" you must get this program from NCSA and compile it. Instructions for setting it up are at

The compiled C program must be renamed imagemap.cgi (or at least something with a suffix .cgi)

HTTP::Server::Simple::Recorder is Perl module for mixin to record HTTP::Server::Simples sockets.

SYNOPSIS

package MyServer;
use base qw/HTTP::Server::Simple::Recorder HTTP::Server::Simple::CGI/;

sub recorder_prefix { "path/to/logs/record" } # defaults to /tmp/http-server-simple-recorder

# logs to path/to/logs/record.34244.1.in,
# path/to/logs/record.34244.1.out,
# path/to/logs/record.34244.2.in,
# path/to/logs/record.34244.2.out, etc, if 34244 is the PID of the server

This module allows you to record all HTTP communication between an HTTP::Server::Simple-derived server and its clients. It is a mixin, so it doesnt itself subclass HTTP::Server::Simple; you need to subclass from both HTTP::Server::Simple::Recorder and an actual HTTP::Server::Simple subclass, and HTTP::Server::Simple::Recorder should be listed first.

Every time a client connects to your server, this module will open a pair of files and log the communication between the file and server to these files. Each connection gets a serial number starting at 1. The filename used is >, then a period, then the connection serial number, then a period, then either "in" or "out". recorder_prefix defaults to /tmp/http-server-simple-recorder, but you can override that in your subclass. For example, you might want to include the process ID.

HttpdBase4J is an embeddable Java web server framework that supports HTTP, HTTPS, templated content and serving content from inside an archive.

The classes are easy to extend as they utilize the Hollywood dont call us, well call you principle to allow the user to overide the framework behaviour during all the different phases of the HTTP transaction.

Note:HttpdBase4J uses the Java 6 com.sun.net.httpserver classes so it wont currently work under earlier versions of Java.

Usage Examples:

The simplest use case is to create an embedded web server on port 8088 with its home directory at htdocs in the local filesystem and a root url at / ie / maps onto htdocs:

homeDir = new java.io.File("./htdocs");
httpd = new FileHttpd(homeDir, 10); // Creates a server with a threadpool of 10
httpd.setLogger(System.err); // Log to console
httpd.start(8088, "/");

Creating a HTTPS server equivalent the the HTTP server above requires passing a keystore and password to start. Passing null will generate a certificate free keystore if you only need the encryption capabilities of HTTPS and not the certificate capability:

httpd = new FileHttpd(homeDir, 10);
m_httpd.start(8089, "/", keystore, password);

Serving content from inside an archive or from a jar or zip in the Java classpath requires creating an ArchiveHttpd instance instead of a FileHttpd. To serve content located in a jar or zip in the class path you need only specify the resource directory in the classpath where the content islocated, for example:

httpd = new ArchiveHttpd("/resources/htdocs", 10);
httpd.start(8088, "/");

To serve content from within a specific archive specify the archive as a Java File when constructing the ArchiveHttpd:

httpd = new ArchiveHttpd(new File("content.zip"), "/resources/htdocs", 10);
httpd.start(8088, "/");

Creating web content using templates is also supported. Currently only the StringTemplate library (http://www.stringtemplate.org) is is supported but it should be relatively easy to create user derived classes for other template implementations. To create an HTTP embedded web server on serving templated content from resources/htdocs in the classpath and having a template file handler (A Java class implenting the Templatable interface that is used to fill the templates) in net.homeip.donaldm.test.templates.

httpd = new ArchiveHttpd("resources/htdocs", 10);

StringTemplateHandler stHandler = new ArchiveStringTemplateHandler(httpd,
"net.homeip.donaldm.test.templates");

httpd.addHandler(".st", stHandler); // .st extension = template files
httpd.start(m_port, "/");

The HTTP transaction handling can be customized at any point by overiding any of the methods in the HttpHandleable interface or by overiding onCreateRequestHandler in Httpd in order to provide your own request handler. A simple example of overiding HttpHandleable methods:

httpd = new TestOverideHttpd(m_homeDir, 10);
httpd.start(m_port, "/");

class TestOverideHttpd extends FileHttpd
{
public HttpResponse onServeHeaders(long id, HttpExchange ex, Request request)
{
//Create or amend content
}
public InputStream onServeBody(long id, HttpExchange ex, Request request)
{
//Return amended or created content
}
}

thttpd is a simple, small, portable, fast, and secure HTTP server:
Simple; It handles only the minimum necessary to implement HTTP/1.1. Well, maybe a little more than the minimum.
Small; See the comparison chart. It also has a very small run-time size, since it does not fork and is very careful about memory allocation.
Portable; It compiles cleanly on most any Unix-like OS, specifically including FreeBSD, SunOS 4, Solaris 2, BSD/OS, Linux, OSF.
Fast; In typical use its about as fast as the best full-featured servers (Apache, NCSA, Netscape). Under extreme load its much faster.
Secure; It goes to great lengths to protect the web server machine against attacks and breakins from other sites.
It also has one extremely useful feature (URL-traffic-based throttling) that no other server currently has. Plus, it supports IPv6 out of the box, no patching required.
Enhancements:
- Move fdwatch initialization before the chroot, so that /dev/poll can work.
- Multiple fdwatch cleanups and fixes (Adam Zell).