From c4f22e750236f4de5e230bdb17ee52cd3ee5f36b Mon Sep 17 00:00:00 2001 From: dgaudet Date: Wed, 18 Feb 1998 10:01:01 +0000 Subject: [PATCH] Fix various parsing bugs with sections. Improve the error messages generated. Introduced cmd->end_token to make it easier to do nested sections with proper error reporting. (Note that it can't be used for or unfortunately.) PR#379: is not allowed within because it has no effect. PR#1817: Change to work with basenames only. This fixes both the bug introduced by the wildcarding change (* doesn't match /) and bugs such as not working. PR: 379, 1817 git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@80233 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/mod/core.html | 17 ++++++++++------- 1 file changed, 10 insertions(+), 7 deletions(-) diff --git a/docs/manual/mod/core.html b/docs/manual/mod/core.html index 65598c9299..f91ba78015 100644 --- a/docs/manual/mod/core.html +++ b/docs/manual/mod/core.html @@ -811,12 +811,17 @@ than the user that starts the server. filename. It is comparable to the <Directory> directive and <Location> directives. It -should be matched with a </Files> directive. Directives that -apply to the filename given should be listed -within. <Files> sections are processed in the +should be matched with a </Files> directive. The +directives given within this section will be applied to any +object with a basename (last component of filename) matching +the specified filename. +<Files> sections are processed in the order they appear in the configuration file, after the <Directory> sections and .htaccess files are -read, but before <Location> sections.

+read, but before <Location> sections. Note that +<Files> can be nested inside <Directory> +sections to restrict the portion of the filesystem they +apply to.

The filename argument should include a filename, or a wild-card string, where `?' matches any single character, and `*' matches any @@ -837,9 +842,7 @@ HREF="#directory"><Directory> and <Location> sections, <Files> sections can be used inside .htaccess files. This allows users to control access to their own files, at a -file-by-file level. When used in an .htaccess file, if the -filename does not begin with a / character, -the directory being applied will be prefixed automatically. +file-by-file level.

-- 2.50.1