Load Balancer Context⇑
Description
A Load Balancer Context can be used to forward one URI or a group of URIs to another location. The destination URI can be either on the same web site or an absolute URI pointing to another web site.
DOCUMENTATION
URI | Cluster | Header Operations | Realm | Authentication Name | Require (Authorized Users/Groups) | Access Allowed | Access Denied | Max Object Size | Cache Stale Age (seconds) | Publicly Cache All | Cache Expire Time (seconds) | Privately Cache All | Private Cache Expire Time (seconds) | Micro Cache 5XX Response | Enable POST cache | Enable Rewrite | Rewrite Inherit | Rewrite Base | Rewrite Rules | Add Default Charset | Customized Default Charset | Enable GeoLocation Lookup | Enable PageSpeed Optimization | PageSpeed Settings
A Load Balancer Context can be used to forward one URI or a group of URIs to another location. The destination URI can be either on the same web site or an absolute URI pointing to another web site.
Specifies the URI for this context.
The URI can be a plain URI (starting with "/") or a Perl compatible regular expression URI (starting with "exp:"). If a plain URI ends with a "/", then this context will include all sub-URIs under this URI. If the context maps to a directory on the file system, a trailing "/" must be added.
Specifies the cluster that handles requests to this context.
Select from drop down list
Specifies additional response/request headers to be added. Multiple header directives can be added with one directive per line. "NONE" can be used to disable parent header inheritance. If no directive is provided 'Header' is assumed.
[Header]|RequestHeader [condition] set|append|merge|add|unset header [value] [early|env=[!]variable]
Syntax and usage are similar to Apache's mod_headers directives for supported operations.
The 'Header' directive is is optional and can be excluded or left in when copying rules from elsewhere without issue.
Specifies the authorization realm for this context. When specified, a valid username and password must be provided in order to access this context. Authorization Realms are set up in the Virtual Host Security section. This setting uses each realm's Realm Name.
Select from drop down list
Specifies an alternative name for the authorization realm for the current context. If not specified, the original realm name will be used. The authentication name is displayed on the browser's login pop-up.
Specifies which user/group can access this context. This allows you to use one user/group database (specified in Realm) across a number of contexts, but only allow certain users/groups from that database to access this context.
Syntax is compatible with Apache's Require directive. For example:
Specifies which IPs or sub-networks are allowed to access resources under this context. Together with Access Denied and server/virtual host level access control, accessibility is determined by the smallest scope that a client's IP address falls into.
Comma-delimited list of IPs/sub-networks.
Specifies which IPs or sub-networks are NOT allowed to access resources under this context. Together with Access Allowed and server/virtual host-level access control, accessibility is determined by the smallest scope that a client's IP address falls into.
Comma-delimited list of IPs/sub-networks.
Specifies the maximum size of an object, up to 100M, that can be stored in the cache directory.
Default value: 10M
Integer number
Specifies how long an object will continue to be served from cache after it has expired but before a new cached copy is available. The default is "10" seconds.
Integer number
Publicly cache all URLs served under the current context (virtual host, or context level).
Virtual hosts configured through Apache's httpd.conf can use the "CacheEnable" and "CacheDisable" directives at the server, virtual host, context, file, and location level or in .htaccess. "CacheEnable" and "CacheDisable" directives are compatible with Apache mod_cache directives. However, when used at the context, file, or location level, or in .htaccess, "CacheEnable" and "CacheDisable" will only be applied to directories below the current level. URL parameters will be ignored.
Select from radio box
Disabled by default. Do not enabled this setting if you are using any LSCache plugins.
Specifies how long an object will be cached. The default is "86400" seconds (one day).
Integer number
Privately cache all URLs served under the current context (virtual host, or context level).
A separate cached copy will be made per user based on their IP and set cookies.
Virtual hosts configured through Apache's httpd.conf can use the "CacheEnable private /url" and "CacheDisable private /url" directives at server, virtual host, directory, file, and location levels or in a .htaccess file. "CacheEnable private" and "CacheDisable private" are compatible with Apache's mod_cache directives and will be applied to all directories below the current level. However, when used at the directory, file, or location level, or in a .htaccess file, "CacheEnable private" and "CacheDisable private" will only be applied to directories below the current level. URL parameters will be ignored.
Select from radio box
Disabled by default. Do not enabled this setting if you are using any LSCache plugins.
Specifies how long an object will be cached in private cache. The default is "60" seconds.
Integer number
Cache pages responding with HTTP status code 5xx (500, 503, etc) for 10 seconds when the cache response header indicates that the page is cacheable.
Default values:
Server level: Yes
VH level: Inherit Server level setting
Context-level Inherit VH level setting
Select from radio box
Enabling this setting is useful for avoiding bad requests but can also act as some added DDoS protection.
Specifies if POST requests can be cached using the "x-litespeed-cache-control" header.
Default value: No
Select from radio box
Specifies whether to enable LiteSpeed's URL rewrite engine. This option can be customized at the virtual host or context level, and is inherited along the directory tree until it is explicitly overridden.
Select from radio box
Specifies whether to inherit rewrite rules from parent contexts. If rewrite is enabled and not inherited, rewrite base and rewrite rules defined in this context will be used.
Select from radio box
Specifies the base URL for rewrite rules.
URL
Specifies a list of rewrite rules at the virtual host level.
Do NOT add any document root level rewrite rules here. If you have any document root level rewrite rules from .htaccess, you should instead create a static context with uri "/" and add the rewrite rules there.
A rewrite rule is comprised of one RewriteRule directive and optionally preceded by multiple RewriteCond directives.
string
Specifies whether to add a character set tag to the "Content-Type" response header, when content type is either "text/html" or "text/plain" without any parameters. When set to Off, this function is disabled. When set to On, either the character set specified by Customized Default Charset or the default "iso-8859-1" will be added.
Select from radio box
Specifies a character set to be used when Add Default Charset is On. This is optional. The default value is iso-8859-1. This entry has no effect when Add Default Charset is Off.
Name of a character set.
Specifies whether to enable/disable IP Geolocation lookup. Can be set at server, virtual host, or context level. IP Geolocation is disabled by default when using value "Not Set".
Select from radio box
Choose whether or not to enable PageSpeed optimization.
Select from radio box
This can be set at the Server Level and overridden at the Virtual Host Level.
Set parameters using Google default filter sets.