class implements the HTTP protocol in version 1.0 as specified in
It dispatches HTTP requests to responders which answer them.
Responders are mounted in areas which form a partition of the
Frontends are special Responders which operate on file-like
resources (so-called NFiles) provided by a
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:
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.
is a gateway to use
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
The specification requires that Servlets are not shared
by multiple virtual hosts. This is not enforced by NetForge.
If you're using name-based virtual hosts, you should
therefore define Servlet areas only within the
virtual hosts (which are separated by a
for compliance with the specification.
A Servlet(Context)'s directory is available as an NFile or
absolute path in the local file system (where available) through
the ServletContext attributes
This is a non-standard extension to the Servlet Specification.
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
Displays all information about an HTTP request. It is useful for debugging.
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
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.
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.
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.
is configured similar to a ProxyResponder but
it redirects a client to a different location instead of making the
is a Metaconf client for configuring NetForge via HTTP forms. See
Administration Tools for details.