filename. It is comparable to the <A
HREF="#directory"><Directory></A> directive and
<A HREF="#location"><Location></A> directives. It
-should be matched with a </Files> directive. Directives that
-apply to the filename given should be listed
-within. <CODE><Files></CODE> 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.
+<CODE><Files></CODE> sections are processed in the
order they appear in the configuration file, after the
<Directory> sections and <CODE>.htaccess</CODE> files are
-read, but before <Location> sections.</P>
+read, but before <Location> sections. Note that
+<Files> can be nested inside <Directory>
+sections to restrict the portion of the filesystem they
+apply to.</P>
<P>The <EM>filename</EM> argument should include a filename, or a
wild-card string, where `?' matches any single character, and `*' matches any
HREF="#location"><CODE><Location></CODE></A> sections,
<CODE><Files></CODE> 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
-<EM>filename</EM> does not begin with a <CODE>/</CODE> character,
-the directory being applied will be prefixed automatically.
+file-by-file level.
<P>