From e6647e0dcbd8372919330b74a037a69d6cf6f0d0 Mon Sep 17 00:00:00 2001 From: Graham Leggett Date: Fri, 14 Apr 2023 14:03:03 +0000 Subject: Include header file for the explicit regex. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1909136 13f79535-47bb-0310-9956-ffa450edef68 --- include/http_config.h | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) (limited to 'include') diff --git a/include/http_config.h b/include/http_config.h index 39fe72aff8..8f150465a5 100644 --- a/include/http_config.h +++ b/include/http_config.h @@ -313,12 +313,9 @@ struct cmd_parms_struct { apr_pool_t *temp_pool; /** Server_rec being configured for */ server_rec *server; - /** If configuring for a directory, pathname of that directory. - * NOPE! That's what it meant previous to the existence of <Files>, - * <Location> and regex matching. Now the only usefulness that can be - * derived from this field is whether a command is being called in a - * server context (path == NULL) or being called in a dir context - * (path != NULL). */ + /** If configuring for a directory, pathname of that directory. If the + * pathname is a regex, regex will be non-NULL below. If path is NULL, + * the directive is being called from a server context. */ char *path; /** configuration command */ const command_rec *cmd; @@ -331,6 +328,9 @@ struct cmd_parms_struct { /** If the current directive is EXEC_ON_READ, this is the last (non-EXEC_ON_READ) enclosing directive */ ap_directive_t *parent; + + /** If the path is a regex, compiled regex will be not NULL. */ + ap_regex_t *regex; }; /** -- cgit v1.2.1