</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
+ written to the environment with the corresponding name prefixed with
+ "MATCH_" and 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 ^/var/www/combined/(?<sitename>[^/]+)>
+ require ldap-group cn=%{env:MATCH_SITENAME},ou=combined,o=Example
</DirectoryMatch>
</highlight>
</usage>
<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
+ written to the environment with the corresponding name prefixed with
+ "MATCH_" and 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 ^(?<sitename>[^/]+)>
+ require ldap-group cn=%{env:MATCH_SITENAME},ou=combined,o=Example
</FileMatch>
</highlight>
</usage>
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
+ written to the environment with the corresponding name prefixed with
+ "MATCH_" and 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 ^/combined/(?<sitename>[^/]+)>
+ require ldap-group cn=%{env:MATCH_SITENAME},ou=combined,o=Example
</LocationMatch>
</highlight>
</usage>
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
+ written to the environment with the corresponding name prefixed with
+ "MATCH_" and 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 ^http://(?<sitename>[^/]+)>
+ require ldap-group cn=%{env:MATCH_SITENAME},ou=combined,o=Example
</ProxyMatch>
</highlight>
</usage>
#define AP_REG_NOMEM 0x20 /* nomem in our code */
#define AP_REG_DOTALL 0x40 /* perl's /s flag */
+#define AP_REG_MATCH "MATCH_" /** suggested prefix for ap_regname */
+
/* Error values: */
enum {
AP_REG_ASSERT = 1, /** internal error ? */
* @param upper If non zero, uppercase the names
*/
AP_DECLARE(int) ap_regname(const ap_regex_t *preg,
- apr_array_header_t *names, int upper);
+ apr_array_header_t *names, const char *prefix,
+ int upper);
/** Destroy a pre-compiled regex.
* @param preg The pre-compiled regex to free.
if (r) {
conf->refs = apr_array_make(cmd->pool, 8, sizeof(char *));
- ap_regname(r, conf->refs, 1);
+ ap_regname(r, conf->refs, AP_REG_MATCH, 1);
}
ap_add_per_proxy_conf(cmd->server, new_dir_conf);
if (r) {
conf->refs = apr_array_make(cmd->pool, 8, sizeof(char *));
- ap_regname(r, conf->refs, 1);
+ ap_regname(r, conf->refs, AP_REG_MATCH, 1);
}
/* Make this explicit - the "/" root has 0 elements, that is, we
if (r) {
conf->refs = apr_array_make(cmd->pool, 8, sizeof(char *));
- ap_regname(r, conf->refs, 1);
+ ap_regname(r, conf->refs, AP_REG_MATCH, 1);
}
ap_add_per_url_conf(cmd->server, new_url_conf);
if (r) {
conf->refs = apr_array_make(cmd->pool, 8, sizeof(char *));
- ap_regname(r, conf->refs, 1);
+ ap_regname(r, conf->refs, AP_REG_MATCH, 1);
}
ap_add_file_conf(cmd->pool, (core_dir_config *)mconfig, new_file_conf);
}
AP_DECLARE(int) ap_regname(const ap_regex_t *preg,
- apr_array_header_t *names, int upper)
+ apr_array_header_t *names, const char *prefix,
+ int upper)
{
int namecount;
int nameentrysize;
while (names->nelts <= capture) {
apr_array_push(names);
}
- if (upper) {
- char *name = ((char **)names->elts)[capture] =
- apr_pstrdup(names->pool, offset + 2);
- ap_str_toupper(name);
+ if (upper || prefix) {
+ char *name = ((char **) names->elts)[capture] =
+ prefix ? apr_pstrcat(names->pool, prefix, offset + 2,
+ NULL) :
+ apr_pstrdup(names->pool, offset + 2);
+ if (upper) {
+ ap_str_toupper(name);
+ }
}
else {
((const char **)names->elts)[capture] = offset + 2;