<li><A HREF="#clearmodulelist">ClearModuleList</A>
<li><A HREF="#defaulttype">DefaultType</A>
<li><A HREF="#directory"><Directory></A>
+<li><A HREF="#directorymatch"><DirectoryMatch></A>
<li><A HREF="#documentroot">DocumentRoot</A>
<li><A HREF="#errordocument">ErrorDocument</A>
<li><A HREF="#errorlog">ErrorLog</A>
<li><A HREF="#files"><Files></A>
+<li><A HREF="#filesmatch"><FilesMatch></A>
<li><A HREF="#group">Group</A>
<li><A HREF="#hostnamelookups">HostNameLookups</A>
<li><A HREF="#identitycheck">IdentityCheck</A>
<li><A HREF="#listen">Listen</A>
<li><A HREF="#listenbacklog">ListenBacklog</A>
<li><A HREF="#location"><Location></A>
+<li><A HREF="#locationmatch"><LocationMatch></A>
<li><A HREF="#lockfile">LockFile</A>
<li><A HREF="#maxclients">MaxClients</A>
<li><A HREF="#maxkeepaliverequests">MaxKeepAliveRequests</a>
<Directory ~ "^/www/.*/[0-9]{3}">
</pre>
-would match directories in /www/ that consisted of three numbers.<p>
+would match directories in /www/ that consisted of three numbers. In
+Apache 1.3 and later, it is reccomended to use
+<a href="#directorymatch"><DirectoryMatch></a> instead.<p>
<p>If multiple directory sections match the directory (or its parents) containing
a document, then the directives are applied in the order of shortest match
nest, and cannot appear in a <A HREF="#limit"><Limit></A> section.
<p><hr>
+<h2><A name="directorymatch"><DirectoryMatch></A></h2>
+<strong>Syntax:</strong> <DirectoryMatch <em>regex</em>> ... </DirectoryMatch> <br>
+<strong>Context:</strong> server config, virtual host<br>
+<strong>Status:</strong> Core.<br>
+<strong>Compatibility:</strong> Available in Apache 1.3 and later
+
+<p><DirectoryMatch> and </DirectoryMatch> are used to enclose a group of
+directives which will apply only to the named directory and sub-directories
+of that directory, the same as <a
+href="#directory"><Directory></a>. However, it takes as an
+argument a regular expression. For example:</p>
+
+<pre>
+ <DirectoryMatch "^/www/.*/[0-9]{3}">
+</pre>
+
+<p>would match directories in /www/ that consisted of three numbers.</p>
+
+<hr>
+
<h2><A NAME="documentroot">DocumentRoot directive</A></h2>
<!--%plaintext <?INDEX {\tt DocumentRoot} directive> -->
<strong>Syntax:</strong> DocumentRoot <em>directory-filename</em><br>
<Files ~ "\.(gif|jpe?g|png)$">
</pre>
-would match most common Internet graphics formats.
+would match most common Internet graphics formats. In Apache 1.3 and
+later, <a href="#filesmatch"><FilesMatch></a> is perferred,
+however.
<p>Note that unlike <a
href="#directory"><code><Directory></code></a> and <a
<p> <hr>
+<h2><A name="filesmatch"><FilesMatch></A></h2>
+<strong>Syntax:</strong> <FilesMatch <em>regex</em>>
+... </Files><br>
+<strong>Context:</strong> server config, virtual host, htaccess<br>
+<strong>Status:</strong> core<br>
+<strong>Compatibility:</strong> only available in Apache
+1.3 and above.<p>
+
+<p>The <FilesMatch> directive provides for access control by
+filename, just as the <a href="#files"><Files></a> directive
+does. However, it accepts a regular expression. For example:</p>
+
+<pre>
+ <FilesMatch "\.(gif|jpe?g|png)$">
+</pre>
+
+<p>would match most common Internet graphics formats.</p>
+
+<hr>
+
<h2><A name="group">Group directive</A></h2>
<!--%plaintext <?INDEX {\tt Group} directive> -->
<strong>Syntax:</strong> Group <em>unix-group</em><br>
</pre>
<p>would match URLs that contained the substring "/extra/data" or
-"/special/data".</p>
+"/special/data". However, in Apache 1.3 and above, use of <a
+href="#locationmatch"><LocationMatch></a> is perferred.</p>
<p>The <code>Location</code> functionality is especially useful when
combined with the <code><a
</pre>
<hr>
+<h2><a name="locationmatch"><LocationMatch></a></h2>
+
+<strong>Syntax:</strong> <LocationMatch <em>regex</em>>
+... </LocationMatch><br>
+<strong>Context:</strong> server config, virtual host<br>
+<strong>Status:</strong> core<br>
+<strong>Compatibility:</strong> Location is only available in Apache
+1.3 and later.<p>
+
+<p>The <LocationMatch> directive provides for access control by
+URL, in an identical manner to <a
+href="#location"><Location></a>. However, it takes a regular
+expression as an argument instead of a simple string. For example:</p>
+
+<pre>
+ <LocationMatch "/(extra|special)/data">
+</pre>
+
+<p>would match URLs that contained the substring "/extra/data" or
+"/special/data".</p>
+
+<hr>
+
<H2><A NAME="lockfile">LockFile directive</A></H2>
<strong>Syntax:</strong> LockFile <em>filename</em><BR>
<strong>Default:</strong> <code>LockFile logs/accept.lock</code><BR>
<li><A HREF="mod_mime.html#addtype">AddType</A>
<li><A HREF="mod_log_agent.html#agentlog">AgentLog</A>
<li><A HREF="mod_alias.html#alias">Alias</A>
+<li><A HREF="mod_alias.html#aliasmatch">AliasMatch</A>
<li><A HREF="mod_access.html#allow">allow</A>
<li><A HREF="core.html#allowoverride">AllowOverride</A>
<li><A HREF="mod_auth_anon.html#anonymous">Anonymous</A>
<li><A HREF="core.html#defaulttype">DefaultType</A>
<li><A HREF="mod_access.html#deny">deny</A>
<li><A HREF="core.html#directory"><Directory></A>
+<li><A HREF="core.html#directorymatch"><DirectoryMatch></A>
<li><A HREF="mod_dir.html#directoryindex">DirectoryIndex</A>
<li><A HREF="core.html#documentroot">DocumentRoot</A>
<li><A HREF="core.html#errordocument">ErrorDocument</A>
<li><A HREF="mod_expires.html#expiresdefault">ExpiresDefault</A>
<li><A HREF="mod_dir.html#fancyindexing">FancyIndexing</A>
<li><A HREF="core.html#files"><Files></A>
+<li><A HREF="core.html#filesmatch"><FilesMatch></A>
<li><A HREF="mod_mime.html#forcetype">ForceType</A>
<li><A HREF="core.html#group">Group</A>
<li><A HREF="mod_headers.html#header">Header</A>
<li><A HREF="mod_dld.html#loadfile">LoadFile</A>
<li><A HREF="mod_dld.html#loadmodule">LoadModule</A>
<li><A HREF="core.html#location"><Location></A>
+<li><A HREF="core.html#locationmatch"><LocationMatch></A>
<li><A HREF="core.html#lockfile">LockFile</A>
<li><A HREF="mod_log_config.html#logformat">LogFormat</A>
<li><A HREF="core.html#maxclients">MaxClients</A>
<li><A HREF="mod_proxy.html#proxyrequests">ProxyRequests</A>
<li><A HREF="mod_dir.html#readmename">ReadmeName</A>
<li><A HREF="mod_alias.html#redirect">Redirect</A>
+<li><A HREF="mod_alias.html#redirectmatch">RedirectMatch</A>
<li><A HREF="mod_alias.html#redirectperm">RedirectPermanent</A>
<li><A HREF="mod_alias.html#redirecttemp">RedirectTemp</A>
<li><A HREF="mod_log_referer.html#refererignore">RefererIgnore</A>
<li><A HREF="core.html#scoreboardfile">ScoreBoardFile</A>
<li><A HREF="mod_actions.html#script">Script</A>
<li><A HREF="mod_alias.html#scriptalias">ScriptAlias</A>
+<li><A HREF="mod_alias.html#scriptaliasmatch">ScriptAliasMatch</A>
<li><A HREF="mod_cgi.html#scriptlog">ScriptLog</A>
<li><A HREF="mod_cgi.html#scriptlogbuffer">ScriptLogBuffer</A>
<li><A HREF="mod_cgi.html#scriptloglength">ScriptLogLength</A>
<H2>Directives</H2>
<UL>
<li><A HREF="#alias">Alias</A>
+<li><A HREF="#aliasmatch">AliasMatch</A>
<li><A HREF="#redirect">Redirect</A>
+<li><A HREF="#redirectmatch">RedirectMatch</A>
<li><A HREF="#redirecttemp">RedirectTemp</A>
<li><A HREF="#redirectperm">RedirectPermanent</A>
<li><A HREF="#scriptalias">ScriptAlias</A>
+<li><A HREF="#scriptaliasmatch">ScriptAliasMatch</A>
</UL>
<hr>
</p>
<hr>
+<h2><A name="aliasmatch">AliasMatch</A></h2>
+<P>
+<strong>Syntax:</strong> AliasMatch <em>regex directory-filename</em><br>
+<Strong>Context:</strong> server config, virtual host<br>
+<strong>Status:</strong> Base<br>
+<strong>Module:</strong> mod_alias<br>
+<strong>Compatibility:</strong> Available in Apache 1.3 and later
+</P>
+
+<p>This directive is equivilent to <a href="#alias">Alias</a>, but
+makes use of standard regular expressions, instead of simple prefix
+matching. The supplied regular expression is matched against the URL,
+and if it matches, the server will substitute any parenthesized
+matches into the given string and use it as a filename. For example,
+to activate the <code>/icons</code> directory, one might use:
+<pre>
+ AliasMatch ^/icons(.*) /usr/local/etc/httpd/icons$1
+</pre>
+</p>
+
+<hr>
+
<h2><A name="redirect">Redirect directive</A></h2>
<P>
<!--%plaintext <?INDEX {\tt Redirect} directive> -->
</P>
<HR>
+<h2><A name="redirectmatch">RedirectMatch</A></h2>
+<P>
+<strong>Syntax:</strong> RedirectMatch [<em>status</em> <em>regex url</em><br>
+<Strong>Context:</strong> server config, virtual host<br>
+<strong>Status:</strong> Base<br>
+<strong>Module:</strong> mod_alias<br>
+<strong>Compatibility:</strong> Available in Apache 1.3 and later
+</P>
+
+<p>This directive is equivilent to <a href="#alias">Redirect</a>, but
+makes use of standard regular expressions, instead of simple prefix
+matching. The supplied regular expression is matched against the URL,
+and if it matches, the server will substitute any parenthesized
+matches into the given string and use it as a filename. For example,
+to redirect all GIF files to like-named JPEG files on another server,
+one might use:
+<pre>
+ RedirectMatch (.*)\.gif$ http://www.anotherserver.com$1.jpg
+</pre>
+</p>
+
+<hr>
+
<h2><A name="redirecttemp">RedirectTemp directive</A></h2>
<P>
<!--%plaintext <?INDEX {\tt Redirect} directive> -->
run the script /web/cgi-bin/foo.
</P>
+<hr>
+
+<h2><A name="scriptaliasmatch">ScriptAliasMatch</A></h2>
+<P>
+<strong>Syntax:</strong> ScriptAliasMatch <em>regex directory-filename</em><br>
+<Strong>Context:</strong> server config, virtual host<br>
+<strong>Status:</strong> Base<br>
+<strong>Module:</strong> mod_alias<br>
+<strong>Compatibility:</strong> Available in Apache 1.3 and later
+</P>
+
+<p>This directive is equivilent to <a href="#scriptalias">ScriptAlias</a>, but
+makes use of standard regular expressions, instead of simple prefix
+matching. The supplied regular expression is matched against the URL,
+and if it matches, the server will substitute any parenthesized
+matches into the given string and use it as a filename. For example,
+to activate the standard <code>/cgi-bin</code>, one might use:
+<pre>
+ ScriptAlias ^/cgi-bin(.*) /usr/local/etc/httpd/cgi-bin$1
+</pre>
+</p>
+
<!--#include virtual="footer.html" -->
</BODY>
</HTML>
projects / thirdparty / apache / httpd.git / commitdiff
