<p>The <var>match</var> argument specifies a match that will be applied to
the filter's <var>dispatch</var> criterion. The <var>match</var> may be
- a string match (exact match or substring), a <glossary>regex</glossary>,
- an integer (greater,
+ a string match (exact match or substring), a <glossary ref="regex"
+ >regex</glossary>, an integer (greater,
lessthan or equals), or unconditional. The first characters of the
<var>match</var> argument determines this:</p>
<p>The <directive type="section" module="core">Directory</directive>
and <directive type="section" module="core">Files</directive>
-directives, along with their <glossary>regex</glossary> counterparts, apply directives to
+directives, along with their <glossary ref="regex">regex</glossary>
+counterparts, apply directives to
parts of the filesystem. Directives enclosed in a <directive
type="section" module="core">Directory</directive> section apply to
the named filesystem directory and all subdirectories of that
<section id="webspace"><title>Webspace Containers</title>
<p>The <directive type="section" module="core">Location</directive>
-directive and its <glossary>regex</glossary> counterpart, on the other hand, change the
+directive and its <glossary ref="regex">regex</glossary> counterpart, on the
+other hand, change the
configuration for content in the webspace. For example, the following
configuration prevents access to any URL-path that begins in /private.
In particular, it will apply to requests for
will be served from <code>/var/web/dir/file.html</code>. The
<directive module="mod_alias">ScriptAlias</directive> directive
works the same way, with the additional effect that all content
- located at the target path is treated as <glossary>CGI</glossary> scripts.</p>
+ located at the target path is treated as <glossary ref="cgi"
+ >CGI</glossary> scripts.</p>
<p>For situations where you require additional flexibility, you
can use the <directive module="mod_alias">AliasMatch</directive>
projects / thirdparty / apache / httpd.git / commitdiff
