not end in a trailing slash, so expressions that are anchored to the
end of line ($) must be written with care.
</note>
+
+ <p>From 2.5.0 onwards, named groups and backreferences are captured and
+ written to the environment with the corresponding name in upper case.
+ This allows elements of paths to be referenced from within
+ <a href="expr.html">expressions</a> and modules like
+ <module>mod_rewrite</module>. In order to prevent confusion, numbered
+ (unnamed) backreferences are ignored. Use named groups instead.</p>
+
+<highlight language="config">
+<DirectoryMatch ^/var/www/combined/(?<SITENAME>[^/]+)>
+ require ldap-group cn=%{env:SITENAME},ou=combined,o=Example
+</DirectoryMatch>
+</highlight>
</usage>
<seealso><directive type="section" module="core">Directory</directive> for
a description of how regular expressions are mixed in with normal
</highlight>
<p>would match most common Internet graphics formats.</p>
+
+ <p>From 2.5.0 onwards, named groups and backreferences are captured and
+ written to the environment with the corresponding name in upper case.
+ This allows elements of files to be referenced from within
+ <a href="expr.html">expressions</a> and modules like
+ <module>mod_rewrite</module>. In order to prevent confusion, numbered
+ (unnamed) backreferences are ignored. Use named groups instead.</p>
+
+<highlight language="config">
+<FileMatch ^(?<SITENAME>[^/]+)>
+ require ldap-group cn=%{env:SITENAME},ou=combined,o=Example
+</FileMatch>
+</highlight>
</usage>
<seealso><a href="../sections.html">How <Directory>, <Location>
<p>would match URLs that contained the substring <code>/extra/data</code>
or <code>/special/data</code>.</p>
+
+ <p>From 2.5.0 onwards, named groups and backreferences are captured and
+ written to the environment with the corresponding name in upper case.
+ This allows elements of URLs to be referenced from within
+ <a href="expr.html">expressions</a> and modules like
+ <module>mod_rewrite</module>. In order to prevent confusion, numbered
+ (unnamed) backreferences are ignored. Use named groups instead.</p>
+
+<highlight language="config">
+<LocationMatch ^/combined/(?<SITENAME>[^/]+)>
+ require ldap-group cn=%{env:SITENAME},ou=combined,o=Example
+</LocationMatch>
+</highlight>
</usage>
<seealso><a href="../sections.html">How <Directory>, <Location>
identical to the <directive module="mod_proxy"
type="section">Proxy</directive> directive, except it matches URLs
using <glossary ref="regex">regular expressions</glossary>.</p>
+
+ <p>From 2.5.0 onwards, named groups and backreferences are captured and
+ written to the environment with the corresponding name in upper case.
+ This allows elements of URLs to be referenced from within
+ <a href="expr.html">expressions</a> and modules like
+ <module>mod_rewrite</module>. In order to prevent confusion, numbered
+ (unnamed) backreferences are ignored. Use named groups instead.</p>
+
+<highlight language="config">
+<ProxyMatch ^http://(?<SITENAME>[^/]+)>
+ require ldap-group cn=%{env:SITENAME},ou=combined,o=Example
+</ProxyMatch>
+</highlight>
</usage>
<seealso><directive type="section" module="mod_proxy">Proxy</directive></seealso>
</directivesynopsis>
</FilesMatch>
</highlight>
+<p>Regular expressions containing <strong>named groups and
+backreferences</strong> are added to the environment with the
+corresponding name in uppercase. This allows elements of filename paths
+and URLs to be referenced from within <a href="expr.html">expressions</a>
+and modules like <module>mod_rewrite</module>.</p>
+
+<highlight language="config">
+<DirectoryMatch ^/var/www/combined/(?<SITENAME>[^/]+)>
+ require ldap-group cn=%{env:SITENAME},ou=combined,o=Example
+</DirectoryMatch>
+</highlight>
+
</section>
<section id="expressions"><title>Boolean expressions</title>