Note

The Location directive - provides for access control by URL. It is similar to the + limits the scope of the enclosed directives by URL. It is similar to the Directory directive, and starts a subsection which is terminated with a </Location> directive.

The LocationMatch directive - provides for access control by URL, in an identical manner to - Location. However, + limits the scope of the enclosed directives by URL, in an identical manner + to Location. However, it takes a regular expression as an argument instead of a simple string. For example:

While processing a request the server looks for the first existing configuration file from this list of names in every directory of the path to the document, if distributed - configuration files are enabled for that directory. For - example:

If you want the content to be processed by more than one filter, they - have to be separated by semicolons. It's also possible to use one +

If you want the content to be processed by more than one filter, their + names have to be separated by semicolons. It's also possible to use one AddOutputFilterByType directive for each of - them.

The configuration below causes all script output labeled as text/html to be processed at first by the @@ -274,7 +274,10 @@

Note

Enabling filters with AddOutputFilterByType may fail partially or completely in some cases. For expample, no - filters are applied if the content type falls back to the DefaultType, even if the DefaultType is the same.

+ filters are applied if the MIME-type could not be determined and falls + back to the DefaultType setting, + even if the DefaultType is the + same.

However, if you want to make sure, that the filters will be applied, assign the content type to a resource explicitely, for @@ -307,7 +310,7 @@

When the server finds an .htaccess file (as specified by AccessFileName) it needs to know which directives declared in that file can override - earlier access information.

+ earlier configuration directives.

Only available in <Directory> sections

AllowOverride is valid only in @@ -527,10 +530,10 @@ DefaultType image/gif

would be appropriate for a directory which contained many gif +

would be appropriate for a directory which contained many GIF images with filenames missing the .gif extension.

Note that unlike ForceType, this directive is only +

Note that unlike ForceType, this directive only provides the default mime-type. All other mime-type definitions, including filename extensions, that might identify the media type will override this default.

@@ -590,7 +593,7 @@ three numbers.

If multiple (non-regular expression) <Directory> sections - match the directory (or its parents) containing a document, + match the directory (or one of its parents) containing a document, then the directives are applied in the order of shortest match first, interspersed with the directives from the .htaccess files. For example, with

@@ -617,10 +620,11 @@ (disabling .htaccess files).

Apply directive AllowOverride FileInfo (for - directory /home/web).

+ directory /home).

Apply any FileInfo directives in - /home/web/.htaccess

+ /home/.htaccess, /home/web/.htaccess and + /home/web/dir/.htaccess in that order.

Regular expressions are not considered until after all of the @@ -637,9 +641,11 @@

the regular expression section won't be considered until after - all normal <Directory>s and .htaccess - files have been applied. Then the regular expression will match on - /home/abc/public_html/abc and be applied.

Note that the default Apache access for <Directory /> is Allow from All. @@ -1036,12 +1042,12 @@ Module:core

The <Files> directive - provides for access control by filename. It is comparable to the - <Directory> - directive and <Location> directives. It 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 + limits the scope of the enclosed directives by filename. It is comparable + to the <Directory> + and <Location> + directives. It 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 @@ -1087,7 +1093,8 @@ Module:core

The <FilesMatch> directive - provides for access control by filename, just as the <Files> directive + limits the scope of the enclosed directives by filename, just as the + <Files> directive does. However, it accepts a regular expression. For example: