Caution: In this restricted "Fossies" environment the current HTML page may not be correctly presentated and may have some non-functional links.
You can here alternatively try to browse the pure source code or just view or download the uninterpreted raw source code. If the rendering is insufficient you may try to find and view the page on the openlitespeed-1.6.6.src.tgz project site itself.
In LiteSpeed Web Server terminology, a "context" is a virtual location, a common parent URL,
that identifies a group of resources. Contexts can be thought of as different directories
in your website's directory tree. For example, "/" is the root context mapped to the
document root of a website. "/cgi-bin/" is a context farther up on the tree, dedicated
to the CGI applications for this site. A context can be explicitly defined in
LiteSpeed's WebAdmin console for the following purposes:
To make a file system outside of the document root accessible.
To block access to certain resources.
To setup user-level authentication for certain resources.
The type of context created determines it's usage.
Static context can be used to map a URI to a directory either outside document root or within it. Java Web App context is used to automatically import a predefined Java Application in an AJPv13 compilant Java servlet engine. Servlet context is used to import a specific servlet under a web application. Fast CGI context is a mount point of Fast CGI application. LiteSpeed SAPI context can be used to associate a URI with an LSAPI application. Proxy context enables this virtual host to serve as a transparant reverse proxy server to an external web server or application server. CGI context can be used to specify a directory only contains CGI scripts. Load Balancer context can be used to assign a different cluster for that context. Redirect context can set up an internal or external redirect URI. App Server context is specifically used for Rack/Rails, WSGI, and Node.js applications. Module handler context is a mount point of hander type modules.