Users' Manual
Version 1.9 — Rev. 3

# Context

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 set up user-level authentication for certain resources.
- To create mount points for external applications.
- To redirect requests to another location.

### Context Type

#### Description

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.
LiteSpeed SAPI context can be used to associate a URI with an LSAPI application.
Proxy context enables this virtual host to serve as a transparent reverse proxy server to an external web server or application server.
Fast CGI context is a mount point of Fast CGI application.
SCGI context can be used to associate a URI with an SCGI application.
CGI context can be used to specify a directory only contains CGI scripts.
Redirect context can set up an internal or external redirect URI.
Load Balancer context can be used to assign a different cluster for that context.
Java Web App context is used to automatically import a predefined Java Application in an AJPv13 compliant Java servlet engine.
Servlet context is used to import a specific servlet under a web application.
App Server context is specifically used for Rack/Rails, WSGI, and Node.js applications.
uWSGI context can be used to associate a URI with a uWSGI application.
Module handler context is a mount point of handler type modules.