URL Directives
The following directives apply to the URL container context.
<url>
Description | Enclose a group of directives that apply only if the URL matches the given pattern |
Syntax | <url url-pattern> ... </Url> |
Context | global |
<url> and </url> are used to enclose a group of directives that will apply only to URLs that match the pattern. Any directive that is allowed in a Url context may be used. url-pattern is a POSIX 1003.2 compliant extended regular expression that is matched against the url.
If multiple <url> sections match the url (or one of its parents) then the directives are applied in the order of shortest match first. Therefore the longest matches will overwrite the shorter ones.
authorizer
Description | Specifies which authorization module should be used for a request |
Syntax | authorizer module-name |
Context | url |
authorizer specifies which authorization module should be used for requests that match the parent URL. module-name is the name of the module to use. Authorization modules are applied before the Allow/Deny rules as they control access to the web server as a whole. Allow/Deny just apply to serving static content from within the Content_root.
state
Description | Specifies which state module should be used for a request |
Syntax | state module-name |
Context | url |
state specifies which state module should be used for requests that match the parent URL. module-name is the name of the module to use.
redirect
Description | Specifies a URL redirect |
Syntax | redirect url |
Context | url |
Sets up an http redirect from url-pattern to url. Note that url-pattern must be a literal url and not a regular expression. Url redirection occurs before all other processes, including authorization so any url based processes must match against the redirected url, not the original one.
apply_uac
Description | Whether or not UAC is applied to the url |
Syntax | apply_uac on|off |
Context | url |
By default all urls are subject to User Access Control (UAC). Some urls however (EG: static web content) may require access without having a session allocated. These urls can be configured with apply_uac off to exclude them from the UAC process.
upload_target
Description | Marks the URL as an endpoint for content uploading |
Syntax | upload_target path |
Context | url |
Specifying upload_target on a URL enables content upload by posting multitype/form-data to url-pattern. The files within the post are written to the path directory within content root. Note that url-pattern must be a literal url and not a regular expression. See Content Upload for more details.