From 71da11ab4d56ce5028cdf6df0df9b4849ccbfc82 Mon Sep 17 00:00:00 2001
From: Joshua Slive .htaccess
files
to change the scope of other configuration directives.
Related Modulescore mod_proxy | Related Directives<Directory> <DirectoryMatch> <Files> <FilesMatch> <IfDefine> <IfModule> <Location> <LocationMatch> <Proxy> <VirtualHost> |
Related Modulescore mod_proxy | Related Directives<Directory> <DirectoryMatch> <Files> <FilesMatch> <IfDefine> <IfModule> <Location> <LocationMatch> <Proxy> <ProxyMatch> <VirtualHost> |
There are two basic types of containers. Most containers are
evaluated for each request. The enclosed directives are applied only
@@ -165,13 +165,17 @@ SetHandler server-status
The <Directory>
,
<Files>
, and
<Location>
-directives can each use the shell-style wildcard characters "?" to
-match any single character, "*" to match any set of characters, and
-character classes like [a-zA-Z] to match particular characters. This
-is useful to apply the same configuration to a group of filesystem or
-webspace locations. If even more flexible matching is required, each
+directives can each use shell-style wildcard characters as in
+fnmatch
from the C standard library. The character "*"
+matches any sequence of characters, "?" matches any single character,
+and "[seq]" matches any character in seq. The "/"
+character will not be matched by any wildcard; it must be specified
+explictly.
If even more flexible matching is required, each
container has a regular-expression (regex) counterpart <DirectoryMatch>
, <FilesMatch>
, and <LocationMatch>
that allow
-perl-compatibleregular expressions
+perl-compatible
+regular expressions
to be used in choosing the matches. But see the section below on
configuration merging to find out how using regex sections will change
how directives are applied.
The <Proxy>
-container applies enclosed configuration directives only
+
The <Proxy>
+and <ProxyMatch>
+containers apply enclosed configuration directives only
to sites accessed through mod_proxy
's proxy server
that match the specified URL. For example, the following configuration
will prevent the proxy server from being used to access the
@@ -274,8 +279,8 @@ sections is also syntactically allowed in
<FilesMatch>
,
<Location>
,
<LocationMatch>
,
-and
-<Proxy>
+<Proxy>
,
+and <ProxyMatch>
sections. There are some exceptions, however.