DOCUMENTATION
URI | External Redirect | Status Code | Destination URI | Header Operations | Realm | Authentication Name | Require (Authorized Users/Groups) | Access Allowed | Access Denied
A Redirect 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 (internal redirect) or an absolute URI pointing to another web site (external redirect).
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 whether this redirect is external. For external redirection, Status Code may be specified and Destination URI can start either with "/" or "http(s)://". For internal redirection, Destination URI must start with "/".
Specifies the response status code of the external redirection. If the status code is between 300 and 399, Destination URI can be specified.
Select from drop down list
Specifies the target location of the redirect. If this redirected URI maps to a URI in another redirect context, it will be redirected again.
This URI can either be a relative URI on the same web site starting with "/", or an absolute URI pointing to different web site starting with "http(s)://". If the URI contains regular expressions, the destination can reference the matched variables, such as $1 or $2.
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.
