Software & Networking
Previous Page Contents Next Page
 NetForge 1.0 Manual:   The HTTP Server 

The HTTPServer class implements the HTTP protocol in version 1.0 as specified in RFC 1945. It dispatches HTTP requests to responders which answer them. Responders are mounted in areas which form a partition of the server's namespace.

Frontends are special Responders which operate on file-like resources (so-called NFiles) provided by a Backend. The following Frontends are available:

There are also other Responders which do not operate on file-like resources and are therefore not subclasses of Frontend:


A DirectFrontend can send files from a Backend through http connections. This is the traditional use for a Web Server. It also accepts PUT requests to upload files.


The ServletFrontend is a gateway to use Java(tm) Servlets with NetForge. An area is mapped to a Backend directory containing servlet classes. If a servlet class changes in the Backend's repository it is automatically reloaded into the server. All servlets are running in a configurable sandbox.

Compliance with version 2.1 of the Servlet API Specification:


The CgiFrontend class implements the Common Gateway Interface version 1.1, or short CGI/1.1 which is used to launch external programs from a Web Server to process a request.


A TestResponder Displays all information about an HTTP request. It is useful for debugging.


A CounterResponder manages a set of Web counters. A Web counter holds an integer value which is incremented by one every time it is requested. The response contains a string or an image representing the new value. By embedding the response of a CounterResponder as an image into an HTML page, you can provide to the viewer an estimation on how often the page has been requested.


A FormUploadResponder is a gateway which enables you to use RFC 1867-style form-based file upload with NetForge. A FormUploadResponder translates all file upload requests into PUT requests and forwards them to the responder which is responsible for the specified resource.


A HostMultiplexResponder splits an area into parts based on the host name that is transmitted in the "Host:" header of an HTTP request, thus creating non-IP-based virtual servers.


A ProxyResponder retrieves requested resources from a parent proxy or an origin server and sends them to the client. When connecting to a parent proxy you can use any protocol that the parent proxy can bridge to HTTP. Without a parent proxy you can only access HTTP URLs. It can be mounted at areas like "http:" or "ftp:" to be used as a "real" proxy server, or mounted at local areas like "/my/other/server" to map another server's resources into the local server's namespace.


A RedirectionResponder is configured similar to a ProxyResponder but it redirects a client to a different location instead of making the request directly.


A WebconfigResponder is a Metaconf client for configuring NetForge via HTTP forms. See Administration Tools for details.

Last modified Feb/17/1999 by Stefan Zeiger