Add back in logic to put the ending container directive in the tree. This

needs to be there until we have a validating tree.  Without this, it is
possible for a config file to read:

<Ifmodule mod_foo.c>
    some directive
</Limit>

and still be read correctly.  When the tree building functions can validate
for us, this should be removed, and there is a comment that says so.

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@84979 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/server/config.c b/server/config.c
index 8da31354174cce5bacd1bf14460a86d4b7a9f640..03f68dda8e53066f6e9d5eced88a8e6304662bae 100644 (file)
--- a/server/config.c
+++ b/server/config.c
@@ -864,6 +864,13 @@ CORE_EXPORT(const char *) ap_handle_command(cmd_parms *parms, void *config, cons
             current = ap_add_node(&curr_parent, current, newdir, 1);
         }
         else {
+            /* The next line needs to be removed once we have a validating
+             * tree building routine.
+             * It is left in for now, so that we can ensure that
+             * a container directive is followed by an appropriate closing
+             * directive.
+             */
+            current = ap_add_node(&curr_parent, current, newdir, 0);
             current = curr_parent;
             curr_parent = current->parent;
         }